Bug#358254: libxft-dev: same behaviour with amd64 sid

Package: libxft-dev Version: 2.1.8.2-3 Followup-For: Bug #358254 (Reading database ... 114257 files and directories currently installed.) Preparing to replace x11-common 6.9.0.dfsg.1-4 (using .../x11-common_6.9.0.dfsg. 1-5_all.deb) ... Unpacking replacement x11-common ... dpkg: error processing /

Bug#358254: fix found in bug #358682, reinstalled libxft-dev

Package: libxft-dev Version: 2.1.8.2-5.1 Followup-For: Bug #358254 Preparing to replace libxft-dev 2.1.8.2-3 (using .../libxft-dev_2.1.8.2-5.1_amd64.deb) ... Unpacking replacement libxft-dev ... dpkg: warning - unable to delete old directory `/usr/include/X11/Xft': Directory not empty Preparing t

Processed: Re: Bug#358751: xserver-xorg: evdev with MX 1000 mouse doesn't work anymore

Processing commands for [EMAIL PROTECTED]: > retitle 358751 tilt buttons are inverted with MX 1000 mouse Bug#358751: xserver-xorg: evdev with MX 1000 mouse doesn't work anymore Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking sy

Bug#358751: xserver-xorg: evdev with MX 1000 mouse doesn't work anymore

retitle 358751 tilt buttons are inverted with MX 1000 mouse thanks Hi, Would be very nice if the bug submitter can receive a Cc when somebody post to a bug... For Elmimar, not I'm not blind, I read the changelog, and your configuration doesn't work for me, X segfault when launched. Frank, your

Bug#358751: xserver-xorg: evdev with MX 1000 mouse doesn't work anymore

On Sat, 01 Apr 2006 the mental interface of Christian Marillat told: > retitle 358751 tilt buttons are inverted with MX 1000 mouse > thanks > > Hi, > > Would be very nice if the bug submitter can receive a Cc when somebody > post to a bug... > > For Elmimar, not I'm not blind, I read the change

Bug#358751: xserver-xorg: evdev with MX 1000 mouse doesn't work anymore

On Sat, Apr 01, 2006 at 05:22:07PM +0200, Christian Marillat wrote: > Would be very nice if the bug submitter can receive a Cc when somebody > post to a bug... Yes, sorry for that. > Frank, your configuration works for me > but the "tilt" (tilt is explained here > http://floam.sh.nu/guides/mx1000

Bug#358751: xserver-xorg: evdev with MX 1000 mouse doesn't work anymore

Christian Marillat wrote: > retitle 358751 tilt buttons are inverted with MX 1000 mouse > thanks > > Hi, > > Would be very nice if the bug submitter can receive a Cc when somebody > post to a bug... > > For Elmimar, not I'm not blind, I read the changelog, and your > configuration doesn't work for

Bug#360388: xserver-xorg: local user DoS and arbitrary code execution as root [CVE-2006-0745]

Package: xserver-xorg Version: 6.9.0.dfsg.1-4 Severity: grave Tags: security, upstream Justification: user security hole An upstream vulnerability rated as critical by upstream (bug #6213) was fixed in 6.9.0.dfsg.1-5, which was uploaded with urgency high. I'm opening this bug to track this neverth

Bug#360388: xserver-xorg: local user DoS and arbitrary code execution as root [CVE-2006-0745]

Steve Langasek a écrit : Then you should also mark it as *closed* in -5, otherwise you're *complicating* the transition to testing. Hi Steve, you're right. The mail you just sent should do that for me. Thanks. P.S. : If your mail implies there's a way to mark a bug as fixed at the same tim

Bug#360388: marked as done (xserver-xorg: local user DoS and arbitrary code execution as root [CVE-2006-0745])

Your message dated Sat, 1 Apr 2006 13:55:27 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#360388: xserver-xorg: local user DoS and arbitrary code execution as root [CVE-2006-0745] has caused the attached Bug report to be marked as done. This means that you claim that the problem

Bug#360388: xserver-xorg: local user DoS and arbitrary code execution as root [CVE-2006-0745]

On Sat, Apr 01, 2006 at 05:07:42PM -0500, Filipus Klutiero wrote: > P.S. : If your mail implies there's a way to mark a bug as fixed at the > same time as it's open, I'd be glad to improve my debbugs skills as usual :) Unfortunately, opening and closing the bug have to happen as separate steps.