xserver-xorg-input-synaptics: Changes to 'ubuntu'
debian/changelog|8 debian/patches/115_evdev_only.patch | 10 ++ debian/patches/series |1 + 3 files changed, 19 insertions(+) New commits: commit 8e32a78bbc354581dd0728887a2e4b9481adbb06 Author: Chase Douglas Date: Wed Sep 1 15:01:54 2010 -0400 releasing version 1.2.2-2ubuntu2 diff --git a/debian/changelog b/debian/changelog index 4a1d513..4a6122c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -4,7 +4,7 @@ xserver-xorg-input-synaptics (1.2.2-2ubuntu2) maverick; urgency=low (LP: #624985) - Add 115_evdev_only.patch - -- Chase Douglas Wed, 01 Sep 2010 14:50:09 -0400 + -- Chase Douglas Wed, 01 Sep 2010 15:01:28 -0400 xserver-xorg-input-synaptics (1.2.2-2ubuntu1) maverick; urgency=low commit 49f2fa387f22f376a17e663b8d4228030fdf7845 Author: Chase Douglas Date: Wed Sep 1 15:00:41 2010 -0400 Prevent non-evdev devices from firing the eventcomm AutoDevProbe callback (LP: #624985) * Prevent non-evdev devices from firing the eventcomm AutoDevProbe callback (LP: #624985) - Add 115_evdev_only.patch diff --git a/debian/changelog b/debian/changelog index 31d28be..4a1d513 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +xserver-xorg-input-synaptics (1.2.2-2ubuntu2) maverick; urgency=low + + * Prevent non-evdev devices from firing the eventcomm AutoDevProbe callback +(LP: #624985) +- Add 115_evdev_only.patch + + -- Chase Douglas Wed, 01 Sep 2010 14:50:09 -0400 + xserver-xorg-input-synaptics (1.2.2-2ubuntu1) maverick; urgency=low [ Robert Hooker ] diff --git a/debian/patches/115_evdev_only.patch b/debian/patches/115_evdev_only.patch new file mode 100644 index 000..9e61306 --- /dev/null +++ b/debian/patches/115_evdev_only.patch @@ -0,0 +1,10 @@ +Prevent non-evdev devices from firing the eventcomm AutoDevProbe callback. + +--- a/conf/50-synaptics.conf b/conf/50-synaptics.conf +@@ -2,4 +2,5 @@ Section "InputClass" + Identifier "touchpad catchall" + Driver "synaptics" + MatchIsTouchpad "on" ++MatchDevicePath "/dev/input/event*" + EndSection diff --git a/debian/patches/series b/debian/patches/series index 70fd999..dfe5aaf 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -6,3 +6,4 @@ #105_correct_multifinger_click.patch 106_always_enable_vert_edge_scroll.patch 114_jumpy_cursor_first_part.patch +115_evdev_only.patch -- 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/e1ovmli-0002aq...@alioth.debian.org
Processed: retitling
Processing commands for cont...@bugs.debian.org: > retitle 596781 xserver-xorg-video-intel: window corruption when passing over > xfig, xmgrace, and xpaint (and probably more) windows Bug #596781 [xserver-xorg-video-intel] xserver-xorg-video-intel: window corruption when passing over xfig, xmgrace, and xpaint (and probably more) windows (fwd) Changed Bug title to 'xserver-xorg-video-intel: window corruption when passing over xfig, xmgrace, and xpaint (and probably more) windows' from 'xserver-xorg-video-intel: window corruption when passing over xfig, xmgrace, and xpaint (and probably more) windows (fwd)' > stop Stopping processing here. Please contact me if you need assistance. -- 596781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596781 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.r.128443193215185.transcr...@bugs.debian.org
Bug#596775: Xmodmap pointer setting lost across removal/reinsertion of psmouse
Package: xserver-xorg Version: 1:7.3+20 On my system, I run an xmodmap which contains pointer = 1 3 2 This swaps right and middle button which I find useful. If I do this rmmod psmouse modprobe psmouse then when the X server regains its ability to use the mouse, the pointer setting has been forgotten. I noticed this on my IBM Thinkpad R50p, on which I'm using an ancient copy of some hibernation tools which had psmouse in the blacklist for hibernation: the effect was that hibernation lost my mouse settings. (Luckily the psmouse driver seems to be good for hibernation nowadays so I can remove it from the blacklist.) I think the X server should not forget the mappings in this situation. Nor should it forget other parts of its configuration (such as keyboard mappings, key repeat configuration or bell settings). I think this bug likely shares its underlying cause with: #568868 key repeat for caps lock goes away after suspend/resume #582566 bell settings (xset -b) not preserved after suspend/resume #541388 xserver-xorg: Xmodmap settings lost across suspend/hibernate I'm guessing that the data set by xset and xmodmap is nowadays hung off driver-specific stuff in the X server, and gets reinitialised when the devices X is talking to go away and come back. This is not correct of course: from a theoretical point of view xmodmap and xset settings are properties of the server as a whole, and from a practical point of view many systems need to unload and reload drivers during suspend/resume or hibernate/resume. This underlying bug is probably also responsible for the race that I experience on another system, where /etc/X11/Xmodmap_local does not work: it is run too early and the xmodmap sees no keys at all, and apparently X finds the keyboard later but by that time the xmodmap is over and forgotten. I think I reported this to the BTS but I can't find the bug number right now. Thanks, Ian. -- 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/19598.47077.638917.446...@chiark.greenend.org.uk
Bug#590743: keyboard-configuration: XKBOPTIONS seems to be not propagated
reassign 590743 xserver-xorg thank you I suppose this bug ended in console-setup by mistake. Anton Zinoviev On Thu, Jul 29, 2010 at 12:47:49AM +0200, Christoph Anton Mitterer wrote: > > Hi Julien. > > As you've asked me in > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581756#40 here's a new > bug with the requested logs attached. > > It does not seem, as if XKBOPTIONS would be propagated to X, at least it > does not show up in the X log. > > > Please ask if you need anything else :) -- 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/20100913185759.gg2...@debian.lan
Processed: Re: Bug#590743: keyboard-configuration: XKBOPTIONS seems to be not propagated
Processing commands for cont...@bugs.debian.org: > reassign 590743 xserver-xorg Bug #590743 [keyboard-configuration] keyboard-configuration: XKBOPTIONS seems to be not propagated Bug reassigned from package 'keyboard-configuration' to 'xserver-xorg'. Bug No longer marked as found in versions console-setup/1.55. > thank you Stopping processing here. Please contact me if you need assistance. -- 590743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590743 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.12844045241687.transcr...@bugs.debian.org
Re: X failed to work after an upgrade
Hi there, Just tried to run new ubuntu on my old Travelmate 290 computer, Apparently the kernel doesn't like my machine either, display hangs when I tried to run the demo system -- 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/aanlkti=rikocsww5rsuvnzb+eo+eyuhppvmv1v+7h...@mail.gmail.com
Bug#596700: The X server does not deallocate its vt upon shutdown. Restarting the X server results in the use of a higher-numbered vt.
Package: xorg Version: 1:7.5+6 I am running Debian Squeeze on the i386 architecture. The video card has an Nvidia RIVA TNT2 chipset. The nv driver (xserver-xorg-video-nv) is being used. The monitor is a CRT multi-sync monitor with DDC2/EDID support. My Desktop Environment is GNOME. Here's the scenario: (1) I boot the system. The X server starts on vt 7, running the gdm login interface daemon. I login on the X console using my non-superuser userid and password. This works fine. (2) I then logout of the desktop environment using System -> Logout from the GNOME action bar. Logout proceeds without incident, the X server shuts down, then restarts automatically. But when it restarts, it restarts on vt 8 instead of vt 7. This is not immediately apparent, but if I switch to vt 1 via Ctrl+Alt+F1, then attempt to switch back to the X server via Alt+F7, I see a black screen. If I use Alt+F8 instead, I see the gdm login screen. With the help of someone on the debian-user mailing list, plus some trial-and-error experimentation, I have come up with the following procedure which I use to get the X server back on vt 7 again, without a reboot: (a) When you see the gdm login screen again after logging out, switch to text console number 1 via Ctrl+Alt+F1. (b) login as root on vt 1. Attempt to deallocate vt 7 with deallocvt 7 This results in an error message: VT_DISALLOCATE: Device or resource busy (c) Issue the command killall console-kit-daemon (d) Once again issue the command deallocvt 7 This time it succeeds. (e) Restart gdm with /etc/init.d/gdm restart The X server shuts down and restarts, this time on vt 7. Note: for some installations, "/etc/init.d/gdm3 restart" is needed instead. Do not login yet! (f) Switch back to vt 1 via Ctrl+Alt+F1. (g) Issue the command deallocvt 8 to deallocate vt 8, which was used by the previous instance of the X server. This time it works. It is not necessary to kill the console-kit-daemon process this time. (i) Logout of the root session on vt 1. (j) Switch back to the X server via Alt+F7. (k) Login to the X server's desktop environment as usual. This is a cumbersome and convoluted work-around, but it works. The problem does not appear to be GNOME-related. Someone else on the debian-user mailing list requested help with these symptoms. He also was using the nv driver, but he was not using GNOME. He started the X server directly with "startx". I don't remember what window manager he was using, but he was not using a desktop environment. All he has to do is stop the X server, manually deallocate vt 7, and issue startx again. console-kit-daemon is apparently not used in his environment. It is apparently not specific to the nv driver either. I have seen these symptoms in the GNOME environment using the intel driver as well. -- .''`. Stephen Powell : :' : `. `'` `- -- 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/1319956917.71282.1284389205058.javamail.r...@md01.wow.synacor.com
xserver-xorg-video-intel: Changes to 'ubuntu'
debian/patches/104_sandybridge_id_update.patch |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 11d61a537e977d128c5793c59ef5430198217bac Author: Robert Hooker Date: Mon Sep 13 10:30:46 2010 -0400 104_sandybridge_id_update.patch: minor fixup diff --git a/debian/patches/104_sandybridge_id_update.patch b/debian/patches/104_sandybridge_id_update.patch index b8ab2bf..e34dd7e 100644 --- a/debian/patches/104_sandybridge_id_update.patch +++ b/debian/patches/104_sandybridge_id_update.patch @@ -119,7 +119,7 @@ index b8e0c0b..b13894e 100644 + case PCI_CHIP_SANDYBRIDGE_M_GT2: + case PCI_CHIP_SANDYBRIDGE_M_GT2_PLUS: + case PCI_CHIP_SANDYBRIDGE_S_GT: -+ chipset->name = "Sandybridge"; ++ chipname = "Sandybridge"; + break; default: chipname = "unknown chipset"; -- 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/e1ova3a-0008jj...@alioth.debian.org
Bug#596634: x11-common: /etc/X11/Xsession always appends to .xsession-errors
Julien Cristau writes: > That seems to duplicate the last 512kB rather than remove the rest? > Perhaps your '>>' ought to be '>'? Whoops, yes indeed. I had some debugging prints like "starting session on $(date)" there and forgot >>. Fixed version is attached. >From d1df83712f29dc7ffe2203f38efdd290fbac6535 Mon Sep 17 00:00:00 2001 From: Timo Juhani Lindfors Date: Mon, 13 Sep 2010 14:25:54 +0300 Subject: [PATCH] Keep only last 512 KiB of .xsession-errors --- debian/x11-common/etc/X11/Xsession |7 +++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/debian/x11-common/etc/X11/Xsession b/debian/x11-common/etc/X11/Xsession index 6ad7d6e..6145389 100755 --- a/debian/x11-common/etc/X11/Xsession +++ b/debian/x11-common/etc/X11/Xsession @@ -74,6 +74,13 @@ else errormsg "unable to create X session log/error file; aborting." fi +if ERRFILETMP=$(tempfile 2> /dev/null); then +# Keep only last 512 KiB of $ERRFILE +tail --bytes 524288 "$ERRFILE" > "$ERRFILETMP" +cat "$ERRFILETMP" > "$ERRFILE" +rm -f "$ERRFILETMP" +fi + exec >>"$ERRFILE" 2>&1 echo "$PROGNAME: X session started for $LOGNAME at $(date)" -- 1.7.1
Re: Bug#596547: keyboard unusable
On Sun, Sep 12, 2010 at 06:33:51PM +0200, Julien Cristau wrote: > > Anton, do you have an idea how to fix this (or anyone else, for that > matter)? We need to parse the xorg.conf keywords and option names > case-insensitively, but the option values themselves are case-sensitive. Thanks for your work. I commited the patch of Olivier Schwander. 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/20100913130058.gc2...@debian.lan
Bug#596634: x11-common: /etc/X11/Xsession always appends to .xsession-errors
On Mon, Sep 13, 2010 at 14:28:37 +0300, Timo Juhani Lindfors wrote: > Tim Connors writes: > > this (and I *really* hate it when gnome by default limits output and just > > Can you locate where this limit is in gnome? Is it a per-app limit or > global to all gnome applications? > It used to be in gdm, was removed in 2.20.11-2. > >> How about a compromise? Could we truncate all but the last 1000 lines > >> in /etc/X11/Xsession? > > > > Sure. Or perhaps 1000*80 characters (never encountered super long lines > > as output to .xsession-errors, but could happen). > > Good point. I recall seeing binaries in ~/.xsession-errors. > > The attached patch keeps only the last 512 KiB of ~/.xsession-errors > on login. Can you test if this works for you? > > >From 5433fac367d3c14fedfc542b0710cc1399683ac4 Mon Sep 17 00:00:00 2001 > From: Timo Juhani Lindfors > Date: Mon, 13 Sep 2010 14:25:54 +0300 > Subject: [PATCH] Keep only last 512 KiB of .xsession-errors > > --- > debian/x11-common/etc/X11/Xsession |7 +++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > diff --git a/debian/x11-common/etc/X11/Xsession > b/debian/x11-common/etc/X11/Xsession > index 6ad7d6e..6937e8f 100755 > --- a/debian/x11-common/etc/X11/Xsession > +++ b/debian/x11-common/etc/X11/Xsession > @@ -74,6 +74,13 @@ else >errormsg "unable to create X session log/error file; aborting." > fi > > +if ERRFILETMP=$(tempfile 2> /dev/null); then > +# Keep only last 512 KiB of $ERRFILE > +tail --bytes 524288 "$ERRFILE" > "$ERRFILETMP" > +cat "$ERRFILETMP" >> "$ERRFILE" > +rm -f "$ERRFILETMP" > +fi > + That seems to duplicate the last 512kB rather than remove the rest? Perhaps your '>>' ought to be '>'? > exec >>"$ERRFILE" 2>&1 > > echo "$PROGNAME: X session started for $LOGNAME at $(date)" Cheers, Julien signature.asc Description: Digital signature
xorg-server: Changes to 'ubuntu'
debian/changelog| 13 +--
debian/patches/206_intel_8xx_default_to_fbdev.patch | 22
debian/patches/series |1
3 files changed, 33 insertions(+), 3 deletions(-)
New commits:
commit e1f047bc1fe7f3e7c4fa9a2467362250aa25f8bd
Author: Christopher James Halse Rogers
Date: Mon Sep 13 21:32:00 2010 +1000
Don't autoload intel on the annoying i8xx cards
diff --git a/debian/changelog b/debian/changelog
index c89967e..ba29e19 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,17 @@
-xorg-server (2:1.9.0-0ubuntu6) UNRELEASED; urgency=low
-
+xorg-server (2:1.9.0-0ubuntu6) maverick; urgency=low
+
+ [ Chase Douglas ]
* Fix udev USB product ID parsing (LP: #628214)
- debian/patches:
+ 205_udev-product-ids.patch
- -- Chase Douglas Wed, 01 Sep 2010 16:28:23 -0400
+ [ Christopher James Halse Rogers ]
+ * debian/patches/206_intel_8xx_default_to_fbdev.patch:
+- Don't autoload the intel driver on i830, i845g and i855. These are
+ still too unstable with KMS/GEM. X will autoload the fbdev driver
+ (if using KMS) or the vesa driver instead. (LP: #633593)
+
+ -- Christopher James Halse Rogers Mon, 13 Sep 2010
18:48:54 +1000
xorg-server (2:1.9.0-0ubuntu5) maverick; urgency=low
diff --git a/debian/patches/206_intel_8xx_default_to_fbdev.patch
b/debian/patches/206_intel_8xx_default_to_fbdev.patch
new file mode 100644
index 000..c6a0d44
--- /dev/null
+++ b/debian/patches/206_intel_8xx_default_to_fbdev.patch
@@ -0,0 +1,22 @@
+Description: Drop intel from the autoloaded drivers for i830, i845g, i855
+ .
+ These remain too unstable with the intel DDX.
+Author: Christopher James Halse Rogers
+
+Index: xorg-server/hw/xfree86/common/xf86pciBus.c
+===
+--- xorg-server.orig/hw/xfree86/common/xf86pciBus.c2010-09-13
19:54:39.330148002 +1000
xorg-server/hw/xfree86/common/xf86pciBus.c 2010-09-13 20:54:08.0
+1000
+@@ -1112,6 +1112,12 @@
+ driverList[0] = "i740";
+ } else if (dev->device_id == 0x8108) {
+ break; /* "hooray" for poulsbo */
++ } else if (dev->device_id == 0x3577) {
++ break; /* Let i830 fall back to fbdev / vesa */
++ } else if (dev->device_id == 0x2562) {
++ break; /* Let i845g fall back to fbdev / vesa */
++ } else if (dev->device_id == 0x3582) {
++ break; /* Let i855 fall back to fbdev / vesa */
+ } else {
+ driverList[0] = "intel";
+ }
diff --git a/debian/patches/series b/debian/patches/series
index e1e43a9..39e0c56 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -35,3 +35,4 @@
203_gestures-extension.patch
204_fix-neg-sync-transition.patch
205_udev-product-ids.patch
+206_intel_8xx_default_to_fbdev.patch
--
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/e1ov7gn-0001kd...@alioth.debian.org
Processed: Re: Bug#596634: x11-common: /etc/X11/Xsession always appends to .xsession-errors
Processing commands for cont...@bugs.debian.org: > package x11-common Limiting to bugs with field 'package' containing at least one of 'x11-common' Limit currently set to 'package':'x11-common' > tag 596634 patch Bug #596634 [x11-common] x11-common: /etc/X11/Xsession always appends to .xsession-errors Bug #276545 [x11-common] xfree86-common: add Xsession option and logic for controlling number of lines in $HOME/.xsession-errors Bug #287876 [x11-common] xfree86-common: Xsession does nothing to prevent $HOME/.xsession-errors from growing very large Bug #351166 [x11-common] size of .xsession-errors should be limited Ignoring request to alter tags of bug #596634 to the same tags previously set Ignoring request to alter tags of bug #276545 to the same tags previously set Ignoring request to alter tags of bug #287876 to the same tags previously set Ignoring request to alter tags of bug #351166 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 596634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596634 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.128437732323752.transcr...@bugs.debian.org
Bug#596634: x11-common: /etc/X11/Xsession always appends to .xsession-errors
package x11-common tag 596634 patch thanks Tim Connors writes: > this (and I *really* hate it when gnome by default limits output and just Can you locate where this limit is in gnome? Is it a per-app limit or global to all gnome applications? >> How about a compromise? Could we truncate all but the last 1000 lines >> in /etc/X11/Xsession? > > Sure. Or perhaps 1000*80 characters (never encountered super long lines > as output to .xsession-errors, but could happen). Good point. I recall seeing binaries in ~/.xsession-errors. The attached patch keeps only the last 512 KiB of ~/.xsession-errors on login. Can you test if this works for you? >From 5433fac367d3c14fedfc542b0710cc1399683ac4 Mon Sep 17 00:00:00 2001 From: Timo Juhani Lindfors Date: Mon, 13 Sep 2010 14:25:54 +0300 Subject: [PATCH] Keep only last 512 KiB of .xsession-errors --- debian/x11-common/etc/X11/Xsession |7 +++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/debian/x11-common/etc/X11/Xsession b/debian/x11-common/etc/X11/Xsession index 6ad7d6e..6937e8f 100755 --- a/debian/x11-common/etc/X11/Xsession +++ b/debian/x11-common/etc/X11/Xsession @@ -74,6 +74,13 @@ else errormsg "unable to create X session log/error file; aborting." fi +if ERRFILETMP=$(tempfile 2> /dev/null); then +# Keep only last 512 KiB of $ERRFILE +tail --bytes 524288 "$ERRFILE" > "$ERRFILETMP" +cat "$ERRFILETMP" >> "$ERRFILE" +rm -f "$ERRFILETMP" +fi + exec >>"$ERRFILE" 2>&1 echo "$PROGNAME: X session started for $LOGNAME at $(date)" -- 1.7.1
Bug#580980: xserver-xorg-video-radeon: pink tinted translucent windows on Mobility 7500 M7 LW [rv200]
Le lundi 13 septembre 2010, Michel Dänzer a écrit : > On Fre, 2010-09-10 at 09:09 +0200, Fabien Steinmetz wrote: > > > Does > > > > > > Option "RenderAccel" "off" > > > > > > in xorg.conf work around this bug ? > > > > Actually, by setting it to off the translucency isn't pink anymore (with > > OpenGL backend) but it doesn't look like with Xrender either. > > Possibly two separate bugs then, one in the X driver's RENDER > acceleration code and one in the Mesa radeon driver. Just to clean any doubt, by saying "it doesn't look like with Xrender either." I meant that translucency is always fine with XRender engine (whether RenderAccel is on or off) > > NB : 1px white line is displayed both in console & X > > Yet another bug in the kernel then. Is it using the laptop panel's > native resolution? Yes, with the native resolution (1400x1050) -- 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/201009131254.40287.fabie...@yahoo.fr
Processed: merging bugs
Processing commands for cont...@bugs.debian.org: > package x11-common Limiting to bugs with field 'package' containing at least one of 'x11-common' Limit currently set to 'package':'x11-common' > merge 276545 596634 Bug#276545: xfree86-common: add Xsession option and logic for controlling number of lines in $HOME/.xsession-errors Bug#596634: x11-common: /etc/X11/Xsession always appends to .xsession-errors Bug#287876: xfree86-common: Xsession does nothing to prevent $HOME/.xsession-errors from growing very large Bug#351166: size of .xsession-errors should be limited Merged 276545 287876 351166 596634. > thanks Stopping processing here. Please contact me if you need assistance. -- 287876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287876 351166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351166 276545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276545 596634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596634 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.128437187123264.transcr...@bugs.debian.org
Processed: severity of 596630 is normal
Processing commands for cont...@bugs.debian.org: > severity 596630 normal Bug #596630 [xauth] disk full leads to xauth nulling out the Xauthority file completely instead of just failing to create entry Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 596630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596630 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.128437027512212.transcr...@bugs.debian.org
Processed: severity of 596634 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 596634 wishlist Bug #596634 [x11-common] x11-common: /etc/X11/Xsession always appends to .xsession-errors Severity set to 'wishlist' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 596634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596634 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.128437018810539.transcr...@bugs.debian.org
Bug#580980: xserver-xorg-video-radeon: pink tinted translucent windows on Mobility 7500 M7 LW [rv200]
On Fre, 2010-09-10 at 09:09 +0200, Fabien Steinmetz wrote: > > Does > > > > Option "RenderAccel" "off" > > > > in xorg.conf work around this bug ? > > Actually, by setting it to off the translucency isn't pink anymore (with > OpenGL backend) but it doesn't look like with Xrender either. Possibly two separate bugs then, one in the X driver's RENDER acceleration code and one in the Mesa radeon driver. > NB : 1px white line is displayed both in console & X Yet another bug in the kernel then. Is it using the laptop panel's native resolution? -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- 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/1284368180.6653.140.ca...@thor.local
Bug#596588: hurd-i386
Robert Millan, le Mon 13 Sep 2010 09:58:33 +0200, a écrit : > These 3 udebs should probably be added for hurd-i386 too. > > CCing Hurd/D-I folks so they can confirm. Yep! Samuel -- 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/20100913081223.ga5...@const.bordeaux.inria.fr
Bug#596588: hurd-i386
These 3 udebs should probably be added for hurd-i386 too. CCing Hurd/D-I folks so they can confirm. -- Robert Millan -- 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/aanlkti=kgqcuwft8rz1vsfz6j=tuqykwab-klbeya...@mail.gmail.com
Bug#596634: x11-common: /etc/X11/Xsession always appends to .xsession-errors
On Mon, 13 Sep 2010, Timo Juhani Lindfors wrote: > [I'm not a maintainer, just happened be following X bugs...] > > Tim Connors writes: > > before the user gets to review them, they can always log into the > > console and review the errors before they restart X. > > Always might be too strong word. On my PDA I don't have a physical > keyboard, the only way to read .xsession-errors is via X or by > connecting a laptop. And on my laptop switching virtual consoles > sometimes fails if I have used suspend... > > > This is particularly insidious when the disk is full because something > > was writing lots of crap to ~/.xsession-errors. That crap is not > > I think this is the real problem and applications should be fixed to > limit their error output. Yep. But sometimes wmbattery goes haywire trying to connect to HAL, or a homegrown app might output too much. In the absense of a library to do this (and I *really* hate it when gnome by default limits output and just discards the rest - its limit is arbitrarily small, and I have no way of retrieving that lost information after a certain point in a desktop session once it starts discarding data. Fortunately, I do not use gnome often). > > because of too much crap emitted to ~/.xsession-errors? Well, just > > let the unsophisticated user log out and log back in again. > > How about a compromise? Could we truncate all but the last 1000 lines > in /etc/X11/Xsession? Sure. Or perhaps 1000*80 characters (never encountered super long lines as output to .xsession-errors, but could happen). -- TimC Anyone who quotes me in their sig is an idiot. -- Rusty Russell. -- 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/alpine.deb.2.00.1009131745300.2...@dirac.rather.puzzling.org
