Bug#621835: xmodmap -e 'remove lock = Caps_Lock' no longer works.
Hi there! On Mon, 21 Nov 2011 19:30:31 +0100, Carsten Otto wrote: in my case it helped to add caps to XKBOPTIONS in /etc/default/keyboard. After that I had my old behaviour back. Simply adding caps did not worked for me, while it did adding ctrl:nocaps, which is the same setting used by setxkbmap, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621835#58 As explained in /usr/share/doc/keyboard-configuration/README.Debian, I also did: # dpkg-reconfigure keyboard-configuration # dpkg-reconfigure console-setup Thx, bye, Gismo / Luca pgpgsCIOWDKRC.pgp Description: PGP signature
Re: Bug#677425: ITP: xserver-xorg-video-modesetting -- X.Org X server -- Generic modesetting driver
Hi Cyril! On Thu, 14 Jun 2012 10:12:28 +0200, Cyril Brulebois wrote: Luca Capello l...@pca.it (14/06/2012): [...] Thus, I would be a bit more verbose in the long description, to be clear when this driver is useful. [very useful explanation] The plan was updating the long description once things are a bit more settled. Thank you very much for the prompt reply, I have really appreciated and everything is now clear. Thx, bye, Gismo / Luca pgpTYWcdOxdAR.pgp Description: PGP signature
Bug#642012: x11-common: ssh-agent Xsession script does not check if gpg-agent will enable SSH support
usertags 642012 + pca.it-authentication thanks Hi there! Hellekin, the patch you have sent is referring to another bug, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444103#15 BTW, please always check if you need to Cc: other people interested in the bug (you did not Cc: me, so I was not aware of your replies). On Mon, 26 Sep 2011 16:36:52 +0200, Luca Capello wrote: On Mon, 19 Sep 2011 14:57:14 +0200, Julien Cristau wrote: On Sun, Sep 18, 2011 at 21:51:21 +0200, Luca Capello wrote: This leaves the bug opened: I would be glad to explore other solutions, but AFAIK without checking gpg.conf and gpg-agent.conf there is no way to know *beforehand* 1) if gpg-agent will run and 2) if the latter will provide SSH support. This is the real problem. Please note that until now ssh-agent is *never* started if gpg-agent has been started at least once with SSH support, for the following reasons (and this is another bug, no matter what): 1) 90gpg-agent is sourced before 90x11-common_ssh-agent 2) gpg-agent does not remove its PID file when exiting, see #642021 Sounds like that should be fixed. Patch sent upstream and block added. http://news.gmane.org/find-root.php?message_id=1316457193-26043-1-git-send-email-luca%40pca.it http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;bug=642021 Upstream's opinion is that the PID file must not be removed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642021#33 3) 90gpg-agent sources the PID file above, which means that SSH_AUTH_SOCK is defined *before* any gpg-agent is started at all Shouldn't the if ! $GPGAGENT 2/dev/null; then line in 90gpg-agent be followed by unsetting the variables (and maybe removing the file) it just read since it found out they don't work? Good catch, I will follow-up on the other bug report. However, unsetting (at least) the SSH_AUTH_SOCK variable is not correct, because it could be defined in ~/.Xsessionrc. According to its manpage, it is ssh-agent that sets this variable, so any value in ~/.Xsessionrc (sourced by 40x11-common_xsessionrc, so before any 90*agent) should be simply ignored: A UNIX-domain socket is created and the name of this socket is stored in the SSH_AUTH_SOCK environment variable. The socket is made accessible only to the current user. This method is easily abused by root or another instance of the same user. However, given upstream's opinion on the PID file not to be removed, I would simply unset the variables. This at least to be sure that variables from dead gpg-agent processes will not influence the current login. 4) 90x11-common_ssh-agent starts ssh-agent only if SSH_AUTH_SOCK is empty, which is not the case as per point 3 [...] IMHO the real bug is to try to start ssh-agent in a system-wide fashion via /etc/X11/Xsession.options, while this is (clearly) a user option. This is also why I fear the new Xsession use-gpg-agent option at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412993#20. The fact that ssh_config does not have any way to define that we want the agent is probably the original cause of this bug. Can we switch the order so that 1) doesn't apply? And turn ssh-agent into a no-op when it's started by gpg-agent with ssh support (assuming it's not already)? I still fail to see your solution: when both Xsession scripts do their checks there is no agent running at all, so reverting the order should not change anything. Again, how do you know that gpg-agent will be started with SSH support? The key is SSH_AUTH_SOCK, which should be *anyway* set is gpg-agent should be started with the SSH support, which is covered by: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444103#15 Git patch attached. Test packages fixing #444103, #642012 and #642021 are available at: http://people.debian.org/~gismo/tmp/gnupg2_2.0.18-3~gismo444103.642012.642021.1.dsc Finally, may I ask why this file is not provided by openssh-client? I could not find any reference in the x11-common changelog.Debian nor x11-common Recommends:/Suggests:/Enhances: openssh-client. The changelog suggests this was already in xfree86-common with the initial xfree86 4.0 upload 11 years ago. I could go look for earlier changelogs, but I guess hysterical raisins pretty much covers it? I came to the same conclusion. However, I still think openssh-client would be a better place, because until now ssh-agent is started unconditionally without asking the user (and FWIW not event the sysadmin). The fact that there is no way to have ssh-agent configured through a user variable changes the whole situations, so I will not bother any more with this. Attached a Git patch to add the Enhances: above, including dbus-x11 for the very same reason. The last sentence is independent of the gpg-agent stuff, can it be included anyway? Thx, bye, Gismo / Luca From 2125295b8c8348839ddf91db9637b1d97a3d3de2 Mon Sep 17 00:00:00 2001 From: Luca Capello l...@pca.it
Re: Bug#619636: Info received (Clutter problem?)
user 619636 l...@pca.it
usertags 619636 + pca-communication
thanks
Hi there!
Cc:ing all the people involved with this bug, sorry for the spam. Also
Cc:ing the Debian X Strike Force for comments about the Mesa part.
On Sat, 16 Apr 2011 17:38:51 +0200, Alex Stewart wrote:
See also bug 620908. IMO, they should not be merged, because 619636
can be solved in two ways: depending on a version of libclutter-1.0-0
with a fix for bug 620908 or, AFAICT, building empathy without
libchamplain support.
I can confirm that with the following diff empathy works without no
problem on a last-week up-to-date sid on libvirt/KVM with no HW
acceleration:
--8---cut here---start-8---
diff -Nru empathy-3.2.2/debian/control empathy-3.2.2/debian/control
--- empathy-3.2.2/debian/control2011-11-19 18:24:56.0 +0100
+++ empathy-3.2.2/debian/control2011-11-21 00:36:24.0 +0100
@@ -13,7 +13,6 @@
debhelper (= 8),
rarian-compat,
librarian-dev,
- libchamplain-gtk-0.12-dev,
libglib2.0-dev (= 2.28),
libgtk-3-dev (= 3.0.2),
libtelepathy-glib-dev (= 0.16.0),
diff -Nru empathy-3.2.2/debian/rules empathy-3.2.2/debian/rules
--- empathy-3.2.2/debian/rules 2011-11-19 18:24:56.0 +0100
+++ empathy-3.2.2/debian/rules 2011-11-21 00:51:04.0 +0100
@@ -13,7 +13,7 @@
DEB_CONFIGURE_EXTRA_FLAGS := --enable-spell \
--enable-webkit \
- --enable-map=yes \
+ --enable-map=no \
--enable-geocode=yes \
--with-cheese \
--with-eds \
--8---cut here---end---8---
On Wed, 16 Nov 2011 11:07:45 +0100, Laurent Bigonville wrote:
According to upstream this is a known issue and due to the software
rasterizer in mesa. The only way here is, for now, to use proper
hardware acceleration.
Until this week-end Mesa updates (see below), it seemed that there was
another way: installing libgl1-mesa-swx11 solved the problem for two
up-to-date sid, a schroot and the libvirt/KVM above. However, in the
latter case GNOME 3 always crashes and I can not login (this should be
confirmed on a real machine, i.e. not on a VM). So the situation was
the following:
1) libgl1-mesa-glx alone
= empathy segfault
2) libgl1-mesa-glx *AND* libgl1-mesa-dri *AND* HW acceleration
= empathy works
3) libgl1-mesa-swx11 (with or without libgl1-mesa-dri)
= empathy works, but GNOME 3 crashes
libclutter-1.0 already Depends: on 'libgl1-mesa-glx | libgl1' and this
includes also libgl1-mesa-swx11 (which Provides: libgl1). What it could
be needed is a Depends: on 'libgl1-mesa-dri | libgl1-mesa-swx11':
--8---cut here---start-8---
diff -Nru clutter-1.0-1.8.2/debian/control.in
clutter-1.0-1.8.2/debian/control.in
--- clutter-1.0-1.8.2/debian/control.in 2011-11-14 13:18:06.0 +0100
+++ clutter-1.0-1.8.2/debian/control.in 2011-11-21 15:16:07.0 +0100
@@ -36,6 +36,7 @@
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
+ libgl1-mesa-dri | libgl1-mesa-swx11
Recommends: libclutter-1.0-common
Breaks: python-clutter ( 1.3.2)
Pre-Depends: ${misc:Pre-Depends}
--8---cut here---end---8---
The long term solution is to switch to llvmpipe in debian to make it
work for people that cannot get hardware acceleration. I think that the
next release of mesa has switch to this.
It seems that upstream Mesa already solved this in a different way:
https://bugs.archlinux.org/task/26686
https://bugzilla.redhat.com/show_bug.cgi?id=747276#c18
The upstream fix went into the new Mesa package during the week-end (I
was building the old 7.11-6 plus this patch, but given that the build
process needed more than 5 GB of disk space I could not get it earlier):
http://anonscm.debian.org/gitweb/?p=pkg-xorg/lib/mesa.git;a=commitdiff;h=b2fbf8225bfed2d6f5339ba0a97ddbc5e6cc491a
http://packages.qa.debian.org/m/mesa/news/2028T002111Z.html
Nevertheless, empathy still segfaults witwh libgl1-mesa-glx_7.11.1-1
alone (i.e. without libgl1-mesa-dri) on both sid above, the schroot and
the libvirt/KVM. However, the error on the latter is a bit more
explicative:
=
luca.capello@gismo-sid:~$ empathy
(empathy:2824): Clutter-CRITICAL **: Unable to initialize Clutter: \
The OpenGL version could not be determined
Segmentation fault
luca.capello@gismo-sid:~$ empathy
=
Installing libgl1-mesa-dri solves the problem, which is anyway a
progress, given that before it did not work at all on libvirt/KVM with
no HW acceleration (see point 2 above).
Thx, bye,
Gismo / Luca
pgpIHE2nSDccu.pgp
Description: PGP signature
Bug#642012: x11-common: ssh-agent Xsession script does not check if gpg-agent will enable SSH support
block 642012 by 642021 thanks Hi there! On Mon, 19 Sep 2011 14:57:14 +0200, Julien Cristau wrote: On Sun, Sep 18, 2011 at 21:51:21 +0200, Luca Capello wrote: This leaves the bug opened: I would be glad to explore other solutions, but AFAIK without checking gpg.conf and gpg-agent.conf there is no way to know *beforehand* 1) if gpg-agent will run and 2) if the latter will provide SSH support. This is the real problem. Please note that until now ssh-agent is *never* started if gpg-agent has been started at least once with SSH support, for the following reasons (and this is another bug, no matter what): 1) 90gpg-agent is sourced before 90x11-common_ssh-agent 2) gpg-agent does not remove its PID file when exiting, see #642021 Sounds like that should be fixed. Patch sent upstream and block added. http://news.gmane.org/find-root.php?message_id=1316457193-26043-1-git-send-email-luca%40pca.it http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;bug=642021 3) 90gpg-agent sources the PID file above, which means that SSH_AUTH_SOCK is defined *before* any gpg-agent is started at all Shouldn't the if ! $GPGAGENT 2/dev/null; then line in 90gpg-agent be followed by unsetting the variables (and maybe removing the file) it just read since it found out they don't work? Good catch, I will follow-up on the other bug report. However, unsetting (at least) the SSH_AUTH_SOCK variable is not correct, because it could be defined in ~/.Xsessionrc. 4) 90x11-common_ssh-agent starts ssh-agent only if SSH_AUTH_SOCK is empty, which is not the case as per point 3 [...] IMHO the real bug is to try to start ssh-agent in a system-wide fashion via /etc/X11/Xsession.options, while this is (clearly) a user option. This is also why I fear the new Xsession use-gpg-agent option at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412993#20. The fact that ssh_config does not have any way to define that we want the agent is probably the original cause of this bug. Can we switch the order so that 1) doesn't apply? And turn ssh-agent into a no-op when it's started by gpg-agent with ssh support (assuming it's not already)? I still fail to see your solution: when both Xsession scripts do their checks there is no agent running at all, so reverting the order should not change anything. Again, how do you know that gpg-agent will be started with SSH support? Please also note that unfortunately ssh-agent starts a new instance even if another one is already running: = $ gpg-agent gpg-agent: gpg-agent running and available $ export | grep -e GPG -e SSH declare -x GPG_AGENT_INFO=/tmp/gpg-g4sLIi/S.gpg-agent:1943:1 declare -x SSH_AGENT_PID=1943 declare -x SSH_AUTH_SOCK=/tmp/gpg-Gy6MdS/S.gpg-agent.ssh $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-CdRxIRsi7792/agent.7792; export SSH_AUTH_SOCK; SSH_AGENT_PID=7793; export SSH_AGENT_PID; echo Agent pid 7793; $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-PsTeGnGE7845/agent.7845; export SSH_AUTH_SOCK; SSH_AGENT_PID=7846; export SSH_AGENT_PID; echo Agent pid 7846; $ export | grep -e GPG -e SSH declare -x GPG_AGENT_INFO=/tmp/gpg-g4sLIi/S.gpg-agent:1943:1 declare -x SSH_AGENT_PID=1943 declare -x SSH_AUTH_SOCK=/tmp/gpg-Gy6MdS/S.gpg-agent.ssh $ ls -l /tmp/ | grep -e gpg -e ssh drwx-- 2 luca luca 60 Sep 25 17:29 gpg-g4sLIi drwx-- 2 luca luca 60 Sep 25 17:29 gpg-Gy6MdS drwx-- 2 luca luca 60 Sep 26 15:19 ssh-CdRxIRsi7792 drwx-- 2 luca luca 60 Sep 26 15:20 ssh-PsTeGnGE7845 = Finally, may I ask why this file is not provided by openssh-client? I could not find any reference in the x11-common changelog.Debian nor x11-common Recommends:/Suggests:/Enhances: openssh-client. The changelog suggests this was already in xfree86-common with the initial xfree86 4.0 upload 11 years ago. I could go look for earlier changelogs, but I guess hysterical raisins pretty much covers it? I came to the same conclusion. However, I still think openssh-client would be a better place, because until now ssh-agent is started unconditionally without asking the user (and FWIW not event the sysadmin). The fact that there is no way to have ssh-agent configured through a user variable changes the whole situations, so I will not bother any more with this. Attached a Git patch to add the Enhances: above, including dbus-x11 for the very same reason. Thx, bye, Gismo / Luca From 95a9f699207107621cf59443efd7b2a1f2effa0e Mon Sep 17 00:00:00 2001 From: Luca Capello l...@pca.it Date: Mon, 26 Sep 2011 16:31:54 +0200 Subject: [PATCH] debian/control: x11-common Enhances: dbus-x11 and openssh-client Please see #642012 for the full rationale. --- debian/changelog |9 + debian/control |1 + 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/debian/changelog b/debian/changelog index f2198f9..361e81a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +xorg (1:7.6+10) UNRELEASED; urgency=low + + [ Luca Capello ] + * debian/control: ++ add
Bug#642012: x11-common: ssh-agent Xsession script does not check if gpg-agent will enable SSH support
Package: x11-common
Version: 1:7.6+8
Severity: important
File: /etc/X11/Xsession.d/90x11-common_ssh-agent
Affects: openssh-client gnupg-agent
Tags: patch
Hi there!
As the title suggests, if you install both openssh-client and
gnupg-agent and you enable the SSH support in the latter, ssh-agent is
anyway started by the Xsession script:
=
$ ps aux | grep agent
luca 16399 0.0 0.0 12236 304 ?Ss 16:09 0:00 \
/usr/bin/ssh-agent \
/usr/bin/gpg-agent --daemon --sh
--write-env-file=/home/luca/.gnupg/gpg-agent-info-gismo \
/usr/bin/ck-launch-session \
/usr/bin/dbus-launch --exit-with-session /home/luca/.xsession
luca 16400 0.0 0.0 18968 424 ?Ss 16:09 0:00 \
/usr/bin/gpg-agent --daemon --sh
--write-env-file=/home/luca/.gnupg/gpg-agent-info-gismo \
/usr/bin/ck-launch-session \
/usr/bin/dbus-launch --exit-with-session /home/luca/.xsession
$ ls -l /tmp | grep -e gpg -e ssh
drwx-- 2 luca luca 60 Sep 18 16:09 gpg-0drpxf
drwx-- 2 luca luca 60 Sep 18 16:09 gpg-xSZr4Z
drwx-- 2 luca luca 60 Sep 18 16:09 ssh-GmzGjVQ16373
$ grep -s '^[[:space:]]*use-agent' ~/.gnupg/gpg.conf
use-agent
$ grep -s '^[[:space:]]*enable-ssh-support' ~/.gnupg/gpg-agent.conf
enable-ssh-support
$ export | grep -e GPG -e SSH
declare -x GPG_AGENT_INFO=/tmp/gpg-0drpxf/S.gpg-agent:16400:1
declare -x SSH_AGENT_PID=16400
declare -x SSH_AUTH_SOCK=/tmp/gpg-xSZr4Z/S.gpg-agent.ssh
=
Indeed the check for $SSH_AUTH_SOCK is not enough: this variable is not
set given that gpg-agent has not been started yet. Here is the patch:
--8---cut here---start-8---
--- 90x11-common_ssh-agent.ORG
+++ 90x11-common_ssh-agent
@@ -9,10 +9,15 @@
if has_option use-ssh-agent; then
if [ -x $SSHAGENT ] [ -z $SSH_AUTH_SOCK ] \
[ -z $SSH2_AUTH_SOCK ]; then
-STARTSSH=yes
-if [ -f /usr/bin/ssh-add1 ] cmp -s $SSHAGENT /usr/bin/ssh-agent2; then
- # use ssh-agent2's ssh-agent1 compatibility mode
- SSHAGENTARGS=-1
+# check if gpg-agent will be started with SSH support
+: ${GNUPGHOME=$HOME/.gnupg}
+if ! ( grep -qs '^[[:space:]]*use-agent' $GNUPGHOME/gpg.conf \
+ grep -qs '^[[:space:]]*enable-ssh-support'
$GNUPGHOME/gpg-agent.conf ); then
+ STARTSSH=yes
+ if [ -f /usr/bin/ssh-add1 ] cmp -s $SSHAGENT /usr/bin/ssh-agent2; then
+# use ssh-agent2's ssh-agent1 compatibility mode
+SSHAGENTARGS=-1
+ fi
fi
fi
fi
--8---cut here---end---8---
Thx, bye,
Gismo / Luca
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-rc4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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.41
ii lsb-base 3.2-28
x11-common recommends no packages.
x11-common suggests no packages.
-- debconf information:
x11-common/xwrapper/allowed_users: Console Users Only
x11-common/xwrapper/actual_allowed_users: console
pgpD2U5wY5cVK.pgp
Description: PGP signature
Bug#642012: x11-common: ssh-agent Xsession script does not check if gpg-agent will enable SSH support
Hi there! On Sun, 18 Sep 2011 17:05:37 +0200, Julien Cristau wrote: On Sun, Sep 18, 2011 at 16:53:13 +0200, Luca Capello wrote: --8---cut here---start-8--- [patch] --8---cut here---end---8--- NAK, as far as I'm concerned this script has no business looking around in gpg.conf. This leaves the bug opened: I would be glad to explore other solutions, but AFAIK without checking gpg.conf and gpg-agent.conf there is no way to know *beforehand* 1) if gpg-agent will run and 2) if the latter will provide SSH support. Please note that until now ssh-agent is *never* started if gpg-agent has been started at least once with SSH support, for the following reasons (and this is another bug, no matter what): 1) 90gpg-agent is sourced before 90x11-common_ssh-agent 2) gpg-agent does not remove its PID file when exiting, see #642021 3) 90gpg-agent sources the PID file above, which means that SSH_AUTH_SOCK is defined *before* any gpg-agent is started at all 4) 90x11-common_ssh-agent starts ssh-agent only if SSH_AUTH_SOCK is empty, which is not the case as per point 3 Here is the patch to test the behavior above: --8---cut here---start-8--- --- 90x11-common_ssh-agent.ORG +++ 90x11-common_ssh-agent @@ -14,6 +14,11 @@ # use ssh-agent2's ssh-agent1 compatibility mode SSHAGENTARGS=-1 fi + else +cat EOF $HOME/.xsession-errors +/etc/X11/Xsession.d/90x11-common_ssh-agent: SSH_AUTH_SOCK='$SSH_AUTH_SOCK' +/etc/X11/Xsession.d/90x11-common_ssh-agent: not starting ssh-agent +EOF fi fi --8---cut here---end---8--- IMHO the real bug is to try to start ssh-agent in a system-wide fashion via /etc/X11/Xsession.options, while this is (clearly) a user option. This is also why I fear the new Xsession use-gpg-agent option at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412993#20. The fact that ssh_config does not have any way to define that we want the agent is probably the original cause of this bug. Finally, may I ask why this file is not provided by openssh-client? I could not find any reference in the x11-common changelog.Debian nor x11-common Recommends:/Suggests:/Enhances: openssh-client. Thx, bye, Gismo / Luca pgpYqM8CnyFUq.pgp Description: PGP signature
Bug#641588: x11-xserver-utils: [xmodmap] error in manpage example about swapping Control_L/Caps_Lock keys
Package: x11-xserver-utils Version: 7.6+3 Severity: minor File: /usr/bin/xmodmap Tags: upstream patch Hi there! Simply enough, using for CapsLock the same name used later on (patch against upstream Git repository, bug number to be updated): --8---cut here---start-8--- commit c5d1727a37d1edaa269655efe5a14b3e909792ee Author: Luca Capello l...@pca.it Date: Wed Sep 14 15:56:14 2011 +0200 man: s/Shift/CapsLock/ when swapping Control_L/Caps_Lock keys See Debian bug #NN. Signed-off-by: Luca Capello l...@pca.it diff --git a/man/xmodmap.man b/man/xmodmap.man index f864e6e..1ed1ca1 100644 --- a/man/xmodmap.man +++ b/man/xmodmap.man @@ -261,7 +261,7 @@ keysym period = period greater .EE .PP One of the more irritating differences between keyboards is the location of the -Control and Shift Lock keys. A common use of \fIxmodmap\fP is to swap these +Control and CapsLock keys. A common use of \fIxmodmap\fP is to swap these two keys as follows: .EX ! --8---cut here---end---8--- Thx, bye, Gismo / Luca -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-rc4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x11-xserver-utils depends on: ii cpp 4:4.6.1-2 ii libc62.13-21 ii libice6 2:1.0.7-2 ii libx11-6 2:1.4.4-1 ii libxau6 1:1.0.6-3 ii libxaw7 2:1.0.9-2 ii libxcursor1 1:1.1.12-1 ii libxext6 2:1.3.0-3 ii libxi6 2:1.4.3-3 ii libxmu6 2:1.1.0-2 ii libxmuu1 2:1.1.0-2 ii libxrandr2 2:1.3.2-2 ii libxrender1 1:0.9.6-2 ii libxt6 1:1.1.1-2 ii libxxf86vm1 1:1.1.1-2 x11-xserver-utils recommends no packages. Versions of packages x11-xserver-utils suggests: pn cairo-5cnone pn nickle none pn xorg-docs-core none -- no debconf information pgp5XQ6L14V6T.pgp Description: PGP signature
Bug#621835: xmodmap -e 'remove lock = Caps_Lock' no longer works.
unarchive 621835 reopen 621835 ! found 621835 7.6+3 severity 621835 important thanks [Resending because the bug was archived thus the BTS rejected this email, I was sure it would have worked because I seem to remember it did work in the past. Sorry if you got it twice.] Hi there! Reopening this bug, setting myself as submitter, adding the current version of x11-xserver-utils in unstable and setting Severity: important, for obvious reasons. On Sun, 10 Apr 2011 03:40:40 +0200, Cyril Brulebois wrote: jida...@jidanni.org jida...@jidanni.org (10/04/2011): Nobody can figure out how to do it because there are no examples on the setxkbmap man page. I wrote it's an option. So you use: setxkbmap -option $whatiwrote and that works. That does not mean that it is easy to find it out, and I was in the same situation as jidanni, here why. I wanted to map Caps_Lock as Control_L, so I fired up `man xmodmap` and found an example (then discovering a bug, see #641588), but I was too much optimistic. Having found this bug I thought that something like $ setxkbmap -option caps:ctrl would have been correct. Finally, /usr/share/X11/xkb/rules/base.lst told me that what I wanted was the following command, which is counterintuitive to say the least: $ setxkbmap -option ctrl:nocaps CB And stop using xmodmap, that's obsolete. Well why don't you put a warning on its man page. Else how is anybody supposed to know? Well, nobody bothered to send a patch. Feel free to. Nothing wrong with you, but I hope you are kidding, especially for the obsolete part. 1) it seems that xmodmap is still developed: http://cgit.freedesktop.org/xorg/app/xmodmap/ 2) why is CapsLock the only key that stopped working with xmodmap, while for the other everything is OK? Until today I was using myself with success the following ~/.xmodmaprc: --8---cut here---start-8--- !! unset Caps_Lock and Win_key remove lock = Caps_Lock remove mod4 = Super_L ! Caps Lock as Win key keycode 66 = Super_L add mod4 = Super_L --8---cut here---end---8--- I completely understand John's feelings, xmodmap is a default/old Unix tool, why breaking it? What are the advantages of the latter? http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=yesbug=621835#41 Thx, bye, Gismo / Luca -- 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/87obynupvs@gismo.pca.it
Bug#624146: xserver-xorg-video-intel: [SandyBridge] Totem crahses X.Org and then Failed to allocate framebuffer
Package: xserver-xorg-video-intel Version: 2:2.13.0-6 Severity: important Hi there! Well, the subject says all. I tried to play a DivX video in Totem (simply double-clicking on it from Nautilus), then I left before the video started and when I came back the screen was flickering between two previous console states [1]. [1] I am experiencing some libata errors linked to a tape drive, so there are plenty of error messages on the console https://ata.wiki.kernel.org/index.php/Libata_error_messages Restarting GDM3 caused me to discover the error in the X.Org log [2][3], and I am sorry I did not check it before, so I do not really what was the cause of Totem crashing. [3] why do I have 4 different of them? [4] why is GDM3 never picking up VT 7? = luca.capello@tinello:~$ grep VT /var/log/Xorg.* /var/log/Xorg.0.log:(++) using VT number 8 /var/log/Xorg.0.log.old:(++) using VT number 9 /var/log/Xorg.1.log:(++) using VT number 8 /var/log/Xorg.1.log:(II) AIGLX: Suspending AIGLX clients for VT switch /var/log/Xorg.1.log.old:(++) using VT number 8 /var/log/Xorg.1.log.old:(II) AIGLX: Suspending AIGLX clients for VT switch /var/log/Xorg.2.log:(++) using VT number 9 /var/log/Xorg.2.log:(II) AIGLX: Suspending AIGLX clients for VT switch /var/log/Xorg.2.log.old:(++) using VT number 9 /var/log/Xorg.2.log.old:(II) AIGLX: Suspending AIGLX clients for VT switch /var/log/Xorg.3.log:(++) using VT number 9 /var/log/Xorg.3.log:(II) AIGLX: Suspending AIGLX clients for VT switch luca.capello@tinello:~$ = Please note that this is the first time my parents' computer has had such an error: today I installed the 2.6.38 kernel from wheezy (no other backport available) and the network card (8086:1503, Intel 82579V rev 04) needed at least 2.6.37. This action was done to check if the libata error above was still there (which is, FWIW). Given that the machine in question is doing some wiping as another user (luckily on a GNU screen session), I will not stop it for the next 12 hours, in case there is need for some tests. FYI, while now all the 8GB of RAM are full, I also tried when only 5GB of them were occupied, but with no luck. Thx, bye, Gismo / Luca -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Feb 26 22:08 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1889472 Feb 18 21:42 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 26841 Mar 7 22:25 /var/log/Xorg.3.log -rw-r--r-- 1 root root 26846 Apr 16 11:30 /var/log/Xorg.1.log -rw-r--r-- 1 root root 26846 Apr 24 20:16 /var/log/Xorg.2.log -rw-r--r-- 1 root root 15148 Apr 26 00:42 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.37-trunk-amd64 x86_64 Debian Current Operating System: Linux tinello 2.6.38-2-amd64 #1 SMP Thu Apr 7 04:28:07 UTC 2011 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=/dev/mapper/tinello-root ro quiet Build Date: 18 February 2011 08:27:24PM xorg-server 2:1.7.7-13 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Apr 26 00:42:39 2011 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled,
[Planet Debian] Cyril Brulebois: Debian XSF News #5
Hi there! On Thu, 17 Feb 2011 02:00:08 +0100, Planet Debian wrote: URL: http://blog.ikibiki.org/2011/02/17/DXN-5/ [...] * I uploaded a [new xorg-server][5] to `unstable` with the following changes: * The hellish [dependency loop (#362313)][6] is finally gone! A big THANK YOU for that, I was reading that bug and trying to understand if it could have been solved in some way or not, but Cyril got it first :-) Thx, bye, Gismo / Luca pgpiMF21c4PsC.pgp Description: PGP signature
Bug#612471: xserver-xorg-core uninstallable, dependencies broken
Hi there! On Tue, 08 Feb 2011 18:26:09 +0100, Cyril Brulebois wrote: the_...@gmx.net the_...@gmx.net (08/02/2011): Package: xserver-xorg-core Version: 1.9.4-1 Severity: grave not a bug per se. Welcome to sid. This is questionable, there is a bug (upgrades are not possible, of course Severity: at most important, IMHO normal) and the fact that it is in sid or not does not matter. And closing this bug does not help at all users that look at the BTS to find already-reported bug, here what I was submitting as a new bug: --8---cut here---start-8--- I found this problem yesterday morning, but then I waited until today to be sure it was not a problem of mirror syncing (cdn.debian.net - 129.132.86.210 AKA ftp.ch.debian.org). Basically, upgrading to the latest version in sid does not work: = gismo:~# apt-get install xserver-xorg-core xserver-xorg \ xserver-xorg-video-intel xserver-xorg-input-evdev Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-input-evdev is already the newest version. xserver-xorg-input-evdev set to manually installed. xserver-xorg-video-intel is already the newest version. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg : Depends: xserver-xorg-input-all but it is not going to be installed or xorg-driver-input xserver-xorg-core : Breaks: xserver-xorg-input-4 Breaks: xserver-xorg-input-7 Breaks: xserver-xorg-video-6 xserver-xorg-input-evdev : Depends: xorg-input-abi-7.0 xserver-xorg-video-intel : Depends: xorg-video-abi-6.0 E: Broken packages = --8---cut here---end---8--- I'm not sure wether my system is just fucked up, but to me it seems likely, that this bug makes it completely impossible to install any graphical environment right now. For everyone. Yes. Drivers are missing due to: http://bugs.debian.org/612137 Sorry, but I do not see any explanation there which could help users to understand what is the real problem with X.org packages. In the meanwhile, you could pick drivers from experimental. Thanks, this does the trick: = gismo:~# apt-get install xserver-xorg-core xserver-xorg \ xserver-xorg-video-intel/experimental xserver-xorg-input-evdev/experimental Reading package lists... Done Building dependency tree Reading state information... Done Selected version '2:2.14.0-2' (Debian:experimental [amd64]) for 'xserver-xorg-video-intel' Selected version '1:2.6.0-1' (Debian:experimental [amd64]) for 'xserver-xorg-input-evdev' Suggested packages: xfonts-100dpi xfonts-75dpi xfonts-scalable The following packages will be upgraded: xserver-xorg xserver-xorg-core xserver-xorg-input-evdev xserver-xorg-video-intel 4 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. = What I would do: --8---cut here---start-8--- reopen 612471 ! retitle 612471 xserver-xorg: dependencies problem with -input-evdev and -video-intel reassign 612471 xserver-xorg found 612471 1:7.5+8 severity 612471 normal block 612471 by 612137 thanks --8---cut here---end---8--- I did not do anything because you are the maintainer, so I am fine if you want to keep the situation as it is. Thx, bye, Gismo / Luca pgpvJC0QfkZb8.pgp Description: PGP signature
Bug#486317: xterm: missing .desktop files
reopen 486317 ! found 486317 243-1 tags 486317 + patch user pkg-fso-ma...@lists.alioth.debian.org usertags 486317 + xdg-menu thanks Hi there! I re-openend this bug and changed the submitter to myself. I have cc:ed both the original submitter for his information and the pkg-fso-maint@ mailing list since this is important for Debian on the Openmoko Neo FreeRunner. On Sat, 21 Jun 2008 11:18:49 +0200, Julien Cristau wrote: On Sun, Jun 15, 2008 at 11:34:12 +0200, Josef Spillner wrote: The xterm package contains various graphical applications. They should be accessible through the xdg menu system in addition to the Debian menu entries. I would like to see at least a .desktop file for uxterm. There was one at some point, but the desktop environment people didn't seem to like that, so I removed it. I won't add it unless it's requested by gnome/xfce/kde people. E17 menu considers .desktop files in /u/s/applications, which means that if xterm does not provide such a file, it is not possible to start it From the menu. This is even more important when using the Illume profile on the Openmoko Neo FreeRunner. A simple .desktop file based on the one I found on the Ubuntu BTS: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/93151 --8---cut here---start-8--- [Desktop Entry] Encoding=UTF-8 Name=XTerm Comment=X terminal emulator Icon=xterm-color_32x32 TryExec=xterm Exec=xterm Type=Application Categories=Utility;TerminalEmulator; StartupNotify=false --8---cut here---end---8--- There are three open questions... 1) The file above is for the xterm binary only, while the xterm package provide 4 terminal emulators: I am not sure we need a .desktop file for all of them, but I consider lxterm the necessary one, since it consider the user locale. 2) According to the latest freedesktop.org menu specification v1.1 http://standards.freedesktop.org/menu-spec/menu-spec-1.1.html TerminalEmulator applications should be part of the System main category, thus I quickly checked other main terminal emulators: - gnome-terminal is in Utility - konsole is in System - xfce4-terminal is in both System and Utility 3) I am not sure if the value of StartupNotify is correct, according to the latest freedesktop.org desktop entry specification v1.1 http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.1.html Thx, bye, Gismo / Luca pgpbtGWnsxxd0.pgp Description: PGP signature
Bug#520955: ITP: xserver-xorg-video-glamo -- X.Org X server -- SMedia Glamo display driver
Package: wnpp Owner: Luca Capello l...@pca.it Severity: wishlist User: pkg-fso-ma...@lists.alioth.debian.org Usertags: package-creation * Package name: xserver-xorg-video-glamo Version : MMDD.gitCOMMIT (read below) Upstream Author : mainly Lars-Peter Clausen l...@metafoo.de * URL or Web page : http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary * License : multiple, mostly XFree86 (full texts below) Description : X.Org X server -- SMedia Glamo display driver This package provides the driver for the SMedia Glamo 3362 chipset, mostly found on the Openmoko Neo FreeRunner (GTA02). . More information about X.Org can be found at: URL:http://www.X.org URL:http://xorg.freedesktop.org URL:http://lists.freedesktop.org/mailman/listinfo/xorg . This package is built from the X.Org xf86-video-glamo driver module. = NB, I cc:ed a lot of lists: please refrain to discuss non-Debian issues on all of them. Except for general issues, pkg-fso-maint@ is the most relevant one, which should always be cc:ed, TIA. This driver is based on the XFree86 fbdev driver, then adapted to the SMedia Glamo chipset, more information are available at http://wiki.openmoko.org/wiki/Smedia_Glamo_3362 In my plan, this supersedes the Xglamo kdrive X11 server, which AFAIK is not update anymore, ATM available in the pkg-fso repository at http://pkg-fso.alioth.debian.org The xserver-xorg-video-glamo package as well will be maintained under the pkg-fso umbrella, but I would like to work as close as possible with the X Strike Force, to be sure the package conforms their standards. If the X Strike Force would like to take care of the package, I would more than glad to offer it to them... In src/glamo-driver.c, GLAMO_VERSION is set to 1000: however, this driver has not seen any public release yet, thus my intent to use the date of the last Git commit plus the first 8 letters of the Git commit itself as upstream version. The full license texts are: - from COPYING file == Copyright (C) 1994-2003 The XFree86 Project, Inc. All Rights Reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is fur- nished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT- NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON- NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of the XFree86 Project shall not be used in advertising or otherwise to promote the sale, use or other deal- ings in this Software without prior written authorization from the XFree86 Project. = - from C source files = [copyrights holders mainly Openmoko Inc, Lars-Peter Clausen and Eric Anholt] Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of the copyright holders not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. The copyright holders make no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. = - exceptions = * src/glamo-driver.c no license bits, authors Alan Hourihane and Michale Dänzer * src/glamo-regs.h GPL-2+, author Harald Welte I think that not only the two exceptions, but everything about the license needs further investigation, with for sure advices from upstream. I will start to do real works
Bug#508476: xserver-xorg-core: Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
Package: xserver-xorg-core Version: 2:1.5.3-1 Severity: grave Hi there! I tried a configless situation with the latest X.Org in experimental, but this resulted in X not starting at all: = luca$gismo:~$ startx X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.17.7 x86_64 Debian Current Operating System: Linux gismo.pca.it 2.6.27-1-amd64 #1 SMP Wed Dec 10 04:03:39 UTC 2008 x86_64 Build Date: 12 November 2008 12:59:43PM xorg-server 2:1.5.3-1 (bui...@xenophanes) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 11 01:04:20 2008 (EE) Unable to locate/open config file New driver is intel (==) Using default built-in configuration (30 lines) Fatal server error: Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. l...@gismo:~$ = I do not remember why I have installed the X.Org fbdev, but simply removing it (version 1:0.4.0-2 from experimental) lets X starts. I am not completely sure the severity is correct, but from what I understood X tries to use every driver is installed, which does not sound correct to me. BTW1, in the information below, I substituted the Xorg.0.log with the one coming from the non-starting X BTW2, why does X consider not having a config file an non-fatal error? Should not that be a warning instead? Thx, bye, Gismo / Luca -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-10-13 18:41 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1797392 2008-11-12 14:14 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) /etc/X11/xorg.conf does not exist. Xorg X server log files on system: -rw-r--r-- 1 root root 22434 2008-12-11 02:13 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.17.7 x86_64 Debian Current Operating System: Linux gismo.pca.it 2.6.27-1-amd64 #1 SMP Wed Dec 10 04:03:39 UTC 2008 x86_64 Build Date: 12 November 2008 12:59:43PM xorg-server 2:1.5.3-1 (bui...@xenophanes) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 11 01:02:06 2008 (EE) Unable to locate/open config file (II) Loader magic: 0x7b1ec0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on linux (--) using VT number 7 (--) PCI:*(0...@0:2:0) Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xee10/524288, 0xd000/268435456, 0xee20/262144, I/O @ 0x1800/8 (--) PCI: (0...@0:2:1) Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xee18/524288 (II) Scanning /usr/share/xserver-xorg/pci directory for additional PCI ID's supported by the drivers (II) Matched intel from file name intel.ids (==) Matched intel for the autoconfigured driver New driver is intel (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section Device Identifier Builtin Default intel Device 0 Driver intel EndSection Section Screen Identifier Builtin Default intel Screen 0 Device Builtin Default intel Device 0 EndSection Section Device Identifier Builtin Default fbdev Device 0 Driver fbdev EndSection Section Screen Identifier Builtin Default fbdev Screen 0 Device Builtin Default fbdev Device 0 EndSection Section Device Identifier Builtin Default vesa Device 0 Driver vesa EndSection Section Screen
Bug#502120: xserver-xorg: allows different /etc/X11/X symlinks as well as /usr/bin/X
Hi there! On Mon, 13 Oct 2008 23:20:02 +0200, Luca Capello wrote: On Mon, 13 Oct 2008 20:45:26 +0200, Julien Cristau wrote: There used to be some logic to change the /etc/X11/X symlink via debconf until about a year ago (it used to be needed when we had hardware specific X servers, which means before XFree86 4.0 iirc), so it might be possible to reintroduce that if you feel that Xglamo need it. I think that it could be helpful not only for Xglamo, but for the other KDrive servers as well (the first coming to my mind is xserver-xfbdev). A small update, which completely changes the importance of this bug: according to [1], Openmoko seems to consider Xglamo completely dead now in favor of a pure X.Org module. If the above will become official, my request will become a very minor one, since I will stop working on the Xglamo kdriver server ASAP. Thx, bye, Gismo / Luca Footnotes: [1] http://lists.openmoko.org/pipermail/community/2008-November/035903.html pgpABWXTQRaaT.pgp Description: PGP signature
Bug#501367: installation-reports: various problem on an Apple iMac G3
Hi Julien! On Mon, 20 Oct 2008 14:43:41 +0200, Julien Cristau wrote: On Tue, Oct 7, 2008 at 01:18:32 +0200, Luca Capello wrote: 3) X.Org This is the main problem: after the first reboot, X11 starts, but the screen remains black. [...] I can provide X.Org log files from etch and lenny as well as perform other tests or even installations: this is still a playing machine, thus no need to be careful with it :-) Yes please. Without the logs there's nothing we can do. Attached the lenny's one, because of my tests for bug #482140 [1] I already deleted the etch's one, but I can reinstall the latter, if needed. I suspect DDC is just screwed up in the r128 driver, so X can't get the informations about your monitor, and uses defaults that are wrong in your case :/ On etch X.Org was OK without touching anything... Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/482140 Apple-iMac-G3_lenny-Xorg_20081021.log.gz Description: lenny's Xorg.0.log for Apple iMac G3 pgpSMls3Mp7CC.pgp Description: PGP signature
Bug#388308: x11-common: No man page for /usr/bin/X
Hi Brice! On Thu, 14 Jun 2007 20:26:09 +0200, Brice Goglin wrote: For the record, upstream ships several manpages like this one in its xorg-docs repository. And we don't want to divert too much from their layout in our packaging. That's why manpages are in the xorg-docs package and will probably remain there. I don't think requiring ~5MB (i.e. the xorg-docs installed-size) for a single 18K manpage is fair. And FWIW xserver-xorg doesn't suggest xorg-docs or even mention it in the package description. Only the debian/changelog contains some informations about it, but they seem to be broken: = xorg (1:7.2-6) UNRELEASED; urgency=low [ Brice Goglin ] [...] * Move xorg-docs from xorg Depends to Recommends, closes: #427172. [...] -- Brice Goglin [EMAIL PROTECTED] Sat, 11 Aug 2007 19:06:20 +0200 [...] xorg (1:7.2-1) experimental; urgency=low [...] * Add xorg-docs to the xorg package dependencies. There's some very useful manpages in there, among other things. -- David Nusinow [EMAIL PROTECTED] Sun, 4 Mar 2007 15:38:57 -0500 = Thx, bye, Gismo / Luca pgp2fCGF6rXJH.pgp Description: PGP signature
Bug#502120: xserver-xorg: allows different /etc/X11/X symlinks as well as /usr/bin/X
Package: xserver-xorg Version: 1:7.3+18 Severity: wishlist User: [EMAIL PROTECTED] Usertags: package-installation Hi there! Please keep the Debian FSO Team [1] mailing list always Cc:ed. If you do so, no need to cc: me, I read the list. I discovered these issues because of the Xglamo KDrive server [2]. The problem is described also at [3]. Basically, AFAIK xinit/startx requires both /etc/X11/X and /usr/bin/X: let's see both in details, at least as I understood the situation. Since I'm not an X11 expert, feel free to point me at documentation I need to read :-) 1) /etc/X11/X If I understood correctly, this symlink points to the X11 server you want to use. Which means that if you install xserver-xfbdev and you want to use it with the xinit/startx infrastructure, you should change the /etc/X11/X symlink. ATM this symlink is created by xserver-xorg postinst (line 1816), but it points at /usr/bin/Xorg (shipped by xserver-xorg-core). However, if I switch the symlink to /usr/bin/Xglamo (xserver-xglamo [2]), everything works fine. I see only two possibilities to manage /etc/X11/X: either through alternatives (like /usr/bin/x-window-manager) or with a debconf question (like for the Display Managers). 2) /usr/bin/X This is a real executable shipped by xserver-xorg. I still need to understand why xinit/startx need both (/etc/X11/X and /usr/bin/X) and also why X.Org is divided into two (/usr/bin/X and /usr/bin/Xorg). FWIW, it seems that Xglamo works as expected with /usr/bin/X - Xglamo [4]. If /usr/bin/X from xserver-xorg is *required* by every X11 server compiled from the X.Org sources, then please don't depend on xserver-xorg. Otherwise, again, we need a way to manage /usr/bin/X (alternatives or debconf question). Thx, bye, Gismo / Luca Footnotes: [1] http://wiki.debian.org/Teams/DebianFSO [2] http://git.openmoko.org/?p=xglamo.git;a=summary [3] http://lists.linuxtogo.org/pipermail/smartphones-userland/2008-September/000207.html [4] I wanted to test xserver-xfbdev as well, but it's not available for armel -- Package-specific info: [removed since useless, available upon request] -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-14 GNU C Library: Shared libraries ii x11-xkb-utils 7.4+1X11 XKB utilities ii xkb-data1.3-2X Keyboard Extension (XKB) configu ii xserver-xorg-core 2:1.4.2-7Xorg X server - core server ii xserver-xorg-input-kbd 1:1.3.1-1X.Org X server -- keyboard input d ii xserver-xorg-input-mous 1:1.3.0-1X.Org X server -- mouse input driv ii xserver-xorg-video-fbde 1:0.4.0-1X.Org X server -- fbdev display dr ii xserver-xorg-video-inte 2:2.3.2-2+lenny4 X.Org X server -- Intel i8xx, i9xx ii xserver-xorg-video-vesa 1:2.0.0-1X.Org X server -- VESA display dri Versions of packages xserver-xorg recommends: ii libgl1-mesa-dri 7.0.3-6A free implementation of the OpenG ii udev 0.125-7/dev/ and hotplug management daemo xserver-xorg suggests no packages. -- debconf information: shared/fontpath/fontserver: xserver-xorg/multiple_possible_x-drivers: xserver-xorg/config/monitor/use_sync_ranges: true xserver-xorg/config/doublequote_in_string_error: xserver-xorg/config/monitor/screen-size: 17 inches (430 mm) xserver-xorg/config/device/default-identifier: xserver-xorg/autodetect_monitor: true shared/no_known_x-server: xserver-xorg/config/display/default_depth: 24 * xserver-xorg/config/display/modes: 1024x768, 800x600, 640x480 xserver-xorg/config/device/bus_id_error: xserver-xorg/config/monitor/vert-refresh: 43-60 * xserver-xorg/config/inputdevice/keyboard/options: * xserver-xorg/autodetect_keyboard: false xserver-xorg/config/device/use_fbdev: false * xserver-xorg/config/inputdevice/keyboard/variant: xserver-xorg/config/nonnumeric_string_error: * xserver-xorg/config/inputdevice/keyboard/layout: us xserver-xorg/config/inputdevice/mouse/emulate3buttons: true xserver-xorg/config/monitor/horiz-sync: 28-51 xserver-xorg/config/monitor/range_input_error: * xserver-xorg/config/inputdevice/keyboard/model: pc104 * xserver-xorg/config/device/driver: xserver-xorg/config/device/identifier: Generic Video Card xserver-xorg/config/monitor/selection-method: Advanced xserver-xorg/config/null_string_error: shared/multiple_possible_x-servers: xserver-xorg/config/device/bus_id: PCI:0:2:0 xserver-xorg/autodetect_video_card: true
Bug#502120: xserver-xorg: allows different /etc/X11/X symlinks as well as /usr/bin/X
Hi Julien! First of all, thank you for your fast and detailed reply. On Mon, 13 Oct 2008 20:45:26 +0200, Julien Cristau wrote: /usr/bin/X is a setuid wrapper, which does some basic permission checks and then exec()s /etc/X11/X. Am I correct if I say that this is not X.Org specific, i.e. the wrapper can be used with any X11 server? In that case, Xglamo would like to use the wrapper, too, which means that xserver-xorg should not depend on xserver-xorg-core. But this is another step forward :-) So /etc/X11/X should point to the actual X server you want to use when running /usr/bin/X. This is what I did in the (still unofficial) xserver-xglamo package [1]. However, I'd prefer a cleaner solution before Xglamo enters Debian [2]. There used to be some logic to change the /etc/X11/X symlink via debconf until about a year ago (it used to be needed when we had hardware specific X servers, which means before XFree86 4.0 iirc), so it might be possible to reintroduce that if you feel that Xglamo need it. I think that it could be helpful not only for Xglamo, but for the other KDrive servers as well (the first coming to my mind is xserver-xfbdev). Thx, bye, Gismo / Luca Footnotes: [1] http://git.debian.org/?p=pkg-fso/xglamo.git;a=commit;h=b6b0aead642942f5ef1b550a19cbfe2714c618fe [2] about which I still have to write a mail to the Debian X Strike Force pgpu7RdM3R5nS.pgp Description: PGP signature
Bug#500626: [Smartphones-userland] [pkg-fso-maint] Bug#500626: xserver-xglamo: fonts are very large in e.g. midori
clone 500626 -1 retitle -1 xserver-xglamo: crashes after xrandr command thanks Hi Timo! On Tue, 30 Sep 2008 12:21:41 +0200, Timo Juhani Lindfors wrote: I tried xrandr -o 0 xdpyinfo xrandr -o 3 xdpyinfo xrandr -o 3 xdpyinfo xrandr -s 3 xdpyinfo xrandr -s 2 xdpyinfo and then xglamo crashed. I can reproduce this crash every time (at least with version 1.3.0.0+git20080807-3), can you? No, are you sure the sequence above is correct? Anyway, I cloned the original bug, since we've two bugs (big fonts and crashes). Please check the new bug number before replying ;-) Also after crash the display is not in the normal 480x640 mode which is also a bug. I guess this is related to the crash above, thus I'd refrain to open another bug until the above one is fixed. Yes, xrandr --dpi 75 does not change it anymore to 75x75. I'm not really sure this is a bug, since I'm not at all a DPI expert. BTW, do all these bugs also happens with FSO (or any other Openmoko distribution) Xglamo? Thx, bye, Gismo / Luca pgpZzO1svulsg.pgp Description: PGP signature
Re: Bug#500626: [Smartphones-userland] [pkg-fso-maint] Bug#500626: xserver-xglamo: fonts are very large in e.g. midori
Hi Martin! Please don't reply to the bug itself nor to the smartphones-userland ML, this issue has nothing to do with Xglamo. Instead, reply to the XSF ML, I set accordingly M-F-T and R-T. On Thu, 02 Oct 2008 00:17:52 +0200, Julien Cristau wrote: On Thu, Oct 2, 2008 at 00:01:29 +0200, Luca Capello wrote: clone 500626 -1 retitle -1 xserver-xglamo: crashes after xrandr command thanks Can you take these bugs off the xorg package? They were filed against a nonexistent package, then reassigned to xorg, and I don't know what's the appropriate package here. Xglamo is the Openmoko kdrive server [1], maintained in Debian [2] by the Debian FSO Team [3] and distributed in the unofficial team repository [4]. Martin, please stop reassigning them and just leave them assigned to a nonexistent package as for the other packages maintained by the Debian FSO Team [5]. These packages are intended to be uploaded as soon as the libraries dependencies will be satisfied. That's why the Debian FSO team decided to use the Debian infrastructure (including the BTS). I'll reassigned them back to the xserver-xglamo package. Thx, bye, Gismo / Luca Footnotes: [1] http://git.openmoko.org/?p=xglamo.git;a=summary [2] http://git.debian.org/?p=pkg-fso/xglamo.git;a=summary [3] http://wiki.debian.org/Teams/DebianFSO [4] deb http://pkg-fso.alioth.debian.org/debian unstable main [5] http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED] pgpJpDi95Vu5O.pgp Description: PGP signature
Bug#500626: [Smartphones-userland] [pkg-fso-maint] Bug#500626: xserver-xglamo: fonts are very large in e.g. midori
Hi Michael! On Tue, 30 Sep 2008 07:54:07 +0200, Michael 'Mickey' Lauer wrote: Am Montag, den 29.09.2008, 23:57 +0200 schrieb Luca Capello: FSO X (Xglamo or Xfbdev) is started with the following settings,, specified in /etc/X11/Xserver:96: ARGS=$ARGS -dpi 285 -screen 480x640 [...] ;; This means that the value we obtain after the first xrandr command is correct. However, I don't understand why it specifies 285 DPI. Because that's the (one and only) correct value for the display on the Neo GTA01 and GTA02. Thank you for the information, I should have looked for it [1]. This means two things for Debian: 1) we must specify the DPI value even with xserver-xorg. However, since this is something specific to the Neo GTA01 and GTA02, I need to discover how to specify it *without* touching any configuration file provided by other packages (/etc/X11/xserver/ looks promising). 2) Debian Xglamo doesn't correctly manage the DPI value and thus the fonts (*this* is the bug) Thx, bye, Gismo / Luca Footnotes: [1] http://wiki.openmoko.org/wiki/TPO_TD028TTEC1 pgpgLAYEGosS1.pgp Description: PGP signature
Bug#458246: report xrdb: filename:, not stdin
tags 458246 + upstream tags 458246 + patch thanks Hello! On Sun, 30 Dec 2007 19:40:09 +0100, Brice Goglin wrote: [EMAIL PROTECTED] wrote: $ xrdb zz stdin:42:20: warning: missing terminating ' character I clearly gave it a filename, as the xrdb man page instructs, but instead it reports stdin. This causes _many hours_ of chasing down the source of errors when used in scripts! xrdb invokes cpp with your file as stdin. This first warning comes from cpp, that's why the warning talks about stdin, as opposed to other warnings that are issued by xrdb itself. As always, patches are welcome. Given how simple this program is, it would be a good programming exercise for anybody, even a newbie. Against the Debian package (which is upstream 1.0.4 and the same as the upstream git at [1]) and very similar to the WIN32 part: --8---cut here---start-8--- --- x11-xserver-utils-7.3+2/xrdb/xrdb.c.ORG 2006-07-11 04:54:07.0 +0200 +++ x11-xserver-utils-7.3+2/xrdb/xrdb.c 2008-01-06 20:14:06.0 +0100 @@ -1203,10 +1203,13 @@ #else if((cmd = (char *) malloc(strlen(cpp_program) + strlen(includes.val) + 1 + - strlen(defines.val) + 1)) == + strlen(defines.val) + 1 + + strlen(filename ? filename : ) + 1)) == NULL) fatal(%s: Out of memory\n, ProgramName); - sprintf(cmd, %s%s %s, cpp_program, includes.val, defines.val); + sprintf(cmd, %s%s %s %s, cpp_program, + includes.val, defines.val, + filename ? filename : ); if (!(input = popen(cmd, r))) fatal(%s: cannot run '%s'\n, ProgramName, cmd); free(cmd); --8---cut here---end---8--- This has been tested on my sid-amd64: = [EMAIL PROTECTED]:~/test/x11-xserver-utils-7.3+2/xrdb$ ./configure [...] [EMAIL PROTECTED]:~/test/x11-xserver-utils-7.3+2/xrdb$ make [...] [EMAIL PROTECTED]:~/test/x11-xserver-utils-7.3+2/xrdb$ make [empty, waiting for input as expected until CTRL-C] [EMAIL PROTECTED]:~/test/x11-xserver-utils-7.3+2/xrdb$ ./xrdb -merge ~/.Xresources /home/luca/.Xresources:16:13: warning: missing terminating ' character /home/luca/.Xresources:18:17: warning: missing terminating ' character /home/luca/.Xresources:20:18: warning: missing terminating ' character [EMAIL PROTECTED]:~/test/x11-xserver-utils-7.3+2/xrdb$ = Fixing this bug would mean closing bug #443537: since xrdb calls cpp, these warnings (not errors) will always be shown. Thx, bye, Gismo / Luca Footnotes: [1] http://gitweb.freedesktop.org/?p=xorg/app/xrdb.git;a=summary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447519: xterm: [UXTerm] doesn't support *XTerm class in ~/.Xresources
reassign 447519 x11-common retitle 447519 x11-common: [Xresources] doesn't support '*' as a 'common' wildcard found 447519 1:7.3+2 thanks Hi Thomas! Since the problem isn't in xterm, but in Xt resources, I reassigned the bug to x11-common (because it's the package that ships /etc/X11/Xresources). On Tue, 23 Oct 2007 22:15:38 +0200, Thomas Dickey wrote: On Tue, Oct 23, 2007 at 07:42:21PM +0200, Luca Capello wrote: Since resources specified as *XTerm are correctly read by xterm, I assumed that '*' is a wildcard, which stands for all, thus *XTerm means every class which ends in XTerm. Wildcards in Xt resources aren't supposed to do that (oddly enough). They replace whole leaf-names rather than parts of them. The resource syntax is documented in the X manpage (at the moment I'm on Solaris, and know the the Linux manpage is named different...). Here's the text, for reference: Thank you for the explanation and I agree that it's oddly enough that wildcards behave differently in Xt resources I usually do this a different way, setting $XAPPLRESDIR to my $HOME/app-defaults (and putting individual resource files there). Again, thank you for the hint, but I don't have a lot of Xt resources and I prefer to set them in one single file. I haven't closed this bug yet because I don't really know how to proceed: either we just close this bug as a not-a-bug or we leave this bug opened as a wishlist, tagging it upstream, too. In the latter case, since I think it's quite difficult that Xt resources will be changed to use 'common' wildcards, the bug is eligible for a wontfix tag, too. Thx, bye, Gismo / Luca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447519: xterm: [UXTerm] doesn't support *XTerm class in ~/.Xresources
Hi Thomas! On Tue, 23 Oct 2007 17:47:00 +0200, Thomas Dickey wrote: On Sun, Oct 21, 2007 at 11:40:11PM +0200, Luca Capello wrote: I'm not sure this is really a bug, but I cannot find anything in the documentation. In case it's there, can anyone point me at it, please? Basically, I'd like to define UXTerm resources in the *XTerm form (which is perfectly valid for xterm itself), in order to avoid resource duplications. As I wrote, it seems that xterm supports *XTerm, while uxterm no. The uxterm script sets the class to UXTerm so that there are no conflicts in resource intent/interpretation between the two uses. I'm aware of that and indeed this is a reason I started with I'm not sure this is really a bug. If the problem is not clear, here my second try: I usually quite exclusively uxterm and thus I could specify UXTerm resources as UXTerm. However, sometime I start an xterm and, obviously, I don't have my UXTerm settings. Since resources specified as *XTerm are correctly read by xterm, I assumed that '*' is a wildcard, which stands for all, thus *XTerm means every class which ends in XTerm. If the latter is right, this should be the case for UXTerm, too. Since it's not the case, this is a bug. However, if I'm wrong, I'll change the severity of this bug as 'wishlist' ;-) Thx, bye, Gismo / Luca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447519: xterm: [UXTerm] doesn't support *XTerm class in ~/.Xresources
Package: xterm Version: 229-1 Severity: normal Hello, I'm not sure this is really a bug, but I cannot find anything in the documentation. In case it's there, can anyone point me at it, please? Basically, I'd like to define UXTerm resources in the *XTerm form (which is perfectly valid for xterm itself), in order to avoid resource duplications. As I wrote, it seems that xterm supports *XTerm, while uxterm no. Thx, bye, Gismo / Luca -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.6.1-6GNU C Library: Shared libraries ii libfontconfig12.4.2-1.3 generic font configuration library ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libncurses5 5.6+20071013-1 Shared libraries for terminal hand ii libsm62:1.0.3-1+b1 X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxaw7 2:1.0.4-1 X11 Athena Widget library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxmu6 1:1.0.3-1 X11 miscellaneous utility library ii libxt61:1.0.5-3 X11 toolkit intrinsics library ii xbitmaps 1.0.1-2Base X bitmaps Versions of packages xterm recommends: pn xutilsnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433825: xserver-xorg-video-intel: Error in I830WaitLpRing(), timeout for 2 seconds
Hello, I'm sorry for the lag, I have quite forgot this bug because I disabled splashy to avoid the locks. On Sat, 21 Jul 2007 11:24:21 +0200, Brice Goglin wrote: forwarded 433825 https://bugs.freedesktop.org/show_bug.cgi?id=10833 After this mail, I'll add a note about the forward on that bug report. Seems to be related to the URL above. If you have any help to provide there, feel free to do so, nobody seem to be able to reproduce easily so far. For the last 5h I haven't had any lock/X-reload yet (with splashy enabled), so I think it's solved with one of the latest xserver-xorg-video-intel versions. Here the relevant reportbug informations, if neeeded: == Package: xserver-xorg-video-intel Version: 2:2.1.1-1 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-1-amd64 (SMP w/2 CPU cores) 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 xserver-xorg-video-intel depends on: ii libc6 2.6.1-1 GNU C Library: Shared libraries ii libdrm22.3.0-4 Userspace interface to kernel DRM ii xserver-xorg-core 2:1.3.0.0.dfsg-12 X.Org X server -- core server xserver-xorg-video-intel recommends no packages. -- no debconf information = Other informations available upor request. Thx, bye, Gismo / Luca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433825: xserver-xorg-video-intel: Error in I830WaitLpRing(), timeout for 2 seconds
Hello, On Thu, 19 Jul 2007 19:55:34 +0200, Luca Capello wrote: Strangely enough, the first time the error happened was during the creation of a 3.2G data DVD image creation by genisoimage. But then, the error occurred other times, independently of genisoimage. I'd say that the error happens during an heavy load on xterm, for example it happens during a dmesg invocation, also. I can confirm that the problem seems to be related to xterm, at least today it happened when moving down a large text file opened with less. The information in Xorg.0.log is similar to the one I provided in my first mail. A symptom which suggests me that it could be splashy related is the fact that when shutting down after the error occurred, only the splashy progress bar is shown and not the background image. Instead, I can see the normal console output. Thx, bye, Gismo / Luca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433825: xserver-xorg-video-intel: Error in I830WaitLpRing(), timeout for 2 seconds
Package: xserver-xorg-video-intel Version: 2:2.1.0-2 Severity: important Hello! Complete Xorg.0.log attached. Basically, either my X session gets kicked out (i.e., back to the Display Manager) or its freezes. The system is still alive, because SSH works and the hardware (wireless switch and undocking button) generates events in /var/log/syslog. Unfortunately, the keyboard doesn't respond anymore, neither to change to another console. This is the first time I see this error and I don't know who's fault, i.e. the Intel driver, splashy (which IIRC has some problems with GDM/KDM, but I use XDM) or StumpWM [1] (my window manager, but I don't think it's the problem here). Strangely enough, the first time the error happened was during the creation of a 3.2G data DVD image creation by genisoimage. But then, the error occurred other times, independently of genisoimage. I'd say that the error happens during an heavy load on xterm, for example it happens during a dmesg invocation, also. AFAIK this error has never been reported before in the BTS, if this was the case, please excuse me. Thx, bye, Gismo / Luca Footnotes: [1] http://packages.debian.org/unstable/devel/stumpwm -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2007-06-03 00:06 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1904384 2007-07-14 21:56 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 2647 2007-06-17 17:15 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # 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 xorg.conf manual page. # (Type man 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 Files EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us Option XkbVariantintl EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true Option EmulateWheel on Option EmulateWheelButton2 Option YAxisMapping 4 5 Option XAxisMapping 6 7 EndSection #Section InputDevice # Identifier Synaptics Touchpad # Driver synaptics # Option SendCoreEventstrue # Option Device/dev/psaux # Option Protocol auto-dev # Option HorizScrollDelta 0 #EndSection Section Device Identifier Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller Driver intel BusID PCI:0:2:0 # Option XAANoOffscreenPixmaps # Option NoDRI EndSection Section Monitor Identifier LCD+VGA Option DPMS HorizSync 28-50 VertRefresh 40-90 EndSection Section Screen Identifier Default Screen Device Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller Monitor LCD+VGA DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes
Bug#362246: fixed in xorg-server 1:1.0.2-5
reassign 362246 xserver-xorg-core 1:7.0.10 severity 362246 minor merge 362246 356883 close 356883 2:1.1.1-9 thanks Hello! On Mon, 27 Nov 2006 15:00:12 +0100, Luca Capello wrote: I'm cc:ing all the people intersted in this bug report (and the not-yet-merged #356883 [1]) just to be sure they're aware of the situation. Done again, sorry for the (undesired) noise. On Tue, 18 Apr 2006 11:17:43 +0200, Luca Capello wrote: This should be merged with #356883, but I'm not an expert of the merge command... Actually, not only the bug should be merged with #356883 [1], but it should be moved to xserver-xorg-core and marked as fixed since version 2:1.1.1-9, as per /usr/share/doc/xserver-xorg-core/changelog.Debian.gz: [...] I'm going to do this in one week from now if no one replies differently. Doing it with this mail: 1) I preferred to set the severity of this bug to minor (instead of the contrary, severity normal, for bug #356883) because the warning was really a less important one. 2) I used the deprecated 'close' command because I don't know how to properly use the pseudo-header after that the [EMAIL PROTECTED] commands have being processed. Thx, bye, Gismo / Luca pgpUKCTY3Wnam.pgp Description: PGP signature
Bug#362246: fixed in xorg-server 1:1.0.2-5
Hello! I'm cc:ing all the people intersted in this bug report (and the not-yet-merged #356883 [1]) just to be sure they're aware of the situation. On Tue, 18 Apr 2006 11:17:43 +0200, Luca Capello wrote: This should be merged with #356883, but I'm not an expert of the merge command... Actually, not only the bug should be merged with #356883 [1], but it should be moved to xserver-xorg-core and marked as fixed since version 2:1.1.1-9, as per /usr/share/doc/xserver-xorg-core/changelog.Debian.gz: = xorg-server (2:1.1.1-9) unstable; urgency=low [...] [ Eugene Konev ] [...] * Ship SecurityPolicy in xserver-xorg-core. -- David Nusinow [EMAIL PROTECTED] Thu, 28 Sep 2006 23:59:35 -0400 = I'm going to do this in one week from now if no one replies differently. Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356883 pgpP26KF1AAc9.pgp Description: PGP signature
Bug#389358: xkb-data: IBM ThinkPad geometry broken
Hello! On Mon, 25 Sep 2006 10:55:06 +0200, Wouter Cloetens wrote: Package: xkb-data Version: 0.8-13 [...] After an unstable update, I got an error dialogue box at Gnome startup regarding the keyboard. I think I was bitten by this bug. After a reboot, Emacs doesn't recognize anymore the Alt key as Meta. FWIW, the bug is present also in version 0.8-12exp4. The xmodmap output changes from (0.8-12): = xmodmap: up to 3 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lockCaps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1Alt_L (0x40), Alt_L (0x7d), Meta_L (0x9c) mod2Num_Lock (0x4d) mod3 mod4Super_L (0x7f), Hyper_L (0x80) mod5Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift (0x7c) = to (0.8-13): = xmodmap: up to 2 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lockCaps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1Alt_L (0x40), Alt_R (0x71) mod2Num_Lock (0x4d) mod3 mod4 mod5Scroll_Lock (0x4e) = Thx, bye, Gismo / Luca pgpDRBET3MB2Y.pgp Description: PGP signature
Re: glibc and UNACCEPTs
Hello! On Tue, 22 Aug 2006 20:51:56 +0200, David Nusinow wrote: On Tue, Aug 22, 2006 at 03:30:07PM -0400, Joey Hess wrote: Drew Parsons wrote: Unfortunately it's happened against, this time with the upload of xorg-server (xserver-xorg-core) 1:1.1.1-3, accidentally uploaded to unstable instead of experimental. An easy enough mistake, it's only one little field in a changelog file. '2:' is not any worse than '1:', so I don't see why this is any worse than any other bug that upload could have introduced. Upload again with a new epoch, problem solved. This is what I'd consider the appropriate fix. Just do another upload straight away and you don't even need to bother an ftpmaster. It's what I would have done if I'd been awake. Well, the problem is that with my daily `apt-get update apt-get upgrade` I got (again) the xserver-xorg from unstable, ending up with some X.Org packages from unstable and some from experimental, which AFAIK isn't a good thing :-( = [EMAIL PROTECTED]:~$ apt-cache policy xserver-xorg xserver-xorg: Installed: 1:7.0.23 Candidate: 1:7.0.23 Version table: *** 1:7.0.23 0 990 http://ftp.ch.debian.org unstable/main Packages 100 /var/lib/dpkg/status 1:7.0.22 0 500 http://ftp.ch.debian.org testing/main Packages [EMAIL PROTECTED]:~$ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.0.2-10 Candidate: 2:1.0.2-10 Version table: *** 2:1.0.2-10 0 990 http://ftp.ch.debian.org unstable/main Packages 100 /var/lib/dpkg/status 1:1.1.1-2 0 1 http://ftp.ch.debian.org experimental/main Packages 1:1.0.2-9 0 500 http://ftp.ch.debian.org testing/main Packages [EMAIL PROTECTED]:~$ apt-cache policy xserver-xorg-input-mouse xserver-xorg-input-mouse: Installed: 1:1.1.1-2 Candidate: 1:1.1.1-2 Version table: *** 1:1.1.1-2 0 1 http://ftp.ch.debian.org experimental/main Packages 100 /var/lib/dpkg/status 1:1.0.4-3 0 500 http://ftp.ch.debian.org testing/main Packages 990 http://ftp.ch.debian.org unstable/main Packages [EMAIL PROTECTED]:~$ apt-cache policy xserver-xorg-video-v4l xserver-xorg-video-v4l: Installed: 0.1.1-1 Candidate: 0.1.1-1 Version table: *** 0.1.1-1 0 1 http://ftp.ch.debian.org experimental/main Packages 100 /var/lib/dpkg/status 0.0.1.5-1 0 500 http://ftp.ch.debian.org testing/main Packages 990 http://ftp.ch.debian.org unstable/main Packages [EMAIL PROTECTED]:~$ = I don't think it's my fault (not having preserved xserver-xorg-core From an upgrade), but in case of just disregard this post. If it's not my fault, however, I think we need a new package in experimental... Thx, bye, Gismo / Luca pgp7KQmUnfVdm.pgp Description: PGP signature
Bug#376391: xdm: xdm manpage refers to non-existent section 'Typical Usage'
Package: xdm Version: 1:1.0.4-2 Severity: minor Tags: patch Hello, in section 'Session Program', 3rd paragraph, the xdm manpage states: At most installations, Xsession should look in $HOME for a file .xsession, which contains commands that each user would like to use as a ses‐ sion. Xsession should also implement a system default session if no user-specified session exists. See the section Typical Usage. However, the section 'Typical Usage' isn't present in the manpage. The attached patch removes the last sentence. Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xdm depends on: ii cpp 4:4.1.1-1The GNU C preprocessor (cpp) ii debconf [debconf-2.0] 1.5.2Debian configuration management sy ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libice6 1:1.0.0-3X11 Inter-Client Exchange library ii libpam0g0.79-3.1 Pluggable Authentication Modules l ii libselinux1 1.30-1 SELinux shared libraries ii libsm6 1:1.0.0-4X11 Session Management library ii libx11-62:1.0.0-6X11 client-side library ii libxau6 1:1.0.0-3X11 authorisation library ii libxaw7 1:1.0.1-5X11 Athena Widget library ii libxdmcp6 1:1.0.0-4X11 Display Manager Control Protoc ii libxext61:1.0.0-4X11 miscellaneous extension librar ii libxinerama11:1.0.1-4X11 Xinerama extension library ii libxmu6 1:1.0.1-3X11 miscellaneous utility library ii libxpm4 1:3.5.4.2-3 X11 pixmap library ii libxt6 1:1.0.0-5X11 toolkit intrinsics library ii x11-common 1:7.0.22 X Window System (X.Org) infrastruc ii xbase-clients 1:7.1.ds-1.1 miscellaneous X clients xdm recommends no packages. -- debconf information: * shared/default-x-display-manager: xdm xdm/stop_running_server_with_children: false xdm/daemon_name: /usr/bin/X11/xdm --- - 2006-07-02 18:55:46.99958 +0200 +++ /tmp/xdm1x.gz.10758 2006-07-02 18:55:46.0 +0200 @@ -1141,7 +1141,6 @@ which contains commands that each user would like to use as a session. \fIXsession\fP should also implement a system default session if no user-specified session exists. -See the section \fBTypical Usage\fP. .PP An argument may be passed to this program from the authentication widget using the `set-session-argument' action. This can be used to select pgpD0BxqRukPJ.pgp Description: PGP signature
Bug#362246: fixed in xorg-server 1:1.0.2-5
Hello! This should be merged with #356883, but I'm not an expert of the merge command... On Mon, 17 Apr 2006 18:32:29 +0200, David Nusinow wrote: xorg-server (1:1.0.2-5) unstable; urgency=low [...] * Add 12_security_policy_in_etc.diff from Eugene Konev. This will allow us to tell the server on configure to look in /etc/X11/xserver for the SecurityPolicy file. Thanks Joey Hess and Eugene. (closes: #362246) Just upgraded, still unsolved, now resulting in the following error: error opening security policy file /etc/X11/xserver/SecurityPolicy This because the SecurityPolicy file isn't installed on my machine: = [EMAIL PROTECTED]:~$ dpkg -s xserver-xorg | grep Version Version: 1:7.0.14 [EMAIL PROTECTED]:~$ dpkg -s xserver-xorg-core | grep Version Version: 1:1.0.2-5 [EMAIL PROTECTED]:~$ dlocate SecurityPolicy [EMAIL PROTECTED]:~$ apt-file search SecurityPolicy | grep etc xserver-common: etc/X11/xserver/SecurityPolicy = xserver-common is replaced by x11-common, which doesn't include the SecurityPolicy file. Thx, bye, Gismo / Luca pgpX5loTP66Fo.pgp Description: PGP signature
Bug#363041: xdm: ~/.xinitrc is not executed at login
Package: xdm Version: 1:1.0.1-6 Severity: normal Hello, as the title suggests, xdm ignores my ~/.xinitrc. Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xdm depends on: ii cpp 4:4.0.3-3 The GNU C preprocessor (cpp) ii debconf [debconf-2.0]1.4.72 Debian configuration management sy ii libc62.3.6-7 GNU C Library: Shared libraries ii libice6 1:1.0.0-2 X11 Inter-Client Exchange library ii libpam0g 0.79-3.1Pluggable Authentication Modules l ii libselinux1 1.30-1 SELinux shared libraries ii libsm6 1:1.0.0-3 X11 Session Management library ii libx11-6 2:1.0.0-6 X11 client-side library ii libxau6 1:1.0.0-2 X11 authorisation library ii libxaw7 1:1.0.1-4 X11 Athena Widget library ii libxdmcp61:1.0.0-3 X11 Display Manager Control Protoc ii libxext6 1:1.0.0-3 X11 miscellaneous extension librar ii libxinerama1 1:1.0.1-2 X11 Xinerama extension library ii libxmu6 1:1.0.1-2 X11 miscellaneous utility library ii libxpm4 1:3.5.4.2-2 X11 pixmap library ii libxt6 1:1.0.0-3 X11 toolkit intrinsics library ii x11-common 1:7.0.12X Window System (X.Org) infrastruc ii xbase-clients1:7.0.0-4 miscellaneous X clients xdm recommends no packages. -- debconf information: * shared/default-x-display-manager: xdm xdm/stop_running_server_with_children: false xdm/daemon_name: /usr/bin/X11/xdm pgpXdGFeedTAm.pgp Description: PGP signature
Bug#357736: /usr/X11R6/bin/startx: startx needs some way to delete stale $xserverauthfile files
Hello! On Sun, 19 Mar 2006 10:53:39 +0100, Nyk Tarr wrote: I noticed I had a $HOME littered with .serverauth. files, after a bit of prodding, I found that if startx is cut short by eg a shutdown, it doesn't get as far as deleting the $xserverauthfile file. This bug is still present in version 1:7.0.0-4. As a complete X11 profane, why don't create the serverauth files in /tmp, so they are deleted at reboot and a normal user doesn't need to take care of their deletion? Just my 0.02EUR... Thx, bye, Gismo / Luca pgp3KhVq9Rykm.pgp Description: PGP signature
Bug#362291: libxp6: still installs in /usr/X11R6/lib/ instead of /usr/lib/
Package: libxp6 Version: 6.9.0.dfsg.1-6 Severity: normal Hello, as the title suggests... Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libxp6 depends on: ii libc6 2.3.6-6GNU C Library: Shared libraries ii libx11-6 2:1.0.0-6 X11 client-side library ii libxext6 1:1.0.0-3 X11 miscellaneous extension librar libxp6 recommends no packages. -- debconf-show failed pgp9SBI6BwSwy.pgp Description: PGP signature
Bug#362294: xfonts-base-transcoded: still installs in /usr/X11R6/lib/X11/fonts/ instead of /usr/share/fonts/X11/
Package: xfonts-base-transcoded Version: 6.9.0.dfsg.1-6 Severity: normal Hello, of the various xfonts- packages installed on my Debian [1], this is the only one that still has a 6.9* version and thus installs into /usr/X11R6 instead of the new location. Are this fonts still present in the X.org modular version? Thx, bye, Gismo / Luca [1] xfonts-100dpi1.0.0-2 xfonts-100dpi-transcoded 1.0.0-2 xfonts-75dpi 1.0.0-2 xfonts-75dpi-transcoded 1.0.0-2 xfonts-base 1.0.0-3 xfonts-base-transcoded 6.9.0.dfsg.1-6 xfonts-encodings 1.0.0-2 xfonts-scalable 1.0.0-3 xfonts-utils 1.0.0-3 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xfonts-base-transcoded depends on: ii xutils1:7.0.0-3 X Window System utility programs xfonts-base-transcoded recommends no packages. -- debconf-show failed pgpaTipjtaUwa.pgp Description: PGP signature
Bug#354130: xbase-clients: (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap with xorg 7.0
Hello! On Thu, 16 Mar 2006 22:17:27 +0100, Denis Barbier wrote: The us_intl layout was not present in 0.6-2, it was replaced by layout us variant alt-intl In 0.8-1, a compatibility rule had been added, but you should really migrate to the settings above. Done, I didn't know that and I cannot find any reference about it in the Debian changelog. In the upstream one, it seems that the us_intl support was added on 2005-09-30, so before the Debian 0.6-2 release. Anyway, never mind, as I said I changed my settings as you suggested. Anyway there is another problem, files have been moved to /usr/share/X11/xkb and X server has not been updated yet, see /usr/share/doc/xkb-data/README.Debian. Indeed the solution proposed into the README.Debian solved my problem. Simple suggestion: isn't that better into NEWS.Debian? Thx, bye, Gismo / Luca pgpyLVsz3FqZJ.pgp Description: PGP signature
Bug#354130: xbase-clients: (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap with xorg 7.0
Hello! On Tue, 14 Mar 2006 22:10:27 +0100, Denis Barbier wrote: On Tue, Mar 14, 2006 at 02:40:22PM +0100, Luca Capello wrote: Well, it seems that the bug is still present in my Xorg.0.log (attached). My xorg.conf is attached as well. Which version of xkb-data is installed? For the record, until this morning: = [EMAIL PROTECTED]:~$ apt-cache policy xkb-data xkb-data: Installed: 0.6-2 Candidate: 0.6-2 Version table: 0.8-1 0 1 http://debian.fastweb.it experimental/main Packages *** 0.6-2 0 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ = Then I upgraded as every morning: = [EMAIL PROTECTED]:~$ apt-cache policy xkb-data xkb-data: Installed: 0.8-1 Candidate: 0.8-1 Version table: *** 0.8-1 0 1 http://debian.fastweb.it experimental/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ = But the problem is still present: = [EMAIL PROTECTED]:~$ ls -l /var/log/Xorg.0.log -rw-r--r-- 1 root root 23775 2006-03-15 11:32 /var/log/Xorg.0.log [EMAIL PROTECTED]:~$ grep XKB /var/log/Xorg.0.log (**) XKB: rules: xorg (**) XKB: model: thinkpad (**) XKB: layout: us_intl (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap [EMAIL PROTECTED]:~$ = Thx, bye, Gismo / Luca pgp6wjPSflL4o.pgp Description: PGP signature
Bug#354130: xbase-clients: (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap with xorg 7.0
Hello! On Sun, 26 Feb 2006 22:53:06 +0100, David Nusinow wrote: On Fri, Feb 24, 2006 at 09:41:11AM +0200, Daniel Stone wrote: On Thu, Feb 23, 2006 at 10:31:46PM -0500, David Nusinow wrote: On Thu, Feb 23, 2006 at 04:25:31PM +0100, Silvestre Zabala wrote: See subject. The fix was provided by ejka on #debian-x: mkdir /var/lib/xkb/ With /var/lib/xkb/ X starts correctly. Is this an xkb-data bug? I mean, we could supply this directory in the server or whatever, but I get the feeling that it should be in xkb-data. Denis? Whichever package provides xkbcomp. Ok, that'll work too. I'll add that to xbase-clients now. Well, it seems that the bug is still present in my Xorg.0.log (attached). My xorg.conf is attached as well. Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc6 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xbase-clients depends on: ii libc62.3.6-3 GNU C Library: Shared libraries an ii libdmx1 1:1.0.1-1 X11 Distributed Multihead extensio ii libfontconfig1 2.3.2-5 generic font configuration library ii libfreetype6 2.1.10-1.1 FreeType 2 font engine, shared lib ii libfs6 2:1.0.0-1 X11 Font Services library ii libgl1-mesa-glx [libgl1] 6.4.1-0.3 A free implementation of the OpenG ii libice6 1:1.0.0-1 X11 Inter-Client Exchange library ii libpng12-0 1.2.8rel-5 PNG library - runtime ii libsm6 1:1.0.0-2 X11 Session Management library ii libx11-6 2:1.0.0-3 X11 client-side library ii libxau6 1:1.0.0-1 X11 authorisation library ii libxaw7 1:1.0.1-2 X11 Athena Widget library ii libxcursor1 1.1.5.2-1 X cursor management library ii libxext6 1:1.0.0-2 X11 miscellaneous extension librar ii libxft2 2.1.8.2-3 FreeType-based font drawing librar ii libxi6 1:1.0.0-2 X11 Input extension library ii libxinerama1 1:1.0.1-1 X11 Xinerama extension library ii libxkbfile1 1:1.0.1-1 X11 keyboard file manipulation lib ii libxmu6 1:1.0.1-1 X11 miscellaneous utility library ii libxmuu1 1:1.0.1-1 X11 miscellaneous micro-utility li ii libxrandr2 2:1.1.0.2-2 X11 RandR extension library ii libxrender1 1:0.9.0.2-1 X Rendering Extension client libra ii libxss1 1:1.0.1-2 X11 Screen Saver extension library ii libxt6 1:1.0.0-2 X11 toolkit intrinsics library ii libxtrap61:1.0.0-1 X11 event trapping extension libra ii libxtst6 1:1.0.1-1 X11 Testing -- Resource extension ii libxv1 1:1.0.1-1 X11 Video extension library ii libxxf86dga1 2:1.0.0-1 X11 Direct Graphics Access extensi ii libxxf86misc11:1.0.0-2 X11 XFree86 miscellaneous extensio ii libxxf86vm1 1:1.0.0-2 X11 XFree86 video mode extension l ii x11-common 1:7.0.4 X Window System (X.Org) infrastruc ii zlib1g 1:1.2.3-11 compression library - runtime xbase-clients recommends no packages. -- no debconf information Xorg.0.log.gz Description: Xorg.0.log with the XKB keymap error xorg.conf.gz Description: xorg.conf pgpVaGFPdaBpz.pgp Description: PGP signature
Bug#356883: xserver-xorg-core: error opening security policy file /usr/lib/xserver/SecurityPolicy
Package: xserver-xorg-core Version: 1:1.0.1-2 Severity: minor Tags: experimental Hello, as the title suggest, every time I launch `startx` I have that output, which is normal, as there's no SecurityPolicy file on my box where X.org could find it: = gismo:/home/luca# updatedb gismo:/home/luca# locate SecurityPolicy /mnt/hurd/etc/X11/xserver/SecurityPolicy gismo:/home/luca# dlocate SecurityPolicy gismo:/home/luca# update-dlocatedb gismo:/home/luca# = Then I checked the xserver-xorg-core sources: = [EMAIL PROTECTED]:~/test$ apt-get source xserver-xorg-core [...] [EMAIL PROTECTED]:~/test$ find ./ -name SecurityPolicy ./xorg-server-1.0.1/Xext/SecurityPolicy [EMAIL PROTECTED]:~/test$ grep -r SecurityPolicy xorg-server-1.0.1/ [simplified version] xorg-server-1.0.1/Xext/Makefile.in: xorg-server-1.0.1/Xext/security.c: xorg-server-1.0.1/Xext/SecurityPolicy: xorg-server-1.0.1/Xext/Makefile.am: xorg-server-1.0.1/ChangeLog: [EMAIL PROTECTED]:~/test$ = So, it seems that the dpkg-buildpackage doesn't install the SecurityPolicy file. I should admit that I don't know anything about this file, so maybe it's normal it's not installed. Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc6 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-core depends on: ii libc62.3.6-3 GNU C Library: Shared libraries an ii libfontenc1 1:1.0.1-1 X11 font encoding library ii libgcc1 1:4.0.3-1 GCC support library ii libxau6 1:1.0.0-1 X11 authorisation library ii libxdmcp61:1.0.0-1 X11 Display Manager Control Protoc ii libxfont11:1.0.0-2 X11 font rasterisation library ii x11-common 1:7.0.4 X Window System (X.Org) infrastruc ii xserver-xorg-input-kbd [xser 1:1.0.1.3-1 X.Org X server -- keyboard input d ii xserver-xorg-input-mouse [xs 1:1.0.3.1-1 X.Org X server -- mouse input driv ii xserver-xorg-video-ati [xser 1:6.5.7.3-2 X.Org X server -- ATI display driv ii xserver-xorg-video-fbdev [xs 1:0.1.0.5-1 X.Org X server -- fbdev display dr ii xserver-xorg-video-vesa [xse 1:1.0.1.3-1 X.Org X server -- VESA display dri ii xserver-xorg-video-vga [xser 1:4.0.0.5-1 X.Org X server -- VGA display driv ii zlib1g 1:1.2.3-11 compression library - runtime Versions of packages xserver-xorg-core recommends: pn xkeyboard-config none (no description available) -- no debconf information pgpeb580yAmeV.pgp Description: PGP signature
Re: Fixed in upload of xorg 1:7.0.3 to experimental
Hello! On Sun, 12 Mar 2006 01:17:10 +0100, David Nusinow wrote: tag 356039 + fixed-in-experimental [...] xorg (1:7.0.3) experimental; urgency=low . * Include rgb.txt from rgb 1.0.0 upstream release. Also provide symlink to /usr/share/X11 so that the server knows where to look. Thanks Lukasz Panowski. (closes: #356039) I upgraded 5m ago to the latest 1:7.0.3, but the bug is still present, due to the symlink /usr/share/X11/rgb (without the .txt extension). In fact, the following solves the problem: $ mv /usr/share/X11/rgb /usr/share/X11/rgb.txt BTW, to be sure it's not a problem of my xorg.conf, I commented out the RgbPath in it. Thx, bye, Gismo / Luca pgpvZnortSs7y.pgp Description: PGP signature
Bug#356539: xbase-clients: same manpages refer to incorrect location (.so man1x/manpage.1x)
Package: xbase-clients Version: 1:1.0.1-2 Severity: minor Tags: experimental Hello, executing mandb gives errors about some manpages in xbase-clients: = gismo:/home/luca# mandb [...] Updating index cache for path `/usr/share/man/man1'. Wait...mandb: can't open /usr/share/man/man1x/bitmap.1x: No such file or directory mandb: warning: /usr/share/man/man1/atobm.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/bitmap.1x: No such file or directory mandb: warning: /usr/share/man/man1/bmtoa.1x.gz: bad symlink or ROFF `.so' request [...] mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapin.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapout.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapproto.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapreset.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapstats.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapchar.1x.gz: bad symlink or ROFF `.so' request [...] 0 old database entries were purged. gismo:/home/luca# = All the errors are similar to the following: = gismo:/home/luca# zcat /usr/share/man/man1/atobm.1x.gz .so man1x/bitmap.1x gismo:/home/luca# = Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc5 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xbase-clients depends on: ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libdmx1 1:1.0.1-1 X11 Distributed Multihead extensio ii libfontconfig12.3.2-5generic font configuration library ii libfreetype6 2.1.10-1.1 FreeType 2 font engine, shared lib ii libfs62:1.0.0-1 X11 Font Services library ii libgl1-mesa-glx [libgl1] 6.4.1-0.3 A free implementation of the OpenG ii libice6 1:1.0.0-1 X11 Inter-Client Exchange library ii libpng12-01.2.8rel-5 PNG library - runtime ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libx11-6 2:1.0.0-1 X11 client-side library ii libxau6 1:1.0.0-1 X11 authorisation library ii libxaw7 6.9.0.dfsg.1-4 X Athena widget set library ii libxcursor1 1.1.5.2-1 X cursor management library ii libxext6 1:1.0.0-2 X11 miscellaneous extension librar ii libxft2 2.1.8.2-3 FreeType-based font drawing librar ii libxi61:1.0.0-2 X11 Input extension library ii libxinerama1 6.9.0.dfsg.1-4 X Window System multi-head display ii libxkbfile1 6.9.0.dfsg.1-4 X Keyboard Extension file parsing ii libxmu6 6.9.0.dfsg.1-4 X Window System miscellaneous util ii libxmuu1 6.9.0.dfsg.1-4 lightweight X Window System miscel ii libxrandr26.9.0.dfsg.1-4 X Window System Resize, Rotate and ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii libxss1 1:1.0.1-2 X11 Screen Saver extension library ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii libxtrap6 1:1.0.0-1 X11 event trapping extension libra ii libxtst6 1:1.0.1-1 X11 Testing -- Resource extension ii libxv11:1.0.1-1 X11 Video extension library ii libxxf86dga1 2:1.0.0-1 X11 Direct Graphics Access extensi ii libxxf86misc1 1:1.0.0-2 X11 XFree86 miscellaneous extensio ii libxxf86vm1 1:1.0.0-2 X11 XFree86 video mode extension l ii x11-common1:7.0.3X Window System (X.Org) infrastruc ii zlib1g1:1.2.3-11 compression library - runtime xbase-clients recommends no packages. -- no debconf information pgpatw2jVHV9M.pgp Description: PGP signature
Bug#356545: libxau-dev: manpages refer to incorrect location (.so man3x/Xau.3x)
Package: libxau-dev Version: 1:1.0.0-1 Severity: minor Tags: experimental Hello, this is similar to bug #356539 [1], for all the libxau-dev manpages but Xau.3x. = gismo:/home/luca# zcat /usr/share/man/man3/XauGetAuthByAddr.3x.gz .so man3x/Xau.3x gismo:/home/luca# = Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc5 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libxau-dev depends on: ii libxau6 1:1.0.0-1 X11 authorisation library ii x11-common1:7.0.3X Window System (X.Org) infrastruc ii x11proto-core-dev 7.0.4-1X11 core wire protocol and auxilia libxau-dev recommends no packages. -- no debconf information pgprgr85va4ys.pgp Description: PGP signature
Bug#345640: xserver-xorg: New Xorg crashes with kernel 2.6.14, but not with 2.6.12
Hello Michel! On Fri, 06 Jan 2006 14:41:06 +0100, Michel Dänzer wrote: On Fri, 2006-01-06 at 13:41 +0100, Luca Capello wrote: [...] what should I do for the DRI bug? There is no bug, this is the reason why Option AGPFastWrite defaults to off. Sorry, probably I missunderstood what r300 supports and what it doesn't. On XP I installed the Omega drivers and at [1] it seems that AGPFastWrite is available only for 9600 and Athlon 64 systems (which I don't have, it's a Intel Pentium M 1.8GHz). Infact, using the Omega setting tool, I cannot switch the AGPFastWrite option on. So I suppose it's _must_ be off (but I don't know at all about graphic cards). From the r300 [2] and the DRI [3] websites, my FireGL T2 / M10 has the rv350 chipset, which should be *experimentally* supported by the r300 DRI driver. Am I correct? Or am I missing something? The problem is that X.Org 6.9.0 with Benjamin's patch still freezes after a while even with AGPFastWrite off (when I start quake3, but not when I start glxgears). I'd like to debug the problem, as this is the only way I can help supporting my M10 by the DRI framework (sorry, I'm not a programmer). Thx, bye, Gismo / Luca [1] http://www.omegadrivers.net/mb_bios.php [2] http://r300.sourceforge.net/R300.php [3] http://dri.freedesktop.org/wiki/ATIRadeon pgpzpX4obBayW.pgp Description: PGP signature
Bug#345640: xserver-xorg: New Xorg crashes with kernel 2.6.14, but not with 2.6.12
Hello Michel! On Thu, 05 Jan 2006 16:50:49 +0100, Michel Dänzer wrote: On Thu, 2006-01-05 at 15:58 +0100, Luca Capello wrote: So, I'd say that I'm experiencing two bugs: the first is a general X.Org freezing (withouth DRI enabled or with DRI enabled and no radeon kernel module), Benjamin Herrenschmidt's patch attached to https://bugs.freedesktop.org/show_bug.cgi?id=3911 (note that he only posted later, improved versions to the xorg mailing list) seems to help with some such problems. I hope you're referring to [1], because I'm going to applying it and locally compiling a custom Debian xserver-xorg-6.9 to test what happens ;-) I'll report my tests ASAP. the second is a specific problem with the DRI r300 driver (this should be bug #345929 [2]). Indeed, but this one as well, according to the submitter. I think you are referring to the submitter of bug #345929. I mean, I'm sure I'm hitting both bugs :-( [1] I tried with xlibmesa-dri and libgl1-mesa-dri, but no differences. These only come into play when running an OpenGL application. Ok, I know nothing at all about DRI/OpenGL. Moreover, I don't know why r300_dri.so is not present in xlibmesa-dri, since X.Org 6.9 ships it: http://wiki.x.org/wiki/ChangesSince68 The X tree doesn't build the r300 driver by default. My fault, I thought that the entry Experimental DRI support for Radeon 9500 and above implied the compilation by default. Thx, bye, Gismo / Luca pgpNyef5B5a9y.pgp Description: PGP signature
Bug#345640: xserver-xorg: New Xorg crashes with kernel 2.6.14, but not with 2.6.12
Hello! On Thu, 05 Jan 2006 17:39:29 +0100, Luca Capello wrote: On Thu, 05 Jan 2006 16:50:49 +0100, Michel Dänzer wrote: On Thu, 2006-01-05 at 15:58 +0100, Luca Capello wrote: So, I'd say that I'm experiencing two bugs: the first is a general X.Org freezing (withouth DRI enabled or with DRI enabled and no radeon kernel module), Benjamin Herrenschmidt's patch attached to https://bugs.freedesktop.org/show_bug.cgi?id=3911 (note that he only posted later, improved versions to the xorg mailing list) seems to help with some such problems. I hope you're referring to [1], because I'm going to applying it and locally compiling a custom Debian xserver-xorg-6.9 to test what happens ;-) I'll report my tests ASAP. Sorry, missing [1]: http://lists.freedesktop.org/archives/xorg/2005-December/011679.html Thx, bye, Gismo / Luca pgpnl2iB0Gqz4.pgp Description: PGP signature
Bug#345640: xserver-xorg: New Xorg crashes with kernel 2.6.14, but not with 2.6.12
Hello! First of all, my machine: - IBM ThinkPad T42p - PCI:*(1:0:0) ATI Technologies Inc M10 NT [FireGL Mobility T2] rev 128, Mem @ 0xe000/27, 0xc010/16, I/O @ 0x3000/8 - 2.6.15-rc7 manually compiled with make-kpkg (but the same results with a Debian official 2.6.14-2-686) - unstable daily upgraded - Eclipse [1] as Windows Mangaer On Tue, 03 Jan 2006 06:44:45 +0100, Patricio Rojo wrote: I think I run into this same problem... I upgraded the kernel from 2.6.12 to 2.6.14 maybe one hour after upgrading the xserver, so I was able to have a working xserver for a little bit In my case, X.org freezes after about 10min and I cannot resolve it but an hard shutdown (pressing the power button 4s). And I have no errors in the logs :-( The problem can be solved by either booting with kernel 2.6.12 or by downgrading the package xserver-xorg to 6.8.2.dfsg.1-11 (and only that package, without any of the other accompanying libs) I downgraded xserver-xorg only to experimental (6.8.99.903.dfsg.1-1) and the X server seems to nicely work since about 1h. So the problem could be in the transition rc3-final. Hope this helps!, Thanks... Sure, at least to have a working X11 in the while :-) BTW, I should say that the same happens if I try 2.6.14-2-686 o 2.6.15-rc7 with the radeon DRM module compiled in: the screen goes black when xdm starts and the system is completely freezed. Thx, bye, Gismo / Luca PS, I didn't provided the whole bunch of reportbug informations, but I can do if necessary. [1] http://common-lisp.net/project/eclipse pgpDheIOEFoQY.pgp Description: PGP signature
