Note, I see this bug between my Natty too... between my Natty
netbook and my Gentoo desktop (once the X server upgraded to 1.12.99,
and still with 1.13.0. Not sure why, because this computer just has a
mouse and keyboard, no touch screen or touchpad to provide exciting new
XInput events.)
I guess I just wasn't patient enough; the bug reports I said had hung
for like an hour actually completed. But, now they want me to make a
new bug report rather than be able to attach it to an existing one.
Whoops. Here's the URLs:
Public bug reported:
(First off, I did try to use ubuntu-bug, as well as collecting info with
apport-cli then submitting with ubuntu-bug. The several automated bug
reports I filed just hung up, launchpad claimed it was processing the
report and refreshed for over an hour.)
Running
Since the bug's still open, I did have it reoccur but found the cause
and fixed it. I had switched to the mesa libGL.so.1 to build some
software*, and firefox 44.0 runs with this, but did crash when I went
back to tegra libGL. Long story short, the firefox profile's from my
previous portable and
Please go ahead and close this bug. When I ran the updates today it
reinstalled 44.0+build3-0ubuntu0.14.04.1, and today it's working fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
I wonder if this is a compiler error? Can anyone tell if Chromium for
Ubuntu 14.04 and Chromium for 16.04 have different build flags, or if
their configure scripts detect something different? To me, it seems
like if they have the same or very similar build flags, 16.04 build
breaks but 14.04
I haven't verified this yet, but it looks from the XOrg log like these
systems are booting into dual head (with the SVideo out on head 2),
2128x800 total. That width over 2048 is probably what's causing the
problem. I did "lose the mouse" on one, and suspected a "phantom head."
I went to System
>I haven't verified this yet, but it looks from the XOrg log like these
systems are booting into dual head (with the SVideo out on head 2),
2128x800 total.
Suspicion confirmed, the "phantom" second head was causing causing
compiz to fail due to the 2128 pixel width exceeding the 2048 pixel
Public bug reported:
I went to install Ubuntu (via systemback) onto some Dell D620s, and found
"Gnome Flashback (compiz)" crashes back to login prompt, while "Gnome Flashback
(Metacity)" does not. The attached logs reflect booting up, (attempting to)
log in with Flashback (compiz) then
Suggested patch.
For now, I've been running mesa 20.0.x on the affected system from (21.0.x is
in ubuntu-updates, 20.0.x in base ubuntu repo, so I downgraded to that and
thank goodness for apt-mark hold...) But I can update it straight away to test
any update that comes out.
Thanks!
--Henry
Public bug reported:
A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both
wine and Proton (on an older system that does not have Vulkan..
SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to
fire up OpenGL.
Wine, for Direct3D support it tries to fire up (in
Public bug reported:
PPA affected is https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa
I'll comment up top there's a patch to fix this issue, and a viable
workaround. I decided to file a bug report primarily so if anyone else
comes across this issue they can see the workaround. It's
No problem! I don't still have the D620 (or run 16.04 on anything...).
Side note, Intel GPU drivers sure have come along way since then! Back
in the day, the Intel driver OpenGL was somewhat questionable, it worked
or it didn't with various games and 3D-using stuff see this very bug
report.
Just for perspective on this, I've used Linux since about 1993
(originally Slackware, then Gentoo, then Ubuntu) and recall manually
adding irqtune to my system in the distant past.
When irqtune was originally developed, it was common to run XT-PIC, all
interrupts were went to CPU 0, period. When
14 matches
Mail list logo
