Selecting/highlighting Text Problem
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I am using Backtrack 5. As it is based on Ubuntu 10.04 I decided to ask my question to here:
I'm having problems selecting text with my mouse. For example when I try to rename a folder, sometimes I can successfully highlight the text but when I release the mouse button, it is no longer highlighted. Sometimes I can't even successfully highlight the part of the text that I want. It highlights more or less of the text then actually selected.
First I thought it was a problem caused by my mouse, however, I tried another mouse and the problem continues. This problem really bothers me while surfing on the net. Could you please help me?
mouse gui text backtrack
add a comment |
up vote
2
down vote
favorite
I am using Backtrack 5. As it is based on Ubuntu 10.04 I decided to ask my question to here:
I'm having problems selecting text with my mouse. For example when I try to rename a folder, sometimes I can successfully highlight the text but when I release the mouse button, it is no longer highlighted. Sometimes I can't even successfully highlight the part of the text that I want. It highlights more or less of the text then actually selected.
First I thought it was a problem caused by my mouse, however, I tried another mouse and the problem continues. This problem really bothers me while surfing on the net. Could you please help me?
mouse gui text backtrack
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I am using Backtrack 5. As it is based on Ubuntu 10.04 I decided to ask my question to here:
I'm having problems selecting text with my mouse. For example when I try to rename a folder, sometimes I can successfully highlight the text but when I release the mouse button, it is no longer highlighted. Sometimes I can't even successfully highlight the part of the text that I want. It highlights more or less of the text then actually selected.
First I thought it was a problem caused by my mouse, however, I tried another mouse and the problem continues. This problem really bothers me while surfing on the net. Could you please help me?
mouse gui text backtrack
I am using Backtrack 5. As it is based on Ubuntu 10.04 I decided to ask my question to here:
I'm having problems selecting text with my mouse. For example when I try to rename a folder, sometimes I can successfully highlight the text but when I release the mouse button, it is no longer highlighted. Sometimes I can't even successfully highlight the part of the text that I want. It highlights more or less of the text then actually selected.
First I thought it was a problem caused by my mouse, however, I tried another mouse and the problem continues. This problem really bothers me while surfing on the net. Could you please help me?
mouse gui text backtrack
mouse gui text backtrack
edited May 12 '13 at 17:10
Runium
17.8k42859
17.8k42859
asked May 12 '13 at 16:28
Xentius
11112
11112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
11
down vote
Possibly something is constantly stealing the X selection. To find out who it is. You could compile this:
#include <stdio.h>
#include <X11/Xlib.h>
#include <X11/Xatom.h>
int main()
printf("%#lxn", XGetSelectionOwner (XOpenDisplay(0), XA_PRIMARY));
return 0;
With:
gcc that-file.c -lX11
That code is to return the window ID of the owner of the PRIMARY
X selection. Then you could use xdotool
to get the PID of the process that owns that window (assuming that Window is from a local client and that it lets the Window Manager know its PID):
ps -fp "$(xdotool getwindowpid "$(./a.out)")
If you don't have xdotool
, you can do it the hard way: you can look up that window ID in the output of xwininfo -root -all
:
xwininfo -root -all | less "+/$(./a.out)"
The window that owns the selection may not have a name, but you can look at its parent or grandparent for more clue. Once you find the ancestor that is managed by the Window manager, you can get the process ID (assuming the window is displayed by a local process) with:
xprop -id that-id _NET_WM_PID
Example:
$ xwininfo -root -wm -tree | grep -B3 "$(./a.out)"
24 children:
0x2800024 "Sun 12 May - 21:40 - zsh (2)": ("xterm" "XTerm") 1920x1059+0+19 +0+19
1 child:
0x280002f (has no name): () 1920x1059+0+0 +0+19
0x280002f owns the PRIMARY selection, whose parent is "xterm" (0x2800024 managed by the Window Manager).
$ xprop -id 0x2800024 _NET_WM_PID
_NET_WM_PID(CARDINAL) = 9707
$ ps -fp 9707
UID PID PPID C STIME TTY TIME CMD
chazelas 9707 1 0 08:50 ? 00:00:02 xterm
And that's its pid.
Once you know who owns that selection, it may become clearer what's happening.
Note: I had to change printf line in the C code to use%lu
instead of%x
as the variable there waslong unsigned int
.
– Kris
2 days ago
And so I suppose I got the wrong number there as an ID as I cannot find that ID within the xwininfo results.
– Kris
2 days ago
@Kris, sorry my bad, I had overlooked that Window IDs werelong
. It should be%lx
(see edit) asxwininfo
displays IDs in hex.
– Stéphane Chazelas
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
11
down vote
Possibly something is constantly stealing the X selection. To find out who it is. You could compile this:
#include <stdio.h>
#include <X11/Xlib.h>
#include <X11/Xatom.h>
int main()
printf("%#lxn", XGetSelectionOwner (XOpenDisplay(0), XA_PRIMARY));
return 0;
With:
gcc that-file.c -lX11
That code is to return the window ID of the owner of the PRIMARY
X selection. Then you could use xdotool
to get the PID of the process that owns that window (assuming that Window is from a local client and that it lets the Window Manager know its PID):
ps -fp "$(xdotool getwindowpid "$(./a.out)")
If you don't have xdotool
, you can do it the hard way: you can look up that window ID in the output of xwininfo -root -all
:
xwininfo -root -all | less "+/$(./a.out)"
The window that owns the selection may not have a name, but you can look at its parent or grandparent for more clue. Once you find the ancestor that is managed by the Window manager, you can get the process ID (assuming the window is displayed by a local process) with:
xprop -id that-id _NET_WM_PID
Example:
$ xwininfo -root -wm -tree | grep -B3 "$(./a.out)"
24 children:
0x2800024 "Sun 12 May - 21:40 - zsh (2)": ("xterm" "XTerm") 1920x1059+0+19 +0+19
1 child:
0x280002f (has no name): () 1920x1059+0+0 +0+19
0x280002f owns the PRIMARY selection, whose parent is "xterm" (0x2800024 managed by the Window Manager).
$ xprop -id 0x2800024 _NET_WM_PID
_NET_WM_PID(CARDINAL) = 9707
$ ps -fp 9707
UID PID PPID C STIME TTY TIME CMD
chazelas 9707 1 0 08:50 ? 00:00:02 xterm
And that's its pid.
Once you know who owns that selection, it may become clearer what's happening.
Note: I had to change printf line in the C code to use%lu
instead of%x
as the variable there waslong unsigned int
.
– Kris
2 days ago
And so I suppose I got the wrong number there as an ID as I cannot find that ID within the xwininfo results.
– Kris
2 days ago
@Kris, sorry my bad, I had overlooked that Window IDs werelong
. It should be%lx
(see edit) asxwininfo
displays IDs in hex.
– Stéphane Chazelas
2 days ago
add a comment |
up vote
11
down vote
Possibly something is constantly stealing the X selection. To find out who it is. You could compile this:
#include <stdio.h>
#include <X11/Xlib.h>
#include <X11/Xatom.h>
int main()
printf("%#lxn", XGetSelectionOwner (XOpenDisplay(0), XA_PRIMARY));
return 0;
With:
gcc that-file.c -lX11
That code is to return the window ID of the owner of the PRIMARY
X selection. Then you could use xdotool
to get the PID of the process that owns that window (assuming that Window is from a local client and that it lets the Window Manager know its PID):
ps -fp "$(xdotool getwindowpid "$(./a.out)")
If you don't have xdotool
, you can do it the hard way: you can look up that window ID in the output of xwininfo -root -all
:
xwininfo -root -all | less "+/$(./a.out)"
The window that owns the selection may not have a name, but you can look at its parent or grandparent for more clue. Once you find the ancestor that is managed by the Window manager, you can get the process ID (assuming the window is displayed by a local process) with:
xprop -id that-id _NET_WM_PID
Example:
$ xwininfo -root -wm -tree | grep -B3 "$(./a.out)"
24 children:
0x2800024 "Sun 12 May - 21:40 - zsh (2)": ("xterm" "XTerm") 1920x1059+0+19 +0+19
1 child:
0x280002f (has no name): () 1920x1059+0+0 +0+19
0x280002f owns the PRIMARY selection, whose parent is "xterm" (0x2800024 managed by the Window Manager).
$ xprop -id 0x2800024 _NET_WM_PID
_NET_WM_PID(CARDINAL) = 9707
$ ps -fp 9707
UID PID PPID C STIME TTY TIME CMD
chazelas 9707 1 0 08:50 ? 00:00:02 xterm
And that's its pid.
Once you know who owns that selection, it may become clearer what's happening.
Note: I had to change printf line in the C code to use%lu
instead of%x
as the variable there waslong unsigned int
.
– Kris
2 days ago
And so I suppose I got the wrong number there as an ID as I cannot find that ID within the xwininfo results.
– Kris
2 days ago
@Kris, sorry my bad, I had overlooked that Window IDs werelong
. It should be%lx
(see edit) asxwininfo
displays IDs in hex.
– Stéphane Chazelas
2 days ago
add a comment |
up vote
11
down vote
up vote
11
down vote
Possibly something is constantly stealing the X selection. To find out who it is. You could compile this:
#include <stdio.h>
#include <X11/Xlib.h>
#include <X11/Xatom.h>
int main()
printf("%#lxn", XGetSelectionOwner (XOpenDisplay(0), XA_PRIMARY));
return 0;
With:
gcc that-file.c -lX11
That code is to return the window ID of the owner of the PRIMARY
X selection. Then you could use xdotool
to get the PID of the process that owns that window (assuming that Window is from a local client and that it lets the Window Manager know its PID):
ps -fp "$(xdotool getwindowpid "$(./a.out)")
If you don't have xdotool
, you can do it the hard way: you can look up that window ID in the output of xwininfo -root -all
:
xwininfo -root -all | less "+/$(./a.out)"
The window that owns the selection may not have a name, but you can look at its parent or grandparent for more clue. Once you find the ancestor that is managed by the Window manager, you can get the process ID (assuming the window is displayed by a local process) with:
xprop -id that-id _NET_WM_PID
Example:
$ xwininfo -root -wm -tree | grep -B3 "$(./a.out)"
24 children:
0x2800024 "Sun 12 May - 21:40 - zsh (2)": ("xterm" "XTerm") 1920x1059+0+19 +0+19
1 child:
0x280002f (has no name): () 1920x1059+0+0 +0+19
0x280002f owns the PRIMARY selection, whose parent is "xterm" (0x2800024 managed by the Window Manager).
$ xprop -id 0x2800024 _NET_WM_PID
_NET_WM_PID(CARDINAL) = 9707
$ ps -fp 9707
UID PID PPID C STIME TTY TIME CMD
chazelas 9707 1 0 08:50 ? 00:00:02 xterm
And that's its pid.
Once you know who owns that selection, it may become clearer what's happening.
Possibly something is constantly stealing the X selection. To find out who it is. You could compile this:
#include <stdio.h>
#include <X11/Xlib.h>
#include <X11/Xatom.h>
int main()
printf("%#lxn", XGetSelectionOwner (XOpenDisplay(0), XA_PRIMARY));
return 0;
With:
gcc that-file.c -lX11
That code is to return the window ID of the owner of the PRIMARY
X selection. Then you could use xdotool
to get the PID of the process that owns that window (assuming that Window is from a local client and that it lets the Window Manager know its PID):
ps -fp "$(xdotool getwindowpid "$(./a.out)")
If you don't have xdotool
, you can do it the hard way: you can look up that window ID in the output of xwininfo -root -all
:
xwininfo -root -all | less "+/$(./a.out)"
The window that owns the selection may not have a name, but you can look at its parent or grandparent for more clue. Once you find the ancestor that is managed by the Window manager, you can get the process ID (assuming the window is displayed by a local process) with:
xprop -id that-id _NET_WM_PID
Example:
$ xwininfo -root -wm -tree | grep -B3 "$(./a.out)"
24 children:
0x2800024 "Sun 12 May - 21:40 - zsh (2)": ("xterm" "XTerm") 1920x1059+0+19 +0+19
1 child:
0x280002f (has no name): () 1920x1059+0+0 +0+19
0x280002f owns the PRIMARY selection, whose parent is "xterm" (0x2800024 managed by the Window Manager).
$ xprop -id 0x2800024 _NET_WM_PID
_NET_WM_PID(CARDINAL) = 9707
$ ps -fp 9707
UID PID PPID C STIME TTY TIME CMD
chazelas 9707 1 0 08:50 ? 00:00:02 xterm
And that's its pid.
Once you know who owns that selection, it may become clearer what's happening.
edited 2 days ago
answered May 12 '13 at 20:45
Stéphane Chazelas
293k54550891
293k54550891
Note: I had to change printf line in the C code to use%lu
instead of%x
as the variable there waslong unsigned int
.
– Kris
2 days ago
And so I suppose I got the wrong number there as an ID as I cannot find that ID within the xwininfo results.
– Kris
2 days ago
@Kris, sorry my bad, I had overlooked that Window IDs werelong
. It should be%lx
(see edit) asxwininfo
displays IDs in hex.
– Stéphane Chazelas
2 days ago
add a comment |
Note: I had to change printf line in the C code to use%lu
instead of%x
as the variable there waslong unsigned int
.
– Kris
2 days ago
And so I suppose I got the wrong number there as an ID as I cannot find that ID within the xwininfo results.
– Kris
2 days ago
@Kris, sorry my bad, I had overlooked that Window IDs werelong
. It should be%lx
(see edit) asxwininfo
displays IDs in hex.
– Stéphane Chazelas
2 days ago
Note: I had to change printf line in the C code to use
%lu
instead of %x
as the variable there was long unsigned int
.– Kris
2 days ago
Note: I had to change printf line in the C code to use
%lu
instead of %x
as the variable there was long unsigned int
.– Kris
2 days ago
And so I suppose I got the wrong number there as an ID as I cannot find that ID within the xwininfo results.
– Kris
2 days ago
And so I suppose I got the wrong number there as an ID as I cannot find that ID within the xwininfo results.
– Kris
2 days ago
@Kris, sorry my bad, I had overlooked that Window IDs were
long
. It should be %lx
(see edit) as xwininfo
displays IDs in hex.– Stéphane Chazelas
2 days ago
@Kris, sorry my bad, I had overlooked that Window IDs were
long
. It should be %lx
(see edit) as xwininfo
displays IDs in hex.– Stéphane Chazelas
2 days ago
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f75534%2fselecting-highlighting-text-problem%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown