Public bug reported:
3d graphic's in blender go crazy using ati radeon x1200 chip. ubuntu
12.04lts
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
Uname: Linux 3.2.0-67-generic x86_64
.tmp.unity.support.test.0:
Public bug reported:
Since updating Ubuntu my screen brightness is locked on high and neither
the fn+up or fn+down keys work or using the slider in the menu.
Is there a simple fix to this problem?
- Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSig
** Changed in: metacity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/907709
Title:
Windows fail to refresh unless moved
To manage
Please confirm that this is seen on an SNB or newer platform.
--
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/976489
Title:
[arrandale mesa] GPU lockup render.IPEHR: 0x02
I have very similar problem on Solaris with Radeon card and driver.
I realize this bug is not for Solaris, but this is the only other
reference I could find... and I am also a Ubuntu user ;)
I restarted my X session to open an xterm only. I was scared it could be a
low-level driver bug
but then,
Before installing the x-staging ppa
===
Both packages you listed (libgl1-mesa-dri:i386 & libgl1-mesa-glx:i386) are
already installed. The package manager doesn't complain about corrupted
packages, so I guess there is no problem. Starting Steam with my hardware
configurat
I was able to trace 2 separate crashes. It appears as though the second
crash/trace can only be triggered immediately after the first one. I was
able to do so by typing "btrunybt" in the
GDB shell after kicking off the initial "run". Attached is the output.
@Timo, were you unable to reproduce just
I'm unable to reproduce this with both trusty and utopic on a machine
that has an N-Trig Duosense multitouch panel.. Both installations are
stock ones with no added extras. I wonder if there might be something
else needed to trigger this?
** Changed in: xorg (Ubuntu)
Status: Confirmed => In
It would be nice to get an unity crash report, see:
https://wiki.ubuntu.com/Unity/FilingBugs#Getting_a_stack_trace
As for the security issue it seems related to lp:1308800
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https:/
Hello everyone.
I just upgraded to trusty and this bug popped up. And I think I managed
to fix it.
In short, previously my touchpad was handled by the driver from
`synaptics-touchpad' package (which has old ABI). After the upgrade not
only did xserver fail to load the driver, but it also didn't e
** Package changed: unity (Ubuntu) => xorg (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/1351616
Title:
Ubuntu 14.04: multi-touch screen can cause desktop to unlock
To manage notifica
** This bug is no longer a duplicate of bug 1068994
button1 gets stuck after a while
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1121379
Title:
Multiple finger touch fa
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
Steps to reproduce on a laptop with a multitouch screen (in my case, a
Lenovo X1 Carbon Gen 2):
1. Lock the desktop.
2. Start lightly tapping away on the laptop screen and triggering various bogus
mu
*** This bug is a duplicate of bug 1338492 ***
https://bugs.launchpad.net/bugs/1338492
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1338492, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
I fixed my graphics card so that it could support glx, but now it has
another problem; it won't use direct rendering.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-g
It would help to detail exactly which aspect you consider unusable. (I
think you have a menu of options :)
For me it was the fact that palmdetect was not working. Therefore I
currently use this in .config/upstart/touchpad.conf:
description "Configure the Hellpad"
author "Serge Hallyn "
#start
Seems like you're having a problem with acceleration. Can you test
ppa:canonical-x/x-staging ? And because you have problems with steam,
can you make sure all the 32-bits libs are installed? libgl1-mesa-
dri:i386 and libgl1-mesa-glx:i386 might be missing or corrupt.
** Changed in: xorg-server (Ubu
Public bug reported:
This has apparently been ongoing for a long time. I have a Saitek
Eclipse ii keyboard and I and others report that when you click the
keyboard button to change the back light color, it triggers mouse
events. These end up disabling the mouse, in my case Microsoft
Intellimous
** Information type changed from Private to Public
** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-nouveau
(Ubuntu)
--
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/1349134
Ti
*** This bug is a duplicate of bug 1033533 ***
https://bugs.launchpad.net/bugs/1033533
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1033533
Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW
rendering
--
You recei
This has apparently been ongoing for a long time. I have a Saitek
Eclipse ii keyboard and I and others report that when you click the
keyboard button to change the back light color, it triggers mouse
events. These end up disabling the mouse. Unplugging and replugging
the USB cable for the keybo
Public bug reported:
dependency leavin unconfigurt
iniscripts,upstart,plymouth,initramfs-tools,ifupdown,plymouth-
label,dbus,dbusx11,gconf2,libreoffice-gnom
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname
Public bug reported:
Xorg detects every Display twice.
I have this Notebook (Specs:)
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&dlc=en&tmp_geoLoc=true&docname=c02262928
I have the latest Bios Update (v25)
The Graphics cards in this Machine are:
Intel Core i5-430UM Processor (this is
unassiging the team from the desktop team, we are not working on it
is that still an issue?
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)
--
You received this bug notification because you are a member of Ubunt
25 matches
Mail list logo
