Re: 6.2-Release - Firefox and Codeblocks Issues
On 2017-10-16 20:30, Josh Grosse wrote: 1. Discussion was moved to ports@. 2. I have tested a fix, which I will publish for -current and 6.2-stable. 3. I will need to build and test the -stable package, and can then make it available to you if you want to trust an unsigned package from the port maintainer. To close the loop, an improved fix for devel/codeblocks has been submitted to ports@. https://marc.info/?t=15111045484=1=2
Re: 6.2-Release - Firefox and Codeblocks Issues
1. Discussion was moved to ports@. 2. I have tested a fix, which I will publish for -current and 6.2-stable. 3. I will need to build and test the -stable package, and can then make it available to you if you want to trust an unsigned package from the port maintainer.
Re: 6.2-Release - Firefox and Codeblocks Issues
On 2017-10-15 21:01, tec...@protonmail.com wrote: > Hi, > > Firefox / Firefox-ESR > I can not access my protonmail.com email account on both of these versions > as I can't get to the login screen (it hangs on the loading screen) - this is > evident by going to https://mail.protonmail.com/login. I have experienced > this same issue on two different installs, so I believe anyone trying to > access this site or some others will face the same issue. My guess is that > it is due to the JavaScript functions it is running on this page. > > Chromium works without issue and shows the login form. Problem is, I really > despise Chromium and actively try to stay away from all Google services. > > ### > > Codeblocks > This crashes as soon as I open it. I can briefly see the codeblocks graphic > before it does so. > > $ codeblocks > Starting Code::Blocks Release 16.01 rev 10692 Oct 2 2017, 19:06:03 - > wx2.8.12 (OpenBSD, unicode) - 64 bit > Initialize EditColourSet . > Initialize EditColourSet: done. > Abort trap (core dumped) > > $ gdb > (gdb) core codeblocks.core > Core was generated by `codeblocks'. > Program terminated with signal 6, Aborted. > #0 0x0f1d99cdb2da in ?? () Same problem here after upgrading to 6.2 (moved to latest snapshot and it's still the same) and I did pkg_add -u. You can see the backtrace. I'm trying to compile the codeblocks ports but for (another reason I should investigate), the build process is very slow while the CPU is almost (82%) idle and it will takes a while: (gdb) bt #0 thrkill () at -:3 #1 0x01c2120ac7fd in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51 #2 0x01c1ca250ec1 in wxFatalSignalHandler () from /usr/local/lib/libwx_base.so.3.0 #3 #4 0x01c1ca20d500 in wxStringBase::operator= () from /usr/local/lib/libwx_base.so.3.0 #5 0x01c26c874b50 in wxPGProperty::wxPGProperty () from /usr/local/lib/libcodeblocks.so.0.1 #6 0x01c26c8996e1 in wxStringProperty::wxStringProperty () from /usr/local/lib/libcodeblocks.so.0.1 #7 0x01bfae5aba40 in WatchesProperty::wxCreateObject () from /usr/local/bin/codeblocks #8 0x01bfae5174ae in DebugInterfaceFactory::OnEditorDeactivate () from /usr/local/bin/codeblocks #9 0x01c26c5ef3b1 in DebuggerManager::CreateWindows () from /usr/local/lib/libcodeblocks.so.0.1 #10 0x01c26c5f0282 in DebuggerManager::SetInterfaceFactory () from /usr/local/lib/libcodeblocks.so.0.1 #11 0x01bfae55cea7 in MainFrame::OnUnlockLogManager () from /usr/local/bin/codeblocks #12 0x01bfae5565c7 in MainFrame::OnMouseRightUp () from /usr/local/bin/codeblocks #13 0x01bfae554f18 in MainFrame::OnMouseRightUp () from /usr/local/bin/codeblocks #14 0x01bfae506e9d in CodeBlocksApp::OnTBIconLeftDown () from /usr/local/bin/codeblocks #15 0x01c1ca1e4200 in wxEntry () from /usr/local/lib/libwx_base.so.3.0 #16 0x01bfae504f9f in wxCreateApp () from /usr/local/bin/codeblocks #17 0x01bfae504e04 in ?? () from /usr/local/bin/codeblocks #18 0x in ?? () Current language: auto; currently asm
Re: 6.2-Release - Firefox and Codeblocks Issues
On Sun, Oct 15, 2017 at 12:31:42PM -0400, tec...@protonmail.com wrote: > Hi, > > Firefox / Firefox-ESR > I can not access my protonmail.com email account on both of these versions > as I can't get to the login screen (it hangs on the loading screen) - this is > evident by going to https://mail.protonmail.com/login. I have experienced > this same issue on two different installs, so I believe anyone trying to > access this site or some others will face the same issue. My guess is that > it is due to the JavaScript functions it is running on this page. > > Chromium works without issue and shows the login form. Problem is, I really > despise Chromium and actively try to stay away from all Google services. > > ### > > Codeblocks > This crashes as soon as I open it. I can briefly see the codeblocks graphic > before it does so. Thank you for your report regarding codeblocks. I am able to replicate the abort signal, and will try to diagnose. --->>> Transitioning this discussion to ports@ <<<--- > > $ codeblocks > Starting Code::Blocks Release 16.01 rev 10692 Oct 2 2017, 19:06:03 - > wx2.8.12 (OpenBSD, unicode) - 64 bit > Initialize EditColourSet . > Initialize EditColourSet: done. > Abort trap (core dumped) > > $ gdb > (gdb) core codeblocks.core > Core was generated by `codeblocks'. > Program terminated with signal 6, Aborted. > #0 0x0f1d99cdb2da in ?? ()
6.2-Release - Firefox and Codeblocks Issues
Hi, Firefox / Firefox-ESR I can not access my protonmail.com email account on both of these versions as I can't get to the login screen (it hangs on the loading screen) - this is evident by going to https://mail.protonmail.com/login. I have experienced this same issue on two different installs, so I believe anyone trying to access this site or some others will face the same issue. My guess is that it is due to the JavaScript functions it is running on this page. Chromium works without issue and shows the login form. Problem is, I really despise Chromium and actively try to stay away from all Google services. ### Codeblocks This crashes as soon as I open it. I can briefly see the codeblocks graphic before it does so. $ codeblocks Starting Code::Blocks Release 16.01 rev 10692 Oct 2 2017, 19:06:03 - wx2.8.12 (OpenBSD, unicode) - 64 bit Initialize EditColourSet . Initialize EditColourSet: done. Abort trap (core dumped) $ gdb (gdb) core codeblocks.core Core was generated by `codeblocks'. Program terminated with signal 6, Aborted. #0 0x0f1d99cdb2da in ?? ()
