Still no solution, but I've at least (hopefully) eliminated some more
variables.
As I know this problem doesn't currently exist on Vivid, I tried back-
porting `network-manager` and `network-manager-applet` from Vivid, but
no luck... same problem still exists.
And on the off chance that this is
Hmm, after more careful investigation, I think my hunch about
differences in the DBus related process was a dead end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388130
Title:
Cannot connect to
Also tried back-porting `policykit-1` (which needed a back-port of
`glib2.0` and `gobject-introspection`)... still no luck.
But at this point, the delta between Utopic and Vivid is still pretty
small, so I feel this is a promising avenue, at least as far as shot-
gunning goes.
--
You received
This fix seems to be working well. I have test packages here if anyone
wants to test them:
https://launchpad.net/~jderose/+archive/ubuntu/nvidia-test
** Patch added: possible-fix.diff
You'd think it wouldn't be related to the nvidia driver... but it
definitely is.
At System76, we've frequently encountered scattered problems like this.
The nvidia proprietary effects the boot sequence enough (for example, no
kms) that it frequently exposes subtle problems in the overall
Oh, and a little more detail on why I'm certain this is related to the
nvidia proprietary driver...
Part of our QA process after we image a system (before it's shipped to
the customer) is to test WiFi. Since we started shipping Utopic, we've
had 0% failure on systems with Intel graphics.
On
Okay, think I just found a lead in /var/log/upstart/lightdm.log:
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Failed to get D-Bus connection
BTW, it was the Failed to get D-Bus connection bit above that seems
problematic.
Also, looking in syslog, there are some interesting tidbits:
Nov 21 13:17:45 system76-pc NetworkManager[977]: info (wlan0): device state
change: config - need-auth (reason 'none') [50 60 0]
Nov 21 13:17:45
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
Public bug reported:
nvidia-graphics-drivers-331 (331.89-0ubuntu5) will fail to remove/purge
nvidia-331 when /usr/bin/nvidia-persistenced is running.
The reason is the nvidia-331.postrm script hasn't been updated to
reflect that nvidia-persistenced is now started via udev rather than
Upstart
Ah, one thing I had wrong /usr/bin/stop-nvidia-persistenced needs to
be called in nvidia-331.prerm, not nvidia-331.postrm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394348
Title:
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
Okay, figured this out, more or less.
I was mocking DMI information in qemu using:
-smbios file=smbios_type_1.bin
The dump was from actual hardware, but under the seemingly more strict
parsing done either by the newer kernel and/or dmidecode, the system-
product-name ends up with a hugely long
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234542/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234540/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234544/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234541/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234543/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234545/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234546/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234548/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234550/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234552/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234554/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234555/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234556/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234558/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234547/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234553/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234551/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234549/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234559/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234557/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234560/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366351
Title:
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234561/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Logan: gotcha, applogies!
Marco Trevisan mentioned on Google+ that a trace made when the glib and
gtk dbg packages were installed would be helpul, but I probably didn't
submit the trace in the way he intended.
He also said to install compiz and unity dbg packages, but I can't seem
to find them.
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
Public bug reported:
System76 is frequently getting this crash on all our Intel Haswell
(Intel GPU) laptops.
Doesn't look hardware specific, but I don't see any current bug
containing this crash in a recent bug report.
Note this crash doesn't happen on Haswell CPU with Nvidia GPU.
ProblemType:
Colan,
How frequently does this happen, would you say? What percentage of
suspend/resumes encounter this failure?
If you're up for it, the FirmWare Test Suite has a handy way to
repeatedly rest suspend/resume:
https://wiki.ubuntu.com/Kernel/Reference/fwts
Which you can run like this:
sudo
Thanks for the feedback!
System76 has been doing extensive testing internally on Utopic since the
3.16 kernel landed. Thus far we haven't encountered this resume from
suspend issue, but we'll keep a eye out for it!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Is this still happening with the 3.16.0-18-generic kernel (current
Utopic kernel)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332398
Title:
[System76, Inc. Galago UltraPro] suspend/resume
Interestingly, this same crash is happened when using OEM config with a
14.04.1 guest on a 14.10 host.
Normal mode 14.04.1 and 14.10 guests install fine on a 14.10 host, only
the OEM config mode is crashing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
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.
The Help option in the boot menu also seems rather broken (displays
something help-ish for a short time, then automatically boots into the
live environment.
FYI, if anyone needs to work-around this in the mean time, you can do so
with this kernel boot param (hit F6 then ESC to get to the line of
Okay, seems to only happen under KVM, not on physical hardware.
Wondering if this is the same problem discussed here:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1371651
** Information type changed from Private to Public
--
You received this bug notification because you are a
Colin,
If possible, I'd like to have this changed to Private and then I'll fill
in details.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356952
Title:
System76: Guidance on `fwts
@jcollins... interesting, I'll give that a try. Thanks!
I'm installing into a VM (golden image mastering for Sytem76), so vt
switching is a bit less obvious there :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
doko, do you think your build fix is be suitable for a Trusty SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359738
Title:
couchdb-bin doesn't install on ppc64le
To manage notifications about
Thanks, Jorge!
I recall a while back seeing a couchdb build failure on ppc64el, but I
didn't have time to look into it further (an edianness issue in one of
its internal C libraries, I reckon).
I'll try and track it down.
--
You received this bug notification because you are a member of Ubuntu
Ah, here's the log for the failed build:
https://launchpadlibrarian.net/181306900/buildlog_ubuntu-utopic-ppc64el.couchdb_1.6.0-0ubuntu1_FAILEDTOBUILD.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Will see if I change this to private before adding details...
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: fwts 14.03.01-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
** Changed in: couchdb (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/1345672
Title:
Please update to CouchDB 1.6.0
To manage notifications about this bug
So unfortunately the upstream 1.6.0 source tarball annoyingly includes a
number of pre-minified JavaScript files for which the actual source
isn't included, discussed at some length here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752420
And which produce source-is-missing Lintian errors
Okay, after testing over the weekend, CouchDB 1.6.0 seems just as solid
with Erlang 17 as it does with Erlang 16.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1345672
Title:
Please update to
So is the plan to bring 3.4.1 into Trusty then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348954
Title:
update Python3 for trusty
To manage notifications about this bug go to:
Update: oops, now this isn't ready for review...
Erlang 17.1 just landing in Utopic, so I need to do a rebuild test and
then test all my CouchDB consumers against it.
Hopefully no big surprises, as CouchDB 1.6.0 does officially support
Erlang 17.
--
You received this bug notification because
Attaching couchdb_1.5.0-0ubuntu1_to_couchdb_1.6.0-0ubuntu1.debdiff.xz
After beating up on this package for the last week, I feel 1.6.0 is a
solid and rather low risk release.
** Attachment added:
couchdb_1.5.0-0ubuntu1_to_couchdb_1.6.0-0ubuntu1.debdiff.xz
Public bug reported:
This is a bug to track progress on getting CouchDB 1.6.0 into Utopic:
http://www.apache.org/dist/couchdb/notes/1.6.0/apache-couchdb-1.6.0.html
** Affects: couchdb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Branch linked: lp:~jderose/ubuntu/utopic/couchdb/1.6.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1345672
Title:
Please update to CouchDB 1.6.0
To manage notifications about this bug go to:
Initial progress with the CouchDB 1.6.0 package is good overall.
The only issue I've run into is that I can't seem to start CouchDB 1.6
with a CouchDB 1.5 (and earlier) style -hashed- password like:
[admins]
admin = -hashed-HEXDIGEST,SALT
It seems that CouchDB 1.6 will only honor a
Correction to my previous comment:
As they are *hashed* passwords, of course there is no way for CouchDB to
transparently convert a -hashed- password into a -pbkdf2- password prior
to starting the server. At best, CouchDB could write a -pbkdf2- style
hashed password upon the first successful
As far as I can tell, there is no difference between using the proposed
linux-firmware (1.127.5) package vs the stable linux-firmware (1.127.4)
package plus a manually installed /lib/firmware/iwlwifi-7260-8.ucode
file, a combination that has produced favorable results in my previous
testing.
I
Hmm, I guess a verification-needed tag wasn't actually present,
despite the (automated?) comment #69.
Regardless, I added a verification-done tag for good measure :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
CouchDB 1.6.0 test packages are now available in ppa:novacut/daily for
Trusty and Utopic:
https://launchpad.net/~novacut/+archive/ubuntu/daily/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293569
Title:
iwlwifi-7260-8.ucode causes network disconnections
I put 3.13.0-32.56 with the iwlwifi-7260-8.ucode through around 32 hours
of continuous testing on a 7260 WiFi card and encountered zero
disconnects.
I tested with a mix of both sustained high network utilization and long
periods of inactivity, both when running on battery and when running on
AC,
I've been testing the proposed trusty kernel (3.13.0-32.56) with the
iwlwifi-7260-8.ucode firmware, and so far so good:
$ dmesg | grep 22.24.8.0
[2.840202] iwlwifi :04:00.0: loaded firmware version 22.24.8.0 op_mode
iwlmvm
Experience is similar to when I was testing Seth's patched
@jasauders: you'll need to download iwlwifi-7260-ucode-22.24.8.0.tgz
from here:
http://wireless.kernel.org/en/users/Drivers/iwlwifi
Extract the tarball, then copy iwlwifi-7260-8.ucode into /lib/firmware,
then reboot, check dmesg to make sure it loaded the correct version:
$ dmesg | grep iwlwifi
Seth, I noticed that the linux-firmware package in proposed (1.127.3)
doesn't have the 7260 -8 firmware, but does have the 3160 -8 firmware?
Is this intentional?
$ dpkg -L linux-firmware | egrep 7260|3160
/lib/firmware/iwlwifi-3160-8.ucode
/lib/firmware/iwlwifi-7260-7.ucode
Public bug reported:
The current linux-firmware package in proposed (1.127.3) added the -8
firmware for the Intel 3160, but not for Intel 7260.
This seems like it was perhaps a mistake, as the -9 firmware has been
added for both.
$ dpkg -L linux-firmware | egrep 7260|3160
Seth,
Progress report from testing your patched 3.13.0-27 build... I made it
through almost 5 days of continuous use without a disconnect. Even
though I did eventually get a disconnect, it seems to happen far less
frequently with the -8 firmware when combined with the disabled beacon
filtering.
Emmanuel, maybe I'm missing something obvious, but isn't wpasupplicant
2.1 already the newest version?
http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/ChangeLog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: system76
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/1288004
Title:
hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell
HDMI,
** 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/1256655
Title:
[Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
Marked as fixed release for System76 as the 14.04.5 release of the
system76-driver includes a grub line fix for this:
http://bazaar.launchpad.net/~system76-dev/system76-driver/trunk/view/head:/debian/changelog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Marked as fixed release for System76 as the 14.04.5 release of the
system76-driver includes a grub line fix for this:
http://bazaar.launchpad.net/~system76-dev/system76-driver/trunk/view/head:/debian/changelog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Scott,
I've been testing your kernel build with the iwlwifi-7260-8.ucode
firmware (22.24.8.0), and so far so good. Although the particular
problem I've been encountering sometimes takes a day or two to occur, so
I'll let you know how it fairs after a few more days of use.
However, I have
Emmanuel,
I'll test the -9.ucode ASAP. Are there any bits from 3.14 or 3.15 that
should be backported in order for the Ubuntu 3.13 kernel to work best
with the -9.ucode?
System76 customers are experiencing a lot of problems with 7260/3160
cards, and so we're keen on getting -9.ucode in a
Seth,
Just finish building. All I did was bump IWL7260_UCODE_API_MAX,
IWL3160_UCODE_API_MAX to 9.
Loaded -9 firmware correctly, seems to be working fine so far:
[2.936156] iwlwifi :04:00.0: loaded firmware version 23.214.9.0
op_mode
--
You received this bug notification because you
This also affects the `gnome-keyring` package. The System76 imaging
system (Tribble) uses a tar-based approach similar to the MAAS fast-path
installer, and we've had to add a work-around for /usr/bin/gnome-
keyring-daemon on our desktop images:
$ getcap /usr/bin/gnome-keyring-daemon
Stéphane,
Gotcha, thanks for the feedback! So am I correct in thinking that the
--xattrs option is currently broken in tar on 14.04? If so, is there any
chance this could be fixed in an SRU?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Clint,
Ah, thanks for bringing up --xattrs-include=*, I didn't notice this
option!
I agree this is really a bug/misfeature in tar... if I use --xattrs both
when creating and unpacking a tarball, I expect it to just work.
--
You received this bug notification because you are a member of Ubuntu
This also affects the `gnome-keyring` package. The System76 imaging
system (Tribble) uses a tar-based approach similar to the MAAS fast-path
installer, and we've had to add a work-around for /usr/bin/gnome-
keyring-daemon on our desktop images:
$ getcap /usr/bin/gnome-keyring-daemon
Stéphane,
Gotcha, thanks for the feedback! So am I correct in thinking that the
--xattrs option is currently broken in tar on 14.04? If so, is there any
chance this could be fixed in an SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Clint,
Ah, thanks for bringing up --xattrs-include=*, I didn't notice this
option!
I agree this is really a bug/misfeature in tar... if I use --xattrs both
when creating and unpacking a tarball, I expect it to just work.
--
You received this bug notification because you are a member of Ubuntu
What version of Ubuntu are you on, and what CouchDB version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070575
Title:
failed to remove local database when purging the package
To manage
Janos,
You seem to be using an unofficial backport of CouchDB 1.5.0. Where did
you install this from?
The official CouchDB 1.5.0-0ubuntu1 package in Ubuntu 14.04 LTS doesn't
have a chdir in its Upstart script.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Alberto - thanks very much for the explanation, I've always been
confused about that!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287753
Title:
Please update to 331. 49 and/or provide Nvidia
Note this is still present in the final 3.4.0-1 Ubuntu package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264618
Title:
Wrong OSError message from os.rename() when dst is a non-empty
Alberto,
BTW, what's the difference between `nvidia-331` and
`nvidia-331-updates`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287753
Title:
Please update to 331. 49 and/or provide Nvidia
I can confirm this. This will happen if when you boot from the live CD,
you press shift to get the menu, pick your language, and then Install
Ubuntu.
This does not happen if you Try Ubuntu without installing, because in
this case you are passed into the normal desktop session, rather than
the
Merge proposal for a fix here:
https://code.launchpad.net/~jderose/ubiquity/fix-1297312/+merge/212745
I confirmed this fixes the issue with regard to the customer first boot
in OEM mode by manually editing /usr/bin/ubiquity-dm.
I haven't confirmed whether this fixes Install Ubuntu as that would
Public bug reported:
When doing a server install with the latest Trusty daily (2014-03-24) in
OEM mode, the boot hangs during the first boot after the install. Please
see the attached screenshot.
At the time when it hangs, this is the final output on the console:
* Starting End-user
Considering the maintenance burden there would be maintaining two
Python3 versions during the 5 year 14.04 support lifetime, I think this
is a great idea. Even if there are a few Python 3.4 related rough-edges
in some packages that might need SRUs early in 14.04's life, it still
seems to me like
301 - 400 of 804 matches
Mail list logo
