Another update: I think I've ruled out nvidia-persistenced being started
via udev as the possible culprit.
I tried Trusty with the nvidia-343 driver from the System76 PPA (which
starts nvidia-persistenced with udev)... and I can connect to WiFi just
fine.
I also tried an up-to-date Vivid install
disabled
** Affects: system76
Importance: Critical
Assignee: Jason Gerard DeRose (jderose)
Status: Triaged
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug utopic
** Attachment added: Screenshot from 2014-10
Note I confirmed that WiFi works fine when using nouveau on the same
hardware.
Also I tried a minimal a nvidia-331 install with --no-install-
recommends, just in case the problem is related to any of the optimus
stuff, which isn't needed for System76 hardware... and still no dice.
Installing
Public bug reported:
mkfs.ext4 (and friends) behave differently on Utopic vs Trusty when an
existing filesystem is present on the partition you're formatting.
On Utopic, mkfs.ext4 will prompt you to confirm overwriting of the
existing filesystem, which makes it difficult to use non-interactively
** Description changed:
mkfs.ext4 (and friends) behave differently on Utopic vs Trusty when an
existing filesystem is present on the partition you're formatting.
On Utopic, mkfs.ext4 will prompt you to confirm overwriting of the
existing filesystem, which makes it difficult to use
** Description changed:
mkfs.ext4 (and friends) behave differently on Utopic vs Trusty when an
existing filesystem is present on the partition you're formatting.
On Utopic, mkfs.ext4 will prompt you to confirm overwriting of the
existing filesystem, which makes it difficult to use
** Summary changed:
- mkfs.ext4 and friends need a safer option for non-interactive use when
existing filesystem is present
+ mkfs.ext4 [Utopic+] needs a safer option for non-interactive use when
existing filesystem is present
--
You received this bug notification because you are a member of
I'm not sure whether this can provide any clues, but this Ubiquity oem-
config crash rings a bit similar in that it's only happening when
running under KVM, not when running on hardware:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1374193
Haven't tried it yet on Virtual Box, though.
So is the plan to bring 3.4.1 into Trusty then?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1348954
Title:
update Python3 for trusty
Status in “python3.4” package
101 - 109 of 109 matches
Mail list logo
