On 10/9/20 7:15 PM, DennisG wrote:
On 10/9/20 1:21 PM, Doug McGarrett wrote:
On 10/9/20 12:56 PM, Carlos E. R. wrote:
On 09/10/2020 17.24, DennisG wrote:
On 10/8/20 7:17 PM, Doug McGarrett wrote:
On 10/8/20 4:28 PM, Bengt Gördén wrote:
Thank you, Bengt! I don't know how it got modified to begin with, but I like it better in plain black!
Actually Doug, you probably do know.
Welcome to Tumbleweed, where TBird has been updated 3 times in the last 2 weeks.
With a /rolling/ release, when there is a sudden change in behavior in the system or an app, usually the first place to look is whether there was just an update. While sometimes it is not clear what the culprit was, other times it is obvious - like when the misbehaving app was itself just updated, as in this case.
It is the user's responsibility to do some investigation first before asking others to do so. Especially with a rolling release.
And btw, you also need to know how to find/reinstall a previous version if the new version is not acceptable. You lucked out in this case.
And of course, people like me were baffled by the question, not understanding it - because he did not say this was on Tumbleweed.
That's interesting. I'd like to know how to find/reinstall a previous version--maybe the upgrade to TW is why the scanner no longer works--I blamed it on destructive interference from Aver Media EZRecorder. (I am returning the Aver device anyway. It doesn't work the way I would like a TV recorder to work.) And if the responder would be so kind as to tell me how to find information like this myself I'd be grateful. --doug
I can't find his reply at the moment, but shortly after you posted about the scanner Carlos asked if you had had a recent update. I don't recall you following up on that. In any event, of course the first logical suspect when anything like this happens, is to look into the recent update(s). Tumbleweed is IMHO of extraordinary value as it provides rigorous testing for what will become the next point release. Using a rolling release usually requires additional attention, and certainly the ability to navigate unexpected surprises anywhere in the system.
--dg
I don't remember the recent update question, which is not to say that there wasn't one. Now I am thoroughly aware of the possibility of an update breaking something. I wonder if a future update will fix what broke, or what the user can do to help locate the particular problem. All I know is that the scanner which worked perfectly one day is no longer visible to the system or yast. How do the developers know what broke, and where to look for a fix--should I be reporting the scanner problem to someplace other than this forum? (As it happens, in my ignorance, I ran the update on the Leap machine also, and it doesn't recognize the scanner either! But I had not yet installed it. Only when I went to do so, did I find that yast cannot find it. I suppose one is not supposed to run update on Leap.--I will learn, I hope, before I die! --doug -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org