Package: xserver-xorg-core
Version: 2:1.9.5-1
Severity: important
Tags: d-i
Hi,
After discuting and disculping the nouveau driver from the last update, it
seems that the designated culprit for the bad Xorg initialization with the last
update may be xserver-xorg-core, even thought it didn't appear
pport against xserver-xorg-core as recommended.
Stephane
--
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/banlktinhdw1lksboffjgofr+crg9gxo...@mail.gmail.com
Mac). The
kernel fails to even initialize it.
I will check by forcing the nouveau driver in the xorg.conf, though. back soon.
Thanks for the tips.
Stephane
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
[35.952] (--) Mitsumi Electric Apple Extended USB Keyboard: Found keys
[ 35.952] (II) Mitsumi Electric Apple Extended USB Keyboard:
Configuring as keyboard
[35.952] (II) XINPUT: Adding extended input device "Mitsumi
Electric Apple Extended USB Keyboard" (type: KEYBOARD)
[
Stephane Glondu a écrit :
> I've been experiencing similar problems since a recent upgrade of
> xkb-data to 1.6-1:
> [...]
> - they work if I leave the option level3(lwin_switch) set, but
>downgrade xkb-data to 1.5-2
Bisecting identifies the first bad commit as:
http://g
as would get rid of the problem after disabling
rwin_switch.
HTH,
--
Stephane
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2
On Sun, Mar 16, 2008 at 04:21:50PM +0100, Brice Goglin wrote:
[...]
> > If, from xorg, I switch to another VT while pressing a key, the
> > original X server keeps sending keypress events to the
> > previously focused client (and keyrelease events to some other
> > client which I've not determined)
Package: xserver-xorg-input-kbd
Version: 1:1.2.2-3
Severity: normal
Hiya,
this has been buggering me for a long time, only now I've put a
little investigation in it.
If, from xorg, I switch to another VT while pressing a key, the
original X server keeps sending keypress events to the
previously
Package: xorg-docs
Severity: normal
Hi,
This package conflicts with xprt-xprintorg
The problem comes from file /usr/share/man/man7/Xprint.7.gz
See below
Regards
Stephane
Atteint ftp://ftp2.fr.debian.org unstable Release.gpg
Atteint ftp://ftp2.fr.debian.org unstable Release
Atteint ftp://ftp2
OK, xorg-core propagated to testing/Etch. Package updated yesterday and
the bug no longer appears on my Mac-mini. It can be closed AFAIKS.
Thank you for all.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Paul Collins a écrit :
This sounds like bug #392453. With the updated packages installed,
compiz now displays correctly on my PowerBook.
Indeed, it seems I wrote a bug report the same day the package was
updated to unstable. My bad.
Hence, I'll wait for the new xorg-core 1.1.1-11 to propaga
Package: compiz-core
Version: 0.2.2-1
I tried compiz on my PPC mac-mini, but colours are wrongs. Compiz itself
seems to have a little warning when it is starts:
~$ compiz --replace &
[1] 6396
~$ libGL warning: 3D driver claims to not support visual 0x4b
libGL warning: 3D driver claims to not
And here is the init script I run to configure the keys#
# (1) If pressing a key produces the following in the console & syslog
#
# Use 'setkeycodes e012 ' to make it known.
#
# (2) in the linux sources look for the following table in
# the file drivers/char/keyboard.c
#
# static
One more detail.
My keyboard a different model (Logitech Deluxe Access) so you might want
to use different keycodes.
ode/9028#comment-932
I hope that helps.
Stephane.
Hello,
In each directory /etc/rcN.d/ with N a runlevel (2,3,4 or 5) there
must be a symbolic link S99gdm or S99xdm. Remove it and reboot.
See also the runlevel information in the debian reference manual.
http://qref.sourceforge.net/quick/reference.en.html
S.
--
Stephane Chauveau
Leenderweg
Hello,
I'm afraid this bug doesn't come from Xfree only, but
rather from xfree and kde. I've tried to launch
xscreensaver from twm with the command "xscreensaver &
xscreensaver-demo" and the opengl screensavers are..
ok !
Strange... I've upgraded to x-windows-system-core
3.1.0-5, and with Kde 3.1.
It's my first bug report, sorry for my lack of
précision, I'll try to correct this...
1) I'm using a SID with kde 3.1.5. I've the package
kscreensaver (4:3.1.5-2), xscreensaver (4.14-2) and
xscreensaver-gl (4.14-2) installed. When I'm using
xfree 4.2.1, all the screensavers work fine (opengl
and n
Package: xserver-xfree86
Version: 4.3.0-3
Severity: important
Tags: sid
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.22-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
Versions of pa
LD_PRELOAD to load the lib:
# export LD_PRELOAD=/home/chauveau/libfoo.so
# glxinfo
I dont know what sse_test_dummy is supposed to do but I was able to run
all my GL apps without any problems (including RTCW and ET).
--
Stephane Chauveau
Leenderweg 112
CG Valkenswaard
The Netherlands
Tel
20 matches
Mail list logo
