** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/bugs/729110/+attachment/1885415/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in ubuntu.
https://bugs.launchpad.net/bugs/729110
Title:
mouse button mapp
Public bug reported:
Binary package hint: xinput
I have an Evoluent VerticalMouse and mapped the buttons a bit different
using the following command:
/usr/bin/xinput set-button-map 12 1 9 2 4 5 6 7 3 8
Every once in a while, the button mapping is reset to default. This
happens from once every
I didn't see this bug on Lucid for now. Looks fine. :)
--
Using Chromium crashed X and made kernel panic
https://bugs.launchpad.net/bugs/526757
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
_
@SolidSlash #21: I guess you have the same problem as I had: fglrx
conflicts with the "radeon" kernel module. You have to add "nomodeset"
or "radeon.setmode=0" to your kernel options, i.e. get into GRUB, edit
the parameters for recovery mode and add it manually to the kernel line.
After getting int
The 2:8.721-0ubuntu2 package for amd64 is missing the
/usr/lib/fglrx/ld.so.conf and thus it doesn't configure correctly. You
can fix this for now by creating that file with the contents
"/usr/lib/fglrx" (without quotes) and then doing a "dpkg --configure
-a". Worked fine for me.
--
Does not suppo
Forgot to add: I'm using an Aiptek SlimTablet 600U (Model WCK-C121) and
have NOT installed xserver-xorg-input-aiptek but xserver-xorg-input-
wacom (the tablet also uses the "wacom" kernel module). The problem
seems to be the same though. So it might have nothing to do with the
specific input driver
Just wanted to add that for me (Jaunty, all updates as of today) X/GDM
won't start correctly if the tablet is plugged in. Also I got X crashing
when trying to start a new console (Terminator) while the tablet is
plugged in. And yes, unplugging the tablet also hangs and then restarts
X.
--
Unplugg
I now found out that the gray stripes have to do with the
"compositing_manager" option under /apps/metacity/general . When
enabled, I see the gray stripes. When disabled, I see my desktop but see
garbage in some apps e.g. the VLC window (might be all Qt interfaces
which fail).
--
[HD 3650] cannot
> I just installed the PPA version again and had a closer look. With and
> without XAA my Xorg defaults to VESA?!?
The latest xserver-xorg seems to not recognize this card anymore. To
force it to use the ati driver, add the line
Driver "ati"
to the Section "Device" in your /etc/X11/xorg.conf .
Here's the "screenshot". This bug happens for some tormodvolden-builds
now. About a month ago these builds worked fine.
The bluish thing around the edges is "Gnome Do", which originally
appears at the center of the screen. The mouse cursor is rendered fine,
by the way.
** Attachment added: "P1010
I have the same(?) problem on Jaunty with a ATI Mobility Radeon M6 LY.
Using the latest package from tormodvolden's PPA, after login I get
horizontal gray and black stripes and on the black stripes in some areas
every second pixel shows the desktop. I'll try to make a photo...
The interesting thin
@Timo Jyrinki:
On my Mobility M6 LY (16MB), EXA with both of your optimizations is still
slower than XAA. Using EXA, showing the selection list of "Gnome Do" (down
arrow) is presented in 3 hard steps whereas using XAA it is smoothly animated.
Same goes for expanding the playlist in VLC player.
Also tried it. With the default screen size of 1024x768 (notebook TFT
panel) it's still nothing near the XAA speed. When switching to dual-
screen resolution 2304x1024, some options (like ColorTiling) get
disabled according to Xorg.log because the card can't handle it at this
resolution. And perfor
13 matches
Mail list logo
