There are packages available for testing in my PPA:
sudo add-apt-repository ppa:niemeyer/ppa
sudo apt-get upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721801
Title:
llseek bug in amd64 hos
That's awesome, thanks Peter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721801
Title:
llseek bug in amd64 host
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736681
Title:
unexpected keyword argument 'control'
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
Public bug reported:
Binary package hint: exuberant-ctags
The behavior of exuberant-ctags has recently changed so that, when
indexing Python code, imports will be mixed up with definitions. In
practice, it means that when one searches for ClassName, everything
which lists ClassName in an import
I have discussed this with Scott over the phone a while ago, but didn't
write anything in the bug about it. Sorry about that.
So here are the possible outcomes with this bug:
1) I fix the problem myself
2) I guide someone else to fixing the problem
3) The feature is removed from the Image Store
4
Oh, there's another one which I missed:
5) Provide a ramdisk and kernel to images installed via the store.
This would be pretty easy from an Image Store perspective, of course.
--
image-store does not support images without a ramdisk
https://bugs.launchpad.net/bugs/572317
You received this bug
** Changed in: image-store-proxy (Ubuntu Maverick)
Assignee: Gustavo Niemeyer (niemeyer) => (unassigned)
--
image-store does not support images without a ramdisk
https://bugs.launchpad.net/bugs/572317
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: chromium-browser
Chromium as distributed per Ubuntu should not be sending data to Google
unnecessarily:
http://groups.google.com/a/chromium.org/group/chromium-
discuss/browse_thread/thread/574c792f23ab2ffd/8bbf44e8b1d877a0?pli=1#
** Affects: chromium-br
Yes, potentially invalid now, so feel free to close it. I haven't
investigated the code myself. Given that the referred thread is from
today, though, I imagined that updating the code to a version that does
ping home might be in the works, so it felt sensible to increase
awareness over the issue.
I'm not going to be investigating this further myself. It'd be good to
keep an eye on the code going into 10.10 to avoid releasing these
unwanted bits, which are definitely in the upstream project right now.
--
Chromium sends data to Google
https://bugs.launchpad.net/bugs/615969
You received thi
The behavior of snapd seems correct, in the sense different revisions of
the snap may have different licenses. "Rectifying" a license in a way
that future information affect past code seems very bogus in this
context.
With that said, we might have a special case for "unset".
--
You received this
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803834/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803835/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803836/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Public bug reported:
I've been using a Lenovo X12 Detachable Gen 2 model from 2024 [1] to
encode some video files with ffmpeg, and the system becomes completely
unresponsive for as long as the process executes. Although small, this
is a pretty good device hardware wise, and while executing the sys
** Also affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-signed (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Description changed:
I've been using a Lenovo X12 Detachable Gen 2 model from 2024 [1] to
encode some video files with ffmpeg, and the system becomes completely
unresponsive for as long as the process executes. Although small, this
is a pretty good device hardware wise, and while execut
Thanks for the reply, Aaron.
The dmesg.log file is already attached above.
Your ffmpeg example is on the simple side compared to the pipeline that
creates the issue for me, where ffmpeg has multiple inputs and a
pipeline that touches both the GPU and the CPU. For simple things it
works okay here
> 100% usage of Render/3D means copy, vpp or display are stuck,
The issue is certainly related to the 100% render/compute, but this
looks like a symptom and a consequence rather than a cause.
> since multiple inputs are set, could it work when encoding a single
input each time?
Yeah, there are s
Can confirm the fix works here too. Compute jumps to 100%, but system
remains fully usable and the process moves on slowly.
Thanks again for your help, Aaron.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
201 - 220 of 220 matches
Mail list logo
