Hi everyone ! Considering the potentially very wide scope of a bug that
would freeze the X server, could you guys & gals give more details ?
- OS / ARCH
- GPU
- Proprietary or open source driver ?
- X or Wayland ?
- Any PPA ?
- How often the bug occurs ? Is it completely random ?
- Does it occur
Hi ! I encounter this issue too (complete X freeze sometimes when seeking too
much in videos in VLC).
I thought that was related to using Nvidia VDPAU. I saw this behaviour on 2
very different machines.
Using KDE Neon based on Ubuntu 16.04. Tried latest NVIDIA drivers & VLC
PPA. This PPA is
I'm pleased to announce this issue is *fixed* for me in Ubuntu Natty !
(xserver-xorg-input-joystick must NOT be installed, otherwise the
joystick will control the mouse)
I have some issues with inverted axis though, but it's a distinct issue
!
--
You received this bug notification because you
Well, it's not needed anymore (it was in former Ubuntu releases),
apparently, it must be using the xserver-xorg-input-evdev driver...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
Indeed, it's happened for several Ubuntu releases already : only when
Compiz is enabled (and thus, Unity as well as it's a Compiz plugin), and
apparently only with Nvidia cards (proprietary driver).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Same as mmiicc here (amd64). By the way, I have the same issue with the
alsa backports, which is why I still use an older kernel (2.6.35-22).
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a member of Ubuntu-X,
As of Maverick : no need to install a custom fdi anymore to get the
gamepad recognized : I only needed to install xserver-xorg-input-
joystick.
However, the digital stick still controls the mouse cursor.
--
USB Gamepad detected as mouse (Speedlink 360 style)
I'm not sure my comment will be relevant, but I've just noticed some
tearing *at the top of the screen only* (that's barely noticeable -- in
openGL 2D games like SMC for instance), when using nvidia proprietary
drivers + compiz.
Please note I'm doing the following which usually gives a flawless
Out of curiosity, I tried the updated modules ; it still works properly
(stylus) with my CTH-661 (model ID is 00d3 as well).
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a member of Ubuntu-X,
which is a direct
Stefan : BTW, I don't know what changed meanwhile, but I don't have to
manually insert the updated module anymore : the tablet (stylus only, no
gesture / touch but that's good anyway) works automagically at boot time
:)
Thanks again, Stefan !
--
Wacom Bamboo CTH-661 not recognized
Oh ! Yes it DOES work ; I had to manually sudo insmod
/lib/modules/2.6.35-22-generic/updates/input/wacom.ko !
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a member of Ubuntu-X,
which is a direct subscriber.
Stefan : maybe I missed sth, but I just installed those input backports
modules rebooted ; my Wacom PT (CTH-661) doesn't seem to work. I also
have the package xserver-xorg-input-wacom installed. Are there any other
steps to perform ?
Thanks !
--
Wacom Bamboo CTH-661 not recognized
Well, modinfo wacom gives :
filename:
/lib/modules/2.6.35-22-generic/kernel/drivers/input/tablet/wacom.ko
and uname -r :
2.6.35-22-generic
Thank you !
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a
Well, as of today, Maverick RC, the Wacom PT (CTH-661) is still not
recognized.
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a member of Ubuntu-X,
which is a direct subscriber.
Public bug reported:
Hi !
Ubuntu automatically generates an xorg.conf file when installing the
proprietary Nvidia drivers. It works very well overall, however, one
cannot get a smooth Compiz experience without addiing two options in
xorg.conf.
* Option TripleBuffer True : without this option,
** Attachment added: .proc.driver.nvidia.cards.0.txt
https://bugs.launchpad.net/bugs/635724/+attachment/1570554/+files/.proc.driver.nvidia.cards.0.txt
** Attachment added: .proc.driver.nvidia.registry.txt
I encounter this issue as well (nvidia 256.53, Meerkat beta). BTW, the
IgnoreABI option doesn't seem to be required anymore as of today.
(i.e. : playing HD videos or OpenGL apps are smooth -- scrolling text or
moving a window about a window that is full of text is *extremely* slow,
while it's
Well, your gamepad may not be useless in all cases (for instance, for
fullscreen games that capture the mouse pointer and do not react to
double-clicks).
Here happens with my both controllers : Speedlink 360 style and
Thrustmaster Firestorm Dual Analog.
Anyway, the problem seems to be that X is
Under Ubuntu Lucid RC :
there's definitely progress. A custom .fdi file is not necessary anymore
!
One just has to install the joystick input driver and it works, but
still controls the mouse pointer as well. (plus some invered axis on the
2nd stick + the need to unplug/replug the first time)
Thank you Bryce.
I haven't tried in Lucid yet, but it turns out the issue is upstream
anyway (I just tried and got the very same results in an up to date
ArchLinux distro : works but fdi required, unplug/replug required,
inverted axis, both mouse stick... Worked with evdev instead of
joystick
FYI, there are 2 entries in lshal :
udi = '/org/freedesktop/Hal/devices/usb_device_1a34_802_noserial'
info.linux.driver = 'usb' (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_1d6b_1__00_1a_0'
(string)
info.product = 'USB GAMEPAD 8116' (string)
info.subsystem =
Hi,
well, sorry for the lack of input !
Actually, if I don't install xserver-xorg-input-joystick, it seems I
cannot get the device detected. Which is probably due to the fact that
the .fdi file I *have to* install specifies :
match key=input.product string=ACRUX USB GAMEPAD 8116
remove
Well, I'm a bit lost...
I only manage to get it recognized when using the entry
merge key=input.x11_driver type=stringjoystick/merge
in the relevant .fdi file.
(one OK but not perfect fdi file can be found here :
23 matches
Mail list logo
