Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
11-22-2005, 02:40 PM
|
#1
|
|
LQ Newbie
Registered: Feb 2004
Location: South Carolina
Distribution: Slackware et. al.
Posts: 29
Rep:
|
Can't move or resize windows
I am running Slackware 10.0 with KDE 3.2. I am unable to move or resize windows (except that I can maximize or minimize a window). Any ideas as to what could be causing this?
|
|
|
|
11-22-2005, 07:50 PM
|
#2
|
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.0
Posts: 2,969
|
Just an idea:
1. Open the Control Center.
2. Select the Desktop option.
3. Select the Window Behavior option.
4. Select the Defaults button.
5. Select the Apply button.
Hopefully that helps?
|
|
|
|
11-22-2005, 08:07 PM
|
#3
|
|
LQ Newbie
Registered: Feb 2004
Location: South Carolina
Distribution: Slackware et. al.
Posts: 29
Original Poster
Rep:
|
Tried your suggestion Woodsman. It had no effect. Funny thing is I get the move and resize arrows (cursor), but the window does not respond.
|
|
|
|
11-22-2005, 08:31 PM
|
#4
|
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.0
Posts: 2,969
|
Just another quick hunch, instead of selecting the Window Behavior option, select the Window-Specific Settings option. This is where you save and store window specific options such as window size and placement. If you have anything listed then explore the options to see if that might be the cause.
You create these settings from the GUI by right-clicking on the title bar of a window, then select the Advanced pop-up menu option, then selecting Special Window Settings.
Last edited by Woodsman; 11-22-2005 at 08:48 PM.
|
|
|
|
11-23-2005, 05:49 AM
|
#5
|
|
LQ Newbie
Registered: Feb 2004
Location: South Carolina
Distribution: Slackware et. al.
Posts: 29
Original Poster
Rep:
|
Unfortunately, I don't have anything listed in the window-specific settings. Thanks for the suggestion though.
|
|
|
|
11-23-2005, 10:56 AM
|
#6
|
|
Member
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 13.37, 12.2
Posts: 310
Rep:
|
Have you logged out and back in? I have occasionally had similar symptoms after leaving myself logged in for a long time. Logging out and logging back in fixed it for me.
|
|
|
|
11-23-2005, 02:40 PM
|
#7
|
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.0
Posts: 2,969
|
Quote:
|
Have you logged out and back in?
|
I've seen this help with oddball KDE problems too. Occasionally the DCOP thingy stops working and the only way to resolve that problem is to log out and log in. If I started X/KDE from KDM then that means ending the session and logging back in from KDM. If I started X/KDE from startx then that means ending the X session and restarting X/KDE with startx. With the latter I do not need to actually log out and log in.
Regarding the original problem, I have no more suggestions.  I wish I did!
|
|
|
|
11-23-2005, 03:24 PM
|
#8
|
|
Moderator
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,916
|
Another common (more common than one might assume)
problem is that a "special key" (e.g. Alt, Esc, Ctrl) is stuck,
and alters the mouses behaviour ....
Cheers,
Tink
|
|
|
|
11-23-2005, 08:12 PM
|
#9
|
|
LQ Newbie
Registered: Feb 2004
Location: South Carolina
Distribution: Slackware et. al.
Posts: 29
Original Poster
Rep:
|
statguy found the right answer for me. It had been a long time since I logged out of KDE. When I exited and restarted X-Windows, the problems went away. Thank you, statguy and all the others who offered help.
|
|
|
|
06-04-2010, 01:25 AM
|
#10
|
|
LQ Newbie
Registered: Jun 2010
Posts: 1
Rep:
|
Wayout without logging out the session
Usually for my case closing the session disrupts lots of ongoing work. I have found a way out of this which does not require killing the session. Essentially we need to restart the window manager.
First find out the "kwin" process id
~21> ps -aux | grep `whoami` | grep kwin
madhurk 20669 0.1 0.0 109432 14912 ? S 11:46 0:00 kwin
madhurk 21749 0.0 0.0 3804 580 pts/455 S+ 11:52 0:00 grep kwin
Remember to copy the "kwin" text. Kill the currently running kwin job.
~22> kill -9 21749
Click open the "Run command" action and type paste the "kwin". Run this command and viola everything would be back to normal.
|
|
|
|
01-24-2011, 02:49 AM
|
#11
|
|
LQ Newbie
Registered: Jan 2011
Posts: 1
Rep:
|
Thank physiologoius for your big help, I resolved this problem.
Quote:
Originally Posted by physiologoius
Usually for my case closing the session disrupts lots of ongoing work. I have found a way out of this which does not require killing the session. Essentially we need to restart the window manager.
First find out the "kwin" process id
~21> ps -aux | grep `whoami` | grep kwin
madhurk 20669 0.1 0.0 109432 14912 ? S 11:46 0:00 kwin
madhurk 21749 0.0 0.0 3804 580 pts/455 S+ 11:52 0:00 grep kwin
Remember to copy the "kwin" text. Kill the currently running kwin job.
~22> kill -9 21749
Click open the "Run command" action and type paste the "kwin". Run this command and viola everything would be back to normal.
|
|
|
|
|
04-04-2013, 04:37 PM
|
#12
|
|
LQ Newbie
Registered: Apr 2013
Posts: 1
Rep: 
|
Thanks physiologoius !!!!
I'm using KDE 3.3 and it worked!!! I registered into linuxquestions just to thank you.
Quote:
Originally Posted by physiologoius
Usually for my case closing the session disrupts lots of ongoing work. I have found a way out of this which does not require killing the session. Essentially we need to restart the window manager.
First find out the "kwin" process id
~21> ps -aux | grep `whoami` | grep kwin
madhurk 20669 0.1 0.0 109432 14912 ? S 11:46 0:00 kwin
madhurk 21749 0.0 0.0 3804 580 pts/455 S+ 11:52 0:00 grep kwin
Remember to copy the "kwin" text. Kill the currently running kwin job.
~22> kill -9 21749
Click open the "Run command" action and type paste the "kwin". Run this command and viola everything would be back to normal.
|
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:51 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|