What really makes me want to scream

[glennzo]

is a system update that seems to totally hose what was once a working, usable installation of Fedora $releasever Alpha. Does it really need to be so broken that it won't even finish booting?

[Wayne]

What, you mean actually work and take all the fun out of screaming?

[Dangermouse]

Morning Glen

Yeh i know how ya feel often thought yum-plugin-security should be the default...

[glennzo]

What, you mean actually work and take all the fun out of screaming?

Hi Wayne. Don't care so much about the screaming part. I'd just like to be able to get to the desktop. I really don't want to have to boot into runlevel 1, figure out how to get an Internet connection and undo the last yum update, all the while hoping that "this will fix it".

[glennzo]

Morning Glen

Yeh i know how ya feel often thought yum-plugin-security should be the default...

Hello Dave. yum-plugin-security ??

And, FWIW, using GRUB2 to boot a multi-OS system is a bad idea. So much extra work re: kernel updates. How does this relate to my current issue? After the incomplete boot I wanted to fall back to the earlier kernel. Much to do to accomplish that.


And here's the last thing I see while booting the newest Fedora 15 Alpha.

sedispatch[819] Connection Error: (Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied): AVC will be dropped

Maybe this relates to another of today's threads.

[tox]

Hello Dave. yum-plugin-security ??

And, FWIW, using GRUB2 to boot a multi-OS system is a bad idea. So much extra work re: kernel updates. How does this relate to my current issue? After the incomplete boot I wanted to fall back to the earlier kernel. Much to do to accomplish that.

i believe that plugin only downloads security updates, nothing else

[Dangermouse]

Hello Dave. yum-plugin-security ??

Will only do updates that concern security, which is very very few, good way to keep a comp running securely, without risking updates breaking your comp. (usually)


To install

su -c 'yum install yum-plugin-security'

To use

su -c 'yum update --security'

its also possible to use it to do just bug updates etc..

http://linux.die.net/man/8/yum-security

http://forums.fedoraforum.org/showthread.php?t=260881

[RahulSundaram]

Hello Dave. yum-plugin-security ??

And, FWIW, using GRUB2 to boot a multi-OS system is a bad idea. So much extra work re: kernel updates. How does this relate to my current issue? After the incomplete boot I wanted to fall back to the earlier kernel. Much to do to accomplish that.


And here's the last thing I see while booting the newest Fedora 15 Alpha.



Maybe this relates to another of today's threads.

Yes. Booting with selinux=0 will workaround that.

[glennzo]

Yes. Booting with selinux=0 will workaround that.

And it did Rahul. I'm posting from F15 now.

[leigh123linux]

I just wasted a hour with the beta in VM , the experience sucked so much I deleted it .
I doubt that I will bother testing it again till the final release, even then I'm doubt I will bother giving it real hardware to soil (this is the worst fedora release ever IMO ).

[smr54]

@Leigh, why? (Everyone has different needs for an O/S. My relatively simple workstation needs seem to be met, though I didn't update today, so might be missing some new issue.)

So, what was so bad for you about it?

[leigh123linux]

@Leigh, why? (Everyone has different needs for an O/S. My relatively simple workstation needs seem to be met, though I didn't update today, so might be missing some new issue.)

So, what was so bad for you about it?

I have never seen so many issue on a fedora release

1. Well first it refused to boot with 512mb of ram, it finally booted when I upped it to 1Gb.
2. not fedora issue, vmware only allocated a 50Mb /boot partition which I increased to 300Mb after install .
3. Third issue was no X it crashed on firstboot.
4. Forth issue was screen resolution it refused to go above 1024x768, the vmware driver refused to work leaving me with the crappy vesa driver.
5. It defaulted to the fallback mode (I had no issue with that), when I went to configure it I found most of the usual settings missing from gconf so I installed dconf, this was at total waste of time as it segmented on start.
6. while trying to report several package crashes using ABRT the system just froze (I didn't even get the chance to report the issues found).

[Dan]

Hmmm.

Not in VMware here, but most of that sounds strangely familiar. <....>


Especially the flakey ABRT. Can you get the wireless to hook up to a hidden network?

[SGSeries2]

I just wasted a hour with the beta in VM , the experience sucked so much I deleted it .
I doubt that I will bother testing it again till the final release, even then I'm doubt I will bother giving it real hardware to soil (this is the worst fedora release ever IMO ).

Tell me about it. I tried out the alpha mainly to take a look at systemd, btrfs, and gnome3. I haven't tried the beta, but when I was trying out the alpha on some old hardware I was going to use as server, I lol'd at the fact that I couldn't log in unless I logged in on one of the tty's first. Then, I lol'd again when I actually did end up logging in to find there was nothing there. Then, I lol'd once more by the fact that if I install KDE (and in turn, kdm), there didn't seem to be a straight-forward way of switching from gdm to kdm. (I worked that out by editing /etc/default/display, or some such, but that had its own problems).

For the record, I primarily use KDE, and was pleased to see that the KDE live cd was doing much better (probably because KDE is in a much more stable state now and was being handled by a different team). Maybe fedora should make the switch.

Anyways, after that fiasco, I just installed f14 with, for better or worse, btrfs in hopes that it'll be fine until f15 comes around in a more-or-less stable state when I upgrade later, or btrfs's fsck capabilities are back-ported. We'll see how that goes. Although I hope otherwise, I may be looking at some heartache later.

[smr54]

The alpha was REALLY bad. As mentioned, I'm having good luck with the beta--once again, I think the fact that I don't really use Gnome is part of it.

Gnome 3 not working in VM is a known issue, though somewhere, in one of these threads, someone mentioned that it was working in a VirtualBox beta.

It's actually a relief to read Leigh's explanation--most of these seem either Gnome or VM related, so shouldn't affect me. Argh--just realized that I have an NVidia on the main workstation where I'll be installing it--of course, Leigh's guide always works like a charm for me.


Selfishly yours,