[opensuse-support] Thunderbird printing previous responses in pale blue
Just very recently, received emails by Thunderbird that are quoting a previous email are printing the quote in a light blue text that is hard to read. Can this be fixed, and if so, how? Thanx. --doug -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 2020-10-08 00:45, Doug McGarrett wrote:
Just very recently, received emails by Thunderbird that are quoting a previous email are printing the quote in a light blue text that is hard to read. Can this be fixed, and if so, how? Thanx.
Hi Doug, It can be changed. Go to: Edit->Preferences->General->Plain text messages regards, -- /bengan -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Bengt Gördén <bengan@bag.org> [10-08-20 16:28]:
On 2020-10-08 00:45, Doug McGarrett wrote:
Just very recently, received emails by Thunderbird that are quoting a previous email are printing the quote in a light blue text that is hard to read. Can this be fixed, and if so, how? Thanx.
Hi Doug,
It can be changed. Go to:
Edit->Preferences->General->Plain text messages
isn't that where changes were made to make them print light blue? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 10/8/20 4:49 PM, Patrick Shanahan wrote:
* Bengt Gördén <bengan@bag.org> [10-08-20 16:28]:
On 2020-10-08 00:45, Doug McGarrett wrote:
Just very recently, received emails by Thunderbird that are quoting a previous email are printing the quote in a light blue text that is hard to read. Can this be fixed, and if so, how? Thanx. Hi Doug,
It can be changed. Go to:
Edit->Preferences->General->Plain text messages isn't that where changes were made to make them print light blue?
Not by me! --doug -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [10-08-20 19:23]:
On 10/8/20 4:49 PM, Patrick Shanahan wrote:
* Bengt Gördén <bengan@bag.org> [10-08-20 16:28]:
On 2020-10-08 00:45, Doug McGarrett wrote:
Just very recently, received emails by Thunderbird that are quoting a previous email are printing the quote in a light blue text that is hard to read. Can this be fixed, and if so, how? Thanx. Hi Doug,
It can be changed. Go to:
Edit->Preferences->General->Plain text messages isn't that where changes were made to make them print light blue?
Not by me! --doug
then you *must* have someone else admin'ing your computer. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 2020-10-09 02:01, Patrick Shanahan wrote:
then you*must* have someone else admin'ing your computer.
In this case, don't think he has. I definitely don't have another admin on my laptop. I did however update TW yesterday and after that I had light blue comments in TB. I actually didn't think much of it until Doug mentioned it. But now it's changed to intense red :D There's a whole lot of changes in the new TB. One that doesn't feel that good is all, and I mean _all_ the add-ons that are incompatible with 78.3.1. But that will probably be fixed in later releases. regards, -- /bengan -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 10/8/20 4:28 PM, Bengt Gördén wrote:
On 2020-10-08 00:45, Doug McGarrett wrote:
Just very recently, received emails by Thunderbird that are quoting a previous email are printing the quote in a light blue text that is hard to read. Can this be fixed, and if so, how? Thanx.
Hi Doug,
It can be changed. Go to:
Edit->Preferences->General->Plain text messages
regards,
Thank you, Bengt! I don't know how it got modified to begin with, but I like it better in plain black! -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 10/8/20 7:17 PM, Doug McGarrett wrote:
On 10/8/20 4:28 PM, Bengt Gördén wrote:
On 2020-10-08 00:45, Doug McGarrett wrote:
Just very recently, received emails by Thunderbird that are quoting a previous email are printing the quote in a light blue text that is hard to read. Can this be fixed, and if so, how? Thanx.
Hi Doug,
It can be changed. Go to:
Edit->Preferences->General->Plain text messages
regards,
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. --dg -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Fri, 9 Oct 2020 18:56:31 +0200 "Carlos E. R." <robin.listas@telefonica.net> 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.
No contest but it don't come easy for people who are not on top of a dozen distros all the time :) BTW since when is TW a rolling-release? And I dn't know how to use zypper to backlevel a packagre either zypper backlevel thunderbird? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op vrijdag 9 oktober 2020 19:16:29 CEST schreef ksusup@trixtar.org:
BTW since when is TW a rolling-release? Ever since it was created.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 09/10/2020 19.16, ksusup@trixtar.org wrote:
On Fri, 9 Oct 2020 18:56:31 +0200 "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:
And of course, people like me were baffled by the question, not understanding it - because he did not say this was on Tumbleweed.
No contest but it don't come easy for people who are not on top of a dozen distros all the time :)
BTW since when is TW a rolling-release?
Since always :-)
And I dn't know how to use zypper to backlevel a packagre either
zypper backlevel thunderbird?
Nope, no such command. The "official" method is to have the system on btrfs and go back an snapshot or two. Then you can have a local copy of older rpms and reinstall an old copy of Thunderbird. Or you can grab such an rpm from boombatower. But! If you are unlucky that Thunderbird updated big the configuration file, you can not go back without a copy of that old config file as well, in all those three cases. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
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
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 09/10/2020 19.21, Doug McGarrett wrote:
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 just posted it in the reply to ksusup -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 10/9/20 1:28 PM, Carlos E. R. wrote:
On 09/10/2020 19.21, Doug McGarrett wrote:
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 just posted it in the reply to ksusup
I saw that. It would seem that this would only affect Thunderbird, if I understand this. I'm looking for a way to get scanner back. --doug -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 09/10/2020 20.07, Doug McGarrett wrote:
On 10/9/20 1:28 PM, Carlos E. R. wrote:
On 09/10/2020 19.21, Doug McGarrett wrote:
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 just posted it in the reply to ksusup
I saw that. It would seem that this would only affect Thunderbird, if I understand this. I'm looking for a way to get scanner back.
It applies to anything. Caveats apply. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
* Doug McGarrett <dmcgarrett@optonline.net> [10-09-20 14:09]:
On 10/9/20 1:28 PM, Carlos E. R. wrote:
On 09/10/2020 19.21, Doug McGarrett wrote:
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 just posted it in the reply to ksusup
I saw that. It would seem that this would only affect Thunderbird, if I understand this. I'm looking for a way to get scanner back.
yes, you better read it again as you definitely did not understand it. Thunderbird was used only as an example as it was already being discussed. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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
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 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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
On 10/10/2020 01.49, Doug McGarrett wrote:
(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!
Yes, of course you can update Leap (and you should). There are several tools for doing it, graphical and text. What you can not do is "zypper dup". And of course, you should not add repositories from a different release. I don't remember if yast should "see" your scanner, or if you have to tell it first where the scanner is. As I remember, you have to click on "add". I will not go into the procedure on Tumbleweed, I will not help you with it. Ask somebody else who is familiar with TW. So make clear in your posts what distribution you are talking about, on each thread. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 10/9/20 7:49 PM, Doug McGarrett wrote:
snip
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
You posted the scanner problem on Oct 4. In less than a day Carlos replied with the question: "Any updates to the machine?" Given your description and that there has not been other noise about printers/scanners disappearing, the most likely conclusions are pilot error or update problem or both. With any OS but especially one that is a rolling release, having a backup/recovery strategy is an absolute requirement. Sometimes it is easy to find the culprit in an update, such as with your TBird issue. Sometimes it can be very difficult to impossible, which was probably true for your scanner and is all the more so now. If your Epson's printer function still works, that points to the scanner software as a suspect. IIRC while the print driver was in the Epson driver package from openSUSE, the scanner software you downloaded from Epson and installed it. I took a look at that installation package. It is not trivial, and possibly of importance, there is a proprietary module included (hence not included in the distribution). Proprietary code is vulnerable to breakage, e.g., from a kernel update. In fact, with this problem, a first step would be to boot a previous kernel to see if that corrected the problem (I keep 3 kernel versions). A second thing to try would be to reinstall the scanner software. Third, roll the system back using your backups (but be careful to preserve any new data that you could lose in the process, like email). Beyond that, you're on a wing and a prayer. And btw, please do not include our personal email addresses in your replies to the list. --dg -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (7)
-
Bengt Gördén -
Carlos E. R. -
DennisG -
Doug McGarrett -
Knurpht-openSUSE -
ksusup＠trixtar.org -
Patrick Shanahan