can confirm on my other machine as well
Ivy Bridge + Nvidia 650M
--
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/1388647
Title:
DRI_PRIME=1 has no effect in Ubuntu 14.10
To manage notifications
This happens also for me. Ubuntu 14.10 Geforce GTX 750 and xorg edgers
nvidia-346. But so far I've seen it only in Image Viewer and in gnome
Terminal.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262910/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262909/+files/BootLog.txt
--
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/1354841
apport information
** Tags added: apport-collected
** Description changed:
Sometimes, the characters are rendered as black squares (cf attachment). I
couldn't find any event in the systems logs that could explain that.
I can stop the bug by changing the anti-aliasing options in the system
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262911/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262923/+files/XorgLogOld.txt
--
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/1354841
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262915/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262921/+files/UdevLog.txt
--
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/1354841
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262918/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262926/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262922/+files/XorgLog.txt
--
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/1354841
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262919/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Yes it still happens from time to time on 14.04
Actually, I think it didn't happen at all in Sept-Oct, but it happened a couple
of times in Nov. It coincides with the reboot I did at the beginning of Nov to
upgrade the system, but I can't tell if it's related to the bug due to its
highly
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262916/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262913/+files/Lspci.txt
--
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/1354841
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262920/+files/UdevDb.txt
--
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/1354841
Title:
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262917/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262914/+files/Lsusb.txt
--
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/1354841
Title:
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262912/+files/DpkgLog.txt
--
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/1354841
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262924/+files/Xrandr.txt
--
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/1354841
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1354841/+attachment/4262925/+files/xdpyinfo.txt
--
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/1354841
So far, it seems that disabling JUST id=8 works fine. If both are
enabled, the original problems remain (as expected). If I only disable
id=7, problems are the same.
I will test this a few more days to confirm further. It would be very
good if Lee Willis can reproduce this and confirm also.
--
Some status update: I enabled Don't wait for video sync and Force
full screen redraws from compizconfig. I've not yet experienced the
flickering problem. Before the compizconfig modification the problem was
severe in gnome image viewer, right after rebooting.
I have never seen problems as severe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
I have the same issue:
Ubuntu 14.10
Linux Spinky 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
xserver-xorg-video-intel:
Installed: 2:2.99.914-1~exp1ubuntu4
Candidate: 2:2.99.914-1~exp1ubuntu4.1
Version table:
2:2.99.914-1~exp1ubuntu4.1 0
Hi Bryan,
On my version (Linux Mint 17 Mate based on Ubuntu 14.04), I don't have any
result with your edit. But I had to create myself the patch from your edit to
my the distro package (synaptics 1.7.4) and a lot of things are differents
between this version and 1.8.1.
I see that you partially
** Changed in: fglrx-installer-updates (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-313-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1129409
Title:
Nvidia and
M, as per
http://www.dell.com/support/home/us/en/19/product-support/product/latitude-e5510/drivers
an update to your BIOS is available (A16). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it
doesn't, could you please both specify what
Karmic is past End of Life, and is no longer supported. As such, this
bug is being marked Won't Fix against the Karmic bug task.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
Karmic is past End of Life, and is no longer supported. As such, this
bug is being marked Won't Fix against the Karmic bug task.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in Ubuntu.
Karmic is past End of Life, and is no longer supported. As such, this
bug is being marked Won't Fix against the Karmic bug task.
** Changed in: ia32-libs (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: xserver-xorg-video-intel (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: wacom-tools (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wacom-tools in
Ubuntu 8.04 (Hardy) is EOL.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu Hardy)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to linux-restricted-modules-2.6.24 in Ubuntu.
Ubuntu 8.04 (Hardy) is EOL.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu Hardy)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to linux-restricted-modules-2.6.24 in Ubuntu.
Thanks to carlesa25's last post on this thread -
https://devtalk.nvidia.com/default/topic/734098/linux/-boinc-ubuntu-nvidia-no-usable-gpus-found-/.
..
I found that installing the nvidia-modprobe results in BOINC detecking GPUs
again.
I'm not entirely sure why this works - AFAICT the
Public bug reported:
I believe the report is accurately finding what I'm experiencing.
When attaching an external HDMI cabled monitor to my computer, the
system freezes. This happens on attachment or detachment while booted
up.
If I connect it before I boot the system, it works correctly.
Hello Andreas, or anyone else affected,
Accepted mesa into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/mesa/10.3.2-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hi Pierre. Thank you for taking the time to create a patch.
My biggest change was moving the following up in the HandleState
function, so the low level state is corrected *before* doing button
detection (this removed the quirk that depended on the order in which
fingers hit the touchpad):
Also use synclient to check the value of AreaBottomEdge. Try dropping
this and see if you see different behavior. The patched driver needs
this option set correctly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New = Confirmed
--
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/1315592
Title:
I have two of the same model HP 19 LCD 4:3 monitors connected to a
full-tower Dell Optiplex 755 running Ubuntu Gnome 14.10. One screen is
detected as 19 and the other as 17 but both screens are completely
filled and not overfilled, properly aligned, and otherwise function just
fine--I would never
I don't have this bug anymore on mainline kernel 3.18
** Tags added: kernel-fixed-upstream
--
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/1384297
Title:
gpu i915 OOPS on
Public bug reported:
Sometimes, not every time when I'm playing some Youtube videos in Google
Chrome Unity crashes. After checking in logs I noticed that video driver
has crashed. Nothing helps only reboot.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-intel
Launchpad has imported 17 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=10238.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: mir
Milestone: 0.9.0 = 0.10.0
--
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/1377872
Title:
Double-buffered compositing performance is very poor (30 FPS)
To manage
Ok I've finally gotten around to polish Chris' patch and update
testcase:
http://patchwork.freedesktop.org/patch/37073/
As soon as I have a few tested-by reports I'll pull this in, so please
go wild. Patch applies on top of latest drm-intel-nightly.
--
You received this bug notification
Public bug reported:
problem
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
CompizPlugins: No
Dear Christopher,
Thank you for checking the BIOS version, I haven't thought about that. I
have already done several BIOS upgrades on this machine, so it shouldn't
be a problem. I will update the bug report accordingly once it is done
Thank you
Matthieu
PS: I have at this very moment the white
*** Bug 86437 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR:
*** This bug is a duplicate of bug 1249551 ***
https://bugs.launchpad.net/bugs/1249551
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 #1249551, so is being marked as such.
I am facing the same problem but more frequently. I did not have this
freezing problem with Ubuntu 12.04 on my Dell XPS L502x. Once I
installed 14.04 this freezing problem started. Sometimes to unfreeze
entering into console mode and then going out works else need to reboot
the system.
I have
** Tags added: utopic
--
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/1249551
Title:
Xorg crashed with SIGABRT in RRSetChanged() with nvidia-prime
To manage notifications
sdia, thank you for your comment. So your hardware and problem may be tracked,
could you please file a new report with Ubuntu by executing the following in a
terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux
For more on this, please read the
Same issue on my Dell XPS 13 9333.
--
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/1384297
Title:
gpu i915 OOPS on power change intel_display_power_put+0xf9
To manage
Affects me too.
I have Unity and 14.10 upgraded from 14.04, Dell E7240 notebook with Core
i7-4600U and integrated Intel Haswell-ULT video.
First the problem seemed to appear after upgrade when I decided to try unity8
and installed it packages (the graphics remained slow even when I was in
Should have noted my versions:
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.10
Release:14.10
Codename: utopic
~$ uname -a
Linux xx 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
59 matches
Mail list logo
