wmaker: woody wmaker doesn't pass left click to apps
Hi, sorry about the delay, but I didn't notice this bug until yesterday. For some reason I didn't receive it the first time. [sent to debian-x just in case someone here has seen anything similar] Debian Bug Tracking System [EMAIL PROTECTED] writes: Package: wmaker Version: 0.62.1-0.1 ^^^ Please try with 0.62.1-2 on woody. (not that I expect this to be fixed by random uploads, but the bug is wacky enough to admit the possibility) After upgrading several packages to the latest woody versions, several things broke in X: - Left clicks behaved erratically - Backspace stopped working - The 'Windows' key no longer functioned as a usable meta key I'm not sure whether the keyboard problems are wmaker-related; if I decide it's a likely cause of those problems, I'll file a separate bug. The mouse behavior, OTOH, resolved itself into a consistent pattern after a little experimentation: WindowMaker itself received left clicks, but no How did you test this? (I guess the question is "is left-clicking mapped to some non-default value?") other application received them. Middle clicks are also behaving oddly, but I haven't been able to establish a verifiable pattern. Right clicks behave normally. I need a copy of your ~/GNUstep/Defaults/WindowMaker file then. I don't think I can reproduce this without it. An additional bit of oddness is that xmms, which I have configured to launch at WindowMaker startup, vanishes as soon as I double-left-click anywhere on the screen. It continues to run, but has no visible presence in any workspace. To test this hypothesis, I switched over to fvwm, and all mouse functions behave normally. The mouse problems exist only under wmaker. Uh? Ok, it's got to be some funky mapping on your G/D/W file. My apologies again, Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#76893: wmaker: woody wmaker doesn't pass left click to apps
On Sat, Nov 25, 2000 at 11:46:33AM +0100, Marcelo E. Magallon wrote:
sorry about the delay, but I didn't notice this bug until yesterday.
No biggie.
Please try with 0.62.1-2 on woody. (not that I expect this to be fixed
by random uploads, but the bug is wacky enough to admit the
possibility)
I actually did manage to fix everything with random updates. At this point,
everything is working correctly, but I don't recall exactly how I fixed it.
I'll provide additional information, though, just in case it causes someone
to recognize any suspicious patterns.
After upgrading several packages to the latest woody versions,
several things broke in X:
I suspect that a (if not the) major cause of my problems was that the system
in question was originally slink-with-selected-potato-packages, then I
started adding in selected woody packages without having brought it up to
full potato, so it was a mix of a slink base with a few old potato versions
and a lot of newer woody packages installed on top of it. IIRC, everything
started working again when I upgraded all the slink and old potato code to
current potato.
- Left clicks behaved erratically - Backspace stopped working - The
'Windows' key no longer functioned as a usable meta key
I'm not sure whether the keyboard problems are wmaker-related; if I
decide it's a likely cause of those problems, I'll file a separate
bug.
The mouse behavior, OTOH, resolved itself into a consistent pattern
after a little experimentation: WindowMaker itself received left
clicks, but no
How did you test this? (I guess the question is "is left-clicking
mapped to some non-default value?")
I didn't test it systematically. Left-clicking initially appeared to be
completely dead, then I went to change the volume setting on my sound card
and, out of habit, tried to do so with the mouse. Even though I clicked
within wmmixer's volume control and dragged up (which normally is received by
wmmixer and increases the volume), wmaker behaved as if I had clicked on a
non-application-controlled area of the dockicon and went into 'drag dockapp
to a new location' mode. I then played with it a bit more and saw a
consistent pattern that anything application-controlled (GUI windows,
buttons, etc.) ignored left-clicks, while any of wmaker's decorations (dock,
titlebars, resizebars, etc.) reacted normally to them.
other application received them. Middle clicks are also behaving
oddly, but I haven't been able to establish a verifiable pattern.
Right clicks behave normally.
I need a copy of your ~/GNUstep/Defaults/WindowMaker file then. I
don't think I can reproduce this without it.
I'll attach a copy, although I don't expect it to contain anything
problematic.
--
"Two words: Windows survives." - Craig Mundie, Microsoft senior strategist
"So does syphillis. Good thing we have penicillin." - Matthew Alton
Geek Code 3.1: GCS d? s+: a- C++ UL++$ P+ L+++ E- W--(++) N+ o+
!K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r++ y+
{
WorkspaceSpecificBack = ((), (), ());
NoWindowOverIcons = YES;
NoWindowOverDock = YES;
IconPosition = blv;
CirculateRaise = NO;
WindowPlaceOrigin = (64, 16);
HelpBalloons = NO;
Superfluous = YES;
WindowShortcut2Key = None;
WindowShortcut3Key = None;
DoubleClickTime = 245;
DisableBlinking = NO;
IconificationStyle = Random;
DontConfirmKill = Yes;
AClipColor = "#47";
IClipColor = "#10";
SClipColor = red;
DisableSound = Yes;
MiniwindowTitleBalloons = Yes;
SmoothWorkspaceBack = Yes;
NewStyle = YES;
AppIconBalloons = No;
DontLinkWorkspaces = No;
FocusMode = SemiAuto;
WindowPlacement = Smart;
WindowShortcut1Key = None;
DisplayFont = "-bh-lucida-medium-r-normal-*-12-*-*-*-p-*-iso8859-1";
LargeDisplayFont = "-adobe-helvetica-medium-r-normal-*-*-240-*-*-p-*-iso8859-1";
ClipTitleFont = "-bh-lucida-medium-r-normal-*-10-*-*-*-p-*-iso8859-1";
WindowTitleFont = "-bh-lucida-medium-r-normal-*-12-*-*-*-p-*-iso8859-1";
MenuTitleFont = "-bh-lucida-bold-r-normal-*-12-*-*-*-p-*-iso8859-1";
MenuTextFont = "-bh-lucida-medium-r-normal-*-12-*-*-*-p-*-iso8859-1";
IconTitleFont = "-bh-lucida-medium-r-normal-*-10-*-*-*-p-*-iso8859-1";
TitleJustify = left;
HighlightColor = "#66";
HighlightTextColor = "#cdd8e6";
ClipTitleColor = "#646f99";
CClipTitleColor = "#cdcdcd";
FTitleColor = "#020202";
PTitleColor = "#66";
UTitleColor = "#96949b";
FTitleBack = (
tvgradient,
"../Pixmaps/Dragon-Skin-blue.png",
100,
"#ff",
"#00"
);
PTitleBack = (
tvgradient,
"../Pixmaps/Dragon-Skin-white.png",
100,
"#ff",
"#00"
);
UTitleBack = (
tvgradient,
"../Pixmaps/Dragon-Skin-grey.png",
100,
"#ff",
"#00"
);
ResizebarBack = (
tvgradient,
"../Pixmaps/Dragon-Skin-grey.png",
100,
"#ff",
"#00"
);
MenuTitleColor =
[pelux@tiscalinet.it: Xfree prob.]
- Forwarded message from pelux [EMAIL PROTECTED] - From: "pelux" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Xfree prob. Date: Sat, 25 Nov 2000 04:46:29 -0600 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] (added by twingo.tiscalinet.it) Importance: Normal X-Mailer: VisualMail 3.0 ( http://www.minter.com.ar/visualmail ) When i try to install (with apt-get install) the xfree 4.01 -07 System i get errors when it "configure" packages before installing it... here it the script of my intall! I hope it could help you :) by3 Ste -- TiscaliNet, libero accesso ad Internet. http://www.tiscalinet.it - End forwarded message - -- G. Branden Robinson|You live and learn. Debian GNU/Linux |Or you don't live long. [EMAIL PROTECTED] |-- Robert Heinlein http://deadbeast.net/~branden/ | PGP signature
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
Please don't send mail directly to Branden. For the DGA stuff, X4 uses DGA V2, X3 uses DGA V1, that is probably why you are having this problem. Zephaniah E. Hull. -- PGP EA5198D1-Zephaniah E. Hull [EMAIL PROTECTED]-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Here's your cable. We made it fifty feet long, just in case. In case what, in case tectonic movement makes the serial ports farther apart? -- Carl Jacobs on ASR. PGP signature
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
On Sat, Nov 25, 2000 at 02:47:39PM -0500, Zephaniah E. Hull wrote: Please don't send mail directly to Branden. For the DGA stuff, X4 uses DGA V2, X3 uses DGA V1, that is probably why you are having this problem. Hum, then why would it work on my work machine? I asked about this on #[EMAIL PROTECTED] yesteraday. People who sucessfully use xawtv and xfree 4.0 also see dga related lines in /var/log/XFree86.0.log (mine doesnt mention dga). Another person mentioned that he had to explicitly enable dga because its off by default, but I am unable to find any docs on how to do that. from /usr/doc/xawtv/README.xfree4: XFree86 4.0 tips tricks = DGA problems Release 4.0 has DGA turned off by default. You'll have turn it on in XF86Config, otherwise v4l-conf will not work correctly. It should work for most cards this way, althrouth some drivers don't handle DGA correctly in 4.0 (that's why it is off...) But it doesnt mention how to enable dga either. Thanks, Norbert PGP signature
Re: Prepackaged indirected X terminal
Have you tried one of $ X -query otherhost $ X -broadcast $ X -indirect otherhost or $ man Xserver | sed -n -e '288,340p' XDMCP OPTIONS X servers that support XDMCP have the following options. See the X Display Manager Control Protocol specification for more information. -query host-name Enable XDMCP and send Query packets to the speci fied host. -broadcast Enable XDMCP and broadcast BroadcastQuery packets to the network. The first responding display man ager will be chosen for the session. -indirect host-name Enable XDMCP and send IndirectQuery packets to the specified host. -port port-num Use an alternate port number for XDMCP packets. Must be specified before any -query, -broadcast or -indirect options. -class display-class XDMCP has an additional display qualifier used in resource lookup for display-specific options. This option sets that value, by default it is "MIT-Unspecified" (not a very useful value). -cookie xdm-auth-bits When testing XDM-AUTHENTICATION-1, a private key is shared between the server and the manager. This option sets the value of that private data (not that it is very private, being on the command line!). X Version 11 Release 6.3 5 XSERVER(1) XSERVER(1) -displayID display-id Yet another XDMCP specific value, this one allows the display manager to identify each display so that it can locate the shared key. $ Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- From: Alexander Perry [EMAIL PROTECTED] Subject: Prepackaged indirected X terminal Date: Fri, 24 Nov 2000 13:30:46 -0800 I know how to have xdm use the indirect and chooser features to work with external X terminals and determine where they go. Works great, but it leaves me with a simple question ... Is there a clean way to specify that the locally managed display should be indirected (like a terminal would be) for the option of attaching it elsewhere instead of locally ? I can do it by disabling it in xdm and putting a line in the inittab, but the authentication stuff is a pain and I'm assuming there must be a better way of setting it all up. Separately to that, the X traffic of a remoted display is not normally encrypted. Sometimes that is important. Is there a clean way to have that local X display make its connection to the remote machine using (for example) ssh -X ? I know how to do it manually, with some extra scripting, but I was hoping that there was something packaged for this. Alex. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
But it doesnt mention how to enable dga either. Are you loading extmod? -- Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
On Sun, Nov 26, 2000 at 01:10:54AM +0100, Marcelo E. Magallon wrote: But it doesnt mention how to enable dga either. Are you loading extmod? Yes, my original message mentions that, and contains my XF86Config, I'm not sure if it made it to the list though as I'm not on it. PGP signature
100% loss 3D Speed
Hi. (Sorry for my diction, but I´ll give my very best). In case I´m on the wrong place here, I apologize, but I do not have a idea, where else to ask. I was very happy with the 4.0.1-5 Version, because I had horrendous GL performance with this build and my Matrox G400. In comparsion with the builds 6,7,8 there is perfomance loss of about 100%. (I know, gears is not really a benchmarking program, but it works fine for me.) ;) Anyway I´d like to ask, where this difference comes from. I matters for me, seeing the gears rotate with 850FPS, or with maximal 400FPS. And I´d like to know, if it is possible to increase the speed performance again? - Or am I only in luck with a ´broken´ package? -- Regards, GR | GnuPG-key avaible Can't forget you, Muck. | or mail -s 'get gpg-key' "Mach kein TOFU (Text oben Fullqoute unten). ;)" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Woody + X4 debs + DGA = :|
Allright, I've been trying to take this up with matroxusers, matrox' technical support people, etc, and I still haven't gotten a straight answer. Matrox G400 32mb DH card on an up-to-date woody installation, and the most recent 2.4.0-test kernel. The problem described below has appeared for as long as I can remember. (Relatively early in Branden's phase-2 debs) DGA display does not want to work. Whenever a program attempts to perform a dga operation, the video mode changes, but only a blank screen is displayed. Everything else (sound, input etc) seems to go on, but there's no display whatsoever. Once the program stops using DGA (or successfully terminates, whatever comes first), the display becomes usable again as one might expect. No errors are reported, by the server, nor on the standard output of the program in question. I've attached my XF86Config-4 file, but I get the impression this isn't going to help much, and I'll tell you why. I _can_ get DGA working if I switch to Matrox's now-over-2-month-old driver. The only problem with this solution is that it's compiled for DRM1, so using it will kill off my currently working (and very well i should add) GL. I also haven't been able to extract from matrox any information on when they plan to release updated drivers. I'm not sure of any other information to add, but if there's something you'd like, please go ahead and ask. I also cannot confirm whether or not these symptons exhibit themselves in the current XFree4 CVS. (I'm on a 28.8 modem, and my access to the local T1 is sporadic). Any comment with respect to that would also be greatly appreciated. -- Jeremy Nickurak -= [EMAIL PROTECTED] =- "Time is infinite. You are finite, Zathras is finite. This... this is wrong tool. Very bad. Never use this tool." - Zathras, Babylon 5 # XF86Config-4 (XFree86 server configuration file) generated by Dexter, the # Debian X Configuration tool. # # Edit this file with caution, and see the XF86Config manual page. # (Type "man XF86Config" at the shell prompt.) Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "ServerFlags" EndSection Section "Module" Load"ddc" Load"GLcore" Load"dbe" Load"dri" Load"extmod" Load"glx" Load"pex5" Load"record" Load"xie" Load"bitmap" Load"freetype" Load"speedo" Load"type1" Load"vbe" Load"int10" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "CorePointer" Option "Protocol" "ImPS/2" Option "Device""/dev/input/mice" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "Generic Graphics Device" Driver "mga" EndSection Section "Monitor" Identifier "Generic Monitor" HorizSync 30-85 VertRefresh 50-130 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Generic Graphics Device" Monitor "Generic Monitor" DefaultDepth16 SubSection "Display" Depth 1 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display"
Re: Prepackaged indirected X terminal
From: Karl Hammar [EMAIL PROTECTED] $ man Xserver | sed -n -e '288,340p' Yes, I know. From: Alexander Perry [EMAIL PROTECTED] [...] I can do it by disabling it in xdm and putting a line in the inittab, but the authentication stuff is a pain and I'm assuming there must be a better way of setting it all up. xdm (for example) supports - local: the server is local and the management is local - foreign: the server is remote and we need to kick it - xdmcp: the server is remote and it will come to us I was wondering whether there was a way to request - remote: the server is local and management is remote I'd like xdm to deal with monitoring and restarting the server, yet not try to take control of that display. Alex. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xmms is crashing my XFree4.0.1...
I have a voodoo3, and I ran into the same problem. I think the Xserver segfault occured when xmms was changing songs. I tracked the problem to the "glx" module. Couldn't get much farther because my attempts at debugging X failed miseribly. Igor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[nveber@primusolutions.net: DGA problems in 4.0.1]
- Forwarded message from Norbert Veber [EMAIL PROTECTED] - From: Norbert Veber [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: DGA problems in 4.0.1 Date: Sat, 25 Nov 2000 02:04:04 -0500 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i Hi, I have a few programs that use DGA extentions such as xawtv, and vmware, but they have stopped working as of 4.x. For example if I try to run xawtv, I get: This is xawtv-3.24, running on Linux/i686 (2.2.17) visual: id=0x22 class=4 (TrueColor), depth=16 visual: id=0x23 class=4 (TrueColor), depth=16 x11: 1152x864, 16 bit/pixel, 0 byte/scanline WARNING: No DGA support available for this display. WARNING: couldn't find framebuffer base address, try manual configuration (v4l-conf -a addr) WARNING: No DGA support available for this display. WARNING: couldn't find framebuffer base address, try manual configuration (v4l-conf -a addr) v4l: bttv version 0.7.46 v4l: 1152x864, 16 bit/pixel, 2304 byte/scanline wmhooks: gnome no infrared remote support available ioctl VIDIOCCAPTURE: Invalid argument ioctl VIDIOCCAPTURE: Invalid argument The end result is that I get audio-only, and no picture from my tv tuner. Vmware just pops up a box saying DGA is not available, and full screen mode wont work. My video card is a Tseng Labs ET6000 with 2mb video ram. The strange thing is that it works fine on my debian machine at work. I am pretty much stumped. The XF86Config-4 loads the extmod module which is supposed to contain DGA support, I'm not sure where else to look. Attached is my startx output, as well as my XF86Config-4 file. Thanks for your time. This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.0.1e / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 6 November 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.18pre15 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.1.log, Time: Sat Nov 25 01:31:49 2000 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Graphics Device (**) |--Input Device Generic Keyboard (**) XKB: rules: xfree86 (**) XKB: model: pc104 (**) XKB: layout: us (**) |--Input Device Generic Mouse (**) FontPath set to unix/:7100,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/misc/:unscaled,/usr/X11R6/lib/X11/fonts/cyrillic/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/cyrillic/,/usr/X11R6/lib/X11/fonts/freefont/,/usr/X11R6/lib/X11/fonts/sharefont/ (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 8 (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.0.1e, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.0.1e, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.0.1e, module version = 0.1.0 (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (--) PCI: (0:8:0) BrookTree unknown chipset (0x036e) rev 2, Mem @ 0xe7002000/12 (--) PCI:*(0:9:0) Tseng Labs ET6000/6100 rev 48, Mem @ 0xe400/24, I/O @ 0xe400/8 (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor=The XFree86 Project compiled for 4.0.1e, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor=The XFree86 Project compiled for 4.0.1e, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor=The XFree86 Project compiled for 4.0.1e, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor=The XFree86 Project compiled for 4.0.1e, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor=The XFree86 Project compiled for 4.0.1e, module version = 1.0.0
wmaker: woody wmaker doesn't pass left click to apps
Hi, sorry about the delay, but I didn't notice this bug until yesterday. For some reason I didn't receive it the first time. [sent to debian-x just in case someone here has seen anything similar] Debian Bug Tracking System [EMAIL PROTECTED] writes: Package: wmaker Version: 0.62.1-0.1 ^^^ Please try with 0.62.1-2 on woody. (not that I expect this to be fixed by random uploads, but the bug is wacky enough to admit the possibility) After upgrading several packages to the latest woody versions, several things broke in X: - Left clicks behaved erratically - Backspace stopped working - The 'Windows' key no longer functioned as a usable meta key I'm not sure whether the keyboard problems are wmaker-related; if I decide it's a likely cause of those problems, I'll file a separate bug. The mouse behavior, OTOH, resolved itself into a consistent pattern after a little experimentation: WindowMaker itself received left clicks, but no How did you test this? (I guess the question is is left-clicking mapped to some non-default value?) other application received them. Middle clicks are also behaving oddly, but I haven't been able to establish a verifiable pattern. Right clicks behave normally. I need a copy of your ~/GNUstep/Defaults/WindowMaker file then. I don't think I can reproduce this without it. An additional bit of oddness is that xmms, which I have configured to launch at WindowMaker startup, vanishes as soon as I double-left-click anywhere on the screen. It continues to run, but has no visible presence in any workspace. To test this hypothesis, I switched over to fvwm, and all mouse functions behave normally. The mouse problems exist only under wmaker. Uh? Ok, it's got to be some funky mapping on your G/D/W file. My apologies again, Marcelo
[pelux@tiscalinet.it: Xfree prob.]
- Forwarded message from pelux [EMAIL PROTECTED] - From: pelux [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Xfree prob. Date: Sat, 25 Nov 2000 04:46:29 -0600 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] (added by twingo.tiscalinet.it) Importance: Normal X-Mailer: VisualMail 3.0 ( http://www.minter.com.ar/visualmail ) When i try to install (with apt-get install) the xfree 4.01 -07 System i get errors when it configure packages before installing it... here it the script of my intall! I hope it could help you :) by3 Ste -- TiscaliNet, libero accesso ad Internet. http://www.tiscalinet.it - End forwarded message - -- G. Branden Robinson|You live and learn. Debian GNU/Linux |Or you don't live long. [EMAIL PROTECTED] |-- Robert Heinlein http://deadbeast.net/~branden/ | pgpsfGLggkfbT.pgp Description: PGP signature
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
Please don't send mail directly to Branden. For the DGA stuff, X4 uses DGA V2, X3 uses DGA V1, that is probably why you are having this problem. Zephaniah E. Hull. -- PGP EA5198D1-Zephaniah E. Hull [EMAIL PROTECTED]-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Here's your cable. We made it fifty feet long, just in case. In case what, in case tectonic movement makes the serial ports farther apart? -- Carl Jacobs on ASR. pgpx4IQpY35X2.pgp Description: PGP signature
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
On Sat, Nov 25, 2000 at 02:47:39PM -0500, Zephaniah E. Hull wrote: Please don't send mail directly to Branden. For the DGA stuff, X4 uses DGA V2, X3 uses DGA V1, that is probably why you are having this problem. Hum, then why would it work on my work machine? I asked about this on [EMAIL PROTECTED] yesteraday. People who sucessfully use xawtv and xfree 4.0 also see dga related lines in /var/log/XFree86.0.log (mine doesnt mention dga). Another person mentioned that he had to explicitly enable dga because its off by default, but I am unable to find any docs on how to do that. from /usr/doc/xawtv/README.xfree4: XFree86 4.0 tips tricks = DGA problems Release 4.0 has DGA turned off by default. You'll have turn it on in XF86Config, otherwise v4l-conf will not work correctly. It should work for most cards this way, althrouth some drivers don't handle DGA correctly in 4.0 (that's why it is off...) But it doesnt mention how to enable dga either. Thanks, Norbert pgpyvrhChod1R.pgp Description: PGP signature
Re: Prepackaged indirected X terminal
Have you tried one of $ X -query otherhost $ X -broadcast $ X -indirect otherhost or $ man Xserver | sed -n -e '288,340p' XDMCP OPTIONS X servers that support XDMCP have the following options. See the X Display Manager Control Protocol specification for more information. -query host-name Enable XDMCP and send Query packets to the speci fied host. -broadcast Enable XDMCP and broadcast BroadcastQuery packets to the network. The first responding display man ager will be chosen for the session. -indirect host-name Enable XDMCP and send IndirectQuery packets to the specified host. -port port-num Use an alternate port number for XDMCP packets. Must be specified before any -query, -broadcast or -indirect options. -class display-class XDMCP has an additional display qualifier used in resource lookup for display-specific options. This option sets that value, by default it is MIT-Unspecified (not a very useful value). -cookie xdm-auth-bits When testing XDM-AUTHENTICATION-1, a private key is shared between the server and the manager. This option sets the value of that private data (not that it is very private, being on the command line!). X Version 11 Release 6.3 5 XSERVER(1) XSERVER(1) -displayID display-id Yet another XDMCP specific value, this one allows the display manager to identify each display so that it can locate the shared key. $ Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- From: Alexander Perry [EMAIL PROTECTED] Subject: Prepackaged indirected X terminal Date: Fri, 24 Nov 2000 13:30:46 -0800 I know how to have xdm use the indirect and chooser features to work with external X terminals and determine where they go. Works great, but it leaves me with a simple question ... Is there a clean way to specify that the locally managed display should be indirected (like a terminal would be) for the option of attaching it elsewhere instead of locally ? I can do it by disabling it in xdm and putting a line in the inittab, but the authentication stuff is a pain and I'm assuming there must be a better way of setting it all up. Separately to that, the X traffic of a remoted display is not normally encrypted. Sometimes that is important. Is there a clean way to have that local X display make its connection to the remote machine using (for example) ssh -X ? I know how to do it manually, with some extra scripting, but I was hoping that there was something packaged for this. Alex. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
But it doesnt mention how to enable dga either. Are you loading extmod? -- Marcelo
Re: [nveber@primusolutions.net: DGA problems in 4.0.1]
On Sun, Nov 26, 2000 at 01:10:54AM +0100, Marcelo E. Magallon wrote: But it doesnt mention how to enable dga either. Are you loading extmod? Yes, my original message mentions that, and contains my XF86Config, I'm not sure if it made it to the list though as I'm not on it. pgpsjDYl1bGfe.pgp Description: PGP signature
Re: 100% loss 3D Speed
Sorry, I forget to say, that of course DRI is/was working without errors. The log says: (...) (0): [drm] installed DRM signal handler (0): [DRI] installation complete (II) MGA(0): direct rendering enabled (...) in every 4.0.1-[1-8]. :) -- Regards, GR | GnuPG-key avaible Can't forget you, Muck. | or mail -s 'get gpg-key' Mach kein TOFU (Text oben Fullqoute unten). ;)
Woody + X4 debs + DGA = :|
Allright, I've been trying to take this up with matroxusers, matrox' technical support people, etc, and I still haven't gotten a straight answer. Matrox G400 32mb DH card on an up-to-date woody installation, and the most recent 2.4.0-test kernel. The problem described below has appeared for as long as I can remember. (Relatively early in Branden's phase-2 debs) DGA display does not want to work. Whenever a program attempts to perform a dga operation, the video mode changes, but only a blank screen is displayed. Everything else (sound, input etc) seems to go on, but there's no display whatsoever. Once the program stops using DGA (or successfully terminates, whatever comes first), the display becomes usable again as one might expect. No errors are reported, by the server, nor on the standard output of the program in question. I've attached my XF86Config-4 file, but I get the impression this isn't going to help much, and I'll tell you why. I _can_ get DGA working if I switch to Matrox's now-over-2-month-old driver. The only problem with this solution is that it's compiled for DRM1, so using it will kill off my currently working (and very well i should add) GL. I also haven't been able to extract from matrox any information on when they plan to release updated drivers. I'm not sure of any other information to add, but if there's something you'd like, please go ahead and ask. I also cannot confirm whether or not these symptons exhibit themselves in the current XFree4 CVS. (I'm on a 28.8 modem, and my access to the local T1 is sporadic). Any comment with respect to that would also be greatly appreciated. -- Jeremy Nickurak -= [EMAIL PROTECTED] =- Time is infinite. You are finite, Zathras is finite. This... this is wrong tool. Very bad. Never use this tool. - Zathras, Babylon 5 # XF86Config-4 (XFree86 server configuration file) generated by Dexter, the # Debian X Configuration tool. # # Edit this file with caution, and see the XF86Config manual page. # (Type man XF86Config at the shell prompt.) Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section ServerFlags EndSection Section Module Loadddc LoadGLcore Loaddbe Loaddri Loadextmod Loadglx Loadpex5 Loadrecord Loadxie Loadbitmap Loadfreetype Loadspeedo Loadtype1 Loadvbe Loadint10 EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option CorePointer Option Protocol ImPS/2 Option Device/dev/input/mice Option Emulate3Buttons true EndSection Section Device Identifier Generic Graphics Device Driver mga EndSection Section Monitor Identifier Generic Monitor HorizSync 30-85 VertRefresh 50-130 Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Graphics Device Monitor Generic Monitor DefaultDepth16 SubSection Display Depth 1 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier
