December 2018 - nmglug - lists.coactcloud.com

DNS servers
by Tom Ashcraft 13 Dec '18

13 Dec '18

Anyone know how to set up CloudFlare DNS on a home computer running Kubuntu 18.04?

3 4

Cloudflare /etc/systemd/resolved.conf versus /etc/netplan/*.yaml; Avahi
by Tom Ashcraft 10 Dec '18

10 Dec '18

Hey Anthony, Jared, and Eric, I really can't thank you enough for all the insights and direct assistance you've recently provided in relation to my difficulties with Thunderbird and Cloudflare. My interest in Cloudflare is two-fold. First, perhaps from NMCSLUG meetings, Anthony may remember that for some time I've had this notion that maybe if I got set up to use Cloudflare I would be to some extent bypassing Comcast's undesirable potential for abusing it's position as a gatekeeper. Second, through his help with troubleshooting the quirky behavior of my instances of Thunderbird and IMAP servers under Kubuntu 18.04 (multiple, thanks to Jared), Anthony posited that symptoms indicate problems with local networking. Hence, he suggested that I should reset DNS servers to Google or Cloudflare and try again, presumably to confirm and narrow things down. Whereupon I remembered old roadblocks and confusion I'd encountered some months back trying to get my computer to talk to Cloudflare servers. (No problem with Win 10 VMs, but no recommendations seemed to apply properly to my particular Linux circumstances.) So after whining to but not hearing back from Anthony, on whom I did not wish to overly presume, I put to NMGLUG my recent query for assistance with Cloudflare. Shortly thereafter Anthony chimed in again and very generously and quickly substantially reproduced, validated and overcame difficulties and concerns I'd had previously. He documented his journey and solution for me in a clear and comprehensive how-two (ultimately modify /etc/systemd/resolved.conf and restart resolved). Also, simultaneously, Eric responded with great information about Netplan, something I'd never even heard of (new to Kubuntu as of 18.04; configure the entry in a yaml file you'll find in /etc/netplan; a link to Netplan examples). >From my readings, Netplan seems to imply a very elegant solution approach that appears to me to have potentially broader applicability, considering both of the interests I mentioned above. I've tried to poke around and grok everything; and, I intend to give it all further study. But obviously I'm thinking it can't hurt to submit this summary for further discussion and suggestions from any interested participants and observers before I start monkeying around again. I'll be working on it all as time and opportunity presents. But at the moment, I'm not yet particularly confident that I possess sufficient comprehension of the issues so that I won't screw up something important. Clearly, backups of involved files are in order, etc. It's all still pretty scary to me. Thank you for patiently holding my hand and not telling me to go RTFMP. Also, I thought I might ask about Avahi. Might it also be involved; should it be taken into consideration? Tom

2 1

The troubled laptop,
by Ted Pomeroy 08 Dec '18

08 Dec '18

NMGLugers, Well this is trivial compared to the e-mail issues. My G570 still has display errors, but now running Debian Stretch (9.6) I see a way forward. I had to re-install Stretch from my own media, but it went quickly at home. Updated and looked for CPU tools and found iucode-tool, intel-microcode and firmware-misc-nonfree. Too bad about the last item, but some of the CPU microcode is non-free. I seem to be a little better, and time will tell. I had one screen disturbance today, but also one "Battery is Full" notice without a screen mishap. (the screen goes all snowy white and pastel for those not at our meeting.) I will continue testing and see if the microcode can fix BIOS errors/omissions as advertised. Thanks for all the help, Ted P.

1 0

Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients
by Tom Ashcraft 08 Dec '18

08 Dec '18

Jared, Looking at how the server SSL certificates turn up when I a) set up the Thunderbird test profile and performed it's initial startup, b) what happened when I started it again, and c) what happened when I next granted the permanent certificate mis-match exception for my original profile, my suspicions continue to comport with negative expectations with regard to Comcast. My current theory (noted again as being rather poorly informed and based on only partial understanding) is that Comcast or General Electric or Xfinity--or who ever decided it was somebody else's job--just didn't bother to provide a current certificate for imap.ge.xfinity.com. I think this because nowhere have I seen or can I find *any* certificate for imap.comcast.net. Only certificates associated with imap.email.comcast.net and imap.ge.xfinity.com seem to appear. And here, I think, might lie the crux of the matter. Could it not be that Comcast simply allowed the certificate for imap.comcast.net to lapse and failed to renew it? Might not such an event--the absence of a certificate--have caused Thunderbird to refuse to connect with imap.comcast.net when it stopped receiving new mail for me on three different computers a few days ago? Note that old iPod app and older Windows versions of Thunderbird, which are probably of less secure design than the then non-receiving current Linux Thunderbird, Kmail, or Sylpheed I have, continued to work properly. Tom On 12/7/18 7:49 PM, Alucard wrote: > Hi Tom, > > No problem. > > Comcast doesn't manage mail well though. They're notoriously bad. > > We have a dedicated smtp server JUST to make sure it plays nice with > Comcast. > > In short, drop them as soon as possible. Pretty much anyone else is > better than them. I know the pain that will cause. But sooner than > later is probably best. > > -- Jared > > On 12/7/18 7:44 PM, Tom Ashcraft wrote: >> Wow. Thanks, Jared. It'll take me a while to grok and test all the >> new info you've provided. Just now have recovered from crashing, >> deleting, and restoring account after most recent experiments. I >> appreciate your help and will keep you appraised as efforts and >> results unfold. OK, back to sawing on the limb I'm sitting on ... >> >> On 12/7/18 7:15 PM, Alucard wrote: >>> Hi Tom, >>> >>> Are you able to reproduce the issue with a new Tbird profile? >>> >>> thunderbird -p >>> >>> Create a test profile, add the account. >>> >>> Use the hostname: >>> imap.ge.xfinity.com for imap 993 SSL/TLS >>> smtp.comcast.net for smtp 465 SSL/TLS >>> >>> Your username is probably the same as the email, without >>> @comcast.net at the end. >>> >>> I used telnet to confirm that those two hostnames are answering on >>> port 143 and 25. >>> >>> If it works after that, I would move over your old profiles' .mab >>> files to the new profile. (all of which is in .thunderbird) >>> >>> Thunderbird makes it super easy to move around in profiles. If you >>> wanted to make Tbird work quickly, I would do the above. If you >>> wanted to try and actually find the issue, I would start with >>> removing any accept invalid certs. >>> >>> Prefrences -> Advanced -> Certificates -> Manage Certificates >>> >>> (Probably back these up first) Find the Comcast cert, and remove it. >>> >>> I'm not 100% which tab it will be in. (Your Certificates, People, >>> Servers, or Authorities) But probably under servers. >>> >>> Let me know how all that goes, please. >>> >>> Thanks! >>> >>> -- Jared >>> >>> On 12/7/18 6:54 PM, Tom Ashcraft wrote: >>>> Thanks for the suggestions, Jared. >>>> >>>> Switching from imap.ge.xfinity.com to mail.comcast.net didn't work >>>> at all (and I think I may have tried that before a couple of days >>>> ago per suggestions found in Comcast support pages) but I suspect >>>> the problem (and the original certificate problem I mentioned >>>> before switching from imap.comcast.net to imap.ge.xfinity.com) has >>>> something to do with the way configuration files get >>>> modified/updated (or not) in Thunderbird. >>>> >>>> It worked the first time (after the warning) going from >>>> imap.comcast.net to imap.ge.xfinity.com but not going from there to >>>> mail.comcast.net. >>>> >>>> I don't really know what to look for in the .thunderbird >>>> directories and I've probably failed to be sufficiently thorough in >>>> my examination of menus. >>>> >>>> At this point I expect I'd best put some time in studying up on SSL >>>> certificates, i.e. when and where they come from and where they go >>>> when they work right. My comprehension of all that is pretty poor. >>>> >>>> On 12/7/18 5:43 PM, Alucard wrote: >>>>> Hi Tom, >>>>> >>>>> Try using this hostname for imap: >>>>> mail.comcast.net >>>>> >>>>> And use this hostname for smtp: >>>>> smtp.comcast.net >>>>> >>>>> That should allow you to get a valid SSL cert. >>>>> >>>>> Let me know how that goes. Also, don't setup your own email. >>>>> Setting up a dovecot server is fun, but maintaining it to work >>>>> with all other email providers is a super big drag. Especially >>>>> when people need to have their email flow without a problem. >>>>> >>>>> -- Jared >>>>> >>>>> On 12/7/18 5:02 PM, Tom Ashcraft wrote: >>>>>> OK, I *think* that having more or less successfully substituted >>>>>> imap.ge.xfinity.com for imap.comcast.net--currently with a >>>>>> certificate mis-match warning I don't yet know how to fix--is >>>>>> probably at least marginally more desirable than having to go >>>>>> through Xfinity mail website... >>>>>> >>>>>> Because, going through the website, Comcast/Xfinity has greater >>>>>> opportunity to do their social engineering infantilization thing, >>>>>> further shape my perceptions, whither my digital self-reliance >>>>>> skillset, more fully exploit me as a consumer milk cow and allow >>>>>> government and corporations to better trace and predict my >>>>>> physical and economic movements should they desire to do so, etc. >>>>>> >>>>>> But am I wrong, should I continue to use the website until I'm >>>>>> completely sure I have the certificate thing properly nailed? >>>>>> >>>>>> On 12/7/18 4:13 PM, Casey Dentinger wrote: >>>>>>> I don't find receiving mail to be that bad but getting it >>>>>>> successfully >>>>>>> delivered is a place where the internet is hamstrung by >>>>>>> corporations. >>>>>>> >>>>>>> On 18-12-07 15:45:26, chochoms(a)earthlink.net wrote: >>>>>>>> >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>>> From: Casey Dentinger <dentinger(a)regnitned.net> >>>>>>>>> Sent: Dec 7, 2018 2:46 PM >>>>>>>>> To: nmglug(a)lists.nmglug.org >>>>>>>>> Subject: Re: [nmglug] Comcast refuses to send mail to Linux >>>>>>>>> desktop email clients >>>>>>>>> >>>>>>>>> That escalated quickly :) >>>>>>>>> >>>>>>>>> Also you don't need imap if you just use mutt locally >>>>>>>>> >>>>>>>>> On Fri, Dec 7, 2018, at 2:43 PM, J Marsden DeLapp wrote: >>>>>>>>>> On Fri, 7 Dec 2018 10:49:39 -0700 >>>>>>>>>> jason schaefer <js(a)jasonschaefer.com> wrote: >>>>>>>>>> >>>>>>>>>>> On 12/1/18 10:47 PM, Tom Ashcraft wrote: >>>>>>>>>>>> What they can't steal from us most of seem to be willing to >>>>>>>>>>>> give to >>>>>>>>>>>> them for free. So much for any hope of anonymity or privacy >>>>>>>>>>>> from our >>>>>>>>>>>> corporate overlords. Might as well let them tatoo a barcode >>>>>>>>>>>> on your >>>>>>>>>>>> forehead--though that wouldn't be nearly as effective. >>>>>>>>>>> Its worth pointing out that if you are concerned about these >>>>>>>>>>> issues >>>>>>>>>>> you shouldn't be using comcast for email... >>>>>>>>>> With a simple >>>>>>>>>> apt install postfix dovecot-imapd >>>>>>>>>> you can run your own mail server. >>>>>>>>>> >>>>>>>>>> Mars >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> ============================================================= >>>>>>>>>> J. Marsden DeLapp, PE >>>>>>>>>> President >>>>>>>> I am following this discussion with great amusement. Maybe you >>>>>>>> guys know something I don't, but having your own email server >>>>>>>> or an email client on your desktop (phones of course are too >>>>>>>> insecure to use for anything important) seems like a lot of >>>>>>>> un-needed work trying to keep things secure. I concluded >>>>>>>> several years ago that I had neither the time nor the >>>>>>>> inclination (plus I am not expert enough in Linux) to harden my >>>>>>>> computer against email-carried malware. Also since someone >>>>>>>> could conceivably get into my computer I don't want them to >>>>>>>> have access to my email. Consequently I use web mail, (not >>>>>>>> GOOGLE!), because the ISP can do a lot better job than I at >>>>>>>> filtering out the malware and protecting against crackers. If I >>>>>>>> need to send something encrypted or very sensitive I use >>>>>>>> Protonmail from CERN. >>>>>>>> >>>>>>>> Problem solved. Doesn't matter what Comcast or anyone else >>>>>>>> allows, plus I can check my mail on any computer in the world. >>>>>>>> >>>>>>>> If I am wrong, please explain to this Linux neophyte why. >>>>>>>> >>>>>>>> >>>>>>>>>> DeLapp & Associates, Inc. dba DeLapp Engineering. >>>>>>>>>> Providing lighting and power planning, design and analysis >>>>>>>>>> services >>>>>>>>>> for commercial, industrial and large residential facilities. >>>>>>>>>> 1190 Harrison Road Ste 3a >>>>>>>>>> Santa Fe NM 87507 >>>>>>>>>> (505) 983-5557 >>>>>>>>>> http://DeLapp.com >>>>>>>>>> ============================================================= >>>>>>>>>> _______________________________________________ >>>>>>>>>> nmglug mailing list >>>>>>>>>> nmglug(a)lists.nmglug.org >>>>>>>>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org >>>>>>>>> _______________________________________________ >>>>>>>>> nmglug mailing list >>>>>>>>> nmglug(a)lists.nmglug.org >>>>>>>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org >>>>>>> _______________________________________________ >>>>>>> nmglug mailing list >>>>>>> nmglug(a)lists.nmglug.org >>>>>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org >>>>>> _______________________________________________ >>>>>> nmglug mailing list >>>>>> nmglug(a)lists.nmglug.org >>>>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org >>>>> >>> >

3 2

Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients
by chochoms＠earthlink.net 07 Dec '18

07 Dec '18

-----Original Message----- >From: Casey Dentinger <dentinger(a)regnitned.net> >Sent: Dec 7, 2018 2:46 PM >To: nmglug(a)lists.nmglug.org >Subject: Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients > >That escalated quickly :) > >Also you don't need imap if you just use mutt locally > >On Fri, Dec 7, 2018, at 2:43 PM, J Marsden DeLapp wrote: >> On Fri, 7 Dec 2018 10:49:39 -0700 >> jason schaefer <js(a)jasonschaefer.com> wrote: >> >> > On 12/1/18 10:47 PM, Tom Ashcraft wrote: >> > > What they can't steal from us most of seem to be willing to give to >> > > them for free. So much for any hope of anonymity or privacy from our >> > > corporate overlords. Might as well let them tatoo a barcode on your >> > > forehead--though that wouldn't be nearly as effective. >> > >> > Its worth pointing out that if you are concerned about these issues >> > you shouldn't be using comcast for email... >> >> With a simple >> apt install postfix dovecot-imapd >> you can run your own mail server. >> >> Mars >> >> -- >> ============================================================= >> J. Marsden DeLapp, PE >> President I am following this discussion with great amusement. Maybe you guys know something I don't, but having your own email server or an email client on your desktop (phones of course are too insecure to use for anything important) seems like a lot of un-needed work trying to keep things secure. I concluded several years ago that I had neither the time nor the inclination (plus I am not expert enough in Linux) to harden my computer against email-carried malware. Also since someone could conceivably get into my computer I don't want them to have access to my email. Consequently I use web mail, (not GOOGLE!), because the ISP can do a lot better job than I at filtering out the malware and protecting against crackers. If I need to send something encrypted or very sensitive I use Protonmail from CERN. Problem solved. Doesn't matter what Comcast or anyone else allows, plus I can check my mail on any computer in the world. If I am wrong, please explain to this Linux neophyte why. >> DeLapp & Associates, Inc. dba DeLapp Engineering. >> Providing lighting and power planning, design and analysis services >> for commercial, industrial and large residential facilities. >> 1190 Harrison Road Ste 3a >> Santa Fe NM 87507 >> (505) 983-5557 >> http://DeLapp.com >> ============================================================= >> _______________________________________________ >> nmglug mailing list >> nmglug(a)lists.nmglug.org >> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org >_______________________________________________ >nmglug mailing list >nmglug(a)lists.nmglug.org >http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org

4 3

Comcast refuses to send mail to Linux desktop email clients
by Tom Ashcraft 07 Dec '18

07 Dec '18

A couple or three days ago Thunderbird stopped receiving messages from my primary email account. Turns out I can now only access Comcast email through the Xfinity webpage and through the mail app on my old Apple iPod 3. Have yet to try my old Android tablet apps. Incoming mail server, imap.comcast.net, fails to connect with up-to-date Thunderbird on three different laptop computers: My newish HP-Notebook running Kubuntu 18.04, my wife's newish HP-Pavilion running Ubuntu MATE 18.04, and my older Acer A0722 Netbook running Lubuntu 18.04. The netbook case is particularly interesting in that the Xfinity email webpage completely crashes Falkon browser and loads exceedingly slowly with Firefox. Moreover, just as with Thunderbird, Comcast server will not connect with Sylpheed mail client. Netbook has only 2MB RAM so lightweight, speedy, and stable Falkon is usually my go-to browser thereupon. Have tried alternative second-choice ports as suggested in Comcast support pages, but these don't work either. I have two other mail accounts, Google Gmail and Microsoft Hotmail/Outlook, both of which continue to work on all machines with Thunderbird and Sylpheed just fine. Anyone else out there having similar Comcast/Xfinity trouble? Thoughts, suggestions? My own bleak opinion is that now that our Comcast/Century Link duopoly has moved from modest net-neutrality regulation under the FCC to near wholesale unfettered accommodation under the FTC--and this after having benefited from de facto conception and nourishment almost exclusively at taxpayer expense (DARPA), and then on to all-out corporate gigantism through gross legal financial exploitation of the consumer (your bill as opposed to one you might experience in, say perhaps, France)--well, they just seem to do to us whatever they think they might be able to get away with. Which under the current political regime seems to be pretty much anything they want. Another dark thought is that permitting access to email exclusively through compulsory use of a website under the complete design and absolute and control of Comcast/Xfinity is partly a ploy (typical of such behemoths) to obtain my (everyone's) cell phone number (which they presently do not have) and thereby gain commercially-exploitable near total knowledge of my whereabouts and most of my economic activity at any and every waking moment. All this being accomplished in concert with, and under cover of, the ruse of the somewhat reasonable general perception of a legitimate need to firmly establish ubiquitous two-factor authentication protocols everywhere. What they can't steal from us most of seem to be willing to give to them for free. So much for any hope of anonymity or privacy from our corporate overlords. Might as well let them tatoo a barcode on your forehead--though that wouldn't be nearly as effective. Enough unsolicited ranting. I have to check in with the Thought Police.

7 7

Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients
by chochoms＠earthlink.net 07 Dec '18

07 Dec '18

I'm no expert either but I do know a thing or two about security. While setting up the server may be a piece of cake, security for it is not trivial and requires a fairly high level of expertise. I attended a briefing a few years ago at the Lab about it and it was way beyond my level of understanding. I think that is what Noah was referring to. You setup a server you open a doorway that had better be properly secured. -----Original Message----- >From: Tom Ashcraft <trailerdog234(a)comcast.net> >Sent: Dec 7, 2018 4:09 PM >To: nmglug(a)lists.nmglug.org >Subject: Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients > >OK, let me see if I've got the general idea straight --but first I'll >mention that I probably have just enough facility with the command line >to be a danger to myself and others; moreover, I vaguely seem to recall >hearing Linux promoter Noah Chelliah spout off about why doing this is >for most folks probably a very bad idea--which is not to rule out that I >might be game or fool enough to give it a try anyway: > >I can install my own server backend to feed my mail client of choice and >thereby avoid the gateway issues ordinarily implied by the facts that >Comcast is my ISP and owns the pipe that comes into my house? Is that >right? Are there scary housekeeping issues involved like maybe filling >up my hard drive with spam before I know what happened? > >On 12/7/18 2:43 PM, J Marsden DeLapp wrote: >> On Fri, 7 Dec 2018 10:49:39 -0700 >> jason schaefer <js(a)jasonschaefer.com> wrote: >> >>> On 12/1/18 10:47 PM, Tom Ashcraft wrote: >>>> What they can't steal from us most of seem to be willing to give to >>>> them for free. So much for any hope of anonymity or privacy from our >>>> corporate overlords. Might as well let them tatoo a barcode on your >>>> forehead--though that wouldn't be nearly as effective. >>> Its worth pointing out that if you are concerned about these issues >>> you shouldn't be using comcast for email... >> With a simple >> apt install postfix dovecot-imapd >> you can run your own mail server. >> >> Mars >> >_______________________________________________ >nmglug mailing list >nmglug(a)lists.nmglug.org >http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org

1 0

Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients
by chochoms＠earthlink.net 07 Dec '18

07 Dec '18

Try Protonmail. I am very happy with it. Plus its super-secure. -----Original Message----- >From: Casey Dentinger <dentinger(a)regnitned.net> >Sent: Dec 7, 2018 4:13 PM >To: chochoms(a)earthlink.net >Cc: dentinger(a)regnitned.net, "NMGLUG.org mailing list" <nmglug(a)lists.nmglug.org> >Subject: Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients > >I don't find receiving mail to be that bad but getting it successfully >delivered is a place where the internet is hamstrung by corporations. > >On 18-12-07 15:45:26, chochoms(a)earthlink.net wrote: >> >> >> >> -----Original Message----- >> >From: Casey Dentinger <dentinger(a)regnitned.net> >> >Sent: Dec 7, 2018 2:46 PM >> >To: nmglug(a)lists.nmglug.org >> >Subject: Re: [nmglug] Comcast refuses to send mail to Linux desktop email clients >> > >> >That escalated quickly :) >> > >> >Also you don't need imap if you just use mutt locally >> > >> >On Fri, Dec 7, 2018, at 2:43 PM, J Marsden DeLapp wrote: >> >> On Fri, 7 Dec 2018 10:49:39 -0700 >> >> jason schaefer <js(a)jasonschaefer.com> wrote: >> >> >> >> > On 12/1/18 10:47 PM, Tom Ashcraft wrote: >> >> > > What they can't steal from us most of seem to be willing to give to >> >> > > them for free. So much for any hope of anonymity or privacy from our >> >> > > corporate overlords. Might as well let them tatoo a barcode on your >> >> > > forehead--though that wouldn't be nearly as effective. >> >> > >> >> > Its worth pointing out that if you are concerned about these issues >> >> > you shouldn't be using comcast for email... >> >> >> >> With a simple >> >> apt install postfix dovecot-imapd >> >> you can run your own mail server. >> >> >> >> Mars >> >> >> >> -- >> >> ============================================================= >> >> J. Marsden DeLapp, PE >> >> President >> I am following this discussion with great amusement. Maybe you guys know something I don't, but having your own email server or an email client on your desktop (phones of course are too insecure to use for anything important) seems like a lot of un-needed work trying to keep things secure. I concluded several years ago that I had neither the time nor the inclination (plus I am not expert enough in Linux) to harden my computer against email-carried malware. Also since someone could conceivably get into my computer I don't want them to have access to my email. Consequently I use web mail, (not GOOGLE!), because the ISP can do a lot better job than I at filtering out the malware and protecting against crackers. If I need to send something encrypted or very sensitive I use Protonmail from CERN. >> >> Problem solved. Doesn't matter what Comcast or anyone else allows, plus I can check my mail on any computer in the world. >> >> If I am wrong, please explain to this Linux neophyte why. >> >> >> >> DeLapp & Associates, Inc. dba DeLapp Engineering. >> >> Providing lighting and power planning, design and analysis services >> >> for commercial, industrial and large residential facilities. >> >> 1190 Harrison Road Ste 3a >> >> Santa Fe NM 87507 >> >> (505) 983-5557 >> >> http://DeLapp.com >> >> ============================================================= >> >> _______________________________________________ >> >> nmglug mailing list >> >> nmglug(a)lists.nmglug.org >> >> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org >> >_______________________________________________ >> >nmglug mailing list >> >nmglug(a)lists.nmglug.org >> >http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org

1 0

Laptop screen issues continue:
by Ted Pomeroy 05 Dec '18

05 Dec '18

NMGLugers, I've been working on a Lenovo G570 with no luck at accurately diagnosing the cause of the screen going snowy white from time to time.I do have some interesting dmesg data: [ 3801.052632] perf: interrupt took too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 [ 4854.434600] perf: interrupt took too long (3172 > 3138), lowering kernel.perf_event_max_sample_rate to 63000 [ 6331.178797] perf: interrupt took too long (3978 > 3965), lowering kernel.perf_event_max_sample_rate to 50250 [ 8761.400542] perf: interrupt took too long (4978 > 4972), lowering kernel.perf_event_max_sample_rate to 40000 Another day: [ 1140.327578] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [ 1140.327612] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [ 2738.169609] perf: interrupt took too long (2540 > 2500), lowering kernel.perf_event_max_sample_rate to 78500 [ 3508.016823] perf: interrupt took too long (3226 > 3175), lowering kernel.perf_event_max_sample_rate to 62000 [ 4803.061071] perf: interrupt took too long (4049 > 4032), lowering kernel.perf_event_max_sample_rate to 49250 [ 6866.952654] perf: interrupt took too long (5089 > 5061), lowering kernel.perf_event_max_sample_rate to 39250 So, I will bring the unit to our GLUG meeting - barring a terrific snowstorm- and see if we can determine whether this is hardware or software. I am reluctant to expend any money without knowing what to fix. For now I close the the lid to restart the display and I can work for longer and longer periods without an issue. Web searches have been fruitless diversions. Thank you, Ted P.

1 0

Paranoia not asuaged, but fix found for failed incoming server in Thunderbird--no thanks to Comcast
by Tom Ashcraft 05 Dec '18

05 Dec '18

Mozilla support forum came through: Terminal command "nslookup imap.comcast.net" yields imap.comcast.net canonical name = imap.ge.xfinity.com. Substituting imap.ge.xfinity.com for imap.comcast.net in the Thunderbird email account "manual setup" window works properly as it should. Hopefully I'll achieve similar results with Kmail and Sylpheed.

1 0