Bug#460838: Please don't ship rules/base in source

2008-01-15 Thread Philippe Cloutier
Package: xkb-data
Version: 1.1~cvs.20080104.1-1
Severity: wishlist

I don't really know how rules/base works, but it seems to be autogenerated and 
possible not to ship it in the source. I see that even upstream tarballs 
contain it, but maybe the Debian patch could just remove it.
The reason I ask this is that having this file seems to cause problems when 
trying to modify rules. Apparently if I build the package, then edit the 
source code and finally build and retry cleaning, cleaning fails because 
rules/base is updated so unpatching fails:
Le patch add_void_definition_pl-324647.diff ne se retire pas proprement 
(rafraichissez le, ou forcez avec -f)

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.22-3-686

Debian Release: lenny/sid
  990 testing security.debian.org 
  990 testing debian.ift.ulaval.ca 
  500 unstabledebian.savoirfairelinux.net 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
| 




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



Bug#397197: The same on intel

2008-01-15 Thread Martin Devera

I only want to confirm the bug on intel driver too. It is with latest
1.4.1~git20080105-1 xorg-core.
I can do dpms force but dpms 10 20 30 doesn't work...



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



Bug#460866: can't open display

2008-01-15 Thread Carsten Pfeiffer
Package: xvfb
Version: 2:1.1.1-21etch1

xvfb in etch simply doesn't work for me. Whatever X-client I start with 
xvfb-run, it cannot connect to the DISPLAY. E.g.

[EMAIL PROTECTED]:~ $ xvfb-run xterm
xterm Xt error: Can't open display: :99
/usr/bin/xvfb-run: line 158: kill: (4889) - Kein passender Prozess gefunden

This happens not only with the default display 99, but also when I explicitly 
specify e.g. a lower display number.

xvfb from testing works perfectly, though.

Cheers,
Carsten




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



Bug#460820: x11-common: no login shell run when logging in through gdm

2008-01-15 Thread Michal Suchanek
On 15/01/2008, Brice Goglin [EMAIL PROTECTED] wrote:
 Michal Suchanek wrote:
  Package: x11-common
  Version: 1:7.3+10
  Severity: normal
 
 
  When I log in through gdm no login shell is run. I can tell because when
  I run bash -l manually it adds ~/bin to my path but it is not there when
  I log in through gdm.
 

 Isn't $HOME/.xsessionrc exactly what you want ?


No, I would have to set up everything in there then. Even if it worked
(the script was just sourced), it is not documented anywhere.

And I do not see why I have to correct the xsession scripts on every
machine. They should do the right thing, that's why they are packaged
and customized for Debian, right?

Thanks

Michal



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



Bug#460866: can't open display

2008-01-15 Thread Julien Cristau
On Tue, Jan 15, 2008 at 12:37:26 +0100, Carsten Pfeiffer wrote:

 xvfb in etch simply doesn't work for me. Whatever X-client I start with 
 xvfb-run, it cannot connect to the DISPLAY. E.g.
 
 [EMAIL PROTECTED]:~ $ xvfb-run xterm
 xterm Xt error: Can't open display: :99
 /usr/bin/xvfb-run: line 158: kill: (4889) - Kein passender Prozess gefunden
 
I can't reproduce that.  Please try to get more information about the
problem (with the -e option to xvfb-run for a start).

Cheers,
Julien



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



Bug#460866: can't open display

2008-01-15 Thread Carsten Pfeiffer
Am Dienstag, 15. Januar 2008 schrieben Sie:

Thanks for the quick reply!

 I can't reproduce that.  Please try to get more information about the
 problem (with the -e option to xvfb-run for a start).

Here's what I get with -e (reproduced on two different systems, neither of 
these run an X session):

_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running

Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already 
running

Thanks,
Carsten




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



Bug#460186: compiz-kde: some windows do not get active frames

2008-01-15 Thread Emilio Scalise

Do you have the focus prevention setting enabled?

For example I have a similar issue with the Run dialog (commonly alt+f2 
on kde). I press alt+f2 and it remains in background. This is a very old 
issue, that they introduced in the 0.3.x branch and they never fixed. 
Does is it similar to your problem?




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



