18:10:29 does crash reporting - ah, maybe because it's a wg9s build... if so, i can fire up a Release & send... ? 18:13:16 Release looks to need a un/pw to submit a crash? 18:14:23 ah, that only happens if you try to "open" (Report) the link in a new tab 18:14:38 clicking directly on the link works 18:27:50 "works". worked for 2 older crashes (probably immaterial, & they were old), but not on today's crash? 18:28:21 and even with the ones that did go through, seems there isn't really much "there" 20:34:13 therube symbols probably missing currently. Still working some kinks out. If you have something reproducible best to try with the official beta. 20:35:18 no, it was just something out of the blue, totally unexpected, & it was that that made say, "hey i wonder what the report might show" 20:36:57 i've not crashed in ages. & the two that did go through, while i don't remember any details, it was most likely something i did knowingly & purposely, so the fact that i might have crashed was immaterial as i knew i was going to - ahead of time 20:44:16 therube Windows 10 19045 ? 20:44:49 Win7 SP2 :-) 20:46:18 therube which id? 20:46:51 frg_Away: cf34310f-acd0-4a3d-95ff-33ce18386c82 20:47:08 therube this is an old one. 20:47:33 not bugsplat 20:47:48 heh, ah, you're right. it was the one that was left under Report rather then submit 20:48:01 so it is then either 20:48:02 https://crash-reports-test.seamonkey-project.org/report/index/bp-aea0ab16-f563-49b6-a3f2-9a17b0231116 20:48:04 or 20:48:09 https://crash-reports-test.seamonkey-project.org/report/index/bp-249ba487-80c4-4f57-8240-862690231116 20:48:22 these are both old ones 20:48:42 & it's going to be the 1st one - cause that is 2.53.18 20:49:14 Not the beta for sure. 20:49:29 This is one I did intentionally with the beta: 20:49:30 https://app.bugsplat.com/v2/crash?database=seamonkey_project&id=1875 20:49:54 SystemMemoryUse 53%, that seems odd 20:50:01 What is you build id? 20:52:17 frg_Away: not sure offhand (as i put in 2.53.19 after it happened) - actually i can probably tell - in a moment or two... 20:52:35 The ones above are ancient 2.53.17 and 2.53.18 20:56:00 frg_Away: well the 1 report shows, 20230609110002, so that should be Jun 9 20:56:28 yes ancient :) 20:56:56 you're right, old. unless that happened to be an old report, not sure now? 20:58:15 maybe a report did not get generated at all this time? & i simply took the 3 that did show as "2 are old" & 1 was the actual crash from today, so thought i'd just submit all of them, not paying attention to what was actually there? 21:02:31 i do have other 2.53.18's - of 07-02 09-17 & 10-01, & i've got to assume that if i downloaded them, i did actually install them? so that would point to a build of 20231001210003 21:03:32 but then, crash reporter certainly did come up. 21:06:18 frg_Away: i think i missed 1, it must be this, https://crash-reports-test.seamonkey-project.org/report/index/bp-a8acf476-5198-4d6b-9d0a-7acd40231116 21:07:26 therube Anything going to crash-reports is/was old. Early October build 20231001210003 21:07:34 missed one that did in fact get submitted (just didn't realize) - again there were 3 & i saw 1 left (that didn't go through), so i only looked a 1 + 2 more - ignoring the fact that 3 did go through 21:07:48 yes, that was my last build prior to getting 2.53.19 21:09:50 therube maybe grab the current 2.53.19 then. Just updated nss and nspr and could use some testing. 21:10:02 i've not manually deleted that 1 old "stuck" crash report if i happen to crash again, that won't be there to confuse me 21:10:13 frg_Away: yes, i'm on that now 21:11:01 20231116140004 21:11:15 Probably good. The ones from today. Should show NSS 3.90 not 3.79.4 in about:support 21:18:15 yes, 3.90 21:20:16 maybe that's why i can't log in to gmail !!! 21:20:18 (or, could it be that i've forgotten the passwword ;-) 21:20:19 not to mention, that the reason for all of this is that they're doing away with "Basic" gmail - which is all i ever use. so on that note, i might just do away with them. 21:20:21 "Time to use the latest Gmail" - bla! 21:22:05 first (gmail) pop stopped working in Eudora. now they're getting rid of Basic webmail. hmphf. 21:22:29 therube all for the good of humanity I am sure. 21:22:55 or better data scraping & tracking 21:33:50 stupid crap. so gmail sends a "code" (or prompt) to my brothers phone (i have none) & he types in the code which i am reading into his phone, at which point i theoretically should be "in", but i'm not. so i go through the same nonsense 3 more times, & it was on the 4th that my end finally said "did you enter the code on your phone" & on clicking 'yes' on my end, so now i can get into gmail... 21:33:51 ...- for now. 21:34:54 here's another one, https://secure.login.gov/ that is going to be a winner. login.gov. now what could possibly go wrong. 21:36:28 had a login for eftps.com. first have to go through login.gov. had a login for ssa.gov. first have to go through login.gov. but that doesn't work - because they have to send a code - via postal mail (usps, 5-7 days ;-))