If its an app that is important and you use a lot (and can not wait for a fix) then I recommend you go back.
Until very recently, I always waited until 2 months after a new release before I installed it. Recently I’ve been testing the alpha, beta and RC versions (on an old test pc) prior to the release, so I know in advance which of my favourite applications will and will not work . Based on that I make my update decisions.
If you can wait a couple months, then it is likely there will be a fix for your app. Contact the packager of your non-functional apps, and send them an email, advising them it does not work. I find the packagers are very helpful.
oldcpu wrote:
> Robert Carlson;1917581 Wrote:
>> Don’t know that it will be worth the bother after I installed Gramps 3.0
>> genealogy app and can’t even get it to run. Other users of openSUSE
>> 11.1 have reported the same problem. I could try to drop back to
>> version 2.2 of the app, but YaST won’t uninstall the 3.0 version. I
>> have been a happy with openSUSE since I first installed it about 2
>> years
>> ago, and I would be reluctant to change, but I may have no choice.
>
> If its an app that is important and you use a lot (and can not wait for
> a fix) then I recommend you go back.
>
> Until very recently, I always waited until 2 months after a new release
> before I installed it. Recently I’ve been testing the alpha, beta and
> RC versions (on an old test pc) prior to the release, so I know in
> advance which of my favourite applications will and will not work .
> Based on that I make my update decisions.
Well, that method of testing wouldn’t tell you that sound that worked in
10.2 on the Intel ICH8 audio device hardware wouldn’t in 11.1. I would
have stuck with 10.2 longer, but it was no longer supported. So instead
of moving to 10.3 for a few months, the logical thing was to move to 11.1.
> If you can wait a couple months, then it is likely there will be a fix
> for your app. Contact the packager of your non-functional apps, and
> send them an email, advising them it does not work. I find the
> packagers are very helpful.
I have just downloaded the 32-bit version of 11.1 and do a fresh
install. I like KDE 4.1 well enough and am willing to put up with the
bugs that it has provided it can run version 2.2 of the Gramps
application. If it can’t, I will be switching to Gnome, but I don’t
think I’ll be trying that in 11.1; instead I’d probably switch to Ubuntu.
Its hard for me to make an assessment without the entire perspective as to what you have installed, and what you do not. Also, as to what your priorities are.
If it were me, and if sound was not a top priority, but gramps program was, I would have stayed in 10.2.
10.2 is still supported by packman and a few months without Novell support is not going to hurt, at least until one determines if there will be gramps support for 11.1. And while waiting I would have emailed the gramps packager for the previous openSUSE versions, and investigated the probability with them that there would be a functional gramps for 11.1.
I still recommend you email the packager.
I confess I see your logic, but I have a different view. In the openSource world, if I see an app that I like that is not functional, I wait for it to be available, and in the mean time, in parallel while waiting, I politely ask a packager to help me out. I don’t jump distributions.
I find jumping distributions far more disruptive than sorting out some minor hiccups with the help of this forum, with the help of experts on the IRC chat channels, and with the help of the packagers, and with the help of the devs (via bug reports). Plus IMHO in the process I am able to contribute more to a distribution.
My expertise in sound did not come from jumping from distribution to distribution. I stayed with openSUSE since 7.3, although on numerous occasions I did install other Linux versions on an old test PC, playing with some for some time. My view is if I had jumped from distribution to distribution at each hiccup I would have learned about more different apps, but my in depth sound knowledge would never have happened, as I would have been too busy jumping to a new distribution.
But thats just me.
One of the beauties of Linux is that it is all about choice.
oldcpu wrote:
> Robert Carlson;1918021 Wrote:
>> oldcpu wrote:
>>> If its an app that is important and you use a lot (and can not wait
>> for
>>> a fix) then I recommend you go back.
>>>
>>> Until very recently, I always waited until 2 months after a new
>> release
>>> before I installed it. Recently I’ve been testing the alpha, beta
>> and
>>> RC versions (on an old test pc) prior to the release, so I know in
>>> advance which of my favourite applications will and will not work .
>>> Based on that I make my update decisions.
>> Well, that method of testing wouldn’t tell you that sound that worked
>> in
>> 10.2 on the Intel ICH8 audio device hardware wouldn’t in 11.1. I
>> would
>> have stuck with 10.2 longer, but it was no longer supported. So
>> instead
>> of moving to 10.3 for a few months, the logical thing was to move to
>> 11.1. Its hard for me to make an assessment without the entire perspective as
> to what you have installed, and what you do not. Also, as to what your
> priorities are.
>
> If it were me, and if sound was not a top priority, but gramps program
> was, I would have stayed in 10.2.
>
> 10.2 is still supported by packman and a few months without Novell
> support is not going to hurt, at least until one determines if there
> will be gramps support for 11.1. And while waiting I would have emailed
> the gramps packager for the previous openSUSE versions, and investigated
> the probability with them that there would be a functional gramps for
> 11.1.
>
> Robert Carlson;1918021 Wrote:
>> oldcpu wrote:
>>> If you can wait a couple months, then it is likely there will be a
>> fix
>>> for your app. Contact the packager of your non-functional apps, and
>>> send them an email, advising them it does not work. I find the
>>> packagers are very helpful.I still recommend you email the packager.
>
> Robert Carlson;1918021 Wrote:
>> I have just downloaded the 32-bit version of 11.1 and do a fresh
>> install. I like KDE 4.1 well enough and am willing to put up with the
>> bugs that it has provided it can run version 2.2 of the Gramps
>> application.I confess I see your logic, but I have a different view. In the
> openSource world, if I see an app that I like that is not functional, I
> wait for it to be available, and in the mean time, in parallel while
> waiting, I politely ask a packager to help me out. I don’t jump
> distributions.
>
> I find jumping distributions far more disruptive than sorting out some
> minor hiccups with the help of this forum, with the help of experts on
> the IRC chat channels, and with the help of the packagers, and with the
> help of the devs (via bug reports). Plus IMHO in the process I am able
> to contribute more to a distribution.
>
> My expertise in sound did not come from jumping from distribution to
> distribution. I stayed with openSUSE since 7.3, although on numerous
> occasions I did install other Linux versions on an old test PC, playing
> with some for some time. My view is if I had jumped from distribution
> to distribution at each hiccup I would have learned about more different
> apps, but my in depth sound knowledge would never have happened, as I
> would have been too busy jumping to a new distribution.
>
> But thats just me.
>
> One of the beauties of Linux is that it is all about choice.
>
>
Well, had I known, I might have stuck with 10.2 longer, but there was
the annoying problem of printing being broke in Firefox and not working
great in Opera either. And now I find that in 11.1 K3B will not
recognize my Lite-on CD/DVD writer, even though YaST recognizes it as
such. And that has nothing whatever to do with the Intel issue. It is
just unacceptable for that kind of problem to exist in a product that
has been released.
I have a 32-bit version of 11 that I got with the book OpenSUSE 11.0 and
SUSE Linux Enterprise Server, so I guess I will give that a whirl.
You may ask, how could this happen? I tested 11.1 beta5 and the problem was NOT there. I tested 11.1 RC1 and the problem was NOT there. I believe the problem crept in between 11.1 RC1 and 11.1 GM. I suspect it was because the SuSE-GmbH staff were trying too hard to address some bugs in other areas, and thought they had a fix but over looked the side affect. I suspect it may have been the last minute fix to make Hot Plug automount of NTFS formated USB drives (in read/write) or something like that which was fixed at the last minute. This is unfortunate. This is bad luck. But these things happen. But gosh. … this is so trivial to address … I can remember 10.x, 9.x and 8.x releases of SuSE/openSUSE having far greater hiccups. And I’ve seen bigger hiccups on Fedora, Red Hat, and Ubuntu.
But this k3b problem is a simple fix. Every Linux user learns immediately that if one has a problem as a regular user, try the same with higher permissions. Although I guess we all get complacent and times and forget that guiding principle.
I would not be surprised to see an update to some openSUSE files in the near future that will fix that, … presumably a month or two (possibly sooner) after the Christmas break. In the mean time, the work around that I applied for myself works, and the work around in the blog article I quoted work for many.
Starting to close in on this one a bit more.
Under Gnome I get no errors and am making headway.
Under KDE3 I get no errors. Haven’t had time to test further.
Under KDE4 I get the alsa 1200 error and get reset to default.
Haven’t had a lot of time to test but KDE4 seems to have some problems from what I have seen so far. I’ll keep digging and let you know what I can find.
oldcpu wrote:
> Robert Carlson;1918091 Wrote:
>> And now I find that in 11.1 K3B will not
>> recognize my Lite-on CD/DVD writer, even though YaST recognizes it as
>> such. This is a trivial fix in my view.
>
> I also was “bitten” by this. I confess to being stumped for 15
> minutes.
>
> In my case I added my users to group “cdrom” and “disk” and it sorted
> it for me. Others had to do more. Take a look at this blog: ‘Solved :
> K3b Problem with Normal User on openSUSE 11.1 | Spirit of Change’
> (http://tinyurl.com/78jde3)
>
> You may ask, how could this happen? I tested 11.1 beta5 and the
> problem was NOT there. I tested 11.1 RC1 and the problem was NOT there.
> I believe the problem crept in between 11.1 RC1 and 11.1 GM. I suspect
> it was because the SuSE-GmbH staff were trying too hard to address some
> bugs in other areas, and thought they had a fix but over looked the side
> affect. I suspect it may have been the last minute fix to make Hot Plug
> automount of NTFS formated USB drives (in read/write) or something like
> that which was fixed at the last minute. This is unfortunate. This is
> bad luck. But these things happen. But gosh. … this is so trivial to
> address … I can remember 10.x, 9.x and 8.x releases of SuSE/openSUSE
> having far greater hiccups. And I’ve seen bigger hiccups on Fedora, Red
> Hat, and Ubuntu.
>
> But this k3b problem is a simple fix. Every Linux user learns
> immediately that if one has a problem as a regular user, try the same
> with higher permissions. Although I guess we all get complacent and
> times and forget that guiding principle.
There were just too many problems besides this trivial one. I now know
that the Intel sound problem existed since 11.0. Should have been fixed.
> I would not be surprised to see an update to some openSUSE files in the
> near future that will fix that, … presumably a month or two (possibly
> sooner) after the Christmas break. In the mean time, the work around
> that I applied for myself works, and the work around in the blog article
> I quoted work for many.
Perhaps I will consider moving back to 11.1 in 6 months.