xorg-server: Changes to 'ubuntu'
debian/changelog | 15 +++ 1 file changed, 15 insertions(+) New commits: commit e082a6cb0d7c9fc5a33aaa3535ba315d93ac352f Author: Maarten Lankhorst m.b.lankho...@gmail.com Date: Mon May 21 19:41:19 2012 +0200 Refresh patches to apply on x-server 1.12 AKA fix up mess * Refresh patches to apply on x-server 1.12 - patch-x-indent.sh from xorg-pkg-tools was used to redo coding style * Deleted following patches because they have been committed upstream - 224_return_BadWindow_not_BadMatch.diff - 225_non-root_config_paths.patch - 505_query_pointer_touchscreen.patch - 506_touchscreen_pointer_emulation_checks.patch - 507_touchscreen_fixes.patch * Non-trivial refresh of 500_pointer_barrier_thresholds.diff, based on xorg-edgers * Rest was refreshed with patch-x-indent.sh to survive coding style changes diff --git a/debian/changelog b/debian/changelog index e54c296..9b56bf9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,18 @@ +xorg-server (2:1.12.1.902-1ubuntu1) UNRELEASED; urgency=medium + + * Refresh patches to apply on x-server 1.12 +- patch-x-indent.sh from xorg-pkg-tools was used to redo coding style + * Deleted following patches because they have been committed upstream +- 224_return_BadWindow_not_BadMatch.diff +- 225_non-root_config_paths.patch +- 505_query_pointer_touchscreen.patch +- 506_touchscreen_pointer_emulation_checks.patch +- 507_touchscreen_fixes.patch + * Non-trivial refresh of 500_pointer_barrier_thresholds.diff, based on xorg-edgers + * Rest was refreshed with patch-x-indent.sh to survive coding style changes + + -- Maarten Lankhorst maarten.lankho...@canonical.com Mon, 21 May 2012 21:08:48 +0200 + xorg-server (2:1.12.1.902-1) unstable; urgency=medium [ Julien Cristau ] -- 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/e1swjmm-0003uw...@vasks.debian.org
Bug#673170: xfonts-100dpi: fonts not available until X restarted
On Mon, May 21, 2012 at 16:06:44 -0500, Jonathan Nieder wrote: Hi Julien, Julien Cristau wrote: On Wed, May 16, 2012 at 10:59:01 -0500, Jonathan Nieder wrote: Trying to address http://bugs.debian.org/563250 (xvile appearance wrong due to missing font), I installed xfonts-100dpi. Alas: $ xmessage -fn lucidasans-10 It was the best of times Warning: Cannot convert string lucidasans-10 to type FontStruct $ xlsfonts | grep lucida $ Restarting X makes the font show up. [...] Not really. Run xset fp rehash after installing fonts, there's no way for update-fonts-dir to know which (possibly remote) X server may want to use the new fonts. Perhaps this could be documented somewhere, or it could be automatically done by the calling maintainer script for the local X server? The problem is still present: after installing X fonts on a pretty ordinary setup, they are not available for use. Most new users are not going to know about xset fp rehash. They're also not going to be using xmessage, and client-side fonts are immediately picked up by fontconfig/xft/... on install. So I think this is a non-issue. Cheers, Julien -- 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/20120522074418.gc25...@coloquinte.cristau.org
Bug#673170: xfonts-100dpi: fonts not available until X restarted
Julien Cristau wrote: On Mon, May 21, 2012 at 16:06:44 -0500, Jonathan Nieder wrote: Julien Cristau wrote: On Wed, May 16, 2012 at 10:59:01 -0500, Jonathan Nieder wrote: Trying to address http://bugs.debian.org/563250 (xvile appearance wrong due to missing font), I installed xfonts-100dpi. Alas: [...] $ xlsfonts | grep lucida $ [...] Perhaps this could be documented somewhere, or it could be automatically done by the calling maintainer script for the local X server? The problem is still present: after installing X fonts on a pretty ordinary setup, they are not available for use. Most new users are not going to know about xset fp rehash. They're also not going to be using xmessage, and client-side fonts are immediately picked up by fontconfig/xft/... on install. So I think this is a non-issue. That would be a reason not to package xfonts-100dpi at all, right? I was using xmessage and xlsfonts to debug. The actual affected program was xvile. I can imagine users running into this problem with xterm as well. Should I reassign this to xfonts-100dpi where it can be ignored until someone has time for it, or to debhelper (dh_installfonts) which is probably the right place to fix it? Thanks for your help, Jonathan -- 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/20120522074934.GE4486@burratino
Re: Upgrade Xorg in testing with driver ATI proprietary : segment fault in xorg.
Hi, Xavier Manach x...@tekio.org (22/05/2012): I made an wheezy install there is 5 days (2012/05/17). I installed ATI driver with the last ATI proprietary. you would have to talk to the maintainers of that proprietary driver, we don't maintain that. (On a related note, http://bugs.debian.org/671320 suggests that this driver still doesn't work with X 1.12 (lol); so your methodology is flawed in that there's no appropriate dependency on the server, so you can't notice that fact on your own.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#673837: Bug#673839: Building an udeb binary
Le 21/05/2012 21:17, Cyril Brulebois a écrit : It looks to me like a separate build is better as far as d-i is concerned. Ok, the question is rather can we add 45k worth of udeb to make working on GTK3 easier in Debian (i.e reduce the build time a lot by building it only once), the extra ram usage doesn't seem like it would push requirements higher in any visible way. The cost seemed small to me and the benefit valuable for people working on GTK but maybe udeb are restricted over what I though they were (seems to be the case from this discussion) In any case I made my point so it's your call at the end Cheers, Sebastien Bacher -- 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/4fbb6dae.9080...@ubuntu.com
Re: Upgrade Xorg in testing with driver ATI proprietary : segment fault in xorg.
Hi again Xavier, (I'm Ccing the list since I don't want to repeat myself next time someone asks about that stupid driver.) Xavier Manach x...@tekio.org (22/05/2012): I understand that proprietary driver don't interresting you. It's sad because It's worked there is 5 days and lastest change in xorg package broke it. What is sad is: (1) it's proprietary (2) it's not keeping up with X development (3) (1) means we can't help them fix (2) How can I get simply older version of packages ? Downgrade xserver-xorg-core to 1.11 (you can find it on snapshot.debiban.org), it's built from the xorg-server package. You'll need drivers compatible with this version, too. Have you some documentation for - get all xorg packages from git (or other). - get all xorg sources packages from git (or other) and build package and test it ? The problem isn't X. The problem is that fglrx hasn't been updated to work with X 1.12; so newer snapshots from git won't help at all. I will try to found the change that cause this segfault. That's called video ABI changes. Can you give me an advise about package I should try first ? Something that changed in the version commited the last days that can cause a segfault... Use radeon in the meanwhile, removing all traces of fglrx from your system, problem solved (a reboot is probably needed to make the removal effective). Mraw, KiBi. signature.asc Description: Digital signature
Re: Upgrade Xorg in testing with driver ATI proprietary : segment fault in xorg.
Hi. Thanks for explain me this again :) This time, I probably understood. I will try two new install for compare, on with the downgrade with 1.11 with proprietary driver and other with free driver radeon. Sorry, for be so noob ;) A++ Xav. 2012/5/22 Cyril Brulebois k...@debian.org Hi again Xavier, (I'm Ccing the list since I don't want to repeat myself next time someone asks about that stupid driver.) Xavier Manach x...@tekio.org (22/05/2012): I understand that proprietary driver don't interresting you. It's sad because It's worked there is 5 days and lastest change in xorg package broke it. What is sad is: (1) it's proprietary (2) it's not keeping up with X development (3) (1) means we can't help them fix (2) How can I get simply older version of packages ? Downgrade xserver-xorg-core to 1.11 (you can find it on snapshot.debiban.org), it's built from the xorg-server package. You'll need drivers compatible with this version, too. Have you some documentation for - get all xorg packages from git (or other). - get all xorg sources packages from git (or other) and build package and test it ? The problem isn't X. The problem is that fglrx hasn't been updated to work with X 1.12; so newer snapshots from git won't help at all. I will try to found the change that cause this segfault. That's called video ABI changes. Can you give me an advise about package I should try first ? Something that changed in the version commited the last days that can cause a segfault... Use radeon in the meanwhile, removing all traces of fglrx from your system, problem solved (a reboot is probably needed to make the removal effective). Mraw, KiBi. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk+7ce4ACgkQeGfVPHR5Nd1pcQCeKPUD1NUH9ZuImjH7Wh+KLY2G XHUAmwbzPgQkEVyNX9CFN63NcgRw3o/h =Int5 -END PGP SIGNATURE-
Bug#581398: kde4-window-decorator crash when starting
Still broken after all these years. Application: KDE Window Decorator (kde4-window-decorator), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [KCrash Handler] #6 0xb6e7579b in QRasterWindowSurface::~QRasterWindowSurface (this=0x9759860, __in_chrg=optimized out) at painting/qwindowsurface_raster.cpp:117 #7 0xb6e75832 in QRasterWindowSurface::~QRasterWindowSurface (this=0x9759860, __in_chrg=optimized out) at painting/qwindowsurface_raster.cpp:121 #8 0xb6e90ce4 in QWidgetBackingStore::~QWidgetBackingStore (this=0x976be40, __in_chrg=optimized out) at painting/qbackingstore.cpp:909 #9 0xb6c99fbc in QWidgetBackingStoreTracker::destroy (this=0x9779660) at kernel/qwidget.cpp:217 #10 0xb6c9a118 in QWidgetPrivate::deleteExtra (this=0x96d57a8) at kernel/qwidget.cpp:1830 #11 0xb6c9a32c in QWidgetPrivate::~QWidgetPrivate (this=0x96d57a8, __in_chrg=optimized out) at kernel/qwidget.cpp:357 #12 0xb6c9a642 in QWidgetPrivate::~QWidgetPrivate (this=0x96d57a8, __in_chrg=optimized out) at kernel/qwidget.cpp:362 #13 0xb68ef0cb in cleanup (pointer=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #14 ~QScopedPointer (this=0x96247ec, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #15 QObject::~QObject (this=0x96247e8, __in_chrg=optimized out) at kernel/qobject.cpp:817 #16 0xb6c9c50d in QWidget::~QWidget (this=0x96247e8, __in_chrg=optimized out) at kernel/qwidget.cpp:1551 #17 0xb5e2dc0a in ?? () from /usr/lib/libplasma.so.3 #18 0xb5e94c4b in ?? () from /usr/lib/libplasma.so.3 #19 0xb5e936cb in Plasma::Theme::~Theme() () from /usr/lib/libplasma.so.3 #20 0xb5e93a89 in ?? () from /usr/lib/libplasma.so.3 #21 0xb5da19e9 in ?? () from /usr/lib/libplasma.so.3 #22 0xb5a9c50f in __run_exit_handlers (status=0, listp=0xb5bc6324, run_list_atexit=true) at exit.c:78 #23 0xb5a9c57f in *__GI_exit (status=0) at exit.c:100 #24 0xb5a83e4e in __libc_start_main (main=0x804fe30, argc=2, ubp_av=0xbfc2ad44, init=0x8064550, fini=0x8064540, rtld_fini=0xb77f0300, stack_end=0xbfc2ad3c) at libc-start.c:260 #25 0x08050ab5 in ?? () The latest stable release of Compiz is 0.8.8, while the current debian version is 0.8.4-5.1, so I don't know how much sympathy there would be from the Compiz people. Anyone know how it is that debian _unstable_ is a couple of years and four minor releases behind upstream? Is this ultimately a bug in the Qt libraries? There is also idle curiosity here, http://forums.debian.net/viewtopic.php?f=6t=73980 KDE + compiz crashes kde4 window decorator http://ubuntuforums.org/showthread.php?t=1475164 KDE4 Window Decorator Crashes with Compiz in Lucid Lynx 10.04 This is a thread to discuss Bug #572780 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/572780 KDE4 Window Decorator Crashes with Compiz in Lucid Lynx 10.04 James -- 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/e1swtzw-00068j...@jasper.nurealm.net
Bug#581398: kde4-window-decorator crash when starting
James ja...@jasper.nurealm.net (22/05/2012): Anyone know how it is that debian _unstable_ is a couple of years and four minor releases behind upstream? Because nobody has shown any interest in working on it? Are you volunteering? Mraw, KiBi. signature.asc Description: Digital signature
xserver-xorg-input-vmmouse: Changes to 'upstream-unstable'
configure.ac |6 +++---
src/vmmouse.c | 21 +
tools/69-xorg-vmmouse.rules.in |2 +-
3 files changed, 25 insertions(+), 4 deletions(-)
New commits:
commit 3a828d876772d05577b9372e8f6dc068794f4704
Author: Jakob Bornecrantz ja...@vmware.com
Date: Tue May 22 20:14:25 2012 +0200
vmmouse 12.8.0
Signed-off-by: Jakob Bornecrantz ja...@vmware.com
diff --git a/configure.ac b/configure.ac
index 33fbd64..d2fb0b6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -22,7 +22,7 @@
AC_PREREQ(2.57)
AC_INIT([xf86-input-vmmouse],
-[12.8.0],
+[12.9.0],
[https://bugs.freedesktop.org/enter_bug.cgi?product=xorg],
xf86-input-vmmouse)
commit 2a321a39350aa020a8103813bed61ff559088195
Author: Zack Rusin za...@vmware.com
Date: Thu May 10 19:55:01 2012 -0400
Revert Adjust the kernel name in the udev file.
This reverts commit 189dc266a66485d48303acbc1a4fbe4642c75e9f.
It seems that for some reason the device routing is breaking with this.
Possibly related to Win7 x64 hosts because it's not reproducible on
GNU/Linux hosts. Semantially we'd still like to match only on mouse
kernel but for the time being this seems to cause more problems
than it solves. Hence the revert.
diff --git a/tools/69-xorg-vmmouse.rules.in b/tools/69-xorg-vmmouse.rules.in
index 9af3938..602afb6 100644
--- a/tools/69-xorg-vmmouse.rules.in
+++ b/tools/69-xorg-vmmouse.rules.in
@@ -1 +1 @@
-ACTION==add|change, ENV{ID_INPUT_MOUSE}==?*, ATTRS{description}==i8042
AUX port, KERNEL==mouse[0-9]*, PROGRAM=__BIN_PREFIX__/vmmouse_detect,
ENV{ID_INPUT.tags}=vmmouse
+ACTION==add|change, ENV{ID_INPUT_MOUSE}==?*, ATTRS{description}==i8042
AUX port, KERNEL==event[0-9]*, PROGRAM=__BIN_PREFIX__/vmmouse_detect,
ENV{ID_INPUT.tags}=vmmouse
commit 55efac85ca9bd2041240ca29316ca716ddc2185d
Author: Gaetan Nadon mems...@videotron.ca
Date: Tue May 1 16:20:59 2012 -0400
config: replace obsolete AM_CONFIG_HEADER with AC_CONFIG_HEADERS
Moved up in the autoconf init section.
It has been removed from Automake 1.12.
Signed-off-by: Gaetan Nadon mems...@videotron.ca
Signed-off-by: Zack Rusin za...@vmware.com
diff --git a/configure.ac b/configure.ac
index 5938ca7..33fbd64 100644
--- a/configure.ac
+++ b/configure.ac
@@ -28,6 +28,8 @@ AC_INIT([xf86-input-vmmouse],
AC_CONFIG_SRCDIR([Makefile.am])
AC_CONFIG_AUX_DIR(.)
+AC_CONFIG_HEADERS([config.h])
+
AM_INIT_AUTOMAKE([foreign dist-bzip2])
AM_MAINTAINER_MODE
@@ -41,8 +43,6 @@ XORG_DEFAULT_OPTIONS
DRIVER_NAME=vmmouse
AC_SUBST([DRIVER_NAME])
-AM_CONFIG_HEADER([config.h])
-
# Checks for programs.
AC_DISABLE_STATIC
AC_PROG_LIBTOOL
commit 840dcbf947dd9d1383777c3cd811ff680cef5f16
Author: Michal Srb m...@suse.com
Date: Thu May 3 17:55:24 2012 +0200
Enable hardware access during vmmouse preinit.
Vmmouse driver uses outl calls but never requests hardware access.
In case there are no other drivers that requests it, vmmouse
initialization will fail. (Found on KVM virtual machine with fbdev
graphics driver and vmmouse input driver.)
Request hardware access in same way xf86-input-keyboard does.
Signed-off-by: Zack Rusin za...@vmware.com
diff --git a/src/vmmouse.c b/src/vmmouse.c
index 285ba26..7778923 100644
--- a/src/vmmouse.c
+++ b/src/vmmouse.c
@@ -65,6 +65,7 @@
#include xf86Xinput.h
#include xf86_OSproc.h
#include xf86OSmouse.h
+#include xf86Priv.h
#include compiler.h
#if GET_ABI_MAJOR(ABI_XINPUT_VERSION) = 7
@@ -339,6 +340,16 @@ VMMousePreInit(InputDriverPtr drv, IDevPtr dev, int flags)
#endif
/*
+* enable hardware access
+*/
+ if (!xorgHWAccess) {
+ if (xf86EnableIO())
+ xorgHWAccess = TRUE;
+ else
+ return NULL;
+ }
+
+ /*
* try to enable vmmouse here
*/
if (!VMMouseClient_Enable()) {
@@ -399,6 +410,16 @@ VMMousePreInit(InputDriverPtr drv, InputInfoPtr pInfo, int
flags)
VMMousePrivPtr mPriv = NULL;
int rc = Success;
+ /* Enable hardware access. */
+ if (!xorgHWAccess) {
+ if (xf86EnableIO())
+ xorgHWAccess = TRUE;
+ else {
+ rc = BadValue;
+ goto error;
+ }
+ }
+
#if GET_ABI_MAJOR(ABI_XINPUT_VERSION) = 12
/* For ABI 12, we need to return the wrapped driver's pInfo (see
* above). ABI 12, we call NIDR and are done */
--
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/e1swvok-0001rl...@vasks.debian.org
xserver-xorg-input-vmmouse: Changes to 'debian-unstable'
ChangeLog | 49 +
configure.ac |6 ++---
debian/changelog |8 ++
src/vmmouse.c | 21 +
tools/69-xorg-vmmouse.rules.in |2 -
5 files changed, 82 insertions(+), 4 deletions(-)
New commits:
commit 8e50791ac87c2bccb38958b8ec6bd19de7a984b8
Author: Robert Hooker sarv...@ubuntu.com
Date: Tue May 22 16:35:43 2012 -0400
Bump changelogs.
diff --git a/ChangeLog b/ChangeLog
index 0e850d9..b65c479 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,52 @@
+commit 3a828d876772d05577b9372e8f6dc068794f4704
+Author: Jakob Bornecrantz ja...@vmware.com
+Date: Tue May 22 20:14:25 2012 +0200
+
+vmmouse 12.8.0
+
+Signed-off-by: Jakob Bornecrantz ja...@vmware.com
+
+commit 2a321a39350aa020a8103813bed61ff559088195
+Author: Zack Rusin za...@vmware.com
+Date: Thu May 10 19:55:01 2012 -0400
+
+Revert Adjust the kernel name in the udev file.
+
+This reverts commit 189dc266a66485d48303acbc1a4fbe4642c75e9f.
+
+It seems that for some reason the device routing is breaking with this.
+Possibly related to Win7 x64 hosts because it's not reproducible on
+GNU/Linux hosts. Semantially we'd still like to match only on mouse
+kernel but for the time being this seems to cause more problems
+than it solves. Hence the revert.
+
+commit 55efac85ca9bd2041240ca29316ca716ddc2185d
+Author: Gaetan Nadon mems...@videotron.ca
+Date: Tue May 1 16:20:59 2012 -0400
+
+config: replace obsolete AM_CONFIG_HEADER with AC_CONFIG_HEADERS
+
+Moved up in the autoconf init section.
+It has been removed from Automake 1.12.
+
+Signed-off-by: Gaetan Nadon mems...@videotron.ca
+Signed-off-by: Zack Rusin za...@vmware.com
+
+commit 840dcbf947dd9d1383777c3cd811ff680cef5f16
+Author: Michal Srb m...@suse.com
+Date: Thu May 3 17:55:24 2012 +0200
+
+Enable hardware access during vmmouse preinit.
+
+Vmmouse driver uses outl calls but never requests hardware access.
+In case there are no other drivers that requests it, vmmouse
+initialization will fail. (Found on KVM virtual machine with fbdev
+graphics driver and vmmouse input driver.)
+
+Request hardware access in same way xf86-input-keyboard does.
+
+Signed-off-by: Zack Rusin za...@vmware.com
+
commit e925b2e6e9d548db5a6646a76d513fb6881f69b4
Author: Zack Rusin za...@vmware.com
Date: Thu Mar 8 09:51:48 2012 -0500
diff --git a/debian/changelog b/debian/changelog
index add6cda..30cfa88 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+xserver-xorg-input-vmmouse (1:12.9.0-1) UNRELEASED; urgency=low
+
+ * New upstream bugfix release.
+- Fixes erratic mouse behavior with a Windows x64 host. (LP: #996821)
+- Fixes initialization when no other drivers request hardware access.
+
+ -- Robert Hooker sarv...@ubuntu.com Tue, 22 May 2012 16:30:11 -0400
+
xserver-xorg-input-vmmouse (1:12.8.0-1) unstable; urgency=low
* New upstream release.
commit 3a828d876772d05577b9372e8f6dc068794f4704
Author: Jakob Bornecrantz ja...@vmware.com
Date: Tue May 22 20:14:25 2012 +0200
vmmouse 12.8.0
Signed-off-by: Jakob Bornecrantz ja...@vmware.com
diff --git a/configure.ac b/configure.ac
index 33fbd64..d2fb0b6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -22,7 +22,7 @@
AC_PREREQ(2.57)
AC_INIT([xf86-input-vmmouse],
-[12.8.0],
+[12.9.0],
[https://bugs.freedesktop.org/enter_bug.cgi?product=xorg],
xf86-input-vmmouse)
commit 2a321a39350aa020a8103813bed61ff559088195
Author: Zack Rusin za...@vmware.com
Date: Thu May 10 19:55:01 2012 -0400
Revert Adjust the kernel name in the udev file.
This reverts commit 189dc266a66485d48303acbc1a4fbe4642c75e9f.
It seems that for some reason the device routing is breaking with this.
Possibly related to Win7 x64 hosts because it's not reproducible on
GNU/Linux hosts. Semantially we'd still like to match only on mouse
kernel but for the time being this seems to cause more problems
than it solves. Hence the revert.
diff --git a/tools/69-xorg-vmmouse.rules.in b/tools/69-xorg-vmmouse.rules.in
index 9af3938..602afb6 100644
--- a/tools/69-xorg-vmmouse.rules.in
+++ b/tools/69-xorg-vmmouse.rules.in
@@ -1 +1 @@
-ACTION==add|change, ENV{ID_INPUT_MOUSE}==?*, ATTRS{description}==i8042
AUX port, KERNEL==mouse[0-9]*, PROGRAM=__BIN_PREFIX__/vmmouse_detect,
ENV{ID_INPUT.tags}=vmmouse
+ACTION==add|change, ENV{ID_INPUT_MOUSE}==?*, ATTRS{description}==i8042
AUX port, KERNEL==event[0-9]*, PROGRAM=__BIN_PREFIX__/vmmouse_detect,
ENV{ID_INPUT.tags}=vmmouse
commit 55efac85ca9bd2041240ca29316ca716ddc2185d
Author: Gaetan Nadon mems...@videotron.ca
Date: Tue May 1 16:20:59 2012 -0400
config: replace obsolete AM_CONFIG_HEADER with AC_CONFIG_HEADERS
Moved up in the autoconf init section.
It has been removed from Automake
Bug#581398: kde4-window-decorator crash when starting
Because nobody has shown any interest in working on it? Are you volunteering? Ha! Can you give me a clue about what would be involved? I would naively suppose that all I have to do is download the latest release, add a debian/ directory, and compile the application for a bunch of different architectures - not counting also needing a login on some debian server, to upload the packages. But then, I also suspect that it's not that simple. Still, one step at a time. What's to do? James -- 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/e1swxuu-0007bn...@jasper.nurealm.net
Bug#638542: kernel oops when closing the lid
Hello, I have the same problem on my dell XPS 14z, It has an intel graphic card, Intel® HD Graphics 3000 using i915: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Whenever I close the lid, I have a kernel panic in the i915 driver code. My system is running SID and is up to date, I even tried the kernel from experimental, 3.3. Here the trace from syslog: ay 21 18:20:12 TichoLaptop laptop-mode: Warning: Configuration file /etc/laptop-mode/conf.d/board-specific/*.conf is not readable, skipping. May 21 18:20:12 TichoLaptop laptop-mode: Laptop mode May 21 18:20:12 TichoLaptop laptop-mode: enabled, May 21 18:20:12 TichoLaptop laptop-mode: not active [unchanged] May 21 18:20:15 TichoLaptop kernel: [ 1658.787327] BUG: unable to handle kernel paging request at c9001193396c May 21 18:20:15 TichoLaptop kernel: [ 1658.787415] IP: [812474b8] gen6_write_entry+0x4c/0x4f May 21 18:20:15 TichoLaptop kernel: [ 1658.787493] PGD 1cf023067 PUD 1cf024067 PMD 1c89ee067 PTE 0 May 21 18:20:15 TichoLaptop kernel: [ 1658.787570] Oops: 0002 [#1] SMP May 21 18:20:15 TichoLaptop kernel: [ 1658.787614] CPU 1 May 21 18:20:15 TichoLaptop kernel: [ 1658.787637] Modules linked in: aesni_intel cryptd aes_x86_64 aes_generic acpi_cpufreq mperf cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats bnep rfcomm fuse loop ixgb 8390 8139too mii uvcvideo videodev v4l2_compat_ioctl32 media snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb bluetooth crc16 arc4 sr_mod cdrom iwlwifi snd_hda_intel i915 snd_hda_codec mac80211 snd_hwdep drm_kms_helper cfg80211 drm snd_pcm xhci_hcd snd_page_alloc processor battery dell_wmi dell_laptop ehci_hcd usbcore rfkill rts_pstor(C) snd_timer i2c_algo_bit i2c_i801 dcdbas iTCO_wdt i2c_core iTCO_vendor_support snd ac psmouse sparse_keymap serio_raw power_supply button soundcore video atl1c usb_common wmi thermal_sys evdev pcspkr ext3 mbcache jbd sd_mod crc_t10dif ahci libahci libata scsi_mod May 21 18:20:15 TichoLaptop kernel: [ 1658.788707] May 21 18:20:15 TichoLaptop kernel: [ 1658.788732] Pid: 9739, comm: Xorg Tainted: G C 3.2.0-2-amd64 #1 Dell Inc. XPS L412Z/008DD8 May 21 18:20:15 TichoLaptop kernel: [ 1658.788847] RIP: 0010:[812474b8] [812474b8] gen6_write_entry+0x4c/0x4f May 21 18:20:15 TichoLaptop kernel: [ 1658.788951] RSP: 0018:8801c49b3aa0 EFLAGS: 00010202 May 21 18:20:15 TichoLaptop kernel: [ 1658.789017] RAX: 738b2015 RBX: 0500 RCX: 00010001 May 21 18:20:15 TichoLaptop kernel: [ 1658.789098] RDX: 0001738b2010 RSI: c9001193396c RDI: 0001738b2000 May 21 18:20:15 TichoLaptop kernel: [ 1658.789178] RBP: ce5b R08: R09: 00049e04 May 21 18:20:15 TichoLaptop kernel: [ 1658.789261] R10: c9001190 R11: 2d2d R12: May 21 18:20:15 TichoLaptop kernel: [ 1658.789328] R13: 00010001 R14: 8801b0ba2000 R15: 0001 May 21 18:20:15 TichoLaptop kernel: [ 1658.789388] FS: 7fbff0f5a880() GS:8801cfa4() knlGS: May 21 18:20:15 TichoLaptop kernel: [ 1658.789456] CS: 0010 DS: ES: CR0: 80050033 May 21 18:20:15 TichoLaptop kernel: [ 1658.789503] CR2: c9001193396c CR3: 0001a9c1c000 CR4: 000406e0 May 21 18:20:15 TichoLaptop kernel: [ 1658.789562] DR0: DR1: DR2: May 21 18:20:15 TichoLaptop kernel: [ 1658.789622] DR3: DR6: 0ff0 DR7: 0400 May 21 18:20:15 TichoLaptop kernel: [ 1658.789681] Process Xorg (pid: 9739, threadinfo 8801c49b2000, task 8801c644d6d0) May 21 18:20:15 TichoLaptop kernel: [ 1658.789746] Stack: May 21 18:20:15 TichoLaptop kernel: [ 1658.789765] 81248526 8801b0ba2000 12d0 May 21 18:20:15 TichoLaptop kernel: [ 1658.789859] 880161435a00 00010001 1000 8801c71c May 21 18:20:15 TichoLaptop kernel: [ 1658.789956] 0500 0500 a02ec93c 880161435a00 May 21 18:20:15 TichoLaptop kernel: [ 1658.790058] Call Trace: May 21 18:20:15 TichoLaptop kernel: [ 1658.790097] [81248526] ? intel_gtt_insert_sg_entries+0x45/0x8d May 21 18:20:15 TichoLaptop kernel: [ 1658.790192] [a02ec93c] ? i915_gem_gtt_bind_object+0x98/0xc6 [i915] May 21 18:20:15 TichoLaptop kernel: [ 1658.790286] [a02e6ade] ? i915_gem_object_bind_to_gtt+0x34c/0x495 [i915] May 21 18:20:15 TichoLaptop kernel: [ 1658.790380] [812f4d36] ? sk_wake_async+0x19/0x3c May 21 18:20:15 TichoLaptop kernel: [ 1658.790458] [a02e8f0e] ? i915_gem_object_pin+0xb9/0x12d [i915] May 21 18:20:15 TichoLaptop kernel: [ 1658.790550] [a02eb75b] ? i915_gem_do_execbuffer.isra.6+0x2f3/0x10e2 [i915] May 21 18:20:15 TichoLaptop kernel: [ 1658.790647] [a02eb32a] ? i915_gem_execbuffer_reserve.isra.4+0x1b3/0x2e7 [i915] May 21
