Bug#696272: xserver-xorg-core: BadImplementation error with XIAllDevices or XIAllMasterDevices deviceid used in libxi XISelectEvents eventmask
On Sun, 2013-03-03 at 19:06 +0100, Julien Cristau wrote: > On Sun, Mar 3, 2013 at 18:20:15 +0100, Sjoerd Simons wrote: > > > Package: xserver-xorg-core > > Version: 2:1.12.4-5 > > Followup-For: Bug #696272 > > > > As extra info when using gnome-shell 3.7 this is triggered in existing > > application (epiphany and empathy at least). Upstream commit to fix this is > > 314776eb369ca2e438907795ae030dd743c281fc > > > Can't those applications and/or gnome-shell work around the X bug? I'm not sure. In principle it's possible by hacking mutter/gnome-shell to not select for touch events (on older X servers?). And/or by having apps ignore BadImplementation (or also avoid selecting on TouchBegin). Both would be relatively ugly though. The problem with this one is though that it can be triggered by random combinations of applications, so not just gnome/shell & gnome apps. -- Sjoerd Simons -- 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/1362382413.27736.11.ca...@dusk.luon.net
Bug#702212: suggestion for inclusion: x-on-resize
Package: x11-xserver-utils Version: 7.7~3 Severity: wishlist some days ago, a program called "x-on-resize" was published[1], which complements xrandr with a listening mode: x-on-resize keeps running and prints text or executes other scripts as soon as the X configuration changes. as it is a useful x11 utility and comes in a similar form factor as other x11-xserver-utils (eg xrandr itself), i'd like to suggest it for inclusion here. please let me know if you'll accept this or not, for otherwise i'll file an itp for a dedicated package. x-on-resize is of special interest to me as it might be a future recommendation of my arandr package, which has implementing this feature in its todo list. best regards chrysn [1] http://keithp.com/blogs/x-on-resize/ signature.asc Description: Digital signature
Mesa 9 for wheezy-backports?
Is anybody working on packaging / documenting installation of Mesa 9.X on Wheezy? I want to help out if I can for documenting Mesa 9 in Wheezy. I noticed this guide: http://x.debian.net/howto/build-mesa.html Does not seem to work anymore because of new versions of Mesa upstream.. You now need to compile drm as well. Some of the ./configure flags in that guide for mesa don't exist anymore. I was able to successfully compile drm + mesa 9 (32-bit) in Debian Wheezy (64-bit/multiarch) in order to run Steam (32-bit proprietary binary) software well on Intel Ivy Bridge hardware. * Many users of the radeon open source drivers get significant performance gains when running Mesa 9.X. * People running Intel graphics on Ivy Bridge or Sandy Bridge graphics chips /need/ to run Mesa 9.X or they will get severe graphical glitches in Team Fortress 2 and some other very popular Steam games to the point where they aren't playable. In case anybody is interested, I started using this guide here: http://x.debian.net/howto/build-mesa.html. I followed those directions until I started compiling Mesa and it failed because the drm version was too old. So then I started following this guide here: http://dri.freedesktop.org/wiki/Building#Building_libdrm Which worked great for building a 64-bit mesa on my 64-bit Wheezy, but that wasn't what I needed.. So I got some help from some forums and installed the following build dependencies... libudev:i386 libxcb-dri2-0-dev:i386 libxcb-glx0-dev:i386 libxdamage-dev:i386 libxfixes-dev:i386 libx11-xcb-dev:i386 libxext-dev:i386 libcairo2-dev:i386 libfontconfig1-dev:i386 pkg-config:i386 libpciaccess-dev:i386 libc6-dev:i386 gcc-multilib g++-multilib gcc:i386 c-compiler:i386 Then changed the compile flags.. export CFLAGS="-m32" export CXXFLAGS="-m32" ./autogen.sh \ --enable-driglx-direct \ --enable-gles-overlay \ --enable-gles1 \ --enable-gles2 \ --enable-glx-tls \ --with-driver=dri \ --with-dri-driverdir=/usr/lib/dri \ --with-egl-platforms='drm x11' \ --with-state-trackers=egl,glx,dri,vega \ --with-dri-drivers=i965 \ --enable-32-bit \ --disable-64-bit \ --enable-gallium-llvm=disabled \ --enable-gallium-gbm=disabled \ --enable-gallium-egl=disabled \ --with-gallium-drivers= \ --build=i686-pc-linux-gnu \ After that, I was able to build Mesa 9 (32-bit) for Intel Ivy Bridge graphics, no problem. Not sure if that's useful to anybody, but I hope that it is. Running Ivy Bridge graphics, previously Team Fortress 2 (32-bit proprietary binary) would have a big green square from the introduction movie and then go to a black screen with graphical glitches for the menu.. Now the game runs perfectly fine and smooth at 1920x1080 resolution and medium graphics settings with Mesa 9 from git using open source Intel graphics! Cheers and thanks for your time. -David Smith
Processed (with 1 errors): Re: Cannot start luvcview - SDL error
Processing commands for cont...@bugs.debian.org: > forcemerge 292388 522876 Bug #292388 [libx11-6] libx11-6: XOpenDisplay says "XDM authorization key matches an existing client!" Bug #522876 [libx11-6] Cannot start luvcview - SDL error Marked as found in versions xfree86/4.3.0.dfsg.1-10 and libx11/2:1.1.4-2. Added tag(s) upstream. Bug #522876 [libx11-6] Cannot start luvcview - SDL error Ignoring request to alter found versions of bug #522876 to the same values previously set Unable to complete merge on previous attempt; trying again (retry: 2) Bug #522876 [libx11-6] Cannot start luvcview - SDL error Ignoring request to alter found versions of bug #522876 to the same values previously set Unable to complete merge on previous attempt; trying again (retry: 3) Bug #522876 [libx11-6] Cannot start luvcview - SDL error Ignoring request to alter found versions of bug #522876 to the same values previously set After four attempts, the following changes were unable to be made: found_versions of #522876 is 'xfree86/4.3.0.dfsg.1-10 libx11/2:1.1.4-2' not '4.3.0.dfsg.1-10 libx11/2:1.1.4-2' Failed to forcibly merge 292388: Unable to modify bugs so they could be merged. > End of message, stopping processing here. Please contact me if you need assistance. -- 292388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292388 522876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522876 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.13623563224242.transcr...@bugs.debian.org
Bug#700015: libx11-6: crashes on systems using Mali graphics
Hello I moved gnome-shell to /usr/local/bin and use this script instead: #!/bin/sh gdb -ex 'break main' -ex 'r' -ex 'call XInitThreads()' -ex 'c' -ex 'bt full' -ex 'quit' --args /usr/local/bin/gnome-shell.distrib "$@" HTH Michal -- 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/caomqctqyhw+bn73ds-e_dg8u5y7md75h934dqvp4_-mhz+m...@mail.gmail.com
Bug#700015: libx11-6: crashes on systems using Mali graphics
четверг, 7 февраля 2013 г., 16:40:02 UTC+4 пользователь Michal Suchanek написал: > Package: libx11-6 > > Version: 2:1.5.0-1 > > Severity: important > > > > Hello, > > > > the Mali gles library uses threads internally. > > > > The interface to the user program should be single-threaded, however. > > > > Programs linked to libx11 and libgles seem to crash due to locking some > > non-existent mutex. Hello. I have same trouble. Any ideas how to fix it or workaround? -- 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/0172bed6-edb8-478a-917e-56e5e35b0...@googlegroups.com
xorg-server: Changes to 'debian-unstable'
Xi/xiselectev.c |9 +++-- debian/changelog |7 +++ 2 files changed, 14 insertions(+), 2 deletions(-) New commits: commit 2b1356632de667a7f2d05c7e5e5c659902779746 Author: Julien Cristau Date: Sun Mar 3 19:14:25 2013 +0100 Changelog entry diff --git a/debian/changelog b/debian/changelog index 228dc7c..f844f77 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +xorg-server (2:1.12.4-6) UNRELEASED; urgency=low + + * Touch: Fix duplicate TouchBegin selection with virtual devices +(closes: #696272) + + -- Julien Cristau Sun, 03 Mar 2013 19:13:57 +0100 + xorg-server (2:1.12.4-5) unstable; urgency=low * dmx: don't include dmx-config.h from xdmxconfig (closes: #495816) commit e603961447cd2ca69aa070db7bdf0d6af8aac759 Author: Daniel Stone Date: Fri Sep 7 18:17:46 2012 +0100 Touch: Fix duplicate TouchBegin selection with virtual devices Given the following scenario: 1) client A selects for TouchBegin on window W for device D 2) client B selects for TouchBegin on window W for XIAllDevices 3) client C selects for TouchBegin on window W with device E Step 3 will fail with BadImplementation, because attempting to look up XIAllDevices or XIAllMasterDevices with dixLookupDevices doesn't work. This should succeed (or, if it was selecting for device D, fail with BadAccess as it would be a duplicate selection). Fix this by performing the appropriate lookup for virtual devices. Signed-off-by: Daniel Stone Reviewed-by: Chase Douglas (cherry picked from commit 3d2b768efae9936c6929c2bc13c7a1acc074ecd3) [jcristau: backport to 1.12.x, tmp vs dummy variable names] Conflicts: Xi/xiselectev.c diff --git a/Xi/xiselectev.c b/Xi/xiselectev.c index 43a67c8..07d3218 100644 --- a/Xi/xiselectev.c +++ b/Xi/xiselectev.c @@ -180,8 +180,13 @@ ProcXISelectEvents(ClientPtr client) if (CLIENT_ID(iclient->resource) == client->index) continue; -dixLookupDevice(&dummy, evmask->deviceid, serverClient, -DixReadAccess); +if (evmask->deviceid == XIAllDevices) +dummy = inputInfo.all_devices; +else if (evmask->deviceid == XIAllMasterDevices) +dummy = inputInfo.all_master_devices; +else +dixLookupDevice(&dummy, evmask->deviceid, serverClient, +DixReadAccess); if (!dummy) return BadImplementation; /* this shouldn't happen */ -- 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/e1ucdqv-00066s...@vasks.debian.org
Processed: limit source to xorg-server, tagging 696272
Processing commands for cont...@bugs.debian.org: > #xorg-server (2:1.12.4-6) UNRELEASED; urgency=low > # > # * Touch: Fix duplicate TouchBegin selection with virtual devices > #(closes: #696272) > # > limit source xorg-server Limiting to bugs with field 'source' containing at least one of 'xorg-server' Limit currently set to 'source':'xorg-server' > tags 696272 + pending Bug #696272 [xserver-xorg-core] xserver-xorg-core: BadImplementation error with XIAllDevices or XIAllMasterDevices deviceid used in libxi XISelectEvents eventmask Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 696272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696272 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.136233453215030.transcr...@bugs.debian.org
Bug#696272: xserver-xorg-core: BadImplementation error with XIAllDevices or XIAllMasterDevices deviceid used in libxi XISelectEvents eventmask
On Sun, Mar 3, 2013 at 18:20:15 +0100, Sjoerd Simons wrote: > Package: xserver-xorg-core > Version: 2:1.12.4-5 > Followup-For: Bug #696272 > > As extra info when using gnome-shell 3.7 this is triggered in existing > application (epiphany and empathy at least). Upstream commit to fix this is > 314776eb369ca2e438907795ae030dd743c281fc > Can't those applications and/or gnome-shell work around the X bug? Cheers, Julien signature.asc Description: Digital signature
