On Mon, Jan 21, 2013 at 12:28 AM, Ranjan Maitra <maitra.mbox.ignored@xxxxxxxxx> wrote: > Dear friends, > > I recently upgraded from F17 to F18. I chose not to use fedup but > rather I used fedora-upgrade, which is basically a wraparound around > yum upgrade (from the documentation). Everything went through > reasonably smoothly except for the following messages: > > Font messages such as: > > Updating : gnu-free-mono-fonts-20120503-3.fc18.noarch > 1322/3028 Fontconfig warning: > "/etc/fonts/conf.d/65-0-khmeros-base.conf", line 29: Having multiple > values in <test> isn't supported and may not work as expected > Fontconfig warning: "/etc/fonts/conf.d/65-0-khmeros-base.conf", line > 41: Having multiple values in <test> isn't supported and may not work > as expected Fontconfig warning: > "/etc/fonts/conf.d/65-0-khmeros-base.conf", line 53: Having multiple > values in <test> isn't supported and may not work as expected > Fontconfig warning: "/etc/fonts/conf.d/65-0-nhn-nanum-gothic.conf", > line 8: Having multiple values in <test> isn't supported and may not > work as expected > > and the only selinux-policy-targeted message: > > Updating : selinux-policy-targeted-3.11.1-67.fc18.noarch > 1454/3028 libsepol.print_missing_requirements: matahari's global > requirements were not met: bool init_systemd (No such file or > directory). libsemanage.semanage_link_sandbox: Link packages failed (No > such file or directory). /usr/sbin/semodule: Failed! > ************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************ > > > Other than that, everything went through fine. > > Upon reboot, I did not see the F18 grub splash screen, but the F17 one. > > I did not get the SLiM display manager but text. startx gets me to the > desktop (LXDE). > > Other errors: > > 1. pcmanfm does not automount disks, indeed, I get the following errors > when I start it up: > > (pcmanfm:605): GVFS-RemoteVolumeMonitor-WARNING **: remote volume > monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not > supported > > (pcmanfm:605): Gtk-WARNING **: Theme parsing error: <data>:1:6: > Expected a valid selector > > (pcmanfm:605): Gtk-WARNING **: Theme parsing error: <data>:7:7: > Expected a valid selector error: The metadata does not have a thumbnail > property error: The metadata does not have a thumbnail property > error: The metadata does not have a thumbnail property > error: The metadata does not have a thumbnail property > error: The metadata does not have a thumbnail property > error: The metadata does not have a thumbnail property > error: The metadata does not have a thumbnail property > error: The metadata does not have a thumbnail property > error: Invalid MS property section > calling convert > '/home/maitra/.thumbnails/normal/79594e24b205982ddb040918b50b267d.png.DWF3QW' > +matte -thumbnail 128x128 > png:'/home/maitra/.thumbnails/normal/79594e24b205982ddb040918b50b267d.png' > error: No Zip trailer error: No Zip trailer error: No Zip trailer > error: No Zip trailer error: No Zip trailer > error: No Zip trailer > error: No Zip trailer > error: No Zip trailer > > > 2. batti gives me no response and the following error: > > > ERROR:dbus.proxies:Introspect error on :1.80:/org/freedesktop/UPower: > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: > Message did not receive a reply (timeout by message bus) Neither UPower > nor DeviceKit.Power could be initialized! This can have multiple > reasons. Here is the error for UPower: > > org.freedesktop.DBus.Error.ServiceUnknown: The name :1.80 was not > provided by any .service files > > And this is the error for DeviceKit.Power: > > org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.DeviceKit.Power was not provided by any .service files > > > 3. sudo yum *whatever* always has the following: > > Unable to send message to PackageKit > > I am however able to install and update (and erase packages), most > functions, but does take forever to get started now. > > Any suggestions, fixes? > > Many thanks and best wishes, > Ranjan >From what i can see F18 seems an utter disaster... i put F17 back on. james -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
