@Cris: probably because of it's not clear in which order they will be
applied if matrix also used.
Can you suggest link to distro which got it included, I need test it
aap, as I have important project hanging which incdues about hundred
devices with multiple screens and touchscreens. Was fight
Looks I'm getting same eefect with newest releases of Ubuntu and evdev drivers
(tried alot of combos,throughout 2012 year).
Simply, using transformation matrix with evdev driver wich inverts, scales or
shift coordinates causes either jumping to border of screen or jitter when
touch even
*** This bug is a duplicate of bug 1025488 ***
https://bugs.launchpad.net/bugs/1025488
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1025488, so it is being marked as such. Please look
** Branch linked: lp:ubuntu/precise-proposed/xserver-xorg-video-intel
--
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/1091068
Title:
No support for Ivybridge Server GPUs in 12.04
To manage notif
** Summary changed:
- fglrx propliarty driver installation
+ fglrx proprietary driver installation- Samsung 535U4C
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1076298
Title:
fglrx
Yes, this seems to be fixed for me now on Kubuntu 12.04 using libdrm
from precise-proposed on a Dell Precision T1650 with Xeon E3-1225 V2
CPU P4000 integrated graphics.
Thanks - much appreciated.
root@blackbox:~# lspci -nnvv | fgrep Graphics
00:02.0 VGA compatible controller [0300]: Intel Corpor
This bug was fixed in the package jockey - 0.9.7-0ubuntu7.7
---
jockey (0.9.7-0ubuntu7.7) precise-proposed; urgency=low
* data/handlers/fglrx.py:
- Fix typo which caused the handler to fail (LP: #1080588).
jockey (0.9.7-0ubuntu7.6) precise-proposed; urgency=low
* jockey/osli
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Per Bryce, having the updated versions of the driver packages in
-updates without the updated jockey introduces the possibility of wrong
drivers being presented that will break the system. So since this SRU
has been verified, I'm publishing the new jockey to precise-updates now
even though it's on
Yes but this program was already available :D
But ok, you can now download refresh_cd_on_resuming.py ;)
Simply launch it with python:
$ python refresh_cd_on_resuming.py
(or give execution right and double-click on it)
** Attachment added: "refresh_cd_on_resuming.py"
https://bugs.launchpad
It is probably a Compiz bug.
** Also affects: compiz
Importance: Undecided
Status: New
--
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/1020051
Title:
Xorg freeze
To manage notificatio
Public bug reported:
I'm using a Thinkpad T420 with Nvidia 4200M (Optimus). I've been
successfully using Ubuntu 12.04 and now 12.10 with Bumblebee and the
Ubuntu provided Nvidia drivers for a while.
Today - wanting to get the latest release of the Nvidia 310 series
driver, I installed xorg-edgers
Sure. All I have to do is remove the xorg.conf file, reboot and open a mkv
video file with vlc.
Its reproduceable each time-
Not sure about those BIOS warnings, I get them with both SNA and no xorg.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
** Changed in: libdrm (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
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/1091068
Title:
No support for Ivybridge Server GPUs in 12.04
T
I've also double-checked that after installing jockey 0.9.7-0ubuntu7.7,
fglrx-experimental-9 installs cleanly and boots up to a usable Unity
session. Looks good, I'll close out the jockey task as well.
** No longer affects: fglrx-installer (Ubuntu)
** No longer affects: fglrx-installer (Ubuntu
Hi Christopher
Followed instructions above and this is the output from "X -version":-
"X.Org X Server 1.12.3
Release Date: 2012-07-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-31-xen i686 Ubuntu
Current Operating System: Linux ubuntu 3.2.0-29-generic-pae #46-Ubuntu SM
** Changed in: linux (Ubuntu Precise)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Quantal)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.
I've uploaded a new 3.2.2 version with a fix - explicitly check if we're
running as python2 rather than 3, and use python2-compatible string
conversion in that case.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bug
It appears that when installed on quantal, even though the script
specifies /usr/bin/python3, that gets stripped off and the binary is run
as python2. The xpci code then gets hung up on a bytes/string
conversion in python3-specific code.
** Tags removed: verification-needed
** Tags added: verifi
Proprietary drivers version 304 failed to install (from jockey). I
didn't bother to torubleshoot any further so i tried 310 instead.
After rebooting my machine, lightdm failed to start
Syslog:
NVRM: API mismatch: the client has the version 310.14, but
NVRM: this kernel module has the version 304.
I'm having the same exact issue, albeit with Ubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1093788
Title:
X doesn't load after fglrx install
To manage notifications ab
Sorry for double posting.
There is nothing at the time of the crash in syslog. I do have something
in Xorg.0.log.old though.
http://pastebin.com/B9CPJrcc
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https:
I'm having the same issue, it appeared not too long ago.
Kubuntu 13.04 with xorg-edgers PPA.
I'm using the nvidia-313 driver.
Linux user 3.8.0-2-generic #6-Ubuntu SMP Fri Jan 25 22:03:57 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ub
It does specifially not make much sense after the verification was done
& the fix has been released.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/948053
Title:
nvidia-17
hi!
@ searchfgolds67899:
a new bugreport bug1064192 was opened for Quantal, this one got closed.
Therefore removing tag "quantal". Pls. try to get familiar with "How to
report bugs ;-)
** Tags removed: quantal
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I've downgraded the following packages to 2.3.32:
libdrm-radeon1
libdrm2
libdrm-intel1
libdrm-nouveau1a
but the bug is still reproducible. So I guess it is also related to the
following rendering packages, which have been updated two days before libdrm
changes were introduced:
libegl1-mesa-drive
Please forget my last comment about the power supply. This was a test
with kernel version 3.2.27. With current 3.8.0-rc4 this was not an issue
- after system freeze I could plug of the power and system was unchanged
in freeze mode with battery supply. So the information was maybe not
very helpful.
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1091068
Title:
No support for Ivybridge Server GPUs in 12.04
To manage notif
Confirmed with the xserver-xorg-video-intel package from proposed along
with the latest libdrm from proposed and the kernel where the fixes
landed.
With this combination everything looks good.
Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
Results from a fully updated 12.04.2 install using the X backports stack
(xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise2) with
proposed enabled:
ii nvidia-experimental-310 310.14-0ubuntu0.3
Installed fine, verified
ii nvidia-current-updates
The possibility to downgrade to version 2.4.32 seems to broken due to
missing dependencies, so regression testing might be difficult...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1105389
Tit
Per Timo's request, I've,
* installed drm-intel-nightly kernel 2013-01-29
* installed intel-gpu-tools
* run kms_flip
I'll attach the output, but no kernel traces found.
** Attachment added: "kms_flip output"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1097315/+
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libdrm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1105389
Title
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/948053
Title:
nvidia-173 and nvidia-96 uninstallable on Precise
To manage notifications about this b
** This bug is no longer a duplicate of bug 993427
fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build [error:
‘cpu_possible_map’ undeclared (first use in this function)]
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer
Public bug reported:
"/etc/init.d/networking restart" or "service networking restart" causes
X to crash and have to switch to tty to kill X.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
Uname: Linux 3.5.0-22-gen
*** This bug is a duplicate of bug 993427 ***
https://bugs.launchpad.net/bugs/993427
Fixed this by using Holm Dressler's patch from this link:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/993427
** This bug has been marked a duplicate of bug 993427
fglrx 2:8.960-0ubuntu1:
** Attachment added: "Video of the problem"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1108967/+attachment/3505909/+files/flicker.avi
** Attachment removed: "video of the problem"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1108967/+attachment/3505829/+files/Video%2029-01-
Public bug reported:
1. Start up into Ubuntu.
2. Log in to a normal account.
3. From the system menu, choose "Guest Session".
What happens:
1. Ubuntu starts up correctly.
2. The login screen and Ubuntu session work fine.
3. The screen goes black for about 30 seconds.
4. The screen flickers wildly
** Branch linked: lp:ubuntu/precise-proposed/fglrx-installer-
experimental-9
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1080588
Title:
jockey suggests not installa
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics-drivers-
updates
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1080588
Title:
jockey suggests not install
Hello Yung, or anyone else affected,
Accepted xserver-xorg-video-intel into precise-proposed. The package
will build now and be available at http://launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/2:2.17.0-1ubuntu4.3 in a few hours, and then
in the -proposed repository.
Please help us by te
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1108941
Title:
fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build
To manage notification
Public bug reported:
Succesfully created packages using AMD 13.1 display driver package (amd-
driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run) for Ubuntu
12.10. Installation with dpkg failed.
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: fglrx 2:8.970-0ubuntu1
ProcVersionS
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics-drivers-
experimental-310
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1080588
Title:
jockey suggests no
Hello Maarten, or anyone else affected,
Accepted nvidia-graphics-drivers-updates into precise-proposed. The
package will build now and be available at
http://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-
updates/304.64-0ubuntu0.2 in a few hours, and then in the -proposed
repository.
Pleas
Hello Maarten, or anyone else affected,
Accepted nvidia-graphics-drivers-experimental-310 into precise-proposed.
The package will build now and be available at
http://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-
experimental-310/310.14-0ubuntu0.3 in a few hours, and then in the
-proposed
Hello Maarten, or anyone else affected,
Accepted fglrx-installer-experimental-9 into precise-proposed. The
package will build now and be available at
http://launchpad.net/ubuntu/+source/fglrx-installer-
experimental-9/2:9.010-0ubuntu0.3 in a few hours, and then in the
-proposed repository.
Please
You're right. Thank you for noticing the error in my report yesterday.
to my knowledge, I've never seen this issue with the quantal kernel.
I've only had the problem with 3.5.X. Yesterday when I rebooted, and
saw a 3.8.0 and a 3.7.X I didn't think hard and assumed that 3.7 was
quantal, forgetting
Confirmed:
I reproduced the bug on an Asus EEE 901
** Attachment added: "screenshot of the bug"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1100970/+attachment/3505732/+files/IMG_2546.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
X core dumped on hitting the onboard icon.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xserver-xorg 1:7.7+1ubuntu4
Uname: Linux 3.1.10-9-nexus7 armv7l
.tmp.unity.support.test.0:
ApportVersion: 2.8-0ubuntu2
Architecture: armhf
CompizPlugins: No value set for
`/app
*** This bug is a duplicate of bug 948053 ***
https://bugs.launchpad.net/bugs/948053
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
Public bug reported:
dhcp-server appears to be affected have to purge and reinstall
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2
Just for the record, someone reported that this bug occurs in old or
integrated GPUs (eg in netbooks and machines that don't have glsl
support). I didn't manage to reproduce it yet.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vid
** Package changed: xorg (Ubuntu) => unity (Ubuntu)
--
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/1106985
Title:
bug in unity
To manage notifications about this bug go to:
https://bugs.launchp
56 matches
Mail list logo
