Re: Scary message on new installations
(I think that a crosspost to -boot is deserved here) Quoting Frans Pop ([EMAIL PROTECTED]): > On Tuesday 20 June 2006 14:15, Frans Pop wrote: > > Currently X shows a very scary message that upgrades may go wrong > > (template: x11-common/upgrade_issues) on new installations. > > Note that Joey Hess filed this as http://bugs.debian.org/372077 a while > back. We are currently considering upgrading that to RC as we feel we > cannot release D-I Beta3 wile this note is still being displayed for new > installations. > > A reaction would be appreciated. David indeed reacted to a very similar message I posted (see below for my message and answers). My understanding is that David doesn't actually know how to handle this properly to be sure about warning when users upgrade (which seems important). I agree that this should be RC in D-I point of view. We certainly cannot ship with that message displayed on every default install. (personal note: too bad that I'm actually too busy at work and home to meet David who's currently in Paris.:-|) Date: Sun, 11 Jun 2006 21:49:04 +0200 From: Christian Perrier <[EMAIL PROTECTED]> To: debian-x@lists.debian.org Subject: Annoying warning note in fresh installs I was today testing the fresh install of Etch with the desktop task (D-I related work) and I have been very surprised to see the warning note about "possible problems during the major upgrade". I seem to remember reading Steve Langasek (this was actually Joey Hess) mentioning this, but this is something that definitely should go away, at least on fresh installs..:-) David Nusinow's answer: Right, I don't like it but I don't have a clean fix for it yet. The reason being that x11-common didn't exist in sarge so I can't simply check for an upgrade. Ideally I would look for xserver-common being on the system and put the note up in that case, but that package should be removed prior to x11-common's preinst being run due to the conflicts line. Maybe just checking for libx11 would get around it. Alternately, I think joeyh suggested looking for a running X server for the fix (that may be for a different bug though) but I don't think that's an optimal solution for this problem. Fundamentally, I need to check to see exactly what's in the sarge X packages to find out what we could look for. Joey Hess contribution later: If you don't mind depending on people upgrading with apt (rather than using dpkg directly), you could do the check in the config script, which will run before anything is removed in a dist-upgrade. signature.asc Description: Digital signature
Bug#345480: COLSx25: gone for me since X7.0
>From Gregor Zattler <[EMAIL PROTECTED]>: > I use a Matrox G400 card with 32 MB Ram and have the exact same > symptoms using SVGATextMode with 132x43. When using the console > after starting X I can only use the upper 25 columns. Thus my > input and the computers output scoll the upper 25 lines while the > lower rest of lines also scolls and shows garbage. After some > scrolling this garbage gets very colorful. Gregor: ping? Is the bug still there? I can't reproduce it with any xserver-xorg since 7.0, so this bug probably should be closed. -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#184791: want to meet?
Do not ignore me please, I found youra email somewhere and now decidebbd to write you. I am coming to your place in few weekbs and thobught we can meet each other. Let me know if you do not mind. I am aa nice pretty girl. Don't reply to this email. Email me diraeclty at [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: purging away mimuw addresses
Processing commands for [EMAIL PROTECTED]: > submitter 360665 ! Bug#360665: yaird: renders system unbootable on jfs root with iocharset=utf8 Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 365428 ! Bug#365428: exim4/dc_local_interfaces and exim4/dc_relay_nets need re-wording, ; now allowed separator Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 191284 ! Bug#191284: mudnames: repeating output Changed Bug submitter from "KiloByte" <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 295489 ! Bug#295489: openvt: race condition when not using -c Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 345480 ! Bug#345480: xserver-xorg: vt switch changes console size to COLSx25 Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 362248 ! Bug#362248: nvidia-glx: 8756 reads monitor's EDID incorrectly Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 213361 ! Bug#213361: ITP: kbtin -- A text-based MUD client Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 366482 ! Bug#366482: ITP: dnscruft -- feeds Bind a list of domains as useful as doubleclick.com or less Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 299771 ! Bug#299771: ITP: ttf-antp -- Antykwa Poltawskiego font family Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 360158 ! Bug#360158: pound: IPv6 support would be nice Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 368530 ! Bug#368530: joe: Mail would be better word-wrapped at 70 columns. Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > submitter 367348 ! Bug#367348: mc: "bytes" and "count" totals during copy clamped to 2GB Changed Bug submitter from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > owner 213361 ! Bug#213361: ITP: kbtin -- A text-based MUD client Owner changed from Adam Borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > owner 366482 ! Bug#366482: ITP: dnscruft -- feeds Bind a list of domains as useful as doubleclick.com or less Owner changed from adam borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > owner 299771 ! Bug#299771: ITP: ttf-antp -- Antykwa Poltawskiego font family Owner changed from adam borowski <[EMAIL PROTECTED]> to Adam Borowski <[EMAIL PROTECTED]>. > tags 360158 ipv6 Bug#360158: pound: IPv6 support would be nice There were no tags set. Tags added: ipv6 > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#195134: is it you?
Do not ignore mae please, I found yourb email somewhere and now decided to write you. I am coming to your place in few weeks andb thought we can meet each other. Let me know if you do not mind. I am a nice pretty girl. Don't repbly to this email. Embail me direclty at [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package libxau
# # bts-link upstream status pull for source package libxau # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #372672 # * https://bugs.freedesktop.org/show_bug.cgi?id=5628 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> FIXED usertags 372672 + status-RESOLVED resolution-FIXED # remote status report for #372672 # * https://bugs.freedesktop.org/show_bug.cgi?id=5628 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> FIXED usertags 372672 + status-RESOLVED resolution-FIXED # remote status report for #372672 # * https://bugs.freedesktop.org/show_bug.cgi?id=5628 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> FIXED usertags 372672 + status-RESOLVED resolution-FIXED thanks
Bug#193318: going out with you
Hire, !!i am here sitting in the internet caffe. Found your email and decided to write. I might be coming to yaour place in 14 days, so I decided to email you. May be we can meet? I am 25 y.o. girl. I have a picture if you want. No need to reply here as this is not my email. Write me at [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374700: nodeadkeys does not work with xorg/cymotionlinux/de
Hello On 2006-06-20 Denis Barbier wrote: > On Tue, Jun 20, 2006 at 08:14:59PM +0200, Christian Hammers wrote: > > Package: xserver-xorg-input-kbd > > Version: 1:1.0.1.3-2 > > Severity: normal > > > > Hello > > > > With the following configuration, which seems ok to me, the nodeadkeys > > option does not work. Any idea where to look and what to check? X is a > > bit of a black box to me :) > > > > My keyboard is a Cherry CyMotion Master G86. > > > > Section "InputDevice" > > Identifier "Generic Keyboard" > > Driver "kbd" > > Option "CoreKeyboard" > > Option "XkbRules" "xorg" > > Option "XkbModel" "cymotionlinux" > > Option "XkbLayout" "de" > > Option "XkbVariant" "nodeadkeys" > > EndSection > > It works fine here. Please run > setxkbmap -layout de -model cymotionlinux -variant nodeadkeys > If it works now, this probably means that these settings are overridden > somehow. This works. Any idea if KDE could do something wrong here? Anyway, I can put above line in my KDE startup scripts and hopefully the problem will be not fixed but at least work-around-ed :) thanks, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374700: marked as done (nodeadkeys does not work with xorg/cymotionlinux/de)
Your message dated Tue, 20 Jun 2006 22:17:06 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#374700: nodeadkeys does not work with xorg/cymotionlinux/de has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg-input-kbd Version: 1:1.0.1.3-2 Severity: normal Hello With the following configuration, which seems ok to me, the nodeadkeys option does not work. Any idea where to look and what to check? X is a bit of a black box to me :) My keyboard is a Cherry CyMotion Master G86. Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "cymotionlinux" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" EndSection xev prints the following for a single keypress: KeyPress event, serial 32, synthetic NO, window 0x3c1, root 0x44, subw 0x0, time 4070502879, (181,93), root:(746,381), state 0x10, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XmbLookupString gives 0 bytes: XFilterEvent returns: True KeyPress event, serial 32, synthetic NO, window 0x3c1, root 0x44, subw 0x0, time 4070502879, (181,93), root:(746,381), state 0x10, keycode 0 (keysym 0x5e, asciicircum), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 1 bytes: (5e) "^" XFilterEvent returns: False KeyRelease event, serial 32, synthetic NO, window 0x3c1, root 0x44, subw 0x0, time 4070503047, (181,93), root:(746,381), state 0x10, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" bye, -christian- -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages xserver-xorg-input-kbd depends on: ii libc6 2.3.6-15 GNU C Library: Shared libraries xserver-xorg-input-kbd recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- On 2006-06-20 Denis Barbier wrote: > It works fine here. Please run > setxkbmap -layout de -model cymotionlinux -variant nodeadkeys > If it works now, this probably means that these settings are overridden > somehow. After further searching, I found a place in the KDE settings menu where it overrides my xorg.conf settings with wrong ones. So this is no bug. I close it. bye, -christian- --- End Message ---
Bug#374700: nodeadkeys does not work with xorg/cymotionlinux/de
On Tue, Jun 20, 2006 at 08:14:59PM +0200, Christian Hammers wrote: > Package: xserver-xorg-input-kbd > Version: 1:1.0.1.3-2 > Severity: normal > > Hello > > With the following configuration, which seems ok to me, the nodeadkeys > option does not work. Any idea where to look and what to check? X is a > bit of a black box to me :) > > My keyboard is a Cherry CyMotion Master G86. > > Section "InputDevice" > Identifier "Generic Keyboard" > Driver "kbd" > Option "CoreKeyboard" > Option "XkbRules" "xorg" > Option "XkbModel" "cymotionlinux" > Option "XkbLayout" "de" > Option "XkbVariant" "nodeadkeys" > EndSection It works fine here. Please run setxkbmap -layout de -model cymotionlinux -variant nodeadkeys If it works now, this probably means that these settings are overridden somehow. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372077: the debconf note on upgrade
i've had already several troubleshootings, where this note prompted the user to abort the upgrade. apt went in a nice not recoverable dependency loop needed the hammer to get them back: dpkg -i --force-foo the severity of this bug seems much higher than wishlist. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scary message on new installations
On Tue, 2006-06-20 at 19:24 +0200, Frans Pop wrote: > On Tuesday 20 June 2006 14:15, Frans Pop wrote: > > Currently X shows a very scary message that upgrades may go wrong > > (template: x11-common/upgrade_issues) on new installations. > > Note that Joey Hess filed this as http://bugs.debian.org/372077 a while > back. We are currently considering upgrading that to RC as we feel we > cannot release D-I Beta3 wile this note is still being displayed for new > installations. > > A reaction would be appreciated. David Nusinow is on vacation this week, so if you need something before next week, you'll probably have to do an NMU. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#374700: nodeadkeys does not work with xorg/cymotionlinux/de
Package: xserver-xorg-input-kbd Version: 1:1.0.1.3-2 Severity: normal Hello With the following configuration, which seems ok to me, the nodeadkeys option does not work. Any idea where to look and what to check? X is a bit of a black box to me :) My keyboard is a Cherry CyMotion Master G86. Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "cymotionlinux" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" EndSection xev prints the following for a single keypress: KeyPress event, serial 32, synthetic NO, window 0x3c1, root 0x44, subw 0x0, time 4070502879, (181,93), root:(746,381), state 0x10, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XmbLookupString gives 0 bytes: XFilterEvent returns: True KeyPress event, serial 32, synthetic NO, window 0x3c1, root 0x44, subw 0x0, time 4070502879, (181,93), root:(746,381), state 0x10, keycode 0 (keysym 0x5e, asciicircum), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 1 bytes: (5e) "^" XFilterEvent returns: False KeyRelease event, serial 32, synthetic NO, window 0x3c1, root 0x44, subw 0x0, time 4070503047, (181,93), root:(746,381), state 0x10, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" bye, -christian- -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages xserver-xorg-input-kbd depends on: ii libc6 2.3.6-15 GNU C Library: Shared libraries xserver-xorg-input-kbd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374652: xserver-xorg-input-mouse: trouble trying to permute mouse buttons (lefthanded)
On Tue, 2006-06-20 at 18:39 +0200, depuis wrote: > > On Tue, 2006-06-20 at 15:23 +0200, Pascal A. Dupuis wrote: > > > > [...] > > > > > That is, with the left-handed config, pressing either button 1 or 3 > > > generates both events. Any clue ? > > > > Just a guess, but xmodmap (and XFCE is probably using the same > > mechanism) only affects the core pointer. Do you have any other > > non-CorePointer pointer devices configured in X? > > > There is indeed a built-in mouse: > > Section "InputDevice" > Identifier "Laptop Mouse" > Driver "mouse" > Option "SendCoreEvents""true" > Option "Device""/dev/misc/psaux" > Option "Protocol" "PS/2" > Option "Emulate3Buttons" "false" > Option "ZAxisMapping" "4 5" > EndSection > > So ... I guess there is some repeater working from behind ? Yes, /dev/(misc/)psaux is just an alias for /dev/input/mice with 2.6 kernels. > How to sort it out ? Ditch the non-CorePointer? :) -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: Processed: Reassigning xserver-xfree86 bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michel Dänzer wrote: > [ Did you intentionally not CC: debian-x? Feel free to quote this > there. ] No, I'm just very bad at Cc:ing properly. Redirecting. > On Sat, 2006-06-10 at 19:14 -0400, Nathanael Nerode wrote: >>> and because it removes their >>> association with the old packages which are now gone in sid and testing >>> but which are still in stable and most likely still affected by them. >> They're not going to be fixed in stable if they're still present there, >> though, because of the stable update policy leaving them assigned to >> a package where they won't ever be fixed is sort of a recipe for >> ignoring them. > > Maybe, but it also helps prevent them from getting reported again > against the packages in stable. > > OTOH, I can say that old bugs cluttering up the current packages doesn't > exactly motivate me to work even on the current bugs... but maybe that's > just me. > > >>> The other XSF folks may not agree on this, but at any rate I think at >>> least a set of clear rules on how to handle this would be good. >> I kind of realized this after I'd started, hence stopping partway >> through. Sorry I didn't realize it earlier there's a very large >> volume of bugs here, and we do indeed have to come up with some sensible >> way to deal with them. I managed to spot some which were definitely >> fixed upstream and close them while I was at it. >> >> I'd rather not just close them all perhaps we should go on a more >> systematic effort to contact the submitters and close the ones where we >> don't get replies? > > Yeah, basically, I think we should only reassign bugs to the current > packages that have been confirmed to still be there. Then, once a > package goes away completely, close all its bugs that were attempted to > be confirmed without success. OK. It's significantly easier to close the bugs one at a time as they are "unconfirmed" because it allows me to keep track of which ones I've checked and which ones I haven't. That OK? > > >> FYI, The bugs which I *retitled* are bugs which have been proven to >> still be present. (Showing that some of the bugs are definitely still >> present. :-/) The ones which still have "xserver-free86" in the title >> are the ones which haven't been checked yet. In case you needed to tell >> the difference. > > Nice. > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEmDXvRGZ0aC4lkIIRAt0NAJ9jLNt/ck5x8ml3g8VBNWSAyF7ExACcCLpX EvzwtUPIdb2Z365uAuLQFDQ= =xKcr -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373949: [PATCH] Possible fix (added locking)
Attached is a patch which I can confirm fixes the issue on my machine. Unfortunatly, my mail to mesa3d-dev appears to have vanished into the ether so I will resend it there to see I can get some feedback. Have a nice day, -- Martijn van Oosterhout http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to > litigate. diff -ur Mesa-6.4.2/src/mesa/drivers/dri/r128/r128_span.c mesa-6.4.2/src/mesa/drivers/dri/r128/r128_span.c --- Mesa-6.4.2/src/mesa/drivers/dri/r128/r128_span.c2005-07-01 02:08:52.0 +0200 +++ mesa-6.4.2/src/mesa/drivers/dri/r128/r128_span.c2006-06-19 15:18:38.0 +0200 @@ -111,6 +111,12 @@ * Depth buffer */ +/* These functions require locking */ +#undef HW_LOCK +#undef HW_UNLOCK +#define HW_LOCK()LOCK_HARDWARE(R128_CONTEXT(ctx)); +#define HW_UNLOCK() UNLOCK_HARDWARE(R128_CONTEXT(ctx)); + /* 16-bit depth buffer functions */
Bug#374652: xserver-xorg-input-mouse: trouble trying to permute mouse buttons (lefthanded)
> On Tue, 2006-06-20 at 15:23 +0200, Pascal A. Dupuis wrote: > > [...] > > > That is, with the left-handed config, pressing either button 1 or 3 > > generates both events. Any clue ? > > Just a guess, but xmodmap (and XFCE is probably using the same > mechanism) only affects the core pointer. Do you have any other > non-CorePointer pointer devices configured in X? > There is indeed a built-in mouse: Section "InputDevice" Identifier "Laptop Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/misc/psaux" Option "Protocol" "PS/2" Option "Emulate3Buttons" "false" Option "ZAxisMapping" "4 5" EndSection So ... I guess there is some repeater working from behind ? How to sort it out ? TIA Pascal Dupuis -- Wordt ook lid van de Scarlet Club via een bestaande Scarlet klant en ontvang cadeaucheques twv EUR 50! Bezoek snel http://www.scarletclub.be Devenez aussi membre du Club Scarlet via un client Scarlet existant et recevez des cheques cadeaux jusqu'a EUR 50! Surfez vite sur http://www.clubscarlet.be
Bug#374652: xserver-xorg-input-mouse: trouble trying to permute mouse buttons (lefthanded)
On Tue, 2006-06-20 at 15:23 +0200, Pascal A. Dupuis wrote: > > excerpt from xorg.conf: > Section "InputDevice" > Identifier "Configured Mouse" > Driver "mouse" > Option "CorePointer" > Option "Device""/dev/input/mice" > Option "Protocol" "ImPS/2" > Option "Emulate3Buttons" "false" > Option "ZAxisMapping" "4 5" > EndSection > > This is for a USB mouse. If I try to use it lefthanded, either using > xfce4 mouse setup or with xmodmad -e "pointer = 3 2 1 4 5 6 7 8 9", > xev shows this strange behaviour: [...] > That is, with the left-handed config, pressing either button 1 or 3 > generates both events. Any clue ? Just a guess, but xmodmap (and XFCE is probably using the same mechanism) only affects the core pointer. Do you have any other non-CorePointer pointer devices configured in X? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#374652: xserver-xorg-input-mouse: trouble trying to permute mouse buttons (lefthanded)
-- Initial header --- >From : "Michel Dänzer" [EMAIL PROTECTED] To : "Pascal A. Dupuis" [EMAIL PROTECTED],[EMAIL PROTECTED] CC : Date : Tue, 20 Jun 2006 17:35:20 +0200 Subject : Re: Bug#374652: xserver-xorg-input-mouse: trouble trying to permute mouse buttons (lefthanded) > On Tue, 2006-06-20 at 15:23 +0200, Pascal A. Dupuis wrote: > > [...] > > > That is, with the left-handed config, pressing either button 1 or 3 > > generates both events. Any clue ? > > Just a guess, but xmodmap (and XFCE is probably using the same > mechanism) only affects the core pointer. Do you have any other > non-CorePointer pointer devices configured in X? > There is indeed a built-in mouse: Section "InputDevice" Identifier "Laptop Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/misc/psaux" Option "Protocol" "PS/2" Option "Emulate3Buttons" "false" Option "ZAxisMapping" "4 5" EndSection So ... I guess there is some repeater working from behind ? How to sort it out ? TIA Pascal Dupuis -- Wordt ook lid van de Scarlet Club via een bestaande Scarlet klant en ontvang cadeaucheques twv EUR 50! Bezoek snel http://www.scarletclub.be Devenez aussi membre du Club Scarlet via un client Scarlet existant et recevez des cheques cadeaux jusqu'a EUR 50! Surfez vite sur http://www.clubscarlet.be
Bug#356545: Upstream patch
forwarded 356545 https://bugs.freedesktop.org/show_bug.cgi?id=5628 tag 356545 fixed-upstream thanks Here's a patch extracted from the upstream CVS. It's probably better than the one I originally submitted. -- Matt diff -ru libxau-1.0.0-old/Makefile.am libxau-1.0.0/Makefile.am --- libxau-1.0.0-old/Makefile.am2006-06-20 08:27:18.0 -0700 +++ libxau-1.0.0/Makefile.am2006-06-20 08:28:05.0 -0700 @@ -29,6 +29,8 @@ pkgconfigdir = $(libdir)/pkgconfig pkgconfig_DATA = xau.pc +LIB_MAN_DIR_SUFFIX = $(LIB_MAN_DIR:@mandir@/man%=%) + libmandir = $(LIB_MAN_DIR) libman_PRE = Xau.man BUILT_SOURCES = shadows.DONE @@ -51,7 +53,7 @@ shadows.DONE: -rm -f $(Xau_shadows:[EMAIL PROTECTED]@) (for i in $(Xau_shadows:[EMAIL PROTECTED]@) ; do \ -echo .so man$(LIB_MAN_SUFFIX)/Xau.$(LIB_MAN_SUFFIX) > $$i; \ +echo .so man$(LIB_MAN_DIR_SUFFIX)/Xau.$(LIB_MAN_SUFFIX) > $$i; \ done) XORGRELSTRING = @PACKAGE_STRING@ diff -ru libxau-1.0.0-old/Makefile.in libxau-1.0.0/Makefile.in --- libxau-1.0.0-old/Makefile.in2006-06-20 08:27:18.0 -0700 +++ libxau-1.0.0/Makefile.in2006-06-20 08:28:59.0 -0700 @@ -185,6 +185,8 @@ pkgconfigdir = $(libdir)/pkgconfig pkgconfig_DATA = xau.pc +LIB_MAN_DIR_SUFFIX = $(LIB_MAN_DIR:@mandir@/man%=%) + libmandir = $(LIB_MAN_DIR) libman_PRE = Xau.man BUILT_SOURCES = shadows.DONE @@ -717,7 +719,7 @@ shadows.DONE: -rm -f $(Xau_shadows:[EMAIL PROTECTED]@) (for i in $(Xau_shadows:[EMAIL PROTECTED]@) ; do \ -echo .so man$(LIB_MAN_SUFFIX)/Xau.$(LIB_MAN_SUFFIX) > $$i; \ +echo .so man$(LIB_MAN_DIR_SUFFIX)/Xau.$(LIB_MAN_SUFFIX) > $$i; \ done) Xau.$(LIB_MAN_SUFFIX): $(srcdir)/Xau.man signature.asc Description: Digital signature
Processed: Upstream patch
Processing commands for [EMAIL PROTECTED]: > forwarded 356545 https://bugs.freedesktop.org/show_bug.cgi?id=5628 Bug#356545: libxau-dev: manpages refer to incorrect location (.so man3x/Xau.3x) Bug#362783: broken manpages Bug#372672: libxau-dev: mandb messages Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=5628. > tag 356545 fixed-upstream Bug#356545: libxau-dev: manpages refer to incorrect location (.so man3x/Xau.3x) Tags were: patch Bug#362783: broken manpages Bug#372672: libxau-dev: mandb messages Tags added: fixed-upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scary message on new installations
On Tuesday 20 June 2006 14:15, Frans Pop wrote: > Currently X shows a very scary message that upgrades may go wrong > (template: x11-common/upgrade_issues) on new installations. Note that Joey Hess filed this as http://bugs.debian.org/372077 a while back. We are currently considering upgrading that to RC as we feel we cannot release D-I Beta3 wile this note is still being displayed for new installations. A reaction would be appreciated. Cheers, FJP pgpQwHgTJ9HYT.pgp Description: PGP signature
Processed: Patch to correct manual pages
Processing commands for [EMAIL PROTECTED]: > tag 356545 patch Bug#356545: libxau-dev: manpages refer to incorrect location (.so man3x/Xau.3x) There were no tags set. Bug#362783: broken manpages Bug#372672: libxau-dev: mandb messages Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356545: Patch to correct manual pages
tag 356545 patch thanks The attached patch fixes makes the .so references use the correct path to the directory containing Xau.3x.gz. I've verified that it fixes the problem. -- Matt diff -ru libxau-1.0.0-old/Makefile.am libxau-1.0.0/Makefile.am --- libxau-1.0.0-old/Makefile.am2006-06-20 06:50:36.0 -0700 +++ libxau-1.0.0/Makefile.am2006-06-20 07:01:01.0 -0700 @@ -51,7 +51,7 @@ shadows.DONE: -rm -f $(Xau_shadows:[EMAIL PROTECTED]@) (for i in $(Xau_shadows:[EMAIL PROTECTED]@) ; do \ -echo .so man$(LIB_MAN_SUFFIX)/Xau.$(LIB_MAN_SUFFIX) > $$i; \ +echo .so `basename $(LIB_MAN_DIR)`/Xau.$(LIB_MAN_SUFFIX) > $$i; \ done) XORGRELSTRING = @PACKAGE_STRING@ diff -ru libxau-1.0.0-old/Makefile.in libxau-1.0.0/Makefile.in --- libxau-1.0.0-old/Makefile.in2006-06-20 06:50:36.0 -0700 +++ libxau-1.0.0/Makefile.in2006-06-20 07:22:30.0 -0700 @@ -717,7 +717,7 @@ shadows.DONE: -rm -f $(Xau_shadows:[EMAIL PROTECTED]@) (for i in $(Xau_shadows:[EMAIL PROTECTED]@) ; do \ -echo .so man$(LIB_MAN_SUFFIX)/Xau.$(LIB_MAN_SUFFIX) > $$i; \ +echo .so `basename $(LIB_MAN_DIR)`/Xau.$(LIB_MAN_SUFFIX) > $$i; \ done) Xau.$(LIB_MAN_SUFFIX): $(srcdir)/Xau.man signature.asc Description: Digital signature
Re: Where'd GL/GLwMDrawA.h go?
On Tue, 2006-06-20 at 10:34 -0400, Steve M. Robbins wrote: > On Tue, Jun 20, 2006 at 11:51:27AM +0200, Michel Dänzer wrote: > > On Mon, 2006-06-19 at 09:10 -0400, Steve M. Robbins wrote: > > > > It appears that libgl1-mesa-swx11-dev is built from mesa 6.4.2, whilst > > > GL-from-xorg is built from mesa 6.9.0. > > > > There's no such thing. > > No such which? Mesa 6.9.0? I got that from > http://packages.debian.org/unstable/libdevel/xlibmesa-gl-dev which > reads: > > Package: xlibmesa-gl-dev (1:7.0.22, 6.9.0.dfsg.1-6) > > I was just guessing that 6.9.0.dfsg referred to the mesa sources. It refers to X.Org 6.9, which shipped a copy of Mesa 6.4. > > X.Org upstream no longer ships its own GL stuff > > except for the GLX protocol headers, so this will all come from Mesa in > > the future. > > OK. > > But what is the state now? Does xlibmesa-gl-dev come from upstream > xorg? Is it a version of mesa? No, in sid it's purely a transitional package to aid upgrades. > If so, could it supply the GLw library as does libgl1-mesa-swx11-dev? No, and I'm not sure what the point would be, given that it's just a static library. Do you anticipate any problems with building against libgl1-mesa-swx11-dev? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: Where'd GL/GLwMDrawA.h go?
On Tue, Jun 20, 2006 at 11:51:27AM +0200, Michel Dänzer wrote: > On Mon, 2006-06-19 at 09:10 -0400, Steve M. Robbins wrote: > > > It appears that libgl1-mesa-swx11-dev is built from mesa 6.4.2, whilst > > GL-from-xorg is built from mesa 6.9.0. > > There's no such thing. No such which? Mesa 6.9.0? I got that from http://packages.debian.org/unstable/libdevel/xlibmesa-gl-dev which reads: Package: xlibmesa-gl-dev (1:7.0.22, 6.9.0.dfsg.1-6) I was just guessing that 6.9.0.dfsg referred to the mesa sources. > X.Org upstream no longer ships its own GL stuff > except for the GLX protocol headers, so this will all come from Mesa in > the future. OK. But what is the state now? Does xlibmesa-gl-dev come from upstream xorg? Is it a version of mesa? If so, could it supply the GLw library as does libgl1-mesa-swx11-dev? Thanks, -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374652: xserver-xorg-input-mouse: trouble trying to permute mouse buttons (lefthanded)
Package: xserver-xorg-input-mouse Version: 1:1.0.4-3 Severity: normal Hello, excerpt from xorg.conf: Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "false" Option "ZAxisMapping" "4 5" EndSection This is for a USB mouse. If I try to use it lefthanded, either using xfce4 mouse setup or with xmodmad -e "pointer = 3 2 1 4 5 6 7 8 9", xev shows this strange behaviour: ButtonPress event, serial 28, synthetic NO, window 0x361, root 0x4c, subw 0x0, time 4053401923, (134,112), root:(557,405), state 0x0, button 1, same_screen YES ButtonPress event, serial 28, synthetic NO, window 0x361, root 0x4c, subw 0x0, time 4053401923, (134,112), root:(557,405), state 0x100, button 3, same_screen YES ButtonRelease event, serial 28, synthetic NO, window 0x361, root 0x4c, subw 0x0, time 4053402019, (134,112), root:(557,405), state 0x500, button 1, same_screen YES ButtonRelease event, serial 28, synthetic NO, window 0x361, root 0x4c, subw 0x0, time 4053402019, (134,112), root:(557,405), state 0x400, button 3, same_screen YES while the normal behaviour is: ButtonPress event, serial 28, synthetic NO, window 0x361, root 0x4c, subw 0x0, time 4053337678, (78,103), root:(501,396), state 0x0, button 1, same_screen YES ButtonRelease event, serial 28, synthetic NO, window 0x361, root 0x4c, subw 0x0, time 4053337790, (78,103), root:(501,396), state 0x100, button 1, same_screen YES That is, with the left-handed config, pressing either button 1 or 3 generates both events. Any clue ? TIA Pascal Dupuis -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17 Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-input-mouse depends on: ii libc6 2.3.6-13 GNU C Library: Shared libraries ii xserver-xorg-core 1:1.0.2-8 X.Org X server -- core server xserver-xorg-input-mouse recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Scary message on new installations
Hi, Currently X shows a very scary message that upgrades may go wrong (template: x11-common/upgrade_issues). If that warning is really needed, that's fine of course. However, the message is also shown for _new_ installations (and thus during new installations using Debian Installer). And from the text of the message I would say that it does not apply to new installations. Would it be possible to change the code so that the message is only shown during upgrades? Cheers, FJP pgpkSOYz2piLm.pgp Description: PGP signature
x11-common conflicts in SID
Hi, I don't know if it's necessary to open a bug report for this, but I only wanted to bring to your attention that the x11-common package conflicts with the realplayer and cooledit packages. Kind Regards Stefan -- Confidentiality Notice: The above message and all attachments may contain privileged and confidential information intended only for the person or entity to which it is addressed. Any review, retransmission, dissemination, copy or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this message in error, please notify the sender immediately by e-mail, facsimile or telephone and thereafter delete the material from your computer. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the view of the entity transmitting the message. UCS Group Limited and all of its subsidiary companies hereby distances itself from and accepts no liability in respect of the unauthorized use of its e-mail facility or the sending of e-mail communications for other than strictly business purposes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where'd GL/GLwMDrawA.h go?
On Mon, 2006-06-19 at 09:10 -0400, Steve M. Robbins wrote: > On Mon, Jun 19, 2006 at 08:58:10AM +0300, Daniel Stone wrote: > > On Sun, Jun 18, 2006 at 08:48:46PM -0400, Steve M. Robbins wrote: > > > Before the Great Fracturing, I believe this file was in > > > xlibmesa-gl-dev. Where may I find it now? > > > > GLw is not built; it's not in Mesa anywhere that I can see. > > Someone else emailed me privately to say that libgl1-mesa-swx11-dev > has the file. This package is apparently another build of mesa. I > can't keep up with all these things, but my hunch is that combining > libgl1-mesa-swx11 and GL-from-xorg will cause me grief. True? Yes, they'll conflict with each other. However, building against libgl1-mesa-swx11-dev and running against another GL implementation shouldn't be a problem (unless the build process is very broken and checks for stuff that really needs to be checked at runtime, maybe), see below. > It appears that libgl1-mesa-swx11-dev is built from mesa 6.4.2, whilst > GL-from-xorg is built from mesa 6.9.0. There's no such thing. X.Org upstream no longer ships its own GL stuff except for the GLX protocol headers, so this will all come from Mesa in the future. > Did "GLw" get split out to some other place in the meanwhile? Or just > dropped completely? Looks like it's only the static library in libgl1-mesa-swx11-dev ATM; if it needs to be a shared library, it should probably be moved into its own set of packages. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
