Bug 52500 - Impossible to move or resize windows using mouse
Summary: Impossible to move or resize windows using mouse
Status: CLOSED DUPLICATE of bug 54491
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: sawfish (Show other bugs)
(Show other bugs)
Version: roswell
Hardware: i686 Linux
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-24 13:14 UTC by Tor Andre Myrvoll
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-24 21:24:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
The .xsession-errors file (21.12 KB, text/plain)
2001-08-24 15:21 UTC, Tor Andre Myrvoll
no flags Details

Description Tor Andre Myrvoll 2001-08-24 13:14:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010809

Description of problem:
When trying to move or resize windows using the mouse a continuous series
of beeps comes from the speaker and nothing else happens. Also, the mouse
does not "stick" to the spot I grab.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Log in (I use GDM to start a gnome session using the sawfisk WM)
2.Open a window
3.Try to move it

Additional info:

If I log in as root using the GDM nothing of the sort happens. Also, when I
tried removing all my .gnome* .sawfish and .gtkrc files (I suspected they
might be corrupted), I could move my windows, but I couldn't resize them. 

Possibly related item: When I try to change the sawfish appearance by
choosing the menu item from the gnome menu or by clicking the middle button
on the desktop, the window comes up, but just hangs. It can't even be
removed. However, choosing sawfish appearance from the Gnome configuration
tool works fine.

Comment 1 Havoc Pennington 2001-08-24 14:54:28 UTC
Sawfish is no doubt spewing Lisp errors to ~/.xsession-errors - what are those

Comment 2 Tor Andre Myrvoll 2001-08-24 15:21:51 UTC
Created attachment 29374 [details]
The .xsession-errors file

Comment 3 Havoc Pennington 2001-08-24 15:46:40 UTC
OK, something is really screwed - the X server is not providing the "fixed" font.
Several apps other than sawfish seem to be complaining about that.

Does "xlsfonts | grep fixed" show the line "fixed"?

Comment 4 Glen Foster 2001-08-24 15:54:15 UTC
We (Red Hat) should try to fix this before next release.

Comment 5 Tor Andre Myrvoll 2001-08-24 16:39:23 UTC
The fixed font error messages may have occured when I tried to run
/usr/X11R6/bin/XF86_Mach64 this morning (my X dies every night due to a well
known Mach-64+SMP+XFree86 bug, so I was starting to get a bit desperate).

Anyway, when I do the "xlsfonts | grep fixed" I get two lines containing the
word fixed.

Comment 6 Havoc Pennington 2001-08-24 16:42:50 UTC
.xsession-errors should be restarted (cleared out) each time you log in.

What are the two lines with "fixed"? There's no line with just plain "fixed"?

(My test machine has 1009 lines with "fixed")

Comment 7 Havoc Pennington 2001-08-24 18:03:54 UTC
It looks like this may be a duplicate of

Comment 8 Glen Foster 2001-08-24 19:08:17 UTC
Testing -- reporter says they can't post an update to this bug.

Comment 9 Tor Andre Myrvoll 2001-08-24 19:16:46 UTC
I was probably unclear: When running "xlsfonts | grep fixed
" I got two lines containg just the word fixed, but there were 510 lines all in all.

Comment 10 Havoc Pennington 2001-08-24 21:24:48 UTC
does "xlsfonts -fn -*-fixed-medium-r-normal--14-*-*-*-*-*-*-*" list any fonts?
This the Sawfish default font with a recent patch.
If it doesn't list any fonts, that would explain the problem, but I'm not sure
why it wouldn't be listing any fonts.

Comment 11 Havoc Pennington 2001-10-10 04:09:15 UTC

*** This bug has been marked as a duplicate of 54491 ***

Note You need to log in before you can comment on or make changes to this bug.