Colin,
Thank you very much for this bug report. I've encountered some stability
issues with USB3 hard drives and the 3.11.0-13-generic kernel, but your
report makes it sound like it effects all USB devices (at least when
plugged into USB3 ports, it seems).
I probably wont have a chance to dig int
** Branch linked: lp:~jderose/ubuntu/trusty/couchdb/1.5.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254371
Title:
Please update to CouchDB 1.5.0
To manage notifications about this bug go to:
h
Public bug reported:
CouchDB 1.5.0 has been released, a fairly minor update:
http://docs.couchdb.org/en/latest/whatsnew/1.5.html
I see no reason not to have this in Trusty. As CouchDB is now on a
fairly aggressive releases schedule, there is a chance that 1.6.0 will
be released in time for Trust
Public bug reported:
This is a rather odd bug that is only occurring on desktop systems
equipped with an NVidia card in which the customer mistakenly plugged
their monitor into the Intel output on the motherboard when they first
booted their system.
Our steps to reproduce:
1. Image the nvidia sy
Just confirmed the fix on behalf of System76... seems solid, thanks
everyone!
** 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/1237694
Titl
Note I have a hacky (but usable) fix here that System76 will use if need
be:
https://code.launchpad.net/~jderose/ubiquity/fix-1239471
The problem with my fix is it assumes the customer config finishes
successfully. But I think it's workable anyway.
--
You received this bug notification because
Public bug reported:
A regression was introduced in fixing this bug:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231166
As it stands now, the oem user gets deleted every time the oem-config
upstart job gets run (not just when running the end user config, after
clicking "Prepare for s
Problem I just found with the oem-config fix... because that upstart job
always runs, the "oem" user gets deleted the first time you install
2.15.23, first time you boot after doing an OEM mode install.
This fix shows the approach that's needed, but it currently creates
other deal-breaking problem
Another tarball of /var/log. This time I modified oem-config-wrapper so
it will fail if `userdel --force --remove oem` fails, and I booted with
debug-oem-config.
** Attachment added: "log-userdel.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231166/+attachment/3874063/+files/lo
Attached a tarball of /var/log after running the user config (after
clicking "Prepare for shipping to user", rebooting).
** Attachment added: "log.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231166/+attachment/3873989/+files/log.tgz
--
You received this bug notification bec
Not sure if anyone is working on this, but I'm doing my best to track
this down as this bug means System76 can't start shipping Saucy the day
we want to... the day it's released =D
I have zero experience with the Ubiquity code base, but from what I've
dug through so far, my hunch is this regressio
gradeStatus: No upgrade log present (probably fresh install)
** Affects: system76
Importance: Critical
Assignee: Jason Gerard DeRose (jderose)
Status: Triaged
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug saucy ubiquity-2
Thanks, Scott! Not sure if I needed to do a merge proposal still, but here it
is:
https://code.launchpad.net/~jderose/ubuntu/saucy/darktable/merge-1.2.3/+merge/187668
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Gotcha, thanks! So no FFe needed, even when it's a new upstream release?
(Albeit a minor-ish point release.)
Should I change the title of the bug? Anything special I need to do to
get this reviewed and merged?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Attached pbuilder-dist log for building
lp:~jderose/ubuntu/saucy/darktable/merge-1.2.3
** Branch linked: lp:~jderose/ubuntu/saucy/darktable/merge-1.2.3
** Attachment added: "last_operation.log"
https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1231252/+attachment/3841570/+files/last_op
** Changed in: darktable (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/1231252
Title:
[FFE] please merge darktable 1.2.3-1 f
Public bug reported:
Currently on Saucy, darktable 1.2.2-2ubuntu1 crashes[1] any time I try
to export Canon RAW photos.
Although I haven't yet tracked down the cause of this crash, I do know
that merging darktable 1.2.3-1 from Debian testing (or unstable, same
version) fixes it. So I think I can
Thanks, Andrew!
BTW, I didn't do any testing with python-couchdb as I'm not very
familiar with it these days. couchdbkit is another good reverse
dependency to test against.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228197
Title:
darktable crashed with SIGSEGV in _lib_backgroundjobs_destroy()
To manage notificatio
Raymond, thanks for all your detailed help! I'm totally new to ALSA
debugging, so it's taken me a bit to digest what you've already posted,
but here is the output from hda-verb:
$ sudo ./hda-verb /dev/snd/hwC0D0 0x3e 0xf00 0x9
nid = 0x3e, verb = 0xf00, param = 0x9
value = 0x
$ sudo ./hda-
awesome, thanks for the quick fix!
** Changed in: system76-driver
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/1220508
Title:
platform.dist() is not returnin
Gotcha... guess I jumped the gun on the "phase inversion" :P
I attached a screen shot that shows the strange waveform I get in
Audacity when at 100% gain.
I'm waiting to hear back from our ODM on the exact dmics used, and
hopefully I'll get some other useful info as well.
This is new territory f
No, this hasn't happened on Raring, but it didn't previously happen in
Saucy either.
One difference is that the 2nd time testing under Saucy I was connected
to a 2560x1600 monitor via DVI, vs a 1920x1080 monitor via HDMI.
Later this week I'll be able to do more testing and to try and narrow
thing
** Attachment added: "gain-min-broken.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227148/+attachment/3827426/+files/gain-min-broken.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Attachment added: "gain-max-working.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227148/+attachment/3827425/+files/gain-max-working.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
System76 Galago UltraPro (galu1):
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227148
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002978
Title:
[meta-bug] Inverted Internal microph
Public bug reported:
As per this meta-bug:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978
The System76 Galago UltraPro (galu1) has inverted stereo mics. We didn't
catch this in our testing as (interestingly) there is no cancellation
effect when the mic is set at the default g
Public bug reported:
This crash occured while running:
sudo fwts s3 --s3-multiple=500
At one point the resume seemed to hang, so I did a hardware reboot, then
got this Apport crash.
We're in the process of doing our final stability testing to see whether
we can use X.M.P 1833MHz when the memory
*** This bug is a duplicate of bug 1204524 ***
https://bugs.launchpad.net/bugs/1204524
** This bug has been marked a duplicate of bug 1204524
oem temporary user not removed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Marking this as effecting system76-driver also, as we use
platform.dist() to determine the Ubuntu version.
** Also affects: system76-driver
Importance: Undecided
Status: New
** Changed in: system76-driver
Status: New => Triaged
** Changed in: system76-driver
Importance: Undec
Public bug reported:
platform.dist() is currently returning ('debian', 'wheezy/sid', '')
It should return ('Ubuntu', '13.10', 'saucy')
Saucy:
jderose@jgd-gazp7:~$ python3.3
Python 3.3.2+ (default, Jun 5 2013, 10:51:51)
[GCC 4.8.1] on linux
Type "help", "copyright", "credits" or "license" for
Scott, thanks for the Ack!
Assuming someone can figure out why CouchDB 1.2.0 isn't getting
completely terminated during the package upgrade, I think this would be
a great thing to SRU. But I know it's a tricky issue that the Debian
maintainer has battled a lot, and so have I. I'll see what I can c
** Attachment added: "last_operation.log"
https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1212481/+attachment/3798798/+files/last_operation.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Description changed:
- The current CouchDB 1.2.0 package in Saucy is broken and can't be
- installed as it was built against Erlang 15.b.1, and can't be rebuilt
- with the version now in Saucy, Erlang 16.b.1.
+ CouchDB 1.2.0 doesn't work at all with Erlang 16.b.1, so the current
+ CouchDB packa
** Changed in: couchdb (Ubuntu)
Status: In Progress => New
** Summary changed:
- Saucy: CouchDB 1.4.0 needed to work with Erlang 16.b.1
+ [FFE] CouchDB 1.4.0 needed to work with Erlang 16.b.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Micah, is it best to modify this bug or file a new one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212481
Title:
Saucy: CouchDB 1.4.0 needed to work with Erlang 16.b.1
To manage notifications a
Okay, I guess pedantic or not, I have a version that merges 1.4.0-3 from
Debian here:
https://code.launchpad.net/~jderose/ubuntu/saucy/couchdb/1.4.0-from-
debian
This reduces the diff (from Debian) for of a lot of things that don't
have any technical impact (debian/copyright, debian/watch, etc),
** Branch linked: lp:~jderose/ubuntu/saucy/couchdb/1.4.0-from-debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212481
Title:
Saucy: CouchDB 1.4.0 needed to work with Erlang 16.b.1
To manage no
Micah,
I noticed the 1.4.0 package in Debian, and it seems like some of my
packaging work played into it (so I'm glad that my work was perhaps
useful there too).
However, I'd argue the at this point merging from Debian is pedantic and
provides no benefit to Ubuntu users. There is precious little
** Also affects: system76
Importance: Undecided
Status: New
** Changed in: system76
Importance: Undecided => Critical
** Changed in: system76
Status: New => Triaged
** Description changed:
oem-config is currently broken on Saucy. The problem seems to be that
the "oem" us
Public bug reported:
oem-config is currently broken on Saucy. The problem seems to be that
the "oem" user does not get removed, so you end up auto-loging into the
"oem" account every time you boot, even though oem-config seeems to have
sucesfully created the customer's user account.
ProblemType:
Another update: so I went again and split /usr/share/couchdb out into a
new `couchdb-common` package, as that wasn't much work and makes sense
considering how large the data and docs in there have become.
I have builds for Raring and Saucy in the Novacut Daily PPA:
https://launchpad.net/~novacut/+
For what it's worth, I just tested the propose kernel on the System76
desktop products effected by this, and it fixes the problem.
I'm not adding the "verification-done" tag though, since I didn't file
the bug and can't speak to whether this fix is correct for whatever
hardware was originally in q
It's good to know this is being changed upstream. Although I assume
gnome-settings-daemon 3.8 wont be in Saucy, so I'd still like to see my
proposed change in Saucy.
I think the one-line change in ubuntu-settings.gsettings-override is
also pretty darn close to free =)
--
You received this bug no
** Branch linked: lp:~jderose/ubuntu/saucy/ubuntu-settings/2finger
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217166
Title:
"Two finger scroll" should be the default
To manage notifications abo
Public bug reported:
I think it's high time that Ubuntu have two-finger scrolling enabled by
default.
As 12.04 LTS was the last release to offer Unity2D, subsequent releases
all require fairly capable-ish 3D acceleration and fairly modern-ish
hardware (which, BTW, I think was the right move). I t
Using the upstream 1.4.0-rc.1 tarball, I've been working on the UDD
merge against Saucy in this branch:
https://code.launchpad.net/~jderose/ubuntu/saucy/couchdb/1.4.0
I'm still not super UDD savvy, so I'm not 100% confident I didn't goof
anywhere.
The diff of just debian/ looks pretty sane and u
** Branch linked: lp:~jderose/ubuntu/saucy/couchdb/1.4.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212481
Title:
Saucy: CouchDB 1.4.0 needed to work with Erlang 16.b.1
To manage notifications
** Description changed:
On a modern laptop with a large touchpad/clickpad, your palms tend to
brush the touch surface as you type. The problem is that on Ubuntu, this
creates an annoying amount of cursor wiggle. Competing platforms don't
have this problem, so this needs to be improved on U
Note that the diff is mostly UDD accounting in the .pc directory, but
the actual patch is tiny:
http://bazaar.launchpad.net/~jderose/ubuntu/saucy/gnome-settings-daemon
/tune-syndaemon2/view/head:/debian/patches/tune-syndaemon.patch
--
You received this bug notification because you are a member o
3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Thu Aug 22 07:35:33 2013
MarkForUpload: True
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: system76
Importance: High
Ass
Thanks, Jan!
The biggest thing I need is an official CouchDB 1.4.0 release tarball,
ideally before the feature freeze on August 29th :)
Also, if you wouldn't mind looking over my dependencies to see if I'm missing
anything:
http://bazaar.launchpad.net/~jderose/+junk/couchdb/view/head:/debian/con
Quick update: I've now managed to build all the Novacut components
against my latest 1.4.0 package in Saucy. Having all the Novacut unit
tests pass in the build environment makes me pretty confident about the
correctness of the packaging, and the general quality of 1.4.0.
The Novacut Daily PPA now
** Changed 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/1212481
Title:
Saucy: CouchDB 1.4.0 needed to work w
Micah,
Yes, over a year ago I sent a few emails to the debian maintainer, never
heard back. Maybe email isn't the best way to reach him, but I don't
have the time for much process either.
It's not practical for 1.2.x (or 1.3.x) to work with Erlang 16b... it
requires a big, non trivial changes, in
Thanks, Chad! I'll fix the things I already know aren't right, and then
ping you for a review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212481
Title:
Saucy: CouchDB 1.4.0 needed to work with E
** Description changed:
The current CouchDB 1.2.0 package in Saucy is broken and can't be
installed as it was built against Erlang 15.b.1, and can't be rebuilt
with the version now in Saucy, Erlang 16.b.1.
However, the soon to be released CouchDB 1.4.0 does work with Erlang
16.b.1. So
Public bug reported:
The current CouchDB 1.2.0 package in Saucy is broken and can't be
installed as it was built against Erlang 15.b.1, and can't be rebuilt
with the version now in Saucy, Erlang 16.b.1.
However, the soon to be released CouchDB 1.4.0 does work with Erlang
16.b.1. So the options ar
anged in: system76
Assignee: (unassigned) => Jason Gerard DeRose (jderose)
** Changed in: system76
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Also affects: system76
Importance: Undecided
Status: New
** Changed in: system76
Status: New => Triaged
** Changed in: system76
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
We're seeing this issue on various System76 products. A few patterns
we've spotted:
1) It happens more frequently on systems that boot very quickly (fast
CPU, fast SSD)
2) On the same system, it seems to happen more often if in UEFI mode
than in BIOS mode (perhaps because the UEFI boot is just f
Ah, I think this is a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/982889
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173231
Title:
Login screen sometimes fails to ap
Public bug reported:
See attached photo of the screen after the panic.
This kernel panic occurred using Dmedia with two USB3 HDD connected.
Both drives contained Dmedia FileStores, and this happened during
Dmedia's background tasks. I can reliably trigger this panic with Dmedia
(usually happens w
We tested with the 3.9 mainline kernels, and this bug exists there as
well.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1177866
Title:
Sable does not res
** Description changed:
This is a regression from 3.8.0-18, and is present in both 3.8.0-19 and
3.8.0-20.
Resuming from supsend no longer works on the System76 Sable Complete all
in one. When you wake up the system (either with the power button or
- keyboard), the system seems to wake u
A bit more digging... this is more than just the backlight not being
turned on. I installed openssh-server to see if I could SSH into the
system when the screen was black (after attempting to wake up)... no
such luck.
And by watching our DHCP server logs, I've confirmed that this system
never make
Public bug reported:
This is a regression from 3.8.0-18, and is present in both 3.8.0-19 and
3.8.0-20.
Resuming from supsend no longer works on the System76 Sable Complete all
in one. When you wake up the system (either with the power button or
keyboard), the system seems to wake up properly exce
Public bug reported:
Ubiquity always uses the keyboard layout used for the original OEM
install, and is ignoring the keyboard layout the customer chooses during
the first-run config.
Steps to reproduce:
1. Install in OEM mode using keyboard layout FOO
2. During first-run customer config, choose
nee: (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/1161943
Title:
oem-config hangs when removing ubquity
To manage notifications about this bug go to:
Yeah, it doesn't occur for us either as of updates yesterday. We have a
snapshot on which it does occur, so we're going through the package
updates so we can track down what fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Okay, I just tried 2.14.1, but unfortuanately it didn't fix the problem.
`ubiquity-frontend-gtk` now gets removed without any complaints, but
things still hang at "Purging configuration files for Ubiquity..." (see
new screenshot).
So I think the problem wasn't realted to `ubiquity-frontend-gtk` n
Might be a super easy fix. In Raring, it seems `ubiquity-frontend-gtk`
is one of the package present after an OEM mode install. But `ubiquity-
frontend-gtk` is not one of the packages in the remove list in bin/oem-
config-remove-gtk:
def main():
purge = []
for pkg in ('ubiquity', 'ubiquity
** Branch linked: lp:~jderose/ubiquity/fix-1161943
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161943
Title:
oem-config hangs when removing ubquity
To manage notifications about this bug go to:
Public bug reported:
Steps to reproduce:
1) Install in OEM mode
2) Boot system, click "Prep for shipment", shutdown
3) At first customer boot, oem-config will hang trying to remove Ubiquity (see
attached screenshot)
** Affects: system76
Importance: Undecided
Status: New
** Affect
Also incuding a tarball of /var/log at the point of falure. Not sure if
anything useful is in here, but might help.
** Attachment added: "log.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1161943/+attachment/3606506/+files/log.tgz
** Summary changed:
- oem-config fails trying
Christopher,
Please, don't mark this as Invalid... in subsequent 3.8.0 revisions the
behavior has returned. I don't think it was ever truly fixed, I think
there was perhaps some performance regression that prevented this bug
from occuring. I've notice that this bug conistently occurs at high read
I can confirm the same behavior with NFSv3 and overlayfs on Raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039402
Title:
[quantal] overlayfs over r/o NFS mount fails to overwrite existing
Fair enough. To take a different approach, what is blocking vde2 from
being moved into main?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154746
Title:
Please restore --enable-vde
To manage notif
Public bug reported:
If possible, it would be really wonderful to have vde support enabled,
even if qemu-system-* only suggests `vde2`. That way at least someone
could install `vde2` and get proper vde support (I think, anyway).
One problem with it being disabled is that qemu fails silently. A vm
That above bit in debian/rules seems unneeded, and was probably not the
correct fix to whatever issue there was with os.fsync() not being
defined.
Before the sed bit, there is:
#define HAVE_FSYNC 1
#define HAVE_SYNC 1
And after you end up with HAVE_FSYNC being defined twice:
#define HAVE_FSYNC
Hmm, there is this suspicious looking bit in debian/rules line 359:
: # apply workaround for missing os.fsync
sed 's/HAVE_SYNC/HAVE_FSYNC/g' $(1)/pyconfig.h \
> $(1)/pyconfig.h.new
touch -r $(1)/pyconfig.h $(1)/pyconfig.h.new
mv -f $(1)/pyconfig.h.ne
Public bug reported:
os.sync() was added in Python 3.3, but for some reason it's not enabled
in the current Ubuntu package.
I haven't tracked down the details yet, but my hunch is HAVE_SYNC isn't
getting defined for whatever reason.
See Modules/posixmodule.c line 2907:
#ifdef HAVE_SYNC
PyDoc_ST
Public bug reported:
As of gir1.2-appindicator3-0.1_12.10.1daily13.02.13-0ubuntu1, this
doesn't work:
from gi.repository import AppIndicator3
Same under Python2 and Python3, and worked with both with the previous
package version.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gir1.2-appi
I haven't had a chance to test the upstream kernel yet, but I upgraded
my workstation to Raring, and with 3.8.0-5-generic, I can now run my
benchmark without the card-reader being powered off. However, it's
slower than when I use the same card and card-reader plugged into a USB2
port.
With 3.8.0-4
Public bug reported:
Sometime in the past month or so this started happening on raring. Now
and then the fan on this netbook would kick into high gear for no
apparent reason, and often stay that way till I rebooted. Although top
doesn't show anything useful, powertop shows that the audio codec is
Christopher, sure, I can test later this week. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904412
Title:
1033:0194 USB3 card reader hangs/powers off when connected to USB3
port [NEC uPD7
Dmitry, I just built two of the my packages without the
override_dh_sphinxdoc hack, and they built fine.
So this seems to be fixed in 1.1.3+dfsg-5ubuntu1, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Okay, in my case I could work around this with the following target:
override_dh_sphinxdoc:
dh_sphinxdoc -X searchtools.js
I personally still consider this a bug (in either debhelper or sphinx)
as it's unfortunate for every package to require work-arounds for such a
common scenario.
But
Ah, looks like virtualenvwrapper had the same issue, example work-around
here:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/raring/virtualenvwrapper/raring/view/head:/debian/rules
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Oops, that buildlog got deleted when I retried the build. Here's the
buildlog from a failed build from today:
https://launchpadlibrarian.net/123057666/buildlog_ubuntu-
raring-i386.microfiber_12.11.0~bzr162~raring1_FAILEDTOBUILD.txt.gz
--
You received this bug notification because you are a membe
Public bug reported:
On Raring I'm getting build failures like this:
make[1]: Leaving directory `/build/buildd/microfiber-12.11.0~bzr156~raring1'
dh_install
dh_installdocs
dh_sphinxdoc
dh_sphinxdoc: error: unknown JavaScript code:
debian/python3-microfiber-doc/usr/share/doc/python3-micr
FYI, same bug is still present under Quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904412
Title:
1033:0194 USB3 card reader hangs/powers off when connected to USB3
port [NEC uPD720200]
T
** Changed in: couchdb (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037765
Title:
Fatal erl crash no opening log file couch.log
To manage notifications abou
So if you run `couchdb` as a regular user, the process wont have access
to write to the appropriate log and run files. Although starting a per-
user couchdb is a bit of a pain, the problem you're reporting isn't a
bug.
If you're trying to start the system-wide couchdb daemon, do this:
$ sudo /etc
** Attachment added: "pipeline when -bad is installed"
https://bugs.launchpad.net/gstreamer/+bug/1044583/+attachment/3286603/+files/with-bad.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/104458
** Attachment added: "pipeline when -bad is not installed"
https://bugs.launchpad.net/gstreamer/+bug/1044583/+attachment/3286602/+files/without-bad.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=683142
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044583
Title:
h264parse incorrectly reports Canon MOV resolution as 1920x1088
** Bug watch added: GNOME Bug Tracker #683142
https://bugzilla.gnome.org/show_bug.cgi?id=683142
** Also affects: gstreamer via
https://bugzilla.gnome.org/show_bug.cgi?id=683142
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of U
Public bug reported:
If you only have gstreamer1.0-libav installed, you get the correct 1920x1080
resolution.
However, if you also have gstreamer1.0-plugins-bad installed, the h264parse
element gets used, which is broken and results in the incorrect 1920x1088
resolution.
Small test file (21 MB,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037566
Title:
invalid Python installation: unable to open
/usr/lib/python3.3/config-3.3m/Makefile
To manage notifications about this bug go to:
https
401 - 500 of 785 matches
Mail list logo
