After reinstalling my archlinux, I can't use fcitx input method in gnome-terminal. But it's ok in other programs such as gedit, fcitx-configtool. When in terminal, ctrl + space makes no effect. Why? What could have happened during my re-installation?
Ok, I think I have resolved the question. I put "LC_ALL=zh_CN.UTF-8" in my ~/.xinitrc so that gnome-session can not find correct config-file somewhere. Then it set XMODIFIERS=#im=ibus for me, which is not expected. After removing LC_ALL assignment, I can type Chinese in gnome-terminal again!
But, thank you too. And you can ignore this question.
Related
I have a bug on my prestashop website that i don't know how to fix.
My blocklayered module is not working... I've tried refreshing cache and indexes and also restored the module with original one but it's not working... I've also setted permissions to 777 for all the folders and files of the module...
Here is the error line:
v_24_2e5bc2f239b0cac64f2bff372a426d98.js:4 GET https://www.bobo-sport.fr/modules/blocklayered/blocklayered-ajax.php?layered_category_12=12&id_category_layered=13&_=1532013197475 500 ()
You can see the problem on this page for exemple: https://www.bobo-sport.fr/13-soins
Could you please have a look to my problem?
Thanks a lot for your help! :)
Seems like a silly resolution but we had the same issue.
screenshot of blank line
Found the fix by total fluke.
In blocklayered.php remove the blank line on the top of the file.
Some apache configs manage this others not. Sometimes there is a hidden ascii value in there that throws an error of headers already sent.
One of our clever engineers spotted this after hours of searching.
Nearly killed us.
Hope this helps.
Does anyone know why IntelliJ is printing all log messages to my console in red coloured text? This make it really hard to distinguish between info and trace messages and the actual error messages that I need to see!
I'm using Tomee and CDI if this is relevant!
Thanks for your assistance,
Edit
My setting all look okay within the preferences window:
I have stacked with the same problem too. For now I'm using Intellij IDEA 2016.1 and there are no such opportunity to color logs the way you want.
For me I have solved it by using Grep Console Plugin and recommend it to you.
It's easy to install and use.
Before
After
I had exactly same problem. Not sure about your case, but mine was following:
I use SLF4j Simple Logger Facade in my projects (because it is simple, yup). So it turned out that if you don't specify org.slf4j.simpleLogger.logFile property in simplelogger.properties file located in your resources folder (as well as if you don't have that file at all), the logger output defaults to System.err which is red in Idea.
The solution proposed by #pavlo sort of helped, but the base colour was still red.
So I added this line to src/java/main/resources/simplelogger.properties:
org.slf4j.simpleLogger.logFile=System.out
and installed Grep Console Plugin. Together they perfectly solve the problem with SLF4j Simple Logger.
I found that if I map the Console Colors for Bad command or filename to my preferred Logger.INFO color, it works fine.
This is an issue that needs fixing, for for now this workaround works for me.
This can also be solved by adding the following VM option to your run configuration.
-Dorg.slf4j.simpleLogger.logFile=System.out
I had a code in Unity UnityScript, it was working in the morning, and I did not change anything.
Now I opened Unity again, it asked "do you want to update Unity?" , I say yes, now it is downloading UnitySetup-4.3.1.exe in Chrome. This may be relevant to the issue.
Anyway, now I ran my code, and noticed something unusual.
changed my code to this :
function Update()
{
Debug.Log(Input.GetAxis("Vertical"));
}
it prints -1, although I'm not pressing anything, or none of my keys are stuck.
I tried restarting Unity. Changing my code back and forth, so it "rebuilds" (hopefully) the application. None of them worked. Maybe there is some other way to refresh the project ?
Has anyone faced an issue like this? Any ideas for a solution?
Thanks for any help !
I know this is super old question but the same issue faced me with Unity 5.3.3f1, just navigate to Edit -> Project Settings -> Inputs
You'll find 4 (Array Element) for both "Vertical" & "Horizontal" 2 each, delete the duplicate ones and you're good to go.
This is expected. As per the documentation here:
The value will be in the range -1...1 for keyboard and joystick input.
If the axis is setup to be delta mouse movement, the mouse delta is
multiplied by the axis sensitivity and the range is not -1...1.
Installing the latest version (4.3.1) and restarting Unity solved the issue..
When debugging ExtJS 4 (tried both versions 4.1.0 and 4.1.1), FireBug repeatedly shows the following error: An invalid or illegal string was specified
http://docs.sencha.com/ext-js/4-1/extjs/ext-all.js
Line 18. It does not break on the error, though that option is specified. Additionally, neither my code or ext-debug.js and it's loader seem to actually call ext-all.js.
This error gets logged to Firebug's console about once per minute, which is annoying. What bothers me is that I cannot get the error to go away. Is this a FireBug bug? An ExtJS bug? Aliens? How can I debug the debugger?
I had the same problem before and I've solved it by removing a special character at the end of my JS file! (app.js I think)
It was weird, but the problem came from hidden special characters like: Zero-width non-joiner or Right-to-left mark.
Open another JS file but do not copy/paste your code there. Just write it again and check whether the problem exists or not.
And don't forget to check your data if you have some. As this article explains about the problem: http://www.ashorlivs.fr/javascript-jquery/article/an-invalid-or-illegal-string-was
For general debugging see this link http://www.sencha.com/learn/debugging-ext-js-applications/
You can also use ext-all-dev.js while in development mode.
There is another excellent tool on top of firebug, at this link http://www.illuminations-for-developers.com/
PS: I still didn't figured out how to post a comment. I guess it comes when I have more points/reputation. Hence adding it as an answer. thanks.
After setting up a table model in Qt 4.4 like this:
QSqlTableModel *sqlmodel = new QSqlTableModel();
sqlmodel->setTable("Names");
sqlmodel->setEditStrategy(QSqlTableModel::OnFieldChange);
sqlmodel->select();
sqlmodel->removeColumn(0);
tableView->setModel(sqlmodel);
tableView->show();
the content is displayed properly, but editing is not possible, error:
QSqlQuery::value: not positioned on a valid record
I can confirm that the bug exists exactly as you report it, in Qt 4.5.1, AND that the documentation, e.g. here, still gives a wrong example (i.e. one including the removeColumn call).
As a work-around I've tried to write a slot connected to the beforeUpdate signal, with the idea of checking what's wrong with the QSqlRecord that's about to be updated in the DB and possibly fixing it, but I can't get that to work -- any calls to methods of that record parameter are crashing my toy-app with a BusError.
So I've given up on that idea and switched to what's no doubt the right way to do it (visibility should be determined by the view, not by the model, right?-): lose the removeColumn and in lieu of it call tableView->setColumnHidden(0, true) instead. This way the IDs are hidden and everything works.
So I think we can confirm there's a documentation error and open an issue about it in the Qt tracker, so it can be fixed in the next round of docs, right?
It seems that the cause of this was in line
sqlmodel->removeColumn(0);
After commenting it out, everything work perfectly.
Thus, I'll have to find another way not to show ID's in the table ;-)
EDIT
I've said "it seems", because in the example from "Foundations of Qt development" Johan Thelin also removed the first column. So, it would be nice if someone else also tries this and reports results.
I use Qt 4.6.1 in PyQt and the problem is still here. Removing "removeColumn(0)" solves the issue.