I haven't had a chance to test this yet on Wily, but it definitely fixed
it on the hardware I tested on with the 14.04.4 daily ISOs leading up to
the 14.04.4 release.
Also, I'm not entirely sure whether updating the packages from the live
environment gives you an accurate test, so that might be
- Original Message -
From: "Earl Malmrose" <1539...@bugs.launchpad.net>
To: ja...@system76.com
Sent: Thursday, February 25, 2016 2:01:31 PM
Subject: [Bug 1539266] Re: 14.04.4: work-around
"SMBIOS-implementations-newer-than-version-2-8..." junk from dmidecode
Are you sure this was fixed?
Earl... ah, I think that TypeError is something different, likely this
bug:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1374193
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1064151
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/912031
For the hardware I did
Mathieu, yes, this does effect Wily as well, which I forgot to mention.
System76 worked around this by backporting dmidecode 3.0 from Xenial and
delivering it in our PPA.
Originally I thought this would be the best approach for Trusty also,
but dmidecode 3.0 seems to have problems when used with
I get the impression this is known and expected, but this problem still
exists in the latest 14.04.4 daily ISOs (which have proposed enabled).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953875
Okay, I tested:
* Normal install on physical hardware with an Haswell laptop (BIOS mode,
SMBIOS older than 2.8)
* Normal install on physical hardware with a Skylake laptop (UEFI mode,
SMBIOS newer than 2.8)
* OEM mode install under qemu (BIOS mode)
* OEM mode install under qemu (UEFI mode)
*
** Branch linked: lp:~jderose/ubiquity/fix-1539266
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539266
Title:
14.04.4: work-around "SMBIOS-implementations-newer-than-
version-2-8..." junk from
Public bug reported:
With dmidecode older than 3.0, certain newer hardware contains a large
warning message in, say, the system-product-name string.
For example, this:
dmidecode --quiet --string system-product-name
Would return something like:
Link,
Your write-up for getting this working on Fedora is great, thanks!
We're considering adding something like this to the system76-daemon
assuming Nvidia isn't going to support this mechanism any more.
Thanks again!
--
You received this bug notification because you are a member of Ubuntu
Tim, thank you very much for cherry picking this into the 4.3 Xenial
tree!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498633
Title:
drivers/net/ethernet/atheros/alx: please add device ID for
This change is now in Linus's 4.4rc4 tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0208e951d55c435137543e12d7ee795c3784713a
Which means it will make it into Xenial, and could be cherry picked into
the Xenial 4.3 branch in the mean time.
--
You received this
** Changed in: system76
Status: New => Triaged
** Changed in: system76
Importance: Undecided => High
** Changed in: system76
Assignee: (unassigned) => Jason Gerard DeRose (jderose)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This change is now in linux-next, should be in 4.4rc2:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=6d5b18ae67b32dd4dcf1c91a172f2424e72ae74c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With nvidia-352 (and for that matter nvidia-346), the
/sys/class/backlight interface is broken.
Writing to /sys/class/backlight/acpi_video0/brightness has no effect,
and reading from it returns a value that does not necessarily reflect
the current brightness.
I don't know
This change has now been accepted into davem's net tree, should
hopefully make its way into Linux 4.4:
https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=0208e951d55c435137543e12d7ee795c3784713a
Big thanks again to the Ubuntu kernel team for carrying this as a sauce
patch in
Oops, sorry for the confusion, haven't been sleeping enough lately :P
I meant to refer to lp:1508766 which I filed about systemd not creating
/etc/machine-id if it's missing:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1508766
Now that /var/lib/dbus/machine-id is a symlink to
Which I guess raises another question... when booting with sysvinit or
Upstart, what should dbus do when /var/lib/dbus/machine-id is a symlink
to /etc/machine-id and the latter doesn't exist?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Simon,
Also, I just tested with an empty /etc/machine-id file... in this case,
systemd does correctly create a write a random machine-id.
Which kinda makes me wonder if systemd is erroneously concluding the
rootfs is mounted read-write when the /etc/machine-id file is missing
altogether.
--
Simon,
I've never really dug into initramfs-tools enough to know for sure, but
my guess has always been that the rootfs got remounted based on what's
in /etc/fstab, which as far as I know is handled by systemd. But perhaps
the initramfs remounts the rootfs read-write, and then it is remounted a
@seb128: yes.
The two are related in that when /var/lib/dbus/machine-id is a symlink,
the act of starting the system dbus instance can't (or wont, I guess)
generate a machine-id (as the path in question is there, just the
symlink target is missing).
And because of lp:1508697, systemd doesn't
Public bug reported:
After clicking "Prepare for shipping to end user" and rebooting,
Ubiquity does not have networking enable.
When on Ethernet, Ubiquity should have networking enabled and should use
it to guess your timezone. When not on Ethernet and you have a WiFi
card, Ubiquity should
** Description changed:
After clicking "Prepare for shipping to end user" and rebooting,
- Ubiquity does not have networking enable.
+ Ubiquity does not have networking enabled.
When on Ethernet, Ubiquity should have networking enabled and should use
it to guess your timezone. When not
Public bug reported:
If you do a Wily desktop install, /var/lib/dbus/machine-id is a symlink
to /etc/machine-id.
If you do a Wily server install, /var/lib/dbus/machine-id is a file
containing the same value as /etc/machine-id.
Minor issue, but still a weird inconsistency between Ubuntu desktop
Side note: when /var/lib/dbus/machine-id is a symlink to /etc/machine-
id, a related issue issue is that systemd fails to create the later when
missing:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1508697
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
If /etc/machine-id is missing at boot, systemd does not create it.
I came across lp:1387090 in which Martin Pitt mentions that it should be
created if missing, but is unsure why this doesn't work.
I'm likewise unsure why it doesn't work, but this bit from dmesg makes
me
** Description changed:
If /etc/machine-id is missing at boot, systemd does not create it.
I came across lp:1387090 in which Martin Pitt mentions that it should be
created if missing, but is unsure why this doesn't work.
I'm likewise unsure why it doesn't work, but this bit from
** Changed in: system76
Status: New => Triaged
** Changed in: system76
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413440
Title:
USB stops working after
confirmed that this bug is fixed in the latest daily 20151002 ISO
(sha1sum 8c9228963e3884183a9ca8a712bb4aa6d66dd65f).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462688
Title:
ubi-timezone
** Changed in: system76
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498633
Title:
drivers/net/ethernet/atheros/alx: please add device ID for Killer
E2400
>From my home IP address, this bug is still present in the 20150924 daily
ISO (sha1sum be7cb9d4afa95402712ee7ebdaac94d4865ecfee).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494361
Title:
Wily:
This bug is no longer present in the latest daily ISOs, marking as
invalid.
Don't know whether this was actually a Ubiquity bug or a bug elsewhere,
but the important thing is it's fixed :)
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification
Public bug reported:
The intel pstate driver is currently quite broken on on Skylake
hardware.
The symptom is that the pstate driver can scale the frequency up, but
wont then scale it back down. So as soon as you hit a decent amount of
CPU load, you get stuck fluctuating in the turbo frequency
Thanks, Tim!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499040
Title:
Wily: Skylake: intel_pstate: fix PCT_TO_HWP macro
To manage notifications about this bug go to:
** Affects: system76
Importance: Critical
Assignee: Jason Gerard DeRose (jderose)
Status: Triaged
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug wily
** Patch added: "Killer-E2400-device-ID.patch"
https://b
Thanks, Tim!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498633
Title:
drivers/net/ethernet/atheros/alx: please add device ID for Killer
E2400
To manage notifications about this bug go to:
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
--
Ah, yes, I meant the lts-wily HWE stack. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497481
Title:
lts-vivid kernel has IWL8000_UCODE_API_MAX=12, but only iwlwifi-
8000C-13.ucode
Seth,
Gotcha, thanks! So is the expectation then that 8260 WiFi cards wont be
usable on Trusty till 14.04.4 (lts-vivid HWE)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497481
Title:
lts-vivid
Public bug reported:
Intel 8260 WiFi cards currently aren't usable on 14.04.3 (with lts-vivid
HWE, 3.19 kernel).
The problem is that in the kernel, iwl-8000.c defines an
IWL8000_UCODE_API_MAX of 12:
#define IWL8000_UCODE_API_MAX 12
But /lib/firmware/iwlwifi-8000C-13.ucode is the only 8000
Andy: oops, didn't refresh the page and see your latest comments before
I posted the above, please ignore.
I just tested the initramfs-tools package in your PPA, confirmed it
works:
1) No more error in dmesg about skl_dmc not being loaded
2) `lsinitramfs -l` shows both the "skl_dmc_ver1.bin"
Andy, I spotted the problem:
Line 120 in /usr/share/initramfs-tools/hook-functions:
cp -a "$firmware" "$target_dir"
`cp -a` copies the symlink itself rather than the target it points to,
so we end up with a broken symlink in initramfs and no actual firmware
file.
The fix that comes to mind
This bug is still present in 20150917 daily ISO (sha1sum
f37615699aaa3852c1e984422a9af4967dd19c47).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494361
Title:
Wily: ubi-timezone consistently
This bug is still present in 20150917 daily ISO (sha1sum
f37615699aaa3852c1e984422a9af4967dd19c47).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493973
Title:
Wily: oem account no loger
Timo,
I didn't realize that this module is being loaded during the initrd
phase before the rootfs is mounted. Mystery solved, I think :D
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496163
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436330
Title:
Network Manager doesn't set metric for local networks any more,
Public bug reported:
On Skylake, the skl_dmc firmware is failing to load. From dmesg:
[0.728803] i915 :00:02.0: Direct firmware load for
i915/skl_dmc_ver1.bin failed with error -2
[0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to
load firmware
Same crash is likewise happening with the last few days of Ubuntu daily
ISOs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495194
Title:
Kubuntu 15.10 daily (12 +13 sept) unable to install
To
Fix seems solid.
`route -n` with up-to-date Vivid:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.17.76.1 0.0.0.0 UG1024 00 eth0
10.17.75.0 0.0.0.0 255.255.255.0 U 0 0
This bug is still present with the 20150911 daily ISO (sha1sum
cdaf9f6390fb50787beceec87bcbd67d9cb53fc6).
Also, confirmed that from my home IP this bug is present when doing BIOS
mode installs and also when doing "normal" user installs (ie, it's not
specific to OEM installs).
--
You received
Attached a screenshot of the qemu window.
** Attachment added: "Screenshot from 2015-09-10 08-35-31.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1494361/+attachment/4460551/+files/Screenshot%20from%202015-09-10%2008-35-31.png
--
You received this bug notification because you
Public bug reported:
When testing the daily ISOs from the last several weeks, ubi-timezone
will consistently crash if I'm testing from home, but will consistently
work if I'm testing from the System76 office. So it seems the problem is
related to the response the backend service is returning for
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe]
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe] Mesa 11.0.0
To manage
Public bug reported:
If doing an OEM mode install using the 20150909 daily ISO (sha1sum
246575e33e3a4c98a4a2d8be85c51e8cefa2e4bd), the "oem" user account is not
setup to login automatically.
This bug is present in ubiquity 2.21.28 (what is present on the above
daily ISO).
ubiquity 2.21.29
** Description changed:
If doing an OEM mode install using the 20150909 daily ISO (sha1sum
246575e33e3a4c98a4a2d8be85c51e8cefa2e4bd), the "oem" user account is not
setup to login automatically.
This bug is present in ubiquity 2.21.28 (what is present on the above
daily ISO).
Karl,
FYI, network-manager should ignore any interfaces defined in
/etc/network/interfaces.
Which is not to say this bug isn't frustrating, just that you should be
able to manually configure things as you wish without removing network-
manager :D
--
You received this bug notification because
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe] Mesa 11.0.0
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe] Mesa 11.0.0
To manage notifications about this bug go
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
Mathieu, so is it possible to use the signed shim with Syslinux then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465396
Title:
Please provide a signed syslinux-efi for secure-boot enabled
Well, part of the reason for using syslinux over grub is our imaging
system still needs to support PXE booting legacy BIOS systems, and
syslinux is what we've used historically for that.
The other part is that back when I last tried using grub as a PXE
bootloader, I wasn't able to get it working,
Mathieu: also, to clarify because I don't think my original description
was clear enough:
We want to have our firmware in UEFI mode with secure boot on by
default, yet we want to avoid having to toggle secure boot off in order
to image, the toggle it back on prior to shipping to the customer.
Mathieu: my goof... I thought the Booting in insecure mode message was
actually coming from the firmware, didn't realize it was coming from
shim. We confirmed that the shim package in proposed indeed fixes this
behaviour.
And this also unblocks us when it comes to having a signed syslinux.
We're
Hmm, interestingly this scan-build error is only happening when I
instrument the build with asan, ubsan.
Although that still doesn't totally explain it as it works fine when
building against 3.4.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I use Clang's scan-build to do static analysis on my Python3 C
extensions during their Debian package build.
Now that Python 3.5rc1 has hit Wily, this is failing when building
against Python 3.5.
But it wasn't failing against 3.5b4, still isn't failing against 3.4.3.
No
One more note, just in case the above was confusing: I've been using
asan, ubsan to instrument the build I run my unit tests against for
quite some time, so this wasn't a recent change that introduced any new
variables.
My hunch is still that Python 3.5rc1 probably introduced this problem.
--
Looks like this has been fixed as of python3-nacl 0.3.0-1.
** Changed in: python-nacl (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479163
Title:
Wily:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479524
Title:
Totem
** Also affects: system76
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479524
Title:
Totem Crashes at launch from missing libwayland-egl
To manage
** Tags added: 14.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479524
Title:
Totem Crashes at launch from missing libwayland-egl
To manage notifications about this bug go to:
I tried a local rebuild with pbuilder and it soft of fixes things.
python3-nacl now includes these files:
_cffi__x2692a599x2d69d42f.cpython-35m-x86_64-linux-gnu.so
_cffi__xec632e8ax2d69d42f.cpython-34m-x86_64-linux-gnu.so
But there still is a concerning warning:
$ python3.5 -c import
Public bug reported:
python-nacl and python3-nacl are currently broken on Wily.
I believe the issue is it needs to be rebuild against python-cffi
1.1.2-1ubuntu2, although I'm not that familiar with CFFI.
This is easy to test with:
$ python3 -c import nacl.public
Which will give you this
Everything checks out for me. Testing I did:
1) Installed couchdb 1.6.0-0ubuntu5, enabled proposed, made sure there
were no issue upgrading to 1.6.0-0ubuntu5.1 and that couchdb was
actually running after the upgrade
2) Made sure `apt-get remove/purge couchdb` works without issue, stops
couchdb
Now that things have been sorted out for Wily (pending sponsorship
still), I'd like to get this fixed in Vivid also, assuming this is an
SRU-able change.
Here's my merge proposal for Vivid:
https://code.launchpad.net/~jderose/ubuntu/vivid/couchdb/fix-1457464/+merge/264437
** Branch linked:
Martin,
Thanks for your recommendations! Much cleaner now.
So do you think I just totally drop Wants=/After=network-online.target?
My rational for this is if (for whatever reason) someone wanted to bind
CouchDB to a specific IP, say on a server with multiple NICs for
internal and external
Martin, thanks for explaining Wants=/After=network-online.target.
I couldn't seem to get couchdb to *not* start based on what I was doing
with network-manager. I tried unchecking Enable Networking in the
indicator and rebooting, couchdb still started. I also tried rebooting
when networking was
*** This bug is a duplicate of bug 1457464 ***
https://bugs.launchpad.net/bugs/1457464
** This bug has been marked a duplicate of bug 1457464
Init fails to start CouchDB after upgrade to Vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Er, I meant and X, of course... obviously we want couchdb in good
shape for the next LTS :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to
in: couchdb (Ubuntu)
Assignee: (unassigned) = Jason Gerard DeRose (jderose)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage
Martin, do you have any thoughts on this? I got the impression you added
the upstream SysV init script back as a quick stop-gap... but do you see
any reason we shouldn't start CouchDB via debian/couchdb.service
instead?
--
You received this bug notification because you are a member of Ubuntu
Making decent progress, this is my current debian/couchdb.service:
[Unit]
Description=the system-wide CouchDB instance
After=network-online.target
[Service]
Type=simple
ExecStartPre=/bin/mkdir -p /run/couchdb
ExecStartPre=/bin/chown couchdb:couchdb /run/couchdb
ExecStart=/bin/su couchdb -c
** Branch linked: lp:~jderose/ubuntu/wily/couchdb/fix-1457464
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage
As with 14.10, this problem isn't happening with Ubuntu MATE 15.04.
Haven't tried the other flavors yet, but I'm guessing that again this is
only happening with Ubuntu/Unity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI, this bug wasn't initially present on the final 15.04 release, but
has since raised it's ugly head again on 15.04.
Not sure what has changed, but from my previous experience, my bet is
still on `unity-greeter`, even though I'm not sure how exactly it's
causing it.
--
You received this bug
Public bug reported:
syslinux-efi is a great option for PXE booting a UEFI-mode client, but
the current package is not signed and so cannot be used when secure-boot
is enable.
It would be very helpful if there was, say, a `syslinux-signed-efi`
package similar to `linux-signed-generic`, etc.
For
@myramenisgone - so the xorg-edgers PPA fixes this for you on 15.04?
I haven't yet filed an upstream bug because I still haven't figured out
whether this is a bug in the kernel vs. xserver-xorg-video-intel, etc.
But if the xorg-edgers PPA fixes this for you on 15.04, that's an
extremely helpful
** Changed in: system76
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel
To manage
** Changed in: system76
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi networks
@sforshee - thank you very much for your explanation, I think I'm
starting to understand the issue better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437913
Title:
8086:095b [Lenovo ThinkPad
@sforshee - I'm trying to better understand the consequences of Ubuntu
currently having an an old regulatory database version, as some
System76 customers are having WiFi problems when connecting to AC
routers with an Intel 7265 and `sudo iw reg set US` seems to fix their
issues.
In particular,
Okay, after some more careful testing,
afcee962b09842d0f4191beb4a2d08251b4c7705 does indeed fix the problem.
I was having some unrelated issues when connecting to 2.4GHz N when too
far away from the access point (lots of WiFi interference here at
System76 HQ).
But the important thing is that
Likewise, I can confirm that 3.19.0-20-genric from proposed does fix
this problem.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel 3.19.0-18 breaks HDMI audio for
I'm not sure what the relevant difference is, but I'm still having
trouble connecting to 2.4GHz N networks with an Intel 3160 when running
3.19.0-20-generic from proposed (when Bluetooth is turned on). In
particular, my 2.4GHz N SSID frequently isn't showing up in the list of
available access
I can confirm this bug on a System76 Kudu Professional (i7-4900MQ).
Booting with 3.19.0-18-generic, I don't get any HDMI option in the
Output tab in the sound settings UI.
Booting with 3.19.0-16-generic, I get an HDMI option and it works fine.
So this is a regression between 3.19.0-16-generic
This bug should also probably be marked as a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457369
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458922
Title:
No sound output
I can confirm this bug on a System76 Kudu Professional (i7-4900MQ).
Booting with 3.19.0-18-generic, I don't get any HDMI option in the
Output tab in the sound settings UI.
Booting with 3.19.0-16-generic, I get an HDMI option and it works fine.
So this is definitely a regression between
@boratko - no problem, thanks for figuring out that it was related to
bluetooth being turned on!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442411
Title:
Intel 3160 wireless card no longer able
For what it's worth, network-manager 0.9.10.0-4ubuntu15.2 seems to fix
the problem for me.
`route -n` with *ubuntu15.1 with both WiFi and Ethernet connections:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.17.75.1
Mostly just confirming what @boratko already shared, plus perhaps a few
new details:
The ingredients needed to reproduce this bug on Vivid:
1) Intel 3160 WiFi card
2) Boot with bluetooth enabled (turn on in the bluetooth indicator and
reboot if needed)
3) Connect to a 2.4 GHz N router
In
101 - 200 of 804 matches
Mail list logo
