According to this page:
http://wiki.cchtml.com/index.php/Ubuntu_Trusty_Installation_Guide#Hardware_Video_Decode_Acceleration
xvba-va-driver is no more needed since Catalyst 14.12.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer
Today, I accidentally started Chrome, my computer froze immediately. No
need to click a link or anything. Just thought I'd let you know.
--
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/1477649
This happens to me on a Dell M3800 with _no_ external monitor. Probably
a few times a week. After anywhere from 5 minutes to a few hours, the
cursor comes back. I have to use the touchscreen until then. Man I hate
touchscreens.
--
You received this bug notification because you are a member of
It seems to be related to this Chrome issue:
https://code.google.com/p/chromium/issues/detail?id=513685
I don't know if Chrome messing with the GPU should stop Ubuntu?
** Bug watch added: code.google.com/p/chromium/issues #513685
http://code.google.com/p/chromium/issues/detail?id=513685
--
** Package changed: nvidia-graphics-drivers-331-updates (Ubuntu) =
nvidia-graphics-drivers-346 (Ubuntu)
** Changed in: nvidia-graphics-drivers-346 (Ubuntu)
Assignee: (unassigned) = Rutuja (27rutuja)
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
Please sync x11proto-randr 1.5.0-1 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* New upstream release (LP: #1473828)
New upstream release is aleady applied in Debian, as well.
Changelog entries since current wily version
Installed version 346 on my machine (Ubuntu 14.04.2 LTS, linux
3.13.0-58-generic x86_64). There was a minor problem with nvidia-opencl-
icd-346-updates not removing nvidia-opencl-icd-331 and having a
conflicting file. Solved this problem by removing the conflicting
package.
There was no report of
Public bug reported:
I Don't Know If I Am Reporting This Bug To The Right Package.
But I Have A Dell Latitude D820, And I Can't Control The Brightness.
It Stay's At 100% Brightness.
The Only Way To Control It Is TO Reboot Into The BIOS Setup And Change It There.
I Have Ubuntu 15.04, on A i686.
Backup Of My /var/log Directory
** Attachment added: logs.tar.gz
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1478148/+attachment/4433756/+files/logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete = Expired
--
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/1456918
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete = Expired
--
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/1424864
Thanks for the additional workaround. I didn't happen to have this enabled so I
had to:
$ gsettings set org.gnome.settings-daemon.peripherals.mouse locate-pointer true
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Changed in: xf86-input-wacom (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/1464440
Title:
package xserver-xorg-input-wacom
Also affected on this bug. Is there anything you can do, any command you
can type or something like that to flush the memory xorg uses? Or is
the only available workaround to restart xorg?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I've also seen on my Fujitsu U904 (3200x1800) connected over DP to the
external 4k screen. I've worked around it by using Ctrl to highlight
the cursor position until the cursor returns (sometimes it takes more
than a couple of hours, and the only sure way to get it back is to log
out and log back
Not all memory leaks are the same. The original bug here was a definite
bug in one particular driver. Since then this has been falsely
duplicated to a bug in the binary fglrx and also for the pixmap leaks in
plasma. Please always open a bug for yourself, and for memory leak
queries in addition to
16 matches
Mail list logo
