Public bug reported:
I cannot update becuase of some problem with tird party programs, howeve
I deleted all of them an it is still occurring. It also appears a new
user called LibvirtQuemu.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdrm-intel1 2.4.83-1~16.04.1
Proposed update fixed the issue, thanks.
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
$ apt policy libgl1-mesa-dri
libgl1-mesa-dri:
Installed: 17.2.4-0ubuntu1~16.04.4
Candidate: 17.2.4-0ubuntu1~16.04.4
Version table:
*** 17.2.4-0ubuntu1~16.04.4
On a whim, I just checked in on this with the 20160601 Xenial daily
amd64 ISO (sha1sum e07c8b4df1fc71a487fafb309bd318041a65774f), and
everything works great:
http://cdimages.ubuntu.com/xenial/daily-live/pending/
So seems things are on track for this not being a problem in the 16.04.1
release.
Okay, seems that "Download updates while installing" has no effect with
the Ubiquity version on the 16.04 ISOs.
I filed a bug against Ubiquity for this, would appreciate if someone
could confirm my findings:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232
--
You received this
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
Hmm, I just tried this on Skylake hardware, and "Download updates while
installing" isn't doing the trick.
Could be that "Download updates while installing" is broken on the 16.04
ISOs, or this could be a result of the phased updates done by the Ubuntu
Software Updater and related components that
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
Abhinav,
Sounds like you're encountering a different bug, or perhaps your ISO
file is corrupted. Have you verified the checksum of your download?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
** Description changed:
- Currently it's impossible to install from xenial-desktop-amd64.iso on a
- wide range of hardware with Nvidia GPUs.
+ [Description updated to reflect state of 16.04 release ISO]
- The problem is invalid opcode(s) when using llvmpipe (the software
- opengl fallback,
Just confirmed on Skylake hardware that llvm-toolchain-3.8 from proposed
fixes this issue on Skylake hardware using llvmpipe.
Thanks!
** Changed in: system76
Status: Triaged => Fix Committed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
After further investigating, it seems this bug doesn't effect Haswell-E
after all, sorry about the confusion.
Will continue to report back as we learn more.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
I can confirm that tjaalton's above test packages fix the problem on a
Skylake laptop with an i7-6700 CPU and an Nvidia 970m GPU when using the
nouveau driver.
I installed libllvm3.8_3.8-2ubuntu1.1_amd64.deb from a VT then rebooted,
and now I have working Unity again.
--
You received this bug
Oh, and another bit of information: our laptops all use embedded Display
Port for their connection to the internal screen, and in this case, this
bug always manifests.
So at least in our testing so far, both eDP and DP seem to be effected.
--
You received this bug notification because you are a
So there seems to be a curious pattern with this bug (which might
provide an important hint): on desktop systems with 970 GTX or 980 GTX
cards, this bug always seems to happen when connected to a monitor over
DisplayPort, but does *not* seem to happen when connected to a monitor
over HDMI.
We'll
** Changed in: xorg-server (Ubuntu)
Status: New => Fix Released
--
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/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys
Correction: this is fixed as of 1.18.3-1ubuntu2.
1.18.3-1ubuntu1 still had this problem.
--
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/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host
I'm no longer having this problem as of 1.18.3-1ubuntu1.
--
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/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Okay, I just tried this on an Intel GPU system, and it has the same
problem.
Arrow keys are broken with 1.18.2-2ubuntu0.1, but work fine with
1.18.1-1ubuntu4.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow
keys on qemu guests.
Actually, I'm not sure it breaks the arrow keys on the guest in all
scenarios, but it at least breaks them in the pre-boot menu when trying
to install a qemu VM from an ISO.
For
Likewise, I've been doing extensive testing with mesa 11 from the
x-staging PPA on Haswell, Broadwell, and Skylake hardware, haven't hit
any issues.
Timo, when do you expect mesa 11 to at least hit wily-proposed? I'll
admit it makes me a bit nervous that mesa 11 isn't in wily proper yet :D
--
Quick question: mesa11 depends on libllvm3.7, but libllvm3.7 is still in
universe.
Is there a plan to promote libllvm3.7 to main?
--
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/1484279
Title:
Oops, never mind... I see that libllvm3.7 being in main is mentioned in
the summary, sorry for the noise!
--
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/1484279
Title:
[FFe] Mesa 11.0.0
To
Timo,
Awesome, thanks for the quick fix! I'll test it under qemu as soon as
the builds are finished.
Thanks!
--
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/1484279
Title:
[FFe] Mesa 11.0.0
Timo, 11.0.0~rc2-1ubuntu1~ppa2 seems shiny with Unity under qemu.
Thanks!
--
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/1484279
Title:
[FFe] Mesa 11.0.0
To manage notifications about this bug
I've started testing the mesa 11 rc2 packages here:
https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
One issue I've hit is that with mesa 11 rc2 installed, Unity will no
longer run under qemu (note I'm testing with an amd64 VM, Wily host and
Wily guest).
Attaching the full unit7.log
I spent a lot of time beating on the proposed Trusty nvidia-346
(346.82-0ubuntu0.2) and nvidia-340 (340.76-0ubuntu0.1) packages
yesterday, and things seem solid to me.
Package upgrade/downgrade paths I tested:
331 -- 340
331 -- 346
340 -- 346
346 -- 340
I tested that things work correctly re
+1 on getting this properly fixed in the mesa Depends, but at least
fixing it in the ISO manifest is a huge step forward.
Thanks!
--
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/1479524
Title:
Maarten,
System76 has been using a patched unity-settings-daemon that launches
syndaemon with:
syndaemon -i 0.75 -K -R
This has worked extremely well for us on Trusty (and we have solid
customer survey data confirming that this has greatly improved the user
experience).
However, something
Public bug reported:
I've installed Ubuntu Pangolin 12.04 on a Mac Mini and sometimes use a Sony
HMZ-T1 as the display device. On Ocelot everything worked fine, but since
Pangolin I get no X screen, not even the tty's on F1/F2. When the mac starts
up, I'm getting 720p image output from the
** Attachment added: Xorg.0.log on kernel 3.2
https://bugs.launchpad.net/bugs/998414/+attachment/3142761/+files/kernel-3.2-xorg.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Just adding some info. When I add the nomodeset flag to the kernel
boot parameters, the screen now appears, but fixed in 800x600 mode. I
also get access to the tty's on F1..Fx. It's starting in low-graphics
mode still though and cannot be reconfigured to 720p.
--
You received this bug
I'll try to read this mail August 2nd.
Ik ga proberen dit mailtje 2 augustus te lezen.
Regards/Groeten,
Gerard Krol
Zermelo Roostermakers
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-aiptek in Ubuntu.
https
ger...@gt-laptop:~$ sudo find /proc/ -name EDID -exec cat {} \;
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
not supported
Each
/524288
If I understand the asterix next to the PCI line, the driver is trying
to access the wrong PCI slot.
Is there a way to disable 0:0:2:0?
Thanks
Gerard Taylor
(hope this adds value)
--
nvidia propietary driver fails to load X with geforce 310M
https://bugs.launchpad.net/bugs/643895
You
Got the same problem in debian testing (squeeze) for a while. I tried
removing the wacom and synaptics input drivers and hope this will be
effective. I'll report back about that.
Following workarounds were more or less effective for me: rightclicking
on desktop after Super+D, restarting window
I got this error as well, but I kept messing with my script that changes
the key modifiers and it seems to work for me now. The script is
attached in the hopes that it may help someone else until this is
resolved/better understood.
** Attachment added: remap-keys
Itś ok to close the bug.
Was intalling from scratch 9.10 and updating to 10.4. Worked perfect.
2010/5/28 Bryce Harrington br...@bryceharrington.org
We're closing this bug since it is has been some time with no response from
the original reporter. However, if the issue still exists please
You are using the Aiptek drivers (as you should with your tablet),
marking as invalid for wizardpen.
** Changed in: wizardpen
Status: New = Invalid
--
Aiptek tablet only registers as a mouse in /dev/input
https://bugs.launchpad.net/bugs/361693
You received this bug notification because
It's still bad in Karmic (I'm now using the same Satellite Pro 6050 that
Caroline filed this bug concerning) - this is Xorg Server 1.6.2rc1 with
latest everything.
It's a very crusty old driver. I asked on the xorg mailing list about
hints and tips on fixing it, they suggested faking an EDID
Still broken in Karmic.
I think this is upstream in Xorg, but I also think the Trident driver's
so old that upstream won't care unless someone submits them a good patch
- so if we don't want this broken in Ubuntu we'll have to fix it
ourselves first and submit the patch.
--
ubuntu 8.10 detects
41 matches
Mail list logo
