** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/issues #70
https://gitlab.freedesktop.org/xorg/lib/libx11/issues/70
** Also affects: xlibs via
https://gitlab.freedesktop.org/xorg/lib/libx11/issues/70
Importance: Unknown
Status: Unknown
--
You received this bug
FYI a person contacted me about Red v3 and support for that is now
included in upstream,
https://gitlab.freedesktop.org/libinput/libinput/blob/master/quirks/30
-vendor-contour.quirks
If you have other models with other USB ids and find this bug report,
please follow his example and contribute a
The 1.12.6 in disco and my PPA should have the quirk installed by
default for Contour Design RollerMouse Free 2 and Re:d so it should just
work. Hence marking as Fix Released for development release and leaving
it up to stable maintainers to decide whether something should/could be
done for 18.04.
://launchpad.net/~timo-jyrinki/+archive/ubuntu/libinput the
next time I visit. soname seems to be the same so maybe it'd be drop-in
compatible.
** Also affects: libinput (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Everything seems to work on my Intel Broadwell laptop and a desktop with
Radeon 7750 graphics card. With the former I've mostly run normal
desktop stuff, heavy WebGL in Firefox + Chromium and some more basic
OpenGL apps from the archives. With the latter I've run a variety of
Steam games like Gone
Adding my bits that everything seems smooth with the xenial-proposed
libdrm* and mesa* on a Intel Broadwell system and a Haswell system with
AMD Radeon 7750.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
I happen to have Radeon 7750 and I'm happy with the new mesa
12.0.6-0ubuntu0 from proposed. I played Team Fortress 2 among else.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Tags added: r11
--
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/1609745
Title:
Touch screen not working on Acer Chromebook R11,
CONFIG_TOUCHSCREEN_ELAN not enabled on mainline 4.7 kernel
The actual problem/bug is that for some reason the mainline Ubuntu 4.7
kernel lacks CONFIG_TOUCHSCREEN_ELAN. In 4.4 Ubuntu kernel
CONFIG_TOUCHSCREEN_ELAN is defined, but the touchscreen doesn't work.
However with mainline Ubuntu kernel sources, and CONFIG_TOUCHSCREEN_ELAN
enabled manually via a
Actually there was a change: with mainline 4.7 kernel there is no trace
of the touchscreen anymore in dmesg or xinput.
--
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/1609745
Title:
Touch screen
** Bug watch added: Linux Kernel Bug Tracker #151531
http://bugzilla.kernel.org/show_bug.cgi?id=151531
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=151531
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4714585/+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
** Description changed:
Touch screen seems to be identified as far as I can see, but there's no
working input. I've tried among else xinput test-xi2, reattach command
but it seems simply non-functional for whatever reason.
It works on the ChromeOS side.
I'll
No change on 4.7 mainline kernel.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Tags removed: single-occurrence
** Tags added: r11
--
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/1609745
Title:
Touch screen not working on Acer Chromebook R11
To manage notifications
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713919/+files/WifiSyslog.txt
** Description changed:
Touch screen seems to be identified as far as I can see, but there's no
working input. I've tried among else xinput
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713939/+files/WifiSyslog.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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713931/+files/JournalErrors.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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713933/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713927/+files/CRDA.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/1609745
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713930/+files/IwConfig.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/1609745
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713932/+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/1609745
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713937/+files/RfKill.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/1609745
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713912/+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/1609745
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713913/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713938/+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/1609745
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713935/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713928/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713936/+files/ProcModules.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: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713926/+files/AlsaInfo.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/1609745
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713934/+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: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713929/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713917/+files/RfKill.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/1609745
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713914/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713918/+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/1609745
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713916/+files/ProcModules.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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713915/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713911/+files/JournalErrors.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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713910/+files/IwConfig.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/1609745
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713908/+files/CRDA.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/1609745
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713909/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
Touch screen seems to be identified as far as I can see, but there's no
working input. I've tried among else xinput test-xi2, reattach command
but it seems simply non-functional for whatever reason.
It works on the ChromeOS side.
I'll add kernel to the bug report since it
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4713907/+files/AlsaInfo.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/1609745
The mesa update should fix the issue for phone sw. You may remove any
workarounds now.
** Changed in: canonical-devices-system-image
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.
Correcting, err, the fifth time worked or something which I guess
couldn't be possible with this bug. Also I did not find the EGL error
from unity8-dash.log. Sorry for the noise.
** Description changed:
Qt clients are failing to create an egl context when running on Intel
- Pineview and
Added to the description that Cherryview (Braswell 14nm Atom with
Broadwell-level 8th gen Intel graphics) seems similarly affected. I can
test fixes.
** Description changed:
Qt clients are failing to create an egl context when running on Intel
- Pineview systems under Mir.
+ Pineview and
** Tags added: qt5.6
--
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/1585942
Title:
Mesa causes a segmentation fault on arm64 (wrong count of uniform
locations)
To manage notifications about
And it started happening after Qt on arm64 switched to OpenGL ES,
similar to armhf.
--
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/1585942
Title:
Mesa causes a segmentation fault on arm64
Public bug reported:
This bug is to remind that Debian is building mesa against llvm-3.7-dev
instead of 3.6 that Ubuntu does.
llvm-toolchain-3.7 used to fail to build on i386 and powerpc on wily,
but now succeeds on all archs: https://launchpad.net/ubuntu/+source
(llvm 3.7 is a pre-requirement of getting OpenGL 4.1 support for AMD and
NVIDIA)
--
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/1536988
Title:
Merge the change to llvm 3.7 from Debian
To
I've been retesting the newer version now on Haswell + Broadwell without
seeing any issues.
--
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/1471213
Title:
[SKL] noise in unity dash, torcs
To
Broadwell has continued to work well, and I've now been using it also on
a Haswell desktop PC without issues, some game playing etc included.
--
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/1471213
FWIW Intel Broadwell on Dell XPS 13 2015 Dev Ed seems solid with the
update, 25h+ varied usage so far - suspending, browsing, OpenGL, WebGL,
videos.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Hmm, this may have been fixed now in the upcoming 14.04.3 LTS HWE
upgrade, can anyone confirm?
That is, after purging the configuration files of -utopic packages, the
link /etc/X11/X is removed but system continues to work.
I upgraded by temporarily enabling trusty-proposed updates and sudo apt
** Description changed:
+ Bug:
+
+ The bug happens whenever the remaining configuration files of the
+ original X stack is removed, ie purging. It does not happen for users
+ who do not explicitly remove those.
+
+ Workaround:
+
+ For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
+
franglais.125: Yes, I tested it on purpose that bug #1132736 still
happens on 14.04.X HWE updates for the pedantic of us that clean up
removed packages' configuration bits and pieces.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in
** Changed in: xorg-lts-utopic (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/1132736
Title:
Xorg fails to start after installing the hardware enablement
@17: I think that's understandable that not giving enough necessary
packages may make apt do wrong decisions. The upgrade is very complex
package dependency wise so apt needs to be given as much information as
possible so that it's able to do the correct upgrade.
I experienced the same with 12.04
I could not reproduce what comment #15 said, only the correct packages
were pulled when I upgraded with:
sudo apt install libgles2-mesa-lts-utopic libglapi-mesa-lts-utopic
linux-generic-lts-utopic xserver-xorg-lts-utopic libgl1-mesa-dri-lts-
utopic libegl1-mesa-drivers-lts-utopic
Happened now on ubuntu-system-settings-online-accounts autopkgtests,
preventing qtbase from moving from -proposed to -release:
https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-
adt-ubuntu-system-settings-online-
accounts/lastBuild/ARCH=i386,label=adt/console
--
You received
Public bug reported:
With the new Mesa 10.3 we're seeing GLX errors on builds/tests that did
not happen before the new Mesa:
qtbase-opensource-src rebuild:
*** This bug is a duplicate of bug 1374131 ***
https://bugs.launchpad.net/bugs/1374131
** This bug has been marked a duplicate of bug 1374131
qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Also blocks qtbase from landing / running its unit tests successfully
bug #1374355
--
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/1374131
Title:
qtcreator-plugin autopkg test fails on AMD64
armhf has Can't find EGLConfig variant of the error:
https://launchpadlibrarian.net/185824181/buildlog_ubuntu-utopic-armhf
.qtbase-opensource-src_5.3.2%2Bdfsg-
1ubuntu1~utopic1~test7_FAILEDTOBUILD.txt.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New = Confirmed
** Summary changed:
- [Regression] LLVM error in executing Ubuntu UI Toolkit tests on x86
+ [Regression] LLVM ERROR: Do not know how to split the result of this
I'm not sure if this is still reproducable with Qt 5.3.0, but the
upstream seems to point to the libxcb upstream bug which now has a fix.
Another Qt bug linked to the upstream Qt bug report was also reported
fixed in Qt 5.3.0.
** Package changed: qtdeclarative-opensource-src (Ubuntu) = libxcb
For completeness sake, here's mine on Latitude D630 (Intel 965GM
graphics), also inside qglxintegration.cpp but slightly different.
Program received signal SIGSEGV, Segmentation fault.
0x7fffee0aa81c in QGLXContext::swapBuffers (this=0x81d790,
surface=0x638450) at qglxintegration.cpp:392
** Also affects: libxcb (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-
checkbox-gui crashed with following console outputs:
pure virtual method called
terminate called without an active exception
Aborted (core dumped)
Steps to reproduce:
1.
mentioned in a bug report and the bug might be something fixable there
too.
For now I'm out of ideas. An X.org expert would be welcome to
investigate, since most probably the bug is either in libxcb itself or
the Qt's xcb plugin.
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: Timo Jyrinki
** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mouse pointer emulation from touch breaks with
qtbase 5.2.1+dfsg-1ubuntu14.2 SRU for trusty is in unapproved queue now
too
(https://launchpad.net/ubuntu/trusty/+queue?queue_state=1queue_text=)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
-opensource-src (Ubuntu Trusty)
Status: New = In Progress
** Changed in: qtbase-opensource-src (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: qtbase-opensource-src (Ubuntu Trusty)
Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki)
** Changed in: unity (Ubuntu Trusty
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) = Timo Jyrinki (timo-jyrinki)
--
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/1278871
Title:
please
*** This bug is a duplicate of bug 1280665 ***
https://bugs.launchpad.net/bugs/1280665
If you don't mind, I'd mark this bug as duplicate of (later filed) bug
#1280665 which correctly attributes the bug to be in SDL 1.2 which
enables backingstore wrongly in composited environment (if I
(a fixed version of the comment I posted earlier, one link was wrong)
I bumped into this problem on a friend's computer.
Another summary of how to go back, in Terminal app, to the old version
where AMD had not yet dropped support for 2000/3000/4000 Radeons:
If you have 32-bit Ubuntu 12.04,
I bumped into this problem on a friend's computer.
Another summary of how to go back, in Terminal app, to the old version
where AMD had not yet dropped support for 2000/3000/4000 Radeons:
If you have 32-bit Ubuntu 12.04, copy-paste the following to Terminal:
wget
** Tags removed: verification-needed
** Tags added: verification-done-precise verification-needed-saucy
--
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/1243261
Title:
This should be just a packaging change and a patch for Mesa 10.0.1 is at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656719#240
As it continues to be more WIP than stable (correct me if I'm wrong), it
should probably stay in universe and not be installed by default. Still,
offering it would
This seems to apply and build, but I don't currently have my Radeon card
so I could test it. I wasn't sure about the Debian patch's '--disable-
gallium-g3dvl', it's not there in this patch.
** Patch added: patch adapted for Ubuntu
Verifying fullscreen video working good on Haswell with updated xserver-
xorg-video-intel-lts-saucy from precise-proposed. Tested various videos
and seeking in mplayer -vo xv and totem (gstreamer-properties set to the
default auto detection which in turn uses Xv).
** Tags removed:
** Changed in: xserver-xorg-video-intel-lts-saucy (Ubuntu Saucy)
Status: Confirmed = Invalid
--
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/1243261
Title:
apparent
** Description changed:
-
How to reproduce:
1. open libreoffice - file - new - presentation
2. paste any movie; insert - movie
- this bug is quite reproducible and this movie file can be anything that
libreoffice/gstreamer can play.
+ this bug is quite reproducible and this
I had this problem on 12.04 LTS testing the LTS-S hardware enablement
packages. The upstream bug report's fix fixed the problem when I applied
it on top of xserver-xorg-video-intel-lts-
saucy_2.99.904-0ubuntu2~~6ppa1. The patch is also attached here.
** Package changed: xorg (Ubuntu) =
** Tags added: ci
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to glamor-egl in Ubuntu.
https://bugs.launchpad.net/bugs/1253974
Title:
glamor-egl 0.5.1-0ubuntu6 crashes when running autopilot tests
To manage notifications about this bug go
I believe this was fixed as part of https://lists.ubuntu.com/archives
/precise-changes/2013-November/020703.html
(2:2.21.6-0ubuntu4.3~precise1) - it fixed the Xv video output on my
Haswell and eg. the gstreamer-propeties test.
** Changed in: xorg-server-lts-raring (Ubuntu)
Status:
Confirming, just re-encountered this testing LTS-S enablement stack,
after eventually cleaning the residual config packages via Synaptic.
** Also affects: xorg-lts-raring (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-lts-saucy (Ubuntu)
Importance: Undecided
The qa-radeon-7750 is now again removed from usage so it could be used
manually for debugging.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to glamor-egl in Ubuntu.
https://bugs.launchpad.net/bugs/1253974
Title:
glamor-egl 0.5.1-0ubuntu6
Public bug reported:
Still experiencing crashes:
http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label
=qa-radeon-7750/551/artifact/*zip*/archive.zip
[194156.040] (II) glamor: OpenGL accelerated X.org driver based.
[194156.048] (EE)
[194156.048] (EE) Backtrace:
[194156.048]
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1198472/+attachment/3727018/+files/CoreDump.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Attachment removed: DpkgLog.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1102390/+attachment/3492071/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
I experienced this now on XMir today for the first time, in middle of
light usage.
--
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/1220073
Title:
[snb mesa] GPU lockup
Interestingly there's an Ironlake user there as well who didn't have
problems.
--
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/1164093
Title:
FFe: new upstream release 9.1.1
To manage
*** This bug is a duplicate of bug 1098334 ***
https://bugs.launchpad.net/bugs/1098334
** This bug has been marked a duplicate of bug 1098334
Font corruption in Chromium tab bar using Intel SNA
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Working fine with mobile Sandy Bridge (Asus Zenbook).
--
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/1164093
Title:
FFe: new upstream release 9.1.1
To manage notifications about this bug go
** Description changed:
After enabling Intel SNA the favicons in the omnibar search results are
corrupted.
I've attached a screenshot of the issue with the bug report, note the favicon
of the first result is corrupted.
+
+ This bug is probably the same as bug #1098334, more information may
I can still see the corruption on my Dell Latitude D630 with the reddit
test on latest raring (Mesa 9.0.2, intel 2.21.3). Although, bug
#1098489 is still open anyway and has the same upstream bug linked.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
This bug seems to be fixed for me on raring for Zenboox UX31E (sandy
bridge). Earlier I didn't notice the bug at all since I only rarely used
external monitor. The original reported also had SB, so if someone with
Ivy Bridge still has this problem I think it's better to have a separate
bug.
**
I think it's clearer that the settings package bug is separate from the
driver update one, so de-duplicated this.
** This bug is no longer a duplicate of bug 1064192
[update request] nvidia-173.14.36 adds support for xserver ABI 13 [quantal]
--
You received this bug notification because you
De-duplicated the settings bug #1100994, which is different from this
driver package.
If you have hardware supported by the nvidia 173 driver, please test the
precise-proposed version 173.14.36-0ubuntu0.0.1 in 12.04 plus the
12.04.2 stack as instructed in comment #31 and #32.
** Summary changed:
Please someone with nvidia also test the updated version in precise. The
jockey update got into -updates already, so that part should be ok.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
1 - 100 of 154 matches
Mail list logo
