I am trying the following command:
xdotool key --clearmodifiers --delay 500 alt+f
and the result is the following error:
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 132 (XTEST)
Minor opcode of failed request: 2 (X_XTestFakeInput)
Value in failed request: 0x0
Serial number of failed request: 18
Current serial number in output stream: 19
I tried without the --clearmodifiers and --delay but still the same error.
My system is Arch Linux and i3 window manager.
I'm also running the same setup as my primary OS (arch + i3). I tried downloading xdotool and running the same command. It works both with and without the two options.
I'd try the following if it wasn't working (unless you have already):
1> Reinstall *xdotool*, update, and reboot.
2> Although it worked, my mod key is set to the *win* key so I'm not sure if that somehow causes issues with
a programmable keypress (you wouldn't think so). Try temporarily changing the modifier to the *win* key in your config and reinstall xdotool.
3> I would also try reinstalling its dependencies (namely libxtst and libxinerama)
4> If all of the above fails, I'd try the *xdotool-gui* package from the AUR instead and see if that fixes anything.
One question: Just to verify, is that error always persistent, or is it only in that one case of alt+f?
Regards :)
Related
We have a running TwinCat project on a PC. After the restart of the machine, the following error occurs when i try to run the project in "Run Mode" or try Online Reset.
Errors:
Type Server (Port) Timestamp Message
Error (65535) 'Term 29 (EK1100)' (1006): state change aborted (requested 'PREOP', back to 'INIT').
Error (65535) 'Term 29 (EK1100)' (1006): 'INIT to PREOP' failed! Error: 'check product code'. Device 'EL1014-XXXX-XXXX' found and 'EK1100-0000-0018' expected.
Warning (65535) 'Term 33 (EL1014) (1010) - Term 34 (EL1014) (1011)' Communication interrupted
Warning (65535) 'Term 35 (EK1100) (1012) - Term 43 (EL1014) (1020)' Communication interrupted
Tree structure
Online State
The EK1100 and EL1014 were changed, but the error stays. Please, can you suggest a fix for this problem?
Very likely the problem is that the configured ethercat tree structure does not match the one found.
As you can see the Ethercat master expects 'EK1100-0000-0018' but finds 'EL1014-XXXX-XXXX'
Rescan you ethercat tree from the system manager and see if the configured and the found hardware-configuration matches.
Correct your ethercat configuration if you notice errors and reactivate the project.
Specifically take a look at TERM29.
There you can probably find the source of your error.
Either a wrong card has been swapped or the ethercat connection is faulty there.
I am running a code in jupyter notebook (here is the code for reference):
import ROOT as root
f = root.TFile("160721_0828.root")
for event in f.tree.events:
print (1)
It should be a simple code, looping through a file. But when I run it, the kernel crushes and I have to restart everything. I also get in terminal many errors of this kind:
2016-08-08 18:25:20.439 atos[99872:272f] Metadata.framework [Error]: couldn't get the client port
0x0000000100000cc4 in start (in python) + 52
before the program crushes. I am using a Mac, version 10.9.5. What could be the cause?
Perhaps your Spotlight indexing is disabled and necessary metadata is inaccessible.
Try to turn Spotlight indexing On and the error message:
"Metadata.framework [Error]: couldn't get the client port"
disappears and kernel will be stable.
I'm using WordPress 3.5 with child-theme of Twenty Eleven 1.5. Suddenly I'm getting following Warning,
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'cp_admin_init' was given in /home/templ/public_html/wp-includes/plugin.php on line 406
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_canonical_charset' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
I'm using following plugins:
download-manager 2.3.9
wordpress-seo 1.4.7
wp-pagenavi 2.83
Some more points:
1) If I'm giving mysite.com it's giving above 2 line warning. If I give www.mysite.com, the following line also include,
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-includes/pluggable.php on line 876
2) If I give mysite.com/wp-admin/ or www.mysite.com/wp-admin/, It's giving 1st warning and 3rd warning.
3) If I goto www.mysite.com/wp-login.php, It's giving following 5 warning.
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'cp_admin_init' was given in /home/templ/public_html/wp-includes/plugin.php on line 406
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_canonical_charset' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 368
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 380
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'wp_authenticate_spam_check' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
4) If I give correct username and password, it's not going to login. giving following problem,
ERROR: Invalid username or incorrect password.
ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.
I'm trying to find solution. I can't. Can any-one help me?
This sounds like a corrupted install. So you have a few options to fix this:
Attempt to get logins operational again and doing an upgrade though the wp-admin: Explained Below.
Do a manual Update: http://codex.wordpress.org/Updating_WordPress#Manual_Update
But First: Make a Backup
Please be sure to backup your install! Before proceeding: http://codex.wordpress.org/WordPress_Backups
Getting Logins Working: Masking the symptoms
First I would disable debugging output because that should fix most of these issues. When a warning occurs in Wordpress, PHP starts writing the response body and closes the header section of the response. This means that whenever Wordpress tries to add another header after the original warning was raised, PHP will raise another warning:
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 380
So if we disable debugging then we should be able to mask the symptoms. This is a quick patch for a larger problem that we will have to solve with an in-place upgrade
To Disable Debugging
Ensure that the following constants exist and are set correctly is in your wp-config.php file
define('WP_DEBUG', false);
and
define('WP_DEBUG_DISPLAY', false);
Now you should be able to login to your site as an administrator without errors.
Disable your Plugins
Disable all your plugins in Plugins -> Installed Plugins This is imperative so that we can make sure that the update goes smoothly.
Do an Update
Go to Dashboard -> Updates and click either Update Now or Re-install Now
Reactivate your Plugins
Reactivate all your plugins in Plugins -> Installed Plugins and update them if necessary.
That's It
That's the process for reinstalling Wordpress. The key here is that you have Debugging enabled on a production site which is not good. You should always have WP_DEBUG and WP_DEBUG_DISPLAY set to false in a production environment.
I am installing Hunchentoot on a new machine. This time I thought I would try out Lispy, because it appears to be simplest way of managing the dependencies for Hunchentoot in a standard and hopefully automatic way. However, when I install it, it trips on not being able to verify a key. I have seen ASDF-INSTALL try to use a key before, and I have normally found some way to skip verifying the key. I don't really need that kind of security, I trust the people distributing these packages, OK? Anyway, in this case there is no restart to skip the key, so rather than dig into the code and hack my way out of it, I was wondering if there is a more correct way to deal with this. I assume Lispy isn't supposed to be broken and I am using the most standard and supported environment imaginable for Common Lisp: Ubuntu + sbcl. I figure I could make this work, but then again I could just install all the dependencies for Hunchentoot manually using ASDF-INSTALL just as easily, so I figure I'll give Lispy a shot and do it in a more controlled and correct way. Here's the actual log of what I did, cutting out most of the in-between messages:
* (load "asdf-config.lisp")
T
* (asdf:oos 'asdf:load-op :lispy)
; loading system definition from /home/rob/lispy/lispy-0.5/lispy.asd into
...
2010-01-06 23:13:25 "Initializing Lispy system on SBCL 1.0.29.11.debian"
2010-01-06 23:13:25 "Fetching http://common-lisp.net/project/lispy/repository/map.lisp-expr"
2010-01-06 23:13:27 "Fetching http://common-lisp.net/project/lispy/repository/map.lisp-expr.asc"
gpg: Signature made Fri 25 Dec 2009 01:19:20 PM EST using DSA key ID 7CF49723
gpg: Can't check signature: public key not found
debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread" RUNNING {AA5E5E9}>:
GPG verification of map /var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr with signature /var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr.asc failed: "gpg: Signature made Fri 25 Dec 2009 01:19:20 PM EST using DSA key ID 7CF49723
gpg: Can't check signature: public key not found
"
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry performing #<ASDF:LOAD-OP NIL {AAA7F01}> on
#<ASDF:SYSTEM "lispy" {ABF01E9}>.
1: [ACCEPT] Continue, treating #<ASDF:LOAD-OP NIL {AAA7F01}> on
#<ASDF:SYSTEM "lispy" {ABF01E9}> as having been successful.
2: [ABORT ] Exit debugger, returning to top level.
(LISPY::VERIFY-MAP
#P"/var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr.asc"
#P"/var/cache/common-lisp-controller/1000/sbcl/local/home/rob/lispy/maps/map.lisp-expr"
#<PURI:URI http://common-lisp.net/project/lispy/repository/map.lisp-expr>)
Install gpg
wget http://common-lisp.net/project/lispy/key.asc
gpg --import key.asc
You should be good to go.
Have you tried quicklisp? It is amazing.
Oh wow, I just discovered a number of lisp packages are in Ubuntu's apt repository, including Hunchentoot. Amazing! How did I not know about this?
Sorry, not really programming question, but I am not sure where else I could find some help.
After a recent update (Xorg was updated among other things), GTK apps stopped running in my kde4. I have a Debian unstable, updated around 22 April. When I try to run them I get the following error:
ga#grzes:~$ iceweasel
The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadName (named color or font does not exist)'.
(Details: serial 888 error_code 15 request_code 45 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
ga#grzes:~$ gimp The program 'gimp' received an X Window
System error.
This probably reflects a bug in the program.
The error was 'BadName (named color or font does not exist)'.
(Details: serial 6955 error_code 15 request_code 45 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
(script-fu:4643): LibGimpBase-WARNING **: script-fu: gimp_wire_read():
error
I have to restart the font server manually to have it fixed:
ga#grzes:~$ su
Password:
grzes:/home/ga# /etc/init.d/xfs restart
Stopping X font server: xfs.
Setting up X font server socket directory /tmp/.font-unix...done.
Starting X font server: xfs.
Any ideas what could be wrong? Is it a configuration issue? My system has been updated for the last 7 years, so I can have some old settings.
Debian unstable is very... unstable now, since a release was made a short time ago. Major changes and packages migrations are happening. Xorg (and all X related stuff) being one of the critical packages in that process. My advice is to perform a new update/upgrade in order to catch a new version that may resolve this problem.
It's very frequent that after an update some thing will get broken in inexplicable ways, simply because the developers are uploading new, and not much tested, version of the applications
I finally figured this out: seems like xfs is not compatible with the other components currently and luckily removing it form the system completely solves the problem.