** 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.
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
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,
Chris - as I noted in the comment right before yours, the box has been
reimaged to 10.04 and is in use with 10.04. As such, I'm not going to
reimage a working machine that's in use to 12.04 for an irrelevant
exercise in jumping through hoops.
The problem is clearly something introduced by
You really don't appear to have read what's been written already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021069
Title:
[Dell Inspiron Mini 1012] BUG: unable to handle kernel NULL pointer
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/1183125
Title:
Haswell: Ensuring
Public bug reported:
Upgrading from Ubuntu 10.04 to 12.04 produced this error with the
following message: Could not install initramfs-toos. The upgrade will
continue but the 'initramfs-tools' package may not be in a working
state. Please consider submitting a bug report about it. 'subprocess
Removing old kernels solved the problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1207195
Title:
package initramfs-tools 0.99ubuntu13.1 failed to install/upgrade:
ErrorMessage: subprocess
** 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.
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
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
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
Created attachment 79960
picture of rate
See attached picture to see what Reporter means.
For building the chart, I use the RATE function with the guess parameter to
PMT/PV.
This workaround make the RATE function returning expected value.
It is just a workaround, bug is still here and
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
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
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
** 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
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
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.
: (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:
https
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`
** 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:
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',
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
**
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
Right ... how do I find out what the relevant driver to this issue is?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
Toshiba Portege R830-13C no backlight after resume from suspend
Apparently it's in toshiba_acpi, which is presently ... unmaintained!
Fabulous.
There's a workaround here
https://bbs.archlinux.org/viewtopic.php?id=132044 which might help
should anyone with this laptop find this bug report and feel like
working on the problem.
--
You received this bug
Here's the Ubuntu workaround:
http://ubuntuforums.org/showthread.php?t=1550219 This was for the R700.
If something like it can be put into Ubuntu to work around the problem
that upstream have abandoned ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Another bug on the same topic:
https://bugs.launchpad.net/ubuntu/+source/toshset/+bug/644898
The patch for toshset to work was apparently removed by Canonical:
https://lists.ubuntu.com/archives/kernel-team/2010-June/02.html -
that makes this *not* an upstream problem.
--
You received this
Public bug reported:
Toshiba Portege R830-13C: laptop comes back from suspend, but with no
backlight.
I can slightly work around it with the script at
http://www.refreshit.info/2013/03/solved-backlight-problem-after-
suspend.html , but this is less than ideal (and I can't adjust the
backlight
Additional attachments per Debugging information to provide in your bug
report:
** Attachment added: backlight
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595921/+files/backlight
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: acpidump.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595922/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
There must be a better interface than to add each file one at a time
through a painfully slow web interface.
** Attachment added: DSDT.dat
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595923/+files/DSDT.dat
--
You received this bug notification because you are a
** Attachment added: SSDT1.dat
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595926/+files/SSDT1.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: SSDT2.dat
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595928/+files/SSDT2.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: SSDT2.dat
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595929/+files/SSDT2.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: SSDT3.dat
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595930/+files/SSDT3.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: SSDT4.dat
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595931/+files/SSDT4.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: DSDT.dsl
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595932/+files/DSDT.dsl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: fwts
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595933/+files/fwts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
Toshiba
** Attachment added: fwts_method
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595934/+files/fwts_method
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: results.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595935/+files/results.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
** Attachment added: video
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595936/+files/video
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
Toshiba
** Attachment added: dmidecode.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595945/+files/dmidecode.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
** Attachment added: version
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595946/+files/version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
Title:
Toshiba
Rebooted with acpi_backlight=vendor - backlight applet and hotkeys work
fine. Attaching more stuff ...
echo 8 /sys/class/backlight/intel_backlight/brightness does change
the backlight brightness, to dark or near-dark.
** Attachment added: vendorbacklight
** Attachment added: lslabacklight
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159771/+attachment/3595978/+files/lslabacklight
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159771
... suspended, came back and there was still no backlight.
It's taken me half an hour just to file this bug per the list of
requirements. Is there anything else you need?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removed the workaround script, suspended with acpi_backlight=vendor
enabled - came back from suspend with backlight at dark, neither hotkeys
nor applet worked to get it back.
Rebooted with video.use_bios_initial_backlight=0 and hotkeys and applet
both worked just fine. Just
--
You received this
Sadly, it does appear to exist upstream as well - tested with
3.9.0-030900rc4.201303232035 from that directory. Mainline kernel
behaviour is the same: fresh from boot, both the hotkeys and the applet
change the brightness OK; after suspend and resume, the laptop comes
back but the backlight is off
0.4.14 in Raring does not show the crash behaviour. Thanks, and thank
you for stepping in to maintain the package :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056690
Title:
lmms crashed with
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
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
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
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
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
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
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
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:
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
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
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.
Yes, switching first to 12.10 then to the still-supported 10.04 was our
eventual workaround too - since Canonical clearly don't care about a bug
that Canonical clearly introduced into an LTS. This is unfortunate.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
IF you log out and set the session to Ubuntu 2D all these problems will
disappear.
Thanks Christopher Reay
Worked fine with MSI U-100 Wind Notebook with Ubunt 12.04
Best regards,
Gerard Schaafsma
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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
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
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
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:
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]
Appears fixed \o/ Thank you, Lionel! Anyone else?
** 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/1054907
Title:
Fedora has accepted MATE as an alternative desktop, fwiw.
I just installed Ubuntu 10.04 on an old netbook. GNOME2 is hauntingly
usable compared to GNOME3 or Unity (which barely works on the device).
What are the technical barriers to MATE's inclusion in the Ubuntu repos?
--
You received this
*** This bug is a duplicate of bug 1027676 ***
https://bugs.launchpad.net/bugs/1027676
Affects me in Xubuntu on Toshiba Portege R830-13C.
The brightness control in the taskbar works until I suspend. When I come
back from suspend, it doesn't work any more.
The brightness buttons on the
I'm using that locale, yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054907
Title:
xfce4-power-manager crashed with SIGSEGV in vfprintf()
To manage notifications about this bug go to:
Excellent! Any hope of getting those strings fixed for 12.04 and/or
12.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054907
Title:
xfce4-power-manager crashed with SIGSEGV in vfprintf()
To
De-duping this so that there exists a public post people can actually
comment on.
This bug still exists in the release 12.10. Happens every time the power
is plugged in or unplugged.
** This bug is no longer a duplicate of private bug 1037455
--
You received this bug notification because you
Also affected me in Xubuntu 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/182629
Title:
gksu crashed with SIGSEGV in gdk_window_set_opacity()
To manage notifications about this bug go to:
Public bug reported:
winff is a graphical frontend to ffmpeg. It does not have ffmpeg as a
dependency in Ubuntu 12.10.
If you install winff and run it, it complains it can't find ffmpeg or
ffplay.
If you then install ffmpeg, it works.
** Affects: winff (Ubuntu)
Importance: Undecided
I removed the duplicate report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056690
Title:
lmms crashed with SIGABRT in raise()
To manage notifications about this bug go to:
Yes, this duplication appears to be entirely erroneous.
** This bug is no longer a duplicate of private bug 855074
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056690
Title:
lmms crashed with
*** This bug is a duplicate of bug 855074 ***
https://bugs.launchpad.net/bugs/855074
You've just duplicated this to a private bug! How on earth am I supposed
to actually comment there?
(And how old is that bug, that it still has to stay private?)
--
You received this bug notification
*** This bug is a duplicate of bug 1037455 ***
https://bugs.launchpad.net/bugs/1037455
It would be nice if someone went through that bug and made it able to be
made public. *How* many dupes has it got so far?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1037455 ***
https://bugs.launchpad.net/bugs/1037455
This is marked duplicate of an apparently nonexistent bug. Is this a bug
in the bug tracker?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Dear Reinhard
Thanks for looking into this. I wish I could be more helpful here, but I
simply don't have the time to help debug this issue at the moment. If
things eventually calm down at work, I may be able resubmit the bug with a
proper stack trace.
Best regards,
Gerard
On Sep 13, 2012 1:15 AM
Public bug reported:
I run keepassx, close it, then run it again, then close it, etc.
Eventually, something bad happens. I believe that compiz
crashes because all the window borders disappear briefly, and
then all my windows are bunched up on the same workspace.
I am running 12.04 and have made
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
** 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
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,
** 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
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
** 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.
** 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/1044583
I have a report (anecdotal, no kernel.log, sorry) from someone else who
got oopses on recent Ubuntu with a USB Wacom tablet:
http://reddragdiva.dreamwidth.org/582107.html?thread=8104155#cmt8104155
They switched to Linux Mint XFCE and the problem no longer manifested.
Mint XFCE is derived directly
Right, I've tested again. Current Precise kernel, 3.2.0.29, produces the
oops. So the bug is still present.
The interesting thing is that mainline kernel 3.2.0 for Precise, from
the kernel PPA,*does not* show the bug - the Wacom connects just fine.
So it's (a) something Ubuntu has changed from
I have just tried again with 3.2.0-29, first disabling the Broadcom
driver with jockey. I now get the oops in an untainted kernel - this
suggests it is indeed something about the Ubuntu variant.
Realistically, is anyone looking into this problem or going to look into
this problem? I need to know
Public bug reported:
Seems there is perhaps a small packaging issue in Python3.3. I was
trying to install one of my packages in ~/.local for testing and got
this error:
python3.3 setup.py install --user
running install
error: invalid Python installation: unable to open
--
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:
Oleg,
As far as I know, this fix can't be backported. I don't think it's
possible to properly support GstMiniObject because it wasn't designed
with introspection in mind (remember, the GStreamer 0.10 API is almost 7
years old now). I don't believe it's possible to fix this without
breaking the
Same problem affecting me on HP DC7800 with stock 12.04 kernel. Oddly
enough, suspending and resuming worked flawlessly on 10.04. Haven't
tried generic Linus kernel yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
More detail: that's on an HP DC7800 with 12.04 i386 kernel - the 10.04
was amd64 kernel. (No reason for the switch, I just had an i386 ISO to
hand when I was reinstalling.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
601 - 700 of 1534 matches
Mail list logo
