Bug#587618: xserver-xorg: Periodically x switches between virual desktops randomly and at speed
On 30/06/10 14:47, Julien Cristau wrote: On Wed, Jun 30, 2010 at 13:53:42 +0100, Ben Whyall wrote: Attached are the files you asked for. The period when it happened is towards the bottom of the xinputtest.txt file. It's difficult to be more precise as it jumped round 6 or 7 times before allowing me ot move to correct workspace and stop the trace. Weird, the only thing that may be suspicious is devices 10 and 11 (Microsoft 2.4GHz Transceivers) switching around from keyboard to mouse and vice versa halfway in the trace: And now 10 is a slave keyboard and 11 is a slave pointer.. EVENT type 1 (DeviceChanged) device: 2 (11) reason: SlaveSwitch Reporting 7 classes: Class originated from: 11 Buttons supported: 13 Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button Horiz Wheel Left Button Horiz Wheel Right Button Side Button Extra Button Unknown Button Unknown Button Unknown Button Unknown Button state: Class originated from: 11 Keycodes supported: 248 Class originated from: 11 Detail for Valuator 0: Label: Abs X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 1: Label: Abs Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 2: Label: Abs Gas Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 3: Label: Abs Brake Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 4: Label: Abs Misc Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative If that's not it then the problem may not be recorded in the trace. Not sure how to debug then. Cheers, Julien Hi Julien Just some additional information the mouse, keyboard is a microsoft wireless desktop and connected via a bluetooth usb dongle. Also it is connected via a kvm, I am pretty sure I havent switched mid trace, but I wonder if its worth trying to reproduce this without the kvm in the way. Ben -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c2ba108.9010...@whyall-systems.co.uk
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
On Wed, Jun 30, 2010 at 21:24:24 +0300, Anton Zinoviev wrote: > On Wed, Jun 30, 2010 at 03:50:56PM +0200, yellow protoss wrote: > > > > I have been trying the 'setxkbmap us' , 'setxkbmap de' , and > > 'setxkbmap fr' and changed with those 2 keyboards. > > I believe the command you need is 'setxkbmap de nodeadkeys lv3:ralt_switch'. > And if that doesn't work then the only thing I can think of is a broken / too old libX11 that doesn't handle some keysyms. The output of 'dpkg -l libx11-6' and 'ldd /usr/bin/xkbcomp' would probably confirm. Cheers, Julien signature.asc Description: Digital signature
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
On Wed, Jun 30, 2010 at 03:50:56PM +0200, yellow protoss wrote: > > I have been trying the 'setxkbmap us' , 'setxkbmap de' , and > 'setxkbmap fr' and changed with those 2 keyboards. I believe the command you need is 'setxkbmap de nodeadkeys lv3:ralt_switch'. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100630182424.ga17...@debian.lan
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
On Wed, Jun 30, 2010 at 02:25:08PM +0200, yellow protoss wrote: > > Well, I am not expert ni LINUX nor coder. So If you can be specific > what you require, I can surely provide it, and would be pleased to > contribute. As somewone who has actually used JWM I can say that this is an environment for people who are more or less experienced and know how to fix the bugs in their own configurations. Julien provided you with a hint what you should look at: the 'setxkbmap us' command in your startup script is not correct because you want a German layout. I agree with him that for now the best course of action would be to close this bug. My advice for you is to either address some user support forum/mailinglist and provide them with every detail of your particular configuration, or to use some standard environment, such as Gnome or KDE. If you choose the second option, then first make sure you have removed all your system-wide customizations in /etc and second, create a new user and experiment with it. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100630133400.ga14...@debian.lan
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
2010/6/30 Anton Zinoviev > On Wed, Jun 30, 2010 at 02:25:08PM +0200, yellow protoss wrote: > > > > Well, I am not expert ni LINUX nor coder. So If you can be specific > > what you require, I can surely provide it, and would be pleased to > > contribute. > > As somewone who has actually used JWM I can say that this is an > environment for people who are more or less experienced and know how to > fix the bugs in their own configurations. > > Julien provided you with a hint what you should look at: the 'setxkbmap > us' command in your startup script is not correct because you want a > German layout. > I have been trying the 'setxkbmap us' , 'setxkbmap de' , and 'setxkbmap fr' and changed with those 2 keyboards. It did not work at all and altgr remains not working. I tried teh several reconfiguration of the X mapping. I would say that it is a bug, as simply as that. I use debinan since many many years. and in the stable edition, my keyboard was working fully. Never got any problems > > I agree with him that for now the best course of action would be to > close this bug. I do not understand why you would like to close the bug since the issue remains and stable debian distro has workign keyboard: I may quote: I have been trying the 'setxkbmap us' , 'setxkbmap de' , and 'setxkbmap fr' and changed with those 2 keyboards. It did not work at all and altgr remains not working. I tried teh several reconfiguration of the X mapping. I would say that it is a bug, as simply as that. I use debinan since many many years. and in the stable edition, my keyboard was working fully. Never got any problems > My advice for you is to either address some user > support forum/mailinglist and provide them with every detail of your > particular configuration, or to use some standard environment, such as > Gnome or KDE. I have never meet the issue under Debian Stable, previously installed on the machine. I may suppose that it remains under X11 / JWM some further investigations. > If you choose the second option, then first make sure you > have removed all your system-wide customizations in /etc and second, > create a new user and experiment with it. > I have several users , and all users have same issue. My concern is why you would like to close the bug since the issue remains and no solutions may be proposed or have working potential by dint of trying. I bought a new keyboard, and the issue remains. > > Anton Zinoviev > All the best Best regards
Bug#587618: xserver-xorg: Periodically x switches between virual desktops randomly and at speed
On Wed, Jun 30, 2010 at 13:53:42 +0100, Ben Whyall wrote: > Attached are the files you asked for. The period when it happened > is towards the bottom of the xinputtest.txt file. It's difficult to > be more precise as it jumped round 6 or 7 times before allowing me > ot move to correct workspace and stop the trace. > Weird, the only thing that may be suspicious is devices 10 and 11 (Microsoft 2.4GHz Transceivers) switching around from keyboard to mouse and vice versa halfway in the trace: > ??? Virtual core pointer id=2[master pointer (3)] > ??? ??? Virtual core XTEST pointer id=4[slave pointer > (2)] > ??? ??? ATEN Advance Tech Inc. CS-64U V1.0.091 id=9[slave pointer > (2)] > ??? ??? Microsoft Microsoft?? 2.4GHz Transceiver V1.0 id=10 [slave > pointer (2)] > ??? Virtual core keyboard id=3[master keyboard (2)] > ??? Virtual core XTEST keyboard id=5[slave > keyboard (3)] > ??? Power Button id=6[slave > keyboard (3)] > ??? Power Button id=7[slave > keyboard (3)] > ??? ATEN Advance Tech Inc. CS-64U V1.0.091id=8[slave > keyboard (3)] > ??? C-Media USB Headphone Set id=12 [slave > keyboard (3)] > ??? Microsoft Microsoft?? 2.4GHz Transceiver V1.0 id=11 [slave > keyboard (3)] Here 10 is a slave pointer and 11 is a slave keyboard. [...] > EVENT type 12 (PropertyEvent) > property: 136 'Device Enabled' > changed: modified > EVENT type 11 (HierarchyChanged) > Changes happened:[device disabled] > device 2 [master pointer (3)] is enabled > device 3 [master keyboard (2)] is enabled > device 4 [slave pointer (2)] is enabled > device 5 [slave keyboard (3)] is enabled > device 6 [slave keyboard (3)] is enabled > device 7 [slave keyboard (3)] is enabled > device 8 [slave keyboard (3)] is enabled > device 9 [slave pointer (2)] is enabled > device 12 [slave keyboard (3)] is enabled > device 10 [slave pointer (2)] is enabled > device 11 [slave keyboard (3)] is disabled > changes:[device disabled] > EVENT type 12 (PropertyEvent) > property: 253 'Evdev Reopen Attempts' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 136 'Device Enabled' > changed: deleted > EVENT type 11 (HierarchyChanged) > Changes happened:[slave removed] > device 2 [master pointer (3)] is enabled > device 3 [master keyboard (2)] is enabled > device 4 [slave pointer (2)] is enabled > device 5 [slave keyboard (3)] is enabled > device 6 [slave keyboard (3)] is enabled > device 7 [slave keyboard (3)] is enabled > device 8 [slave keyboard (3)] is enabled > device 9 [slave pointer (2)] is enabled > device 12 [slave keyboard (3)] is enabled > device 10 [slave pointer (2)] is enabled > device 11 [slave pointer (0)] is disabled > changes:[slave removed] > EVENT type 12 (PropertyEvent) > property: 136 'Device Enabled' > changed: modified > EVENT type 11 (HierarchyChanged) > Changes happened:[device disabled] > device 2 [master pointer (3)] is enabled > device 3 [master keyboard (2)] is enabled > device 4 [slave pointer (2)] is enabled > device 5 [slave keyboard (3)] is enabled > device 6 [slave keyboard (3)] is enabled > device 7 [slave keyboard (3)] is enabled > device 8 [slave keyboard (3)] is enabled > device 9 [slave pointer (2)] is enabled > device 12 [slave keyboard (3)] is enabled > device 10 [slave pointer (2)] is disabled > changes:[device disabled] > EVENT type 12 (PropertyEvent) > property: 274 'Evdev Drag Lock Buttons' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 273 'Evdev Wheel Emulation Button' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 272 'Evdev Wheel Emulation Timeout' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 271 'Evdev Wheel Emulation Inertia' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 270 'Evdev Wheel Emulation Axes' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 269 'Evdev Wheel Emulation' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 268 'Evdev Middle Button Timeout' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 267 'Evdev Middle Button Emulation' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 266 'Button Labels' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 265 'Axis Labels' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 264 'Evdev Axes Swap' > changed: deleted > EVENT type 12 (PropertyEvent) > property: 262 'Evdev Axis Inversion' >
Bug#551373: warzone2100: Segmentation fault when trying to run game
On 29.6.2010 16:59, Julien Cristau wrote: On Sat, Oct 17, 2009 at 22:10:36 +0200, Tomas Safarik wrote: when I try to run the game Single player -> New game it segfaults. $ warzone2100 Failed to free bo[0x12014278] at 5000 ret = Operation not permitted info|10:02:47: [seq_Play] unable to open 'sequences/cam1/c001.ogg' for playback info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/data/ again info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/share/warzone2100/ again info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/share/games/warzone2100/ again [driAllocateTexture:635] unable to allocate texture Saved dump file to '/tmp/warzone2100.gdmp-NVojET' If you create a bugreport regardings this crash, please include this file. Segmentation fault I'll be happy to provide more information if needed. Is this still reproducible with mesa 7.7 or 7.8? If so please install libgl1-mesa-dri-dbg and libgl1-mesa-glx-dbg, get a stacktrace from gdb, and file a bug at bugs.freedesktop.org against mesa, component Drivers/DRI/r300. Thanks. Cheers, Julien Hello Julien, unfortunately I no longer use powerpc computer so I am not able to test it. -- Tomas Safarik -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c2b3223.3030...@server.cz
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
Well, I am not expert ni LINUX nor coder. So If you can be specific what you require, I can surely provide it, and would be pleased to contribute. Unfortunately I am not developer or coder, so if you inquire a command and an output to be reported, I would surely do my best to do so. I am sorry On Wed, Jun 30, 2010 at 2:11 PM, Julien Cristau wrote: > On Wed, Jun 30, 2010 at 14:04:33 +0200, yellow protoss wrote: > > > I assume that it is not coming from the layout but really a but in itself > of > > X11. > > > > I tried all kind of layouts, and the TTY work flawless (no X). I guess it > > has something to do with X. > > > The layout (xkbcomp output) you attached in this bug looked just fine, > it just wasn't a german layout. There's no evidence of a bug here, so > unless you can provide more details and something that makes some sense, > I'll close this bug. I don't know what you tried, I don't know your > desktop environment, and you don't seem to have even tried to provide > coherent explanations. > > Cheers, > Julien > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQIcBAEBCAAGBQJMKzSMAAoJEDEBgAUJBeQMANAP/iLIBVh5HfUzn7cr45H9Fv9g > h37ZsvGaSE7sZGx2+RVAkNkB1Nf+kZ43jcqEaCFrewo7F0r+Z0e9/ofwxnx1LrSc > bFu23B8RMEoAzuU9RntTaC0ClwTEZjeJLMb2pgCObtEqP4KgK4E/UnFI3eTAwLaH > cixd3PFVYShg7jm54mqhAHEPfk/E/kIIQmrtKrl3yAEV+bAiVBmau6xm4xi9pCf7 > QJBdXuoffIgvAhlXmkjA4kPufI+njAX2ALYdx+SEHA27LiVcjd0Msp4Ge2mAphCr > RcBPPPEPhL7/y5twN/HRqc7JaRITU28sFeqMcueBJEgqaui3kJmieuI9vxCAacRR > SMI+K+L6co6W+//rt33+/XTGVDIlXlcd9GkAManxFyF/MI11lhKL9NT1zwMeeMAW > 8fY3Gw6Myw84C5ZD3mULSYiAPFEtY3NGH+/Hsvc9iq3R+U3JkNg0FTLif3GZ4UPT > TS2VnjqoY7JatiSBOFviIIQgCjPFQDGGl9ydYNYzaGdAbKqBRg/lG8pstrCEit1f > mtukpUILkRma1tR8b9LNcjK2sXqME+Lb7eNJRLYVjmbiIGdUe3OiqhEDA0gNRpa+ > s6iYNh2zByB6vvcxmnslRGKelEew0AGQ0wFdUFBvx34r1GQVG4VapLR4DHHBLKK8 > CM6efJB076GBsSe7SVeI > =BcyJ > -END PGP SIGNATURE- > >
Bug#553006: marked as done (mesa: DRI game (warzone2100) crash)
Your message dated Wed, 30 Jun 2010 13:36:50 +0100 with message-id <20100630123650.gt10...@radis.liafa.jussieu.fr> and subject line Re: Bug#551373: warzone2100: Segmentation fault when trying to run game has caused the Debian Bug report #551373, regarding mesa: DRI game (warzone2100) crash 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 551373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mesa Version: 7.6-1 Severity: normal Hello, I have a problem with crashing application it seem it is because of mesa package on my eBook G4 (powerpc and ATI M11). First I reported this bug to warzone2100 package, but it was closed as this is probably mesa issue. Please see http://developer.wz2100.net/ticket/1009 . I hope this is the right plase to report it if not please let me know. I'll be happy to provide more information if needed. Thank you Tomas Safarik -- System Information: Debian Release: squeeze/sid APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.30-2-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- On Wed, Jun 30, 2010 at 14:01:39 +0200, Tomáš Šafařík wrote: > On 29.6.2010 16:59, Julien Cristau wrote: > >On Sat, Oct 17, 2009 at 22:10:36 +0200, Tomas Safarik wrote: > > > >>when I try to run the game Single player -> New game it segfaults. > >> > >>$ warzone2100 > >>Failed to free bo[0x12014278] at 5000 > >>ret = Operation not permitted > >>info|10:02:47: [seq_Play] unable to open 'sequences/cam1/c001.ogg' for > >>playback > >>info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/data/ > >>again > >>info|10:02:47: [rebuildSearchPath] * Failed to remove path > >>/usr/share/warzone2100/ again > >>info|10:02:47: [rebuildSearchPath] * Failed to remove path > >>/usr/share/games/warzone2100/ again > >>[driAllocateTexture:635] unable to allocate texture > >>Saved dump file to '/tmp/warzone2100.gdmp-NVojET' > >>If you create a bugreport regardings this crash, please include this file. > >>Segmentation fault > >> > >>I'll be happy to provide more information if needed. > >> > >Is this still reproducible with mesa 7.7 or 7.8? If so please install > >libgl1-mesa-dri-dbg and libgl1-mesa-glx-dbg, get a stacktrace from gdb, > >and file a bug at bugs.freedesktop.org against mesa, component > >Drivers/DRI/r300. Thanks. > > > >Cheers, > >Julien > > Hello Julien, > > unfortunately I no longer use powerpc computer so I am not able to test it. > OK, thanks for the followup, I'll close this bug then. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#551373: marked as done (warzone2100: Segmentation fault when trying to run game)
Your message dated Wed, 30 Jun 2010 13:36:50 +0100 with message-id <20100630123650.gt10...@radis.liafa.jussieu.fr> and subject line Re: Bug#551373: warzone2100: Segmentation fault when trying to run game has caused the Debian Bug report #551373, regarding warzone2100: Segmentation fault when trying to run game 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 551373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: warzone2100 Version: 2.2.3-1 Severity: important Hello, when I try to run the game Single player -> New game it segfaults. $ warzone2100 Failed to free bo[0x12014278] at 5000 ret = Operation not permitted info|10:02:47: [seq_Play] unable to open 'sequences/cam1/c001.ogg' for playback info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/data/ again info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/share/warzone2100/ again info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/share/games/warzone2100/ again [driAllocateTexture:635] unable to allocate texture Saved dump file to '/tmp/warzone2100.gdmp-NVojET' If you create a bugreport regardings this crash, please include this file. Segmentation fault I'll be happy to provide more information if needed. Tomas Safarik -- System Information: Debian Release: squeeze/sid APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.30-2-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages warzone2100 depends on: ii libc6 2.10.1-0exp1 GNU C Library: Shared libraries ii libgcc1 1:4.4.1-6 GCC support library ii libgl1-mesa-glx [libgl1] 7.6-1 A free implementation of the OpenG ii libglc0 0.7.2-1QuesoGLC GLC implementation ii libglu1-mesa [libglu1]7.6-1 The OpenGL utility library (GLU) ii libogg0 1.1.4~dfsg-1 Ogg bitstream library ii libopenal11:1.9.563-1Software implementation of the Ope ii libphysfs12.0.0-3filesystem abstraction library for ii libpng12-01.2.40-1 PNG library - runtime ii libpopt0 1.15-1 lib for parsing cmdline parameters ii libsdl-net1.2 1.2.7-2network library for Simple DirectM ii libsdl1.2debian 1.2.13-5 Simple DirectMedia Layer ii libstdc++64.4.1-6The GNU Standard C++ Library v3 ii libtheora01.1.1-2The Theora Video Compression Codec ii libvorbis0a 1.2.3-3The Vorbis General Audio Compressi ii libvorbisfile31.2.3-3The Vorbis General Audio Compressi ii libx11-6 2:1.2.99.901-1 X11 client-side library ii warzone2100-data 2.2.3-1data files for warzone2100 Versions of packages warzone2100 recommends: ii warzone2100-music 2.2.3-1official music for warzone2100 pn warzone2100-video (no description available) warzone2100 suggests no packages. -- no debconf information Program: /usr/games/warzone2100(warzone2100) Command line: "warzone2100" Version: Version r0 - Built Sep 20 2009 Distributor: Debian Compiled on: Sep 20 2009 18:59:02 Compiled by: GCC 4.3.4 Executed on: Sat Oct 17 22:02:36 2009 Operating system: Linux Node name: iBookG4 Release: 2.6.30-2-powerpc Version: #1 Sat Oct 3 22:43:22 UTC 2009 Machine: ppc Pointers: 32bit Compiled against PhysicsFS version: 2.0.0 Running with PhysicsFS version: 2.0.0 Misc Data: [10:02:37]OpenGL Vendor : DRI R300 Project [10:02:37]OpenGL Renderer : Mesa DRI R300 (RV350 4E56) 20090101 AGP 4x PowerPC/Altivec TCL [10:02:37]OpenGL Version : 1.5 Mesa 7.6 [10:02:37]ALC_FREQUENCY = 44100 [10:02:37]ALC_REFRESH = 46 [10:02:37]ALC_SYNC = 0 [10:02:37]ALC_MONO_SOURCES = 255 [10:02:37]ALC_STEREO_SOURCES = 1 [10:02:37]OpenAL Vendor: OpenAL Community [10:02:37]OpenAL Version: 1.1 ALSOFT 1.9.563 [10:02:37]OpenAL Renderer: OpenAL Soft [10:02:37]Using language: System locale [10:02:51]Current Level/map is CAM_1A Dump caused by signal: SIGSEGV: Invalid memory reference: Address not mapped to object Log message: info|10:02:47: [seq_Play] unable to open 'sequences/cam1/c001.ogg' for playback Log message: info|10:02:47: [rebuildSearchPath] * Failed to remove path /usr/data/ again Log message: info
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
I assume that it is not coming from the layout but really a but in itself of X11. I tried all kind of layouts, and the TTY work flawless (no X). I guess it has something to do with X. On Wed, Jun 30, 2010 at 1:44 PM, Julien Cristau wrote: > On Wed, Jun 30, 2010 at 13:39:57 +0200, yellow protoss wrote: > > > thanks for the reply. > > > > So I tried alomost everything, namely with : > > > > .startup script : with setxkbmap us > > > > and also > > .startup script : without any setxkbmap and .startup script empty. > > > > at the start of JWM. > > > > It seems that it comes from X11 + JWM together ... I would suppose. > > > Well there doesn't seem to be a bug in X here. If you're using a us > layout then there's nothing for altgr to do. If you want to use > de(nodeadkeys) then don't set the keymap to us... > > Cheers, > Julien > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQIcBAEBCAAGBQJMKy4HAAoJEDEBgAUJBeQMWJAQAJ4zz/ns7YC7eNi8+lrW8y/R > 0VuHQrOlLyOU+b/1pQyCept8pVVRy+3QXJMRSak8XJXPIE2FKweHYkivAryL5U5K > NKjSEKZ2cCt8Q9DGe3DcZ/cdlqLTpjjOHf6eHolHLv1H+LfuZcZ3IteERZnwl4Cw > ENRk8miZow/nTey63jS5742jzFC8/+bXBRRCdoFSFLVlwKdkhXibl4XNpIuHlHd9 > ns29e6zj5eQ5n7yKS9SrmDIBY1SqCN64zP/le8WnhSkG2fbfPighHWoFSM/8I1jo > eniD4YoBWu3IfXmcun6mRNV3bo1qK4gFeA0nSSxxpPwt80TThXLiQ5WExoCFTZZy > 7XmhZ+UMQHtOTBM+dh11d7aDIflvJC6ROIpLmfF/RHGco/W5tXdNDuDvFMEoGyn7 > Xa8GXmeD+4h01LrNnnzFw4onHFQdG5WddnR9aZMKDL1UeDjILKxdzcGEZqy8kWyZ > wJrftw+ujTo7ESat+s073r4f41VmTwXBfszC+sk+XJEUehX3EBUsdIHEl54T9Kqt > 6pDI+jV+hce3KdstJKzvzz+aLSwbjWibo+dsys43omPn0BvR2RfCATy2EMafUGki > 0T268S4mMOtFG9OmjLra5G2HQrWIrHFHEHWBMH/hN0ZTRhduuTz9hN7z+Fwxo746 > 4GRwG5vHWLYAAaOETYyY > =TAis > -END PGP SIGNATURE- > >
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
On Wed, Jun 30, 2010 at 14:04:33 +0200, yellow protoss wrote: > I assume that it is not coming from the layout but really a but in itself of > X11. > > I tried all kind of layouts, and the TTY work flawless (no X). I guess it > has something to do with X. > The layout (xkbcomp output) you attached in this bug looked just fine, it just wasn't a german layout. There's no evidence of a bug here, so unless you can provide more details and something that makes some sense, I'll close this bug. I don't know what you tried, I don't know your desktop environment, and you don't seem to have even tried to provide coherent explanations. Cheers, Julien signature.asc Description: Digital signature
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
thanks for the reply.
So I tried alomost everything, namely with :
.startup script : with setxkbmap us
and also
.startup script : without any setxkbmap and .startup script empty.
at the start of JWM.
It seems that it comes from X11 + JWM together ... I would suppose.
On Wed, Jun 30, 2010 at 12:13 PM, Julien Cristau wrote:
> On Thu, Jun 17, 2010 at 20:58:49 +0200, yellow protoss wrote:
>
> > I attached the output file.
> > thank you
> > Best regards
> >
> > On Tue, Jun 15, 2010 at 11:33 PM, Julien Cristau >wrote:
> >
> > > On Sat, Jun 12, 2010 at 21:53:30 +0200, yellow protoss wrote:
> > >
> > > > cat /etc/default/keyboard
> > > > # If you change any of the following variables and HAL and X are
> > > > # configured to use this file, then the changes will become visible
> to
> > > > # X only if HAL is restarted. In Debian you need to run
> > > > # /etc/init.d/hal restart
> > > >
> > > > # The following variables describe your keyboard and can have the
> same
> > > > # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions
> options
> > > > # in /etc/X11/xorg.conf.
> > > >
> > > > XKBMODEL="pc105"
> > > > XKBLAYOUT="de"
> > > > XKBVARIANT="nodeadkeys"
> > > > XKBOPTIONS="lv3:ralt_switch"
> > > >
> > > What's the output of 'xkbcomp :0 -'?
> > >
>
> [...]
> > xkb_symbols "pc+us+inet(evdev)+level3(ralt_switch)" {
> >
> This reports a us layout, not de with nodeadkeys... Is your session /
> desktop resetting the layout maybe?
>
> Cheers,
> Julien
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQIcBAEBCAAGBQJMKxi2AAoJEDEBgAUJBeQM6VMQAJpIoeZFI+YzqFcifSeSFXz4
> g5u1ad8eAB4Yk2opaPo7qV2gUyPFhp8GiqeKJ7XRFecwhXLxJrT01J4Rd8CTm/qI
> JFWOskcKmIOjH7u5x1Jyy73XoLAP/J543UJKM+f/yTrgWvZ8tzFsqc6C1hVL34q7
> pWi8So3ymPVuOrcqmsv6vWEMasAiAXD6Intb0FrVt3HQhETv0Ycum8KG+YURz+UH
> eQOTk1QhZVg3eJssq4MAbOfSeo+mwELcbENBoL4ClbuZhIiv1aZ8B2IuR4go2IO5
> xSI6QM5prSAiVw34A8XjQvUHwaJSp7VD/tJU2Kaf6ZvIY+WT+L3X41cXglSt1A1+
> rNWeaUwOIPhSv1XfDMsof2xNxQpzToWbMd7od5uJhXeIN5Og6A+MwnSjl7JNyY1K
> dN4T41q/SFKtsnlaxXt3+WnC6WAO3URCzOuBbeoYf2Pa2n5NmSGprZxE2PQpfMv8
> /pTUjw9EYkwFOz7VEcbP/q3IG+YfdwvGP/UYhZaYFKK3xnPCSS0ByHjKs3eS7Ru7
> t605qwVHNFIzessrp4RtHmtVJsC+taDlih+6ouECnoErrSkd3OZ+Fp15iHUTX2LT
> jHQ5sAIHMsVhSalAAVgXNiENtxb+xAXrH7mpaMjgOfLI1rElQTd/Y7qk2g15ma9g
> vY0jWlUYAQUiQFIpu7BZ
> =g/aV
> -END PGP SIGNATURE-
>
>
Processed: severity of 587618 is normal, tagging 587618
Processing commands for cont...@bugs.debian.org: > severity 587618 normal Bug #587618 [xserver-xorg] xserver-xorg: Periodically x switches between virual desktops randomly and at speed Severity set to 'normal' from 'important' > tags 587618 moreinfo Bug #587618 [xserver-xorg] xserver-xorg: Periodically x switches between virual desktops randomly and at speed Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 587618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12778986678727.transcr...@bugs.debian.org
Bug#587618: xserver-xorg: Periodically x switches between virual desktops randomly and at speed
On Wed, Jun 30, 2010 at 12:20:16 +0100, Ben Whyte wrote: > Package: xserver-xorg > Version: 1:7.5+6 > Severity: important > > > When using X I frequently get rapid switching of workspaces within fluxbox, > on running xev, I see _WIN_workspace and also _net_wn_desktop appear > > I am running fluxbox if that is relevant. > Sounds unlikely to be an X bug. Please provide the output of xinput list and xinput test-xi2 when that happens. Cheers, Julien signature.asc Description: Digital signature
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
On Wed, Jun 30, 2010 at 13:39:57 +0200, yellow protoss wrote: > thanks for the reply. > > So I tried alomost everything, namely with : > > .startup script : with setxkbmap us > > and also > .startup script : without any setxkbmap and .startup script empty. > > at the start of JWM. > > It seems that it comes from X11 + JWM together ... I would suppose. > Well there doesn't seem to be a bug in X here. If you're using a us layout then there's nothing for altgr to do. If you want to use de(nodeadkeys) then don't set the keymap to us... Cheers, Julien signature.asc Description: Digital signature
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
Dear Sir, Regarding teh bug, since the issue remained, I recently bought a new keyboard because of the non working altgr. So I choosed a PS2, could manage to find one, logitech, for 50 euros. And unfortunatley, the keyboard is not working either... so I am so sorry about it. So the other one didnt work either, this altgr. This means that I have 2 keyboards that arent working for this altgr. I am considering teh fact that it is not the keyboard now itself. Could it be X11 itself ? I mean I am using JWM as windows manager on this computer, and visibly hte altgr works when I am under TTY1,2,... when I press alt ctrl F1 best regards Yellow On Thu, Jun 17, 2010 at 8:58 PM, yellow protoss wrote: > > I attached the output file. > thank you > Best regards > > On Tue, Jun 15, 2010 at 11:33 PM, Julien Cristau wrote: > >> On Sat, Jun 12, 2010 at 21:53:30 +0200, yellow protoss wrote: >> >> > cat /etc/default/keyboard >> > # If you change any of the following variables and HAL and X are >> > # configured to use this file, then the changes will become visible to >> > # X only if HAL is restarted. In Debian you need to run >> > # /etc/init.d/hal restart >> > >> > # The following variables describe your keyboard and can have the same >> > # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options >> > # in /etc/X11/xorg.conf. >> > >> > XKBMODEL="pc105" >> > XKBLAYOUT="de" >> > XKBVARIANT="nodeadkeys" >> > XKBOPTIONS="lv3:ralt_switch" >> > >> What's the output of 'xkbcomp :0 -'? >> >> Cheers, >> Julien >> >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.10 (GNU/Linux) >> >> iQIcBAEBCAAGBQJMF/GhAAoJEDEBgAUJBeQMskYP/iWnyZ9MATyfAqTBsKnokJL1 >> RTvBQEeKmQnVkSDQTzfx37/d5NA78KcaTnUNoqxTB6Fn+43WpDtIWJslNb8Z0TnC >> aZTuFhKtgCXlYbcvMbrB5kDXYfSYQ/blLxX69jRcGO49jo0dLq6oMIg3fCaA50Qi >> BywcsEnR1wmtzSBCsjsWd4RmfGVVVKX9Rg9woDAnhQJG7rNekcKL3TDst01bu/Ey >> FF5y0cCUs0oAHpYlc7YlyGFb55UOeiIFaZcjjnckVs2bMH2MMJ0tVoKjkMS9E2FR >> P6l2jEQEh5QXiRtTX8MXZQQn8G8O4ekS9lvmcA+Nr8SNyOBJ0dqYMsjI2LopxEK+ >> O0BW9IH6G0X18y4MtougX8Kw/vD6x/4vFQ3gL7EdzUugz9igpLHhcCkzZVZPBVk6 >> Q/bGytsmHVuKvoiDgwEEGCcRVHEEuZErvJRsQZeMedtMUf9vLLSo3V5vI36lM3i8 >> glVW9DIsGJPDBpIeJaeyzFeP0by2G0Hhjd5wsiTNJ+Q94Nd4C2mgMdFMRh/BEVIk >> ylRBfn64ev60QvGiRvOBZRPnup/tpvPi5C14hhgb1PHLxKpVTUQcPXgvv4O6GmTB >> yEcvgE+CmBeLxNjHxCKx0zwGyeeb9/Tu2xwMBUMn/1ygT9hougGH2tyZnwQW1XNU >> vsnuYORQWxwqv3IO6esP >> =CVvd >> -END PGP SIGNATURE- >> >> >
Bug#585067: keyboard-configuration: No alt+gr keys working after some time
On Thu, Jun 17, 2010 at 20:58:49 +0200, yellow protoss wrote:
> I attached the output file.
> thank you
> Best regards
>
> On Tue, Jun 15, 2010 at 11:33 PM, Julien Cristau wrote:
>
> > On Sat, Jun 12, 2010 at 21:53:30 +0200, yellow protoss wrote:
> >
> > > cat /etc/default/keyboard
> > > # If you change any of the following variables and HAL and X are
> > > # configured to use this file, then the changes will become visible to
> > > # X only if HAL is restarted. In Debian you need to run
> > > # /etc/init.d/hal restart
> > >
> > > # The following variables describe your keyboard and can have the same
> > > # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
> > > # in /etc/X11/xorg.conf.
> > >
> > > XKBMODEL="pc105"
> > > XKBLAYOUT="de"
> > > XKBVARIANT="nodeadkeys"
> > > XKBOPTIONS="lv3:ralt_switch"
> > >
> > What's the output of 'xkbcomp :0 -'?
> >
[...]
> xkb_symbols "pc+us+inet(evdev)+level3(ralt_switch)" {
>
This reports a us layout, not de with nodeadkeys... Is your session /
desktop resetting the layout maybe?
Cheers,
Julien
signature.asc
Description: Digital signature
