You are not logged in.
2 days ago (2014-09-24) I ran pacman -Syu. There was a conflict with ca-certificates-java ca-certificates-utils, so I told it to remove ca-certificates-java and keep only utils. Then utils gave a file conflict error and, because I'm an idiot and assumed it was just "leftover" files that got merged from the Java package into utils, I ran again with --force. It seemed to go fine, something said "failed to run", but everything still worked so I moved on. Rebooting yesterday, however, all my browsers or anything trying to access HTTPS will fail certificate authentication. At first I thought this was clock problems (someone I know was having problems where their clock was constantly resetting to some weird date on windows, so I booted to windows to walk them through setting more coherent sync times, which I thought may have changed my clock to local time), but after triple checking the time and rebooting, the problem still persists.
I searched the forums and it seems it may be related to this, at least the time frame seems more or less correct, it's possible that my problem actually occurred from my update on the 23rd, I didn't give it much thought so the days may be incorrect. However, I now have ca-certificates-20140925-2, same for utils, and the problem has not been resolved.
I tried downgrading ca-certificates{-utils, -cacerts}, to before the 23rd, but to no avail. I've run update-ca-trust and update-ca-certificates (depending in which version of utils I had) and neither of those seem to fix the problem.
Erm... At some point used Rdd to remove all the ca-certificates packages and then reinstalled them all, also no help. However, this did cause the "failed to run" error to go away, which seemed like progress, anyway.
It looks like all the Symlinks are in place and pointed to the correct spot, though I'm not at this system right now so I can't get the ls -l output to prove it. If that's necessary I can get them later tonight when I get back to the system.
I... Think that's everything I've done to my system recently. I'm also only guessing this is a package upgrade issue, it's very possible this thread should be elsewhere, but I don't know. I'm pretty confused at this point, and it doesn't help that my knowledge of certificates is honestly a bit lacking, so any help or suggestions for diagnosis would be appreciated. Thanks.
Edit: Went away today. Don't know why. Possibly because of an update, but I don't think so since I was still in the download phase when I tested it. Whatever, problem solved, I guess, just wish I knew what the cause was...
Last edited by HuFlungDu (2014-09-29 06:20:20)
Offline