On Thu, May 18, 2006 at 04:16:01AM +0200, Josselin Mouette wrote:
> Le mercredi 17 mai 2006 à 12:26 -0500, Donald King a écrit :
> > Ever since a GNOME upgrade around late April, I haven't been able to use
> > GNOME at all. By downgrading to Sarge versions of the kernel, X, and
> > GNOME, I narrow
pulchritudinous Teenie
in harrdcore acttion!
http://fatgirlssite.info/igass.htm?gfibjW-M.YbRQR,gfibjW,VSd
U_N_S_U_BB_$_C_R_I_B_E
http://fatgirlssite.info
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi!
I did some more testing...
- Sid/ppc -> Sid/ppc : works
- Sid/ppc -> Sarge/i386 : doesn't work (same error)
- Sid/ppc -> Sarge/m68k : doesn't work (same error)
Whereas "Sid/ppc ->" means that I'm connecting from my desktop via ssh -X to
the remote box.
- Sid/ppc -> Sarge/i386 starting "wo
* Michel Dänzer
> Both of you, please also make sure (e.g. using xlsclients) that there
> are no 'hidden' clients that could interfere, and that killing the
> clients actually causes them to close their X display connection (and
> possibly open a new one).
I checked this, there is no client lef
Author: bubulle
Date: 2006-05-18 09:20:55 -0400 (Thu, 18 May 2006)
New Revision: 2169
Modified:
trunk/debian/xorg/debian/changelog
trunk/debian/xorg/debian/po/hu.po
Log:
Hungarian translation update
Modified: trunk/debian/xorg/debian/changelog
==
Title: 50 cdr 80 verbatim pour 7.90 Euros
Si cette page ne s'affiche pas correctement dans votre messagerie, cliquez ici Ce message vous a été envoyé pou
I just ran into this problem as well, and was about to report the same
workaround (changing /usr/bin/X11/xdm to /usr/bin/xdm in /etc/init.d/xdm
and /etc/X11/default-display-manager). But I'm still not sure which X
server to use in /etc/X11/xdm/Xservers. There's
-rwxr-xr-x 1 root root 1878204 200
I got this working by changing:
in /etc/init.d/xdm: /usr/bin/X11/xdm to /usr/bin/xdm
in /etc/X11/default-display-manager: /usr/bin/X11/xdm to /usr/bin/xdm
in /etc/X11/xdm/Xservers: /usr/bin/X to /usr/X11R6/bin/Xorg
I am hoping that there will soon be an upgrade that will set the config files
to
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-14sarge1
I recently did an apt-get update ; apt-get dist-upgrade, and when all
was said and done, X no longer worked. I still get the speckled screen
and the X pointer for just a second, and then it quits with a signal 11.
The startx output, config
Package: x-window-system-core
Version: 6.9.0.dfsg.1-6
Description: x-window-system-core is broken/missing fonts.alias file?
Debian / testing
Hi,
Installed kdebase and x-window-system-core packages. However, "startx" results
in the "could not open default font 'fixed';" error. According to the
ht
Author: dnusinow
Date: 2006-05-18 21:43:59 -0400 (Thu, 18 May 2006)
New Revision: 2170
Modified:
trunk/debian/xorg/debian/x11-common.config.in
trunk/debian/xorg/debian/x11-common.preinst.in
Log:
Fix several bugs in the new debconfage
Modified: trunk/debian/xorg/debian/x11-common.config.in
=
Author: dnusinow
Date: 2006-05-18 22:36:20 -0400 (Thu, 18 May 2006)
New Revision: 2171
Modified:
trunk/debian/xorg/debian/changelog
trunk/debian/xorg/debian/control
Log:
* Increment version with xdm conflict to the current version in testing and
unstable. (closes: #363462)
Modified: trunk
Author: dnusinow
Date: 2006-05-18 22:44:53 -0400 (Thu, 18 May 2006)
New Revision: 2172
Modified:
trunk/debian/xorg/debian/control
Log:
Fix formatting gaff
Modified: trunk/debian/xorg/debian/control
===
--- trunk/debian/xorg/debian
X Strike Force SVN Repository Admin <[EMAIL PROTECTED]> writes:
> Author: dnusinow
> Date: 2006-05-18 22:44:53 -0400 (Thu, 18 May 2006)
> New Revision: 2172
> Modified:
>trunk/debian/xorg/debian/control
> Log:
> Fix formatting gaff
Incidentally, per the latest Debian Policy, it's now legal t
Author: dnusinow
Date: 2006-05-18 23:44:06 -0400 (Thu, 18 May 2006)
New Revision: 2173
Modified:
trunk/debian/xorg/debian/changelog
Log:
Prepare changelog for release
Modified: trunk/debian/xorg/debian/changelog
===
--- trunk/debi
Author: dnusinow
Date: 2006-05-18 23:45:13 -0400 (Thu, 18 May 2006)
New Revision: 2174
Added:
tags/debian/xorg/xorg-1:7.0.19/
Log:
Tag upload of xorg-1:7.0.19 to unstable
Copied: tags/debian/xorg/xorg-1:7.0.19 (from rev 2173, trunk/debian/xorg)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Author: dnusinow
Date: 2006-05-18 23:45:34 -0400 (Thu, 18 May 2006)
New Revision: 2175
Modified:
trunk/app/xdm/debian/changelog
Log:
Prepare changelog for release
Modified: trunk/app/xdm/debian/changelog
===
--- trunk/app/xdm/debi
Author: dnusinow
Date: 2006-05-18 23:47:17 -0400 (Thu, 18 May 2006)
New Revision: 2176
Added:
tags/app/xdm/xdm-1:1.0.4-1/
Log:
Tag upload of xdm-1:1.0.4-1 to unstable
Copied: tags/app/xdm/xdm-1:1.0.4-1 (from rev 2175, trunk/app/xdm)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363427: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331553: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363699: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362885: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347481: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#335348: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363169: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364087: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363462: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367556: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365134: fixed in xdm 1:1.0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 21:02:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#366378: fixed in xorg 1:7.0.19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
44 matches
Mail list logo
