Public bug reported:
Using newest utopic my screen flickers to black and back every now and
then during regular use. After a few seconds it comes back. Whenever
this happens I get an error trace in dmesg. All of them are slightly
different, here is an example one:
[55848.787245] CPU: 3 PID:
Public bug reported:
In trusty I get screen corruption when using Thunderbird as shown in the
attached image. Other programs seem to work fine.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic
Public bug reported:
3D rendering landed recently for Southern Islands cards. However there
are some rendering glitches that happen rarely.
The most common of these is text rendering glitch in Firefox. What
happens is that every now and then a letter is drawn incorrectly. It may
be drawn as
I have a different graphics card now so I can't test this any longer.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1135668
Title:
Intel graphics fails when bringing
3D acceleration is not working for me using a Radeon HD 7750 on an up to
date saucy.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1209397
Title:
[radeonsi] radeonhd southern islands 3d
Public bug reported:
According to this page, Radeon HD 7750 should be supported:
https://help.ubuntu.com/community/RadeonDriver
However there is no 3D acceleration:
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.2, 256 bits)
OpenGL version string:
Here's the raw EDID block from dmesg:
[11903.844749] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
remainder is 195
[11903.844754] Raw EDID:
[11903.844756] 00 ff ff ff ff ff ff 00 22 f0 f8 26 01 01 01 01
[11903.844758] 32 12 01 03 80 36 23 78 ee ce 50 a3 54 4c 99
This still happens with release version of raring.
** Changed in: linux (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: linux (Ubuntu Raring)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I tried drm-intel-nightly version 03-05. I suspended an woke the monitor
10 times in a row and it worked fine. There was no unexpected output in
dmesg.
So this bug is probably fixed by said commit.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Debug log attached.
However in this case it brought the monitor up but at the wrong
resolution (1024x768). That happens sometimes. Going to system settings
- displays - detect displays makes it detect the resoutions properly.
I'll try to get a new log which shows the case where it fails to bring
Here's the log when the monitor remains black.
** Attachment added: drm-debug2.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1135668/+attachment/3552587/+files/drm-debug2.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
I have a HP LP2475w monitor. Sometimes when the system has put it to
sleep, it fails in bringing it back up again. The screen remains blank.
Even changing virtual terminals with ctrl+alt+f1 does not work. Ssh'ing
in and running 'sudo service lightdm restart' makes it come
** Description changed:
I have a laptop with a touchpad and an external mouse. External mouse
motion is ignored whenever a keyboard button is held down. This makes
most computer games unplayable because you can't move and turn at the
same time.
The touchpad is not ignored and keeps
Public bug reported:
I have a laptop with a touchpad and an external mouse. External mouse
motion is ignored whenever a keyboard button is held down. This makes
most computer games unplayable because you can't move and turn at the
same time.
The touchpad is not ignored and keeps working
Public bug reported:
Using newest Quantal the mouse cursor started behaving strangely. When I
move the mouse, the cursor jumps back and forth between two locations,
which can up to a centimeter apart. Both cursor locations move according
to mouse motion.
If I push the cursors to the top left
Here's my NVidia bug log.
** Attachment added: nvidia-bug-report.log.gz
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/995239/+attachment/3367990/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Current behaviour of X in precise is that Virtual Core Pointer does not
provide any touches at all. Thus testing whether this bug still exists
or not is impossible.
Will update again once touch reporting works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
A test app that demostrates this bug can be downloaded from here:
lp:~jpakkane/+junk/touchpad-tester.
My setup is that I have a Magic Trackpad and a Macbook Pro multitouch
trackpad. The test app prints out this:
Using device id 2, Virtual core pointer.
Potential device id
Public bug reported:
A test app for this bug can be downloaded from lp:~jpakkane/+junk
/touchpad-tester
When tested with a Magic Trackpad and a Lenovo (?) trackpad, the latter
does not show up in the device listing that touchpadtester prints.
However touching the pad does cause touch events, but
If you look at the second video very carefully you can see that the
cursor does not jump to the corner when the selection expands.
What probably happens is that the application that does the background
selection does not handle XInput valuators properly. An extremely
similar bug was fixed in Qt
It seems that in static EvdevProcessValuators the x and y coordinates
are flipped and the result written back in the valuators. I could not
fully decipher what the code is doing but attached is a patch which at
least roughly shows where I think the problem is.
Chase, any comments on this?
**
When I play back the recording, the behaviour is the following (on both
natty and oneiric):
A swipe from bottom to top. Then it stands still for a while and jitters
a bit within a radius of ̃~5 pixels.
A second swipe from bottom to top. Then jitter as above.
After this the cursor jumps around
Gaah! I knew it had to be something simple that I overlooked.
Pushed a new version to the build service. You know what to do. :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/799202
The PPA packages fix it for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/799202
Title:
wacom stylus jumps with latest xserver-xorg-core
To manage notifications about this bug go
I'll push a newer version. In the mean time you can download the
packages manually and install them with dpkg -i *.deb.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/799202
Title:
wacom
I could not upload because the unstable PPA has run out of space.
Working on it...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/799202
Title:
wacom stylus jumps with latest
This patch has been accepted into Ubuntu proper. It will be in the next
Qt package, which will probably be released on Monday.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/799202
Title:
The reason Krita fails is that it uses the high resolution location and
not cursor location.
High resolution location evaluation is broken whenever the X server does
not send both X and Y coordinates.
Thus the valuator code is still wrong somehow.
I have pushed a hack fix to the PPA that just
I have just uploaded a Qt version to the PPA that preserves the old
values. It should finish building after four hours or so. Please try it
out once it is finished. The new version is 4.7.4-0ubuntu3~utouch2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
The new packages do not fix this for me. I still get ghost jumps.
This makes sense, because if the valuators are parsed incorrectly, then
the Qt tablet app should draw additional loops as well. I even tried
moving the window partially outside the top left corner to make sure any
paint operations
The Krita code that deals with tablet events seems to be this in
kis_canvas_controller.cpp:
-
void KisCanvasController::Private::emitPointerPositionChangedSignals(QEvent
*event)
{
if (!coordinatesConverter) return;
QPoint pointerPos;
QMouseEvent *mouseEvent =
A new Qt version consisting of current packaged code + the valuator
patch has just been pushed to uTouch team's unstable PPA. Once it
finishes building (and there are no build failures :), please test it
out.
It is oneiric only and may eat your soul if mishandled. So be careful.
--
You received
And the jumps happen when I move the pen slowly. When moving it fast,
there are no jumps.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/799202
Title:
wacom stylus jumps with latest
It has built now. The demo app no longer produces huge rectangles for
me.
However Krita does the weird stylus jumps now. Earlier it did not. The
jumps do not always go to the top left corner, though they do go mostly
towards the top left.
--
You received this bug notification because you are a
Animtim, could you try the qt4 tablet test application mentioned above?
Does it behave properly with both pressure and tilt based line width?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Attached is a quick patch that inspects that valuator accesses do not go
out of bounds. I changed only the motion and button accesses and not the
Wacom one. The reason being that it seems to loop over all data so it
should be valid.
I have not tested the patch in any way, so it might not even
I can confirm that on my Wacom Bamboo Pen Touch the behaviour is
exactly the same as j-b-m. The only addition being that I get the huge
rectangles only when I stop moving the pen (but keep it touching the
surface).
My tablet probably does not provide tilt information so could you try
the
I looked into Qt and there are three locations where x and y tilt values
are obtained. They are all in qapplication_x11.cpp in the function
QETWidget::translateXinputEvent.
The first one is this (I have removed quite a lot of lines, check the
original to be sure):
s =
This may be a bug in Krita.
When I install qt4-demos and run
/usr/lib/qt4/examples/widgets/tablet/tablet, pressure works perfectly.
Can someone else with this bug try if the tablet test app works?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This is getting weirder and weirder. I updated my packages and tried
again. Now the behaviour is different. Just adding the struct elements
does *not* break pressure. Previously it did. I verified on previous
test results I had written down with an actual pen and paper.
What happens now is
The cause of (some part) of this bug is somewhere else. I removed all
code from patch 503 and left only the part that adds new fields to
structs. Effectively it looks like this:
--- a/include/inputstr.h
+++ b/include/inputstr.h
@@ -335,6 +335,8 @@ typedef struct _TouchPointInfo {
unsigned
I recorded a couple of pressure swipes with a Wacom. When I play back
the recordings, Krita does not detect any pressure changes. Does anyone
else get pressure info when playing back these traces?
** Attachment added: wacom-bamboo-pen-n-touch.device
** Attachment added: wacom-bamboo-pen-n-touch-pressure.record
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/799202/+attachment/2375684/+files/wacom-bamboo-pen-n-touch-pressure.record
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I build my own X server packages without patches 504, 503 or 502. In
those cases pressure is properly recognised from both evemu recordings.
With patch 502 it is not. Using the Wacom directly works on both (but
breaks with 504 as with others).
--
You received this bug notification because you
I get the same behaviour: regular oneiric X does not draw anything on
the trace files, taking out patches 503 and 504 makes things work.
However there is one major difference.
When I use my own Wacom Bamboo Pen Touch, pressure sensitivity works.
The recordings only produce lines of constant
Another difference: when running an X server with all patches, Krita
draws nothing when I use my Wacom, but does draw if I replay either one
of the recordings.
It seems that there is a larger bug lurking about and the patch only
makes it more/less apparent.
As far as warping goes, the only time
I can't do that because I can't launch a terminal, switching to text
console does not work and you can't ssh in the machine.
However, X itself is not frozen. I can move the mouse, activate top
panel thingies and so on. Pressing the power button shuts down the
machine cleanly.
I have run
Yes, it's exactly the same.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/807584
Title:
Oneiric alpha 2 live session freezes on startup
To manage notifications about this bug go to:
Public bug reported:
I run Oneiric alpha 2 64+mac live CD. Plugging in an external monitor
with a DVI cable causes the screen corruption.
The laptop's main screen splits into two halves. The top one keeps
showing whatever it was showing when the monitor was plugged.
The bottom half displays
** Attachment added: external_corruption.jpg
https://bugs.launchpad.net/bugs/810971/+attachment/2209441/+files/external_corruption.jpg
** Description changed:
I run Oneiric alpha 2 64+mac live CD. Plugging in an external monitor
with a DVI cable causes the screen corruption.
The
Attached.
This does not feel like a dup of that bug to me. The behaviour is
different and this GFX card occasionally has screen corruption even
without an external monitor.
** Attachment added: lspci.txt
apport information
** Tags added: apport-collected running-unity unity-2d
** Description changed:
I booted the oneiric alpha 2 ISO (mac 64 bit). The welcome screen shows
up asking to try or install. I click on live session. Then the
application tries to do something and just freezes. You
Ctrl-t does not work, with or without shift. However I just discovered
something stranger:
If I change language with the list on the left and click try ubuntu
there is no freeze.
If I click on some language, then english again and then try ubuntu
there is no freeze.
If I just click on try
53 matches
Mail list logo
