On Sat, 2010-09-11 at 22:24 -0400, Jonathan Kamens wrote: > (I've been unsubscribed for a month or so because of other business > consuming all my time, so forgive me if I'm beating a dead horse.) > > I just upgraded to F14. I'm really not impressed at its current > quality level and I find it hard to believe it's going to be ready for > a good beta at the end of September. The problems I've encountered so > far (at least, the ones I managed to narrow down enough to be able to > find / report in bugzilla): Sorry to hear you're having trouble. Let's take a look through the bugs. I can't reply in line as Evo is being too 'clever' about your table, sorry, so I'll do it underneath... > ID▼ > Summary > 632939 > dbus-daemon logs a complaint every > time I run "/sbin/service motion > status" as non-root user with > sudoers set up to permit it > 632935 > (thunderbird-bin:9679): > Bonobo-WARNING **: Bonobo must be > initialized before use > 632934 > Gtk-Message: Failed to load module > "atk-bridge": libatk-bridge.so: > cannot open shared object file: No > such file or directory > 632932 > Weird gtk2 behavior with > thunderbird panel with hidden > progress bar > 632929 > network doesn't come up on boot > 632236 > confused old_Hertz_hack - Unknown > HZ value! (93) Assume 1024 > 630253 > gnome-keyring always ask for > password and takes 100% CPU > (couldn't allocate secure memory) > 627662 > [MINOR] log messages missing > trailing '"' in 'comm=' fields > 623550 > /etc/cron.hourly/mcelog.cron: read: > No such device > 610301 > Fontmap.local file created by > package is never used > > And this is after only a few hours of using F14. 632939 - as Lennart says, seems a bit confused; if you could follow up with more information it'd help. 632935 - doesn't seem terribly important, it looks like just a warning; does it appear to cause any problems? I don't think Bonobo does an awful lot any more. I wouldn't worry much about this one, but I expect Matthias will take a look at it. 632934 - are you sure this is new? I vaguely recall seeing this message all the time. atk is accessibility stuff, so you don't need it if you don't need accessibility assistance. I'm not sure if we intend it to be installed by default or not. This kind of message isn't *always* a bug to be fixed; sometimes apps are set up to just always call something and then use it if it turns out to be there but not use it if it isn't, and in that case it's not always a problem that there's an error like this. Matthias is the right assignee, he should know if this is a problem or not. 632932 - no points for h264 format video ;) interesting bug indeed. One possibility here is that it's actually a nouveau bug, especially given your later comment about nouveau. Given that, I've CC'ed Ben onto the bug. 632929 - as you can see, this is a bug a few others have hit already, it seems like we're making good progress on diagnosing / fixing it. 632236 - this is some kind of kernel timer issue. It may help to attach dmesg output to this bug. I suspect it's the kernel rather than procps at fault, so I've reassigned it (we can always assign it back if I'm wrong). It would be useful to know if it happens if you boot with 'nohz=off' or 'clocksource=acpi_pm' . 630253 - matthias has bumped this one upstream and upstream is asking for details: https://bugzilla.gnome.org/show_bug.cgi?id=628984 . Note this isn't universal - it doesn't happen on any of my systems, so there's some specific trigger here, so it will definitely help upstream if you can provide the info they asked for. 627662 - no idea about this one, but the devs appear to be on it. Doesn't look too important, right? 623550 - no idea again, but developer has taken it. Again seems not too important? 610301 - a lot of people seem to be hitting this, yeah. devs appear to be on it. It seems like only a few of the bugs are really significant - the network and gnome-keyring issues - and the devs are working on those. The rest read as pretty minor to me; do let us know if any of them are more significant than they immediately appear. > Also, the nouveau driver still seems pretty fragile, e.g., immediately > after a reboot I was getting all sorts of artifacts on my display and > I had to reboot again to get rid of them, but this is nothing new with > F14 so I didn't bother to file a defect about it. Even if this isn't new you should file a bug as it's the best way to make the developers aware of the issue. If you've already filed a bug before, update it to say it still exists in F14. > Are people other than me encountering a lot of issues with F14? Feel > free to ignore this question if the list has already gone through this > in my absence. ;-) It varies, as it always does. For me personally, it's reasonably good; I have a couple of issues with nouveau and suspend but aside from that I'm okay. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
