Bug#508126: Bug#508125: xine-ui: ctrl/shift key press emulation implementation broken

Hi Ben, Ben Hutchings wrote: > I need some guidance on how to deal with the following related bugs: > > #374644: xine-ui: ctrl/shift key press emulation implementation broken > #506001: xine-ui: xine causes left ctrl keyup events every 20 seconds > These are the same bug: xine-ui suppresses scree

Bug#464848: RFP: xserver-xorg-video-openchrome -- Improved Xorg video driver for VIA UniChrome graphics chipsets

Package: wnpp Severity: wishlist * Package name: xserver-xorg-video-openchrome Version : 0.2.901 Upstream Author : OpenChrome Project <[EMAIL PROTECTED]> * URL : http://www.openchrome.org/ * License : MIT Programming Lang: C Description : Improved Xorg v

Bug#443726: Fixed upstream?

Mattia Dongili wrote: > wow, I nic euser pointed to this: > http://www.postnuklear.de/xorg-patches/files/xf86-input-evtouch-0.8.7-misc.patch > (description at: http://www.postnuklear.de/xorg-patches/) > > I'll give it a try this weekend. > > hurray Great! -- Pelle -- To UNSUBSCRIBE, email

Bug#463630: /etc/init.d/x11-common should not depend on $named

Package: x11-common Version: 1:7.3+10 Severity: normal File: /etc/init.d/x11-common Hi, /etc/init.d/x11-common currently list in its LSB dependencies: # Should-Start: $named # Should-Stop: $named According to LSB 3.2, $named means: "IP name-to-address translation, using the interfac

Bug#450713: calibrator.c

Hi Daniel, Are you the author of calibrator.c, found at ? If you are, what license is the code under? If you're not the author, do you know who is? Thanks in advance! -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "

Bug#443726: Fixed upstream?

Hi, Upstream's CHANGELOG[1] says: 0.8.8 - Make it work for current Xorg-GIT However, no version 0.8.8 has been released yet. Maybe we can ask upstream for a patch in the mean time? [1] http://www.conan.de/touchscreen/CHANGELOG.evtouch -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PR

Bug#368858: Does it still segfault?

reassign 368858 lyx-xforms tag 368858 help thanks Denis Barbier: > On Mon, Jun 12, 2006 at 03:34:27PM +0200, Per Olofsson wrote: > > > It looks a bit like this: > > > > > > http://lists.debian.org/debian-amd64/2005/05/msg00518.html > > > > > > Alt

Re: Bug#368858: Does it still segfault?

reassign 368858 libx11-6 thanks James Stone: > On Wed, May 31, 2006 at 09:10:44PM +0200, Per Olofsson wrote: > > tag 368858 unreproducible > > thanks > > > > James Stone: > > > Program received signal SIGSEGV, Segmentation fault. > > > 0xa7dd0cb8 in

Bug#230664: xserver-common: Manpage missing for X program

Package: xserver-common Version: 4.3.0-0pre1v5 Severity: minor There is no manual page available for the X program. While there is an X(7x), it does not describe the X program but rather the X Window System as a whole. It seems like Xserver(1x) describes the X program, perhaps make a symlink to th

Bug#39964: The xterm bug

On Sat, Mar 08, 2003 at 03:03:25PM -0500, Branden Robinson wrote: > On Sat, Mar 08, 2003 at 12:25:25AM +0100, Per Olofsson wrote: > > According to the Ion [0]FAQ and [1]Wiki this is a bug in xterm, not > > Ion. I am therefore reassigning it to xterm and merging it with bug > >

Bug#39964: The xterm bug

On Sat, Mar 08, 2003 at 03:03:25PM -0500, Branden Robinson wrote: > On Sat, Mar 08, 2003 at 12:25:25AM +0100, Per Olofsson wrote: > > According to the Ion [0]FAQ and [1]Wiki this is a bug in xterm, not > > Ion. I am therefore reassigning it to xterm and merging it with bug > >

Bug#39964: The xterm bug

reassign 146210 xterm tags 146210 upstream merge 146210 39964 thanks According to the Ion [0]FAQ and [1]Wiki this is a bug in xterm, not Ion. I am therefore reassigning it to xterm and merging it with bug #39964 which I think is the same problem. I have verified that this bug still exists in xterm

Bug#39964: The xterm bug

reassign 146210 xterm tags 146210 upstream merge 146210 39964 thanks According to the Ion [0]FAQ and [1]Wiki this is a bug in xterm, not Ion. I am therefore reassigning it to xterm and merging it with bug #39964 which I think is the same problem. I have verified that this bug still exists in xterm