Checked that the new dependencies is running correctly - run cargo and a temporary node in development mode in [node-template].
When I start yarn [Front-End Template] 'Nicks' is not displayed in combo 'Pallet Interactor'..
Checked cargo.toml/lib.rs to ensure that I have followed tutorial, and can not see where I am going wrong.
I would appreciate some advice on where I am going wrong, and how to solve this issue.
When I try and open the application nothing happens, no menu bar/windows, nothing.
I have tried uninstalling - reinstalling.. I have checked the permissions, nothing works.
I tried opening the program using terminal to see if there were any error messages and i got this.
(base) Mac-Pro:~ ash$ /Applications/Backup\ and\ Sync.app/Contents/MacOS/Backup\ and\ Sync
/Applications/Backup and Sync.app/Contents/Resources/lib/python2.7/site-packages.zip/wx/_core.py:16633: UserWarning: wxPython/wxWidgets release number mismatch
2020-05-14 17:04:47.318 Backup and Sync[1538:17017] GsyncAppDeletegate.py : Finder debug level logs : False
I am not really sure how to decipher that. "wxPython/wxWidgets release number mismatch"?
also when I look in activity monitor the process has this weird white box log.
Not really sure how best to either identify the problem or solve it. Any idea's, or pointers/steps i can use to help me figure out what the problem is would be greatly appreciated.
Cheers
I recently installed Manjaro i3 on my laptop and tried to connect an external Monitor, to extend the main Screen when it's plugged in and just use the single monitor mode when not.
This seems to mostly work using arandr. Unfortunately I have to reapply the arandr settings again on every boot to get my layout back, since it gets reset every time.
I have tried exporting the arandr commands to .xinitrc and /root/xinitrc, I have tried editing the xorg confs and I have tried putting it into .screenlayout, but with no result.
So how can I permanently set my screen resolution and layout?
I case somebody comes across this question:
1. open arandr
2. Set your desired layout
3. Export it
4. open /etc/lightdm/xsession
5. Add the exported code before the last line
6. reboot
I am having trouble using Xdebug with PHPStorm. I have searched Google, etc.
I have Xdebug setup on a remote host with my local files mirroring the remote host. I am using the Xdebug Chrome extension.
When I run the debugging through PHPStorm, it OPENS a file and shows a blue-highlighted breakpoint that does NOT exist at that file. It will stay there until I hit "resume" multiple times until I get to the file I actually want to debug. VERY annoying because then the session on Chrome timesout, so I can't debug.
I do not see any code that says xdebug_break(); and I never added a breakpoint to that file. In other words, there are no red markings at the left of the line numbers.
What is going on and how do I fix this? Has anyone else come across this problem?
I have tried skipping and ignoring the file ... still does not work! Yes, I have also viewed breakpoints through a separate window and it does not show the breakpoint that apparently exists.
Check the configuration on PHPStorm stop at first line property and disable it
After that go to Run >> Break at first line in PHP scripts
Try turning it ON and OFF few times. Sometimes it is get stuck in between: showing OFF but in reality it is ON.
This is a well known issue Read: https://youtrack.jetbrains.com/issue/WI-17389
I was having the same problem with my PHPStorm/xdebug config. It turned out I had the path mappings wrong when I mapped the root of the local file directory to the Absolute path on the server - Settings->Languages and Frameworks -> PHP -> Servers.
I fixed the mapping and the system is behaving predictably once again.
n00b here. After searching the forums I have not yet come across this problem as I am experiencing it.
I have a CI site that was working correctly until about three days ago. My problem is as follows:
On button click - Page Loads correctly.
On Enter press - CI Blank Page of Death loads.
For example: When I login, after the login process has run it must reroute me to the Dashboard, unless I still have a temporary password where I get rerouted to the "Change Password" screen first and then to the Dashboard.
AS LONG AS I USE THE BUTTONS AND CLICK THEM EVERYTHING WORKS.
On ENTER PRESS, I get the Blank Screen of Death.
However, on TAB to BUTTON and then ENTER it works.
The problem is not consistent however. I have some processes that do not have views attached and NONE of them will run - hit ENTER and get blank. They are all failing on ENTER PRESS.
I am slowly going off my trolley. Logging is ON, Directories for cache and logs are 775. NOTHING is showing in my logs...
First Try to active error handlers for displaying of errors for addittional info to post here what error is occuring..
// change settings for error handler to show errors
// $this setup is used for checking errors for development to be shown....
ini_set('display_errors', 1);
error_reporting(E_ALL);
by the way if your using CI version 2 higher
you can see it in its index.php file an configuration for displaying error also.
define('ENVIRONMENT', 'development'); //just set up environtment to development
Even though there are accepted answers I wanted to add a way that worked for me to figure out this problem.
Usually the "Blank Page" indicates a PHP parsing error somewhere in the code. Strange thing for me was that on my local MAMP based test server the code ran fine. I FTP it to my hosted server and all of a sudden, blank page of death.
Even though I had errors on, log errors on, display errors on, nothing appears in any log file.
I was able to find the error by a funny little trick. I added an echo line in CodeIgniter.php in the system/core. Obviously hacking the core was not a great idea but all I wanted to do was to see how far it was getting in the load process.
When my echo appeared after trying to load a page on the remote hosted server it also displayed the parsing problem in a derived controller! Not sure why the error did not come out without the "echo" added. But adding it seemed to trigger some output to be generated, IE my echo line and the PHP parse error was appended.
Not sure if this will help anyone but it turned out to be a nice easy way to find the error which only showed on the remote server.
Obviously, don't forget to put your core file back to its original state without the echo.
This was fixed by copying the application into a fresh CI 2.3 install.
I have no idea what actually caused this "erratic" behaviour.
The application worked correctly as designed whenever a BUTTON was CLICKED but gave the blank death screen when ENTER was PRESSED.
This inconsistent behaviour is what threw me. The fact that my logs (CI and APACHE) also showed nothing was also very strange. Had this been a parse error, surely the behaviour on "Click" and on "Enter Press" should have been the same.
My non-view controllers for various ad-hoc admin jobs are now also working correctly, which they were not before, as they use "Enter Press" (having no buttons to "Click").
I am still going to invite best guesses as to why this behaviour occurred the way it did.
Surely someone out there (Phil Sturgeon et al) with extensive CI experience has encountered this non-consistent blank screen behaviour and knows what caused it.
Thank you to all the people who took the time and effort to assist me!!!
Big UP!!! StackOverflow!!!
probably error in INCLUDE login.php
My problem was Apache stop working because of ...Skype! Skype actually work on the same 443 and Apache didn't start! I hate this Skype! Bring me nuts for a while.
Installing php5-pgsql worked for me