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

2009-01-02 Thread Per Olofsson
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 screensavers by injecting
 fake keystrokes, which may be received by other windows.  It also
 suppresses gnome-screensaver cleanly, so we could disable the key
 injection code without affecting GNOME users.  However, this would be a
 regression for users of the X server screensaver, xscreensaver or the
 KDE screensaver.
 
 My proposed fix involves using xdg-screensaver, which supports all the
 different screensavers.  However, this suffers from the following bugs:
 #508125: xdg-screensaver: Race in suspend/resume can lead to process leak
 #508126: x11-utils: xprop -spy does not handle destruction properly
 I do not think that these are, in themselves, RC.

 I have now proposed fixes for all of these, and the result appears to be
 robust.  Should I NMU with these fixes?  Should any of these bugs be
 down/upgraded?

Feel free to NMU xdg-utils, as the maintainer I have no problems with
that. I would appreciate if you commit directly to the git repository,
which is in collab-maint (but it's not necessary).

Sorry for not responding earlier.

-- 
Pelle



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2008-02-09 Thread Per Olofsson
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 video driver for VIA UniChrome graphics 
chipsets

OpenChrome is based on VIA's UniChrome video driver. It seems to be
much more actively maintained than the via driver in Xorg. It also has
features such as 3D acceleration and XvMC for certain chipsets.

There is already an Ubuntu package, and I found this git repository:
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-openchrome.git

But it's still nice to have a wnpp bug tracking it.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#443726: Fixed upstream?

2008-02-02 Thread Per Olofsson
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 to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2008-02-01 Thread Per Olofsson
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 interfaces described in
this specification, are available to the level the system normally
provides them. Example: if a DNS query daemon normally provides this
facility, then that daemon has been started.[1]

However, I can find nothing in /etc/init.d/x11-common which needs DNS
resolution. Therefore, I think this dependency should be removed.

[1] 
http://refspecs.freestandards.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-generic/facilname.html

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages x11-common depends on:
ii  debconf [debconf-2.0] 1.5.18 Debian configuration management sy
ii  debianutils   2.28.2 Miscellaneous utilities specific t
ii  libc6 2.7-6  GNU C Library: Shared libraries
ii  lsb-base  3.1-24 Linux Standard Base 3.1 init scrip

x11-common recommends no packages.

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#443726: Fixed upstream?

2008-01-23 Thread Per Olofsson
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 PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#450713: calibrator.c

2008-01-23 Thread Per Olofsson
Hi Daniel,

Are you the author of calibrator.c, found at
http://linux.chapter7.ch/touchkit/calibrator.c?

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 unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#368858: Does it still segfault?

2006-06-12 Thread Per Olofsson
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 XFindOnExtensionList () from /usr/lib/libX11.so.6
   
   I think it may be related to the fact I have the proprietary
   NVidia driver installed.
  
  Does the problem go away if you switch to the nv driver?
  
  If it indeed does have to do with the proprietary nVidia driver, I'm
  afraid I can't do much to help you.
 
 
 Sorry, should have checked that.. It still segfaults with the nv
 driver. I have built the lyx-xforms by hand with debug enabled,
 and there is no further info, but it still segfaults.
 
 It looks a bit like this:
 
 http://lists.debian.org/debian-amd64/2005/05/msg00518.html
 
 Although not affecting as many apps..

Well, in any case it seems like it's a bug in the X libraries so I'm
reassigning it to libx11-6.

-- 
Pelle


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#368858: Does it still segfault?

2006-06-12 Thread Per Olofsson
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
   
   Although not affecting as many apps..
  
  Well, in any case it seems like it's a bug in the X libraries so I'm
  reassigning it to libx11-6.
 
 Can you please reassign it back to lyx-xforms?
 At the moment, there is nothing in this bugreport to support your claim
 that it is caused by libx11-6.  The backtrace shows
  0xa7db4cb8 in XFindOnExtensionList (structure=0xc09, number=1040697125)
 and these arguments look clearly wrong, but we do not know where they do
 come from.
 Please work first with bug submitter to reproduce it, and then reassign
 it to libx11-6 if there is indeed a bug there, with explanations on how
 to reproduce it.  I am afraid that Debian X maintainers cannot investigate
 random bugs in any X application.
 For instance, the following informations may be helpful:
  * Is X a local or remote display?
  * Does it crash when launched from a newly created account?
  * Does it crash at startup, or when processing a particular file?
  * Any special in user configuration?
  ...

OK, I understand. I thought that this was maybe a known bug.

I think lyx-xforms is deprecated anyway.

-- 
Pelle


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2004-02-01 Thread Per Olofsson
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 that manpage?

/Pelle


signature.asc
Description: Digital signature


Bug#39964: The xterm bug

2003-03-08 Thread Per Olofsson
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
  #39964 which I think is the same problem. I have verified that this
  bug still exists in xterm 4.2.1-6. See the links below for more
  information.
  
  [0] http://modeemi.cs.tut.fi/~tuomov/ion/faq.htm
 
 This link is a 404, BTW.

Oops, sorry, lost the last character. Should be:

http://modeemi.cs.tut.fi/~tuomov/ion/faq.html

  [1] http://wiki.ael.be/ion/index.php/FrequentlyAskedQuestions
 
 Okay, I see.  I'll apply this patch since Debian doesn't care about
 Solaris 2.6.  :)


Ok, good :)

/Pelle




Bug#39964: The xterm bug

2003-03-07 Thread Per Olofsson
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 4.2.1-6. See the links below for more
information.

[0] http://modeemi.cs.tut.fi/~tuomov/ion/faq.htm
[1] http://wiki.ael.be/ion/index.php/FrequentlyAskedQuestions

/Pelle



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#39964: The xterm bug

2003-03-07 Thread Per Olofsson
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 4.2.1-6. See the links below for more
information.

[0] http://modeemi.cs.tut.fi/~tuomov/ion/faq.htm
[1] http://wiki.ael.be/ion/index.php/FrequentlyAskedQuestions

/Pelle