Updating report + questions

[dd_wizard]

Did you add init=/sbin/upstart to /boot/grub/grub.conf? I never actually tried adding it during boot. I successfully booted under systemd, then added it to the grub configuration file. Oh, from the devel mail list, there's this:
And here's another addition: you might also want to run this command
when upgrading from older rwahide to current F-14/rawhide:

# systemctl enable graphical.target

This makes sure the default.target link is created properly

Lennart

--
Lennart Poettering - Red Hat, Inc.

If the livecd has systemd on it, that may work.

dd_wizard

---------- Post added at 06:18 PM CDT ---------- Previous post was at 06:14 PM CDT ----------

Depending how good you are at symlinks, this may help:
[gene@Mobile-PC ~]$ sudo systemctl enable graphical.target
Cannot link /lib/systemd/system/graphical.target to /etc/systemd/system/default.target, symlink exists already and points to /etc/systemd/system/runlevel5.target.

That's what happens when I run the above command on a system that's got the symlink in place already.

dd_wizard

---------- Post added at 06:26 PM CDT ---------- Previous post was at 06:18 PM CDT ----------

Oh, and if you haven't erased systemd-units with rpm and reinstalled it as described in Post 3 of Bug 618315 (https://bugzilla.redhat.com/show_bug.cgi?id=618315), you'll want to do this from the dev mail list:
Heya,

just a little heads up for when you upgrade a rawhide system that is a
few weeks old to current rawhide: since we changed the way how some of
the default symlinks of systemd are created you will end up with an
installation that lacks many of the necessary symlinks -- but only if
you upgrade from a systemd version from older rawhide to current
rawhide. It's really only a problem in this case. It is not a problem
with fresh F14 installations, and it is not a problem with upgrades from
F13. The fix is easy: after upgrading just run this command as root and
the missing links should be created:

# systemctl enable getty at .service prefdm.service getty.target rc-local.service remote-fs.target

And that should make things work again.

Sorry for the late heads-up.

Lennart

--
Lennart Poettering - Red Hat, Inc.


I hope the cut and paste got the spaces correctly. I'm not that familiar with the systemctl syntax.

dd_wizard

[GoinEasy9]

@dd_wizard
I was about to post almost the same thing you did, BUT, update in tonights rawhide killed gnome-panel even though gnome-panel wasn't updated. So I didn't get a chance to try Lennart's fix either. I tried to undo history, but since fedora-release was updated, the update crossed repo lines (14->15), and I can't undo yum history. I tried editing /etc/fedora-release, but to no avail. All I have now is jumping icons on the desktop with no panels. Ctrl-Alt-F2 works at login, so I can play without "X".
Since there isn't an installable F14 at present, I'm going to let it sit until the python rebuild is done, or a new TC comes out that lets me reinstall. I think I need to install with a working systemd, way to many work arounds on this box already.

[dd_wizard]

If you're interested, I can tell you how to totally disable gnome-panel and run with awn. Or you could just run awn and ignore gnome-panel, unless awn is broken for you, too.

WARNING: I updated to the new systemd from koji. The same version is available for F14 and real rawhide, F15. It booted reasonably well, but shutting down required killing power. :( It refused to shut down my lvm system, so I had to do the old Edison disconnect trick. Luckily, it seems to have rebooted under upstart successfully.

dd_wizard

[kurtdriver]

Thanks guys, I did update it for the first time in a couple of weeks, but without being able to boot it I don't know how to run systemctl. If I chrooted from the livecd perhps? I'm reading up on chroot and LVMs now, cause it's been a few years.:)

[tox]

TC2 is out dude http://serverbeach1.fedoraproject.org/pub/alt/stage/14.TC2/Fedora/

Remember, new for Fedora 14, we need to have the desktop validation
tests for KDE, Xfce and LXDE completed, as well as the desktop spin. If
you would like to use a live image for testing, please use the nightly
live images dated 2010-08-03 available here:


http://alt.fedoraproject.org/pub/alt/nightly-composes/

[dd_wizard]

If you boot from a livecd, you should be able to mount your hard drive's /boot partition. Then just add the init=sbin/upstart to the end of your good kernel line in /boot/grub/grub.conf. That's working for me.

dd_wizard

[GoinEasy9]

I appreciate it, but, I think I'll try to install F14, I really think it's time for a fresh install. Although Anaconda is broken, a link to a new install.img file was posted on #fedora-qa. That, and the new fedora-release on koji might give me a working F14 install, besides, I never used .img updates, and, there's no better time than the present to learn how. :)
Wait, just saw fedora-release-14 on koji still points to F15, ah, that'll work out fine, since I want rawhide. Hah, this should be interesting.

[dd_wizard]

You beat me dexta! :) Does TC2 boot with systemd? If it does, I'm really curious how the shutdown goes.

