https://bugzilla.novell.com/show_bug.cgi?id=623286
https://bugzilla.novell.com/show_bug.cgi?id=623286#c30
--- Comment #30 from Nick Couchman
I see that a kernel update fore 11.3 has been started but it has not yet made it to QA.
these issues need to be responded to quickly, and four weeks for a problem of this magnitude is anything but quick.
But it was responded to quickly. The kernel issue was fixed as soon as it was identified - and the fix made available to users. Granted, it wasn't through official update channel, but that's the type of support you get with the enterprise products.
Yes, but it took me two days of banging my head against a wall (that my company paid for, no less) before I decided that maybe I wasn't actually doing something wrong and it may be a bug. Then I posted to the Xen mailing list and someone was kind enough to respond and point me in the direction of this bug. Had the fix that was already out there actually made it to the official update channel, I wouldn't have encountered it at all. I'm not trying to be difficult - I do understand that these things take time, this one just seemed to take a lot longer than usual. That's why it's frustrating and surprising, because it doesn't usually take this long, so, when I run into issues, I'm not in the habit of assuming it's a bug - I usually blame myself! :-)
Issues like this will reflect on the entire "SUSE" product line, and that includes the Enterprise products.
While I understand your frustration, it's unfortunate that the support offered for a free product reflects on the support of a paid product.
Well, unfortunately, that's reality. It isn't so much for folks like me - I do understand that there are differences, that Novell is going to concentrate more effort on the product that brings in revenue, etc. But, if you're trying to build a strong customer and user base for either free or paid products (it's the gateway, right - start with the free, move to the enterprise), it's going to be hard to do when folks stumble across issues like this and don't see fixes appear very quickly. I'll bet that there were some number of folks out there - maybe not a ton of them, but certainly a few - that were trying openSuSE for the first time. They downloaded and installed openSuSE 11.3, started playing with it, and then ran into one of the issues caused by this bug. Perhaps they played with it for a couple of weeks, tried updating, etc., then dropped it and went and found another distribution that worked, or went back to one they had been using. That's not just losing a user of the free product, that's losing a potential customer of the enterprise product. Like it or not, that's how it works. I'm still a SuSE user (both free and paid versions) and have no intention on switching. I think it's a great distribution, and I appreciate all the hard work that goes into it! I'm just trying to point out the negative impact something like this can have on the product perception, and how frustrating it is for those of us who are not accustomed to these sorts of delays :-). Anyway, I think I've hijacked this bug thread enough. Getting back to the bug - it's still listed under the GNOME component - is this really correct, or perhaps it should say kernel, instead?? -Nick -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.