Bug#458464: compiz-kde: part of title bar rendered incorrectly

2008-01-15 Thread Emilio Scalise
I can confirm this bug, and searching on the net, there are also people 
that have this issue with newer git versions 
(http://forum.compiz-fusion.org/showthread.php?p=44667).

No feedback from the developers.

Perhaps I don't know if there is an upstream bug tracking system...



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



Bug#460820: x11-common: no login shell run when logging in through gdm

2008-01-15 Thread Brice Goglin
Michal Suchanek wrote:
 On 15/01/2008, Brice Goglin [EMAIL PROTECTED] wrote:
   
 Isn't $HOME/.xsessionrc exactly what you want 

 No, I would have to set up everything in there then. Even if it worked
 (the script was just sourced), it is not documented anywhere.
   

It's documented in man xsession since x11-common 1:7.3+10 (where the
feature was added).

 And I do not see why I have to correct the xsession scripts on every
 machine. They should do the right thing, that's why they are packaged
 and customized for Debian, right?
   

What do you call the right thing? Do you want us to load your .bashrc
from Xsession? That's the config for your bash, not for X sessions,
that's why it's not loaded here.

Apart from the .xsessionrc file that just got added, there is just no
config file that is loaded for all X sessions automatically.  That's it.
If you want some environment variables for all X clients, they have to
go in .xsessionrc, not in what you call the login shell config.

Brice




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



Bug#460933: synaptics driver is not loaded

2008-01-15 Thread Hans
Package: xserver-xorg-input-synaptics
Version: 0.14.7~git20070706-2
Severity: normal



-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages xserver-xorg-input-synaptics depends on:
ii  libc6  2.7-6 GNU C Library: Shared libraries
ii  libx11-6   2:1.0.3-7 X11 client-side library
ii  libxext6   1:1.0.3-2 X11 miscellaneous extension librar
ii  libxi6 2:1.1.3-1 X11 Input extension library
ii  xserver-xorg-core  2:1.4.1~git20080105-1 Xorg X server - core server

xserver-xorg-input-synaptics recommends no packages.

-- no debconf information
Dear maintainers, 

after the last update the synaptics-driver is either not correctly
recognized, not correctly loaded or its configuration is not working
properly (this might be similar to bug #372692) . The pointer is working,
but the scroll functions at the edge of the mousepad do not work, neither
vertical, nor horizontal. To verify this, here is my
complete xorg.conf (there should be no mistake in it):

- snip --

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  ([EMAIL PROTECTED])  Sat May 12 15:12:41 PDT
# 2007

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type man /etc/X11/xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg
# Section DRI
#   Mode0666
# EndSection

Section ServerLayout
Identifier Default Layout
Screen Default Screen 0 0
InputDeviceGeneric Keyboard
InputDeviceConfigured Mouse
InputDeviceMouse[1]
InputDeviceSynaptics Touchpad
EndSection

Section Files

#   FontPath/usr/X11R6/lib/X11/fonts/cyrillic
# path to defoma fonts
FontPath/usr/share/fonts/X11/misc
FontPath/usr/X11R6/lib/X11/fonts/misc
FontPath/usr/share/fonts/X11/cyrillic
FontPath/usr/share/fonts/X11/100dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/share/fonts/X11/75dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/share/fonts/X11/Type1
FontPath/usr/X11R6/lib/X11/fonts/Type1
FontPath/usr/share/fonts/X11/100dpi
FontPath/usr/X11R6/lib/X11/fonts/100dpi
FontPath/usr/share/fonts/X11/75dpi
FontPath/usr/X11R6/lib/X11/fonts/75dpi
FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
EndSection

Section Module
Load   i2c
Load   bitmap
Load   ddc
Load   extmod
Load   freetype
Load   glx
Load   int10
Load   type1
Load   vbe
EndSection

Section InputDevice
Identifier Mouse[1]
Driver synaptics
Option Device /dev/psaux
Option Protocol auto-dev
Option LeftEdge 1700
Option RightEdge 5300
Option TopEdge 1700
Option BottomEdge 4200
Option FingerLow 25
Option FingerHigh 30
Option MaxTapTime 180
Option MaxTapMove 220
Option VertScrollDelta 100
Option MinSpeed 0.06
Option MaxSpeed 0.12
Option AccelFactor 0.0010
Option SHMConfig on
Option Repeater /dev/ps2mouse
EndSection

Section InputDevice
Identifier Generic Keyboard
Driver kbd
Option CoreKeyboard
Option XkbRules xorg
Option XkbModel pc105
Option XkbLayout de
Option XkbVariant nodeadkeys
EndSection

Section InputDevice
Identifier Configured Mouse
Driver mouse
Option CorePointer
Option Device /dev/input/mice
Option Protocol ExplorerPS/2
Option Emulate3Buttons true
EndSection

Section InputDevice
Identifier Synaptics Touchpad
Driver synaptics
Option SendCoreEvents true
Option Device /dev/psaux
Option Protocol auto-dev
Option HorizScrollDelta 175
Option HorizEdgeScroll 1
EndSection

Section 

Bug#460820: x11-common: no login shell run when logging in through gdm

2008-01-15 Thread Michal Suchanek
On 15/01/2008, Brice Goglin [EMAIL PROTECTED] wrote:
 Michal Suchanek wrote:
  On 15/01/2008, Brice Goglin [EMAIL PROTECTED] wrote:
 
  Isn't $HOME/.xsessionrc exactly what you want
 
  No, I would have to set up everything in there then. Even if it worked
  (the script was just sourced), it is not documented anywhere.
 

 It's documented in man xsession since x11-common 1:7.3+10 (where the
 feature was added).