dd_wizard

[GoinEasy9]

Supposedly, a fresh install will boot systemd correctly, but TC2 has the problems I stated in my last post. That's why I need the new install.img file.

[tox]

You beat me dexta! :) Does TC2 boot with systemd? If it does, I'm really curious how the shutdown goes.

dd_wizard

no idea but here's the announcement by Adam http://lists.fedoraproject.org/pipermail/devel/2010-August/140275.html

[GoinEasy9]

I'm going to download the netinstall and put the new .img file on a usb, that'll hopefully get me a fresh rawhide since the fedora-release-14 on koji is pointing it's repos to F15.

[tox]

Current status

Targeted release: Fedora 14
Last updated: 2010-08-03
Percentage of completion: 96% (16 packages still to rebuild) Python2.7 https://fedoraproject.org/wiki/Features/Python_2.7

[kurtdriver]

If you boot from a livecd, you should be able to mount your hard drive's /boot partition. Then just add the init=sbin/upstart to the end of your good kernel line in /boot/grub/grub.conf. That's working for me.

dd_wizard

That did it. Thank you.

[dd_wizard]

You're welcome, kurt.

@GoinEasy9: I installed fedora-release-14-0.7 a couple of days ago, and it points at the fedora and updates-testing repos. The issue was that a few fc15 packages made it to the fedora repo, but that's been resolved.

Last night, I got the python-2.7 and boost update to install with no errors. Things seem back to normal finally.

dd_wizard

[GoinEasy9]

It still didn't work in rawhide, last I looked there were 6 packages still to be rebuilt. The boost update came in but python is still not finished. I still haven't reinstalled with F14, procrastinating, maybe a new TC will appear. Whichever one comes first, the rawhide python update, or the new TC. I guess they were able to fix F14 first.

[GoinEasy9]

Well, I finished downloading todays nightly build for F14, and decided to look once more at my rawhide install, and, lo and behold, yum update worked (with a side of --skip-broken), but, it got all the python stuff. So I'm trying to gather all the systemd fixes and see if I can get a working desktop with systemd before try a fresh install of F14. After the update, chrome wouldn't launch, and it looks like the systemd upgrade didn't help put the missing pieces in, so, I'll play with it a while.

---------- Post added at 07:48 PM CDT ---------- Previous post was at 07:21 PM CDT ----------

Even with all the fixes, and even with a last attempt of "rpm -e --nodeps systemd systemd-units" and then "yum install systemd-units systemd" still does not make a working rawhide. Time to start from scratch.

[kyryder]

I am in about the same boat with my rolling rawhide. I was able to boot into runlevel 1 with systemd and get it run updates but I still can't get it to boot with systmd to runlevel 3 or >. :( still using upstart

Let us know if a fresh install works. :)
good luck ;)

Ky

[GoinEasy9]

I see there is already a systemd 6.2, but it's not in F14 yet, and, it might be worth trying in Rawhide. The fact that my next day off is Tues, I might just let everything settle. I'm probably not going to get rawhide revived, but I would like to get a clean F14 with functioning systemd. I don't want to start off an install with fixes.

[kyryder]

Thanks GE9,
I tried systemd-6.1 with no joy but haven't tried 6.2 yet. The only dependency issue I have is with bluetooth everything else has updated fine from runlevel 1. Hope to try 6.2 later today.

If 6.2 doesn't work I'm thinking about creating a partition for a fresh install if I can find the time over the weekend. Fingers crossed for 6.2. :)

Thanks

Ky

[GoinEasy9]

OK, I got versions mixed up...systemd 6.1 is the one mentioned in the post, so if it's not working for you, that probably means it won't work for me. I really didn't think I was going to revive it anyhow. Now I'm just watching to make sure there is a F14 iso with a working systemd, then, we start over.

[kyryder]

Sounds like a good plan and consider me signed up.:) Hope to see F14 with a working systemd soon. Kinda itching to play with systemd ;)

Ky

[andrewthomas]

everything on my system is now fully updated and working.
I had been getting a persistent crash of gnome-panel, but I updated in a chroot and was able to update without --skip-broken for the first time in at least a month. Upon reboot I was hit with a bug

https://bugzilla.redhat.com/show_bug.cgi?id=622143

but was able to get around it with (again in a chroot)

touch /.autorelabel
then a reboot.
I even have a new volume icon that had been missing for quite awhile.

EDIT: shutdown still does not work using systemd. Has anyone filed a bug? If so could you post the #?

[GoinEasy9]

Sytemd in rawhide only goes as high as 5-2. F14 updates-testing has 6-2, and, koji has 7-1, so I'm surprised that anything has changed in rawhide. I haven't seen any difference.
The sound icon came in for me, thanks to a hint from dd_wizard in a previous post, the app under the icon is still broken.
The lockup in shutdown is due to some monitoring function not being turned off properly (last I looked). I would hazard a guess and say that might have been fixed in recent versions of systemd.
Since systemd-6-2 is in F14 updates testing, I'm hoping the next nightly build might be useful for a reinstall. Guess we'll wait and see.

[GoinEasy9]

Wiped my rawhide and installed F14 RC3 last night, hey, systemd actually works. I'm going to stay @F14 until they start updating rawhide again. Last I looked, the latest package for systemd in rawhide is 5-2, while F14 has 7-1, and it's working. No need to update to rawhide now.

[andrewthomas]

systemd-7-1.fc15

http://koji.fedoraproject.org/koji/buildinfo?buildID=189463

[kurtdriver]

I've put rawhide back onto my laptop, now updating 861 packages, a glutton for punishment I guess.

[R3353]

I've put rawhide back onto my laptop, now updating 861 packages, a glutton for punishment I guess.

This is what I did after a 3 1/2 week hiatus that ended last week. Grab the aforementioned 7.1 systemd packages from koji. I also had some random stuff to take care of - new version of yelp that's not in the repos yet, removed kudzu b/c of dependencies, a couple f12 python packages that I don't remember but can post details on if you want. Still using init=/sbin/upstart though.

Most things work in ordinary gnome setup, but I haven't really played.

I'd be interested to hear what your yum repolist has to say. Mine has been dynamic. I keep having to turn off f15 entries, which sounds counterintuitive considering I want f15 packages, but only via rawhide.

[andrewthomas]

I booted up a box that hadn't been updated in a month or so and had to
yum distro-sync in order to sort all the perl packages followed by an update and everything has been fixed as far as I can see.

[kurtdriver]

Today's update on my laptop is sure buggy. No gnome-terminal, the background is a plain blue and the only network adapter ifconfig displays is the loopback device. I'm afraid to reboot the desktop, now. Is it just me?

[andrewthomas]

rpm -qa|grep gnome-terminal
gnome-terminal-2.31.90-1.fc15.x86_64
seems ok to me. Only problem I have is with
desktop-effects http://forums.fedoraforum.org/showthread.php?t=250463
OpenGL renderer string: Software Rasterizer

[kurtdriver]

I have gnome-terminal, but it won't run. Sorry about the confusion. I guess I'll be chrooting again tomorrow eve for a yum update.

[R3353]

Those updating to F15 packages might hold off on the new nautilus packages.

I lost my desktop icons and the ability to navigate my hard drive in nautilus windows when nautilus-devel-2.90.1-1.fc15 update hit today.

Downgrading packages back to nautilus-2.31.90-1.fc14 cleared this up.

BTW - still booting with /sbin/upstart and running firefox in safe mode.

[andrewthomas]

nautilus-devel-2.90.1-1.fc15 update hit today.

Downgrading packages back to nautilus-2.31.90-1.fc14 cleared this up.

I see that 2.90 is the package name, but it seems to me it really should be nautilus-2.31.91-1.fc15
http://live.gnome.org/TwoPointThirtyone#Schedule

* Tue Aug 24 2010 Matthias Clasen <mclasen@redhat.com> - 2.90.1-1
- Update to 2.31.91

[R3353]

nice catch. That is odd. I just verified in my yum.log: Aug 26 11:27:41 Updated: nautilus-devel-2.90.1-1.fc15.i686.

[kurtdriver]

Thanks for the warning, I'll hold off for a couple of days.

[andrewthomas]

Here is the nautilus-2.90.1-1.fc15 bug report.

https://bugzilla.redhat.com/show_bug.cgi?id=628273

[kurtdriver]

This was in the update from this morning. What is this connection it's trying to make? There sure isn't a /org on this machine.


Updating : systemd-9-3.fc15.x86_64 52/174
Non-fatal POSTIN scriptlet failure in rpm package systemd-9-3.fc15.x86_64
Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused



---------- Post added at 11:05 AM CDT ---------- Previous post was at 10:59 AM CDT ----------

So I gather that systemd is trying to log something and selinux has prevented it from doing so.

[dd_wizard]

Actually, the problem was in the post update script, not with systemd. That may give you some issues with systemd now.

dd_wizard

[kurtdriver]

non fatal postin, you'd think I'd read the error message. thanks, dd_wizard.

[R3353]

systemd is working well for me. It knocks ~6 seconds off my boot time, which was already under 45 seconds with init=/sbin/upstart.