I was probably looking at the man page in an older version of the
package then, sorry.


  And I do not see why I have to correct the xsession scripts on every
  machine. They should do the right thing, that's why they are packaged
  and customized for Debian, right?
 

 What do you call the right thing? Do you want us to load your .bashrc
 from Xsession? That's the config for your bash, not for X sessions,
 that's why it's not loaded here.

It's the config for my shell. I (or rather the maintainer of bash or
base-files in this case) put that stuff into .bash_profile to be
executed when I log in.

That's why I would like it executed when I log in. If my shell was
tcsh I would like the tcsh setup scripts executed when I log in.


 Apart from the .xsessionrc file that just got added, there is just no
 config file that is loaded for all X sessions automatically.  That's it.
 If you want some environment variables for all X clients, they have to
 go in .xsessionrc, not in what you call the login shell config.

I do not want this to be a variable for my X clients. I want it to be
a variable for my login sessions, graphical or not. I cannot put it
into .bashrc because it would probably not get executed for the X
session anyway, and my path would probably grow insanely in every make
script as nested shells are executed. Even the bash man page advises
against that.

Thanks

Michal



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



Bug#460820: marked as done (x11-common: no login shell run when logging in through gdm)

2008-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2008 22:29:48 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#460820: x11-common: no login shell run when logging in 
through gdm
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: x11-common
Version: 1:7.3+10
Severity: normal


When I log in through gdm no login shell is run. I can tell because when
I run bash -l manually it adds ~/bin to my path but it is not there when
I log in through gdm.

I normally fix this by writing my own .xinitrc/.Xsession but the global
xsession scripts should be fixed so that the wm sees full environment.

Genereal solution might be hard, though. It would be easily fixable for
bash by adding stuff to the session setup but ash/tcsh/... users should
not be left out either I guess.

Possibly the shell packages could install a script that could be used to
execute a progrem as if it was executed from a login shell that would
work the same for any shell :)


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages x11-common depends on:
ii  debconf [debconf-2.0] 1.5.17 Debian configuration management sy
ii  debianutils   2.28.2 Miscellaneous utilities specific t
ii  libc6 2.7-5  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


---End Message---
---BeginMessage---
Please keep the bug in CC when replying.



Michal Suchanek wrote:
 It's the config for my shell. I (or rather the maintainer of bash or
 base-files in this case) put that stuff into .bash_profile to be
 executed when I log in.
   

If it's the config for your shell, it goes in the config file for the
shell. It doesn't have to be loaded anywhere else.

 I do not want this to be a variable for my X clients. I want it to be
 a variable for my login sessions, graphical or not.

What do you mean login session? Your .xsession script? Just use the
right shell in .xsession, it will load its config file, you will get
your environment as in any instance of the shell.

  I cannot put it
 into .bashrc because it would probably not get executed for the X
 session anyway, and my path would probably grow insanely in every make
 script as nested shells are executed. Even the bash man page advises
 against that.
   

Also, you can put your environment definitions in a random script and
source it from both .bashrc and .xsessionrc.

Our Xsession already does everything needed here, so I am closing this bug.

Brice


---End Message---


Bug#425445: hpijs: Does anyone else find this a little annoying?

2008-01-15 Thread Peter Yellman
Package: hpijs
Version: 2.7.10+2.7.10-5
Followup-For: Bug #425445

Doesn't anyone else find it a little annoying to have 2 copies of every HP 
printer driver when defining a new printer in CUPS or KDE print manager?  As 
mentioned, this seems to be caused by the symlink /usr/share/cups/model/hpijs, 
which looks to have been placed there by hpijs-ppds.  The fix seems simple 
(delete the link), but I have to ask What is the function of that link?

Thanks,
Peter Yellman


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

Kernel: Linux 2.6.22.2-BIOSTAR-2007-08-10-a (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages hpijs depends on:
ii  gs-esp  8.15.3.dfsg.1-1  The Ghostscript PostScript interpr
ii  hplip   2.7.10-5 HP Linux Printing and Imaging Syst
ii  libc6   2.7-5GNU C Library: Shared libraries
ii  libcupsys2  1.3.5-1  Common UNIX Printing System(tm) - 
ii  libgcc1 1:4.2.2-4GCC support library
ii  libjpeg62   6b-14The Independent JPEG Group's JPEG 
ii  libsane 1.0.19~cvs20071213-1 API library for scanners
ii  libsnmp15   5.4.1~dfsg-5 SNMP (Simple Network Management Pr
ii  libssl0.9.8 0.9.8g-3 SSL shared libraries
ii  libstdc++6  4.2.2-4  The GNU Standard C++ Library v3
ii  libusb-0.1-42:0.1.12-8   userspace USB programming library

hpijs recommends no packages.

-- no debconf information



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



Bug#22506: A Kiss So Gentle

2008-01-15 Thread wsr001

Eternity of Your Love http://88.87.242.167/




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



Processed: Re: Bug#425445: hpijs: Does anyone else find this a little annoying?

2008-01-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 notfound  425445 hplip/2.7.10-5
Bug#425445: libx11-6: fails to cross-build. tries to run cross-built makekeys 
utility
Bug no longer marked as found in version 2.7.10-5.

 thank you
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#460820: x11-common: no login shell run when logging in through gdm

2008-01-15 Thread Michal Suchanek
On 15/01/2008, Brice Goglin [EMAIL PROTECTED] wrote:
 Please keep the bug in CC when replying.



 Michal Suchanek wrote:
  It's the config for my shell. I (or rather the maintainer of bash or
  base-files in this case) put that stuff into .bash_profile to be
  executed when I log in.
 

 If it's the config for your shell, it goes in the config file for the
 shell. It doesn't have to be loaded anywhere else.

OK, then what is the config file where I configure my path for any
session X or console?

Perhaps this is too general to be solved in this package.


  I do not want this to be a variable for my X clients. I want it to be
  a variable for my login sessions, graphical or not.

 What do you mean login session? Your .xsession script? Just use the
 right shell in .xsession, it will load its config file, you will get
 your environment as in any instance of the shell.

Login session is the stuff that gets executed after I sucessfully
authenticate (log in) to the system. This is currently possible to do
through login (/bin/login) or *dm (like xdm or gdm).


   I cannot put it
  into .bashrc because it would probably not get executed for the X
  session anyway, and my path would probably grow insanely in every make
  script as nested shells are executed. Even the bash man page advises
  against that.
 

 Also, you can put your environment definitions in a random script and
 source it from both .bashrc and .xsessionrc.

Yes I have to fix the scripts on every system. And think about what
stuff gets where if I do not want to break anything. That's what I
would like to avoid.


 Our Xsession already does everything needed here, so I am closing this bug.

Yes, the .xsessionrc support is certainly an improvement.

Thanks

Michal



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