It can be translated. It's software.. everything _can_ be done. It's
just more complex, and not necessarily the best idea given potential
options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
The problem here is lack of entropy in the kernel. A CVE was reported in
the kernel related to low entropy, and the modification prevented the
data from going out. Unfortunately that means any programs at early boot
that attempted to obtain a few bytes of random data would get stuck,
potentially fo
Yeah, we spent a lot of time trying to make the output both compact and
showing command lines. The problem is that once you have more than a few
options, it gets wild and unfriendly as a dump of information after a
typo.
That said, I think we can improve these headings indeed. The output I
see abo
** Changed in: snappy
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/1624322
Title:
console-conf wlan race on pi3
To manage notifications about this bug go to:
https://
*** This bug is a duplicate of bug 169 ***
https://bugs.launchpad.net/bugs/169
We just got a bug report saying gnome-software is actually showing
summaries as a title:
https://forum.snapcraft.io/t/title-summary-pulled-from/469
--
You received this bug notification because you are a
The current behavior was the precise outcome of a very long conversation
we (Mark and I) had in Heidelberg, about the subtle properties of such
updates. We agreed to block devmode => strict refreshes because we could
not get a clear agreement on what was the proper way to treat those
updates. Speci
Per conversation on IRC:
I think it can be closed
18:44:34 snapd indeed operates closer to make -j than it does to apt or deb in
that regard
Those really serialize all steps of the installation, while snapd
goes wild and only rejects known conflicts as you pointed out pedronis
make -j also do
Sorry, it's late here..
> neither the Go community nor the Go core development team (most
important in this case) is not hostile to dynamic linking.
This should read:
> note that neither the Go community nor the Go core development team
(most important in this case) are hostile to dynamic linkin
We've had extensive conversations on this topic elsewhere, and these
were pretty much entirely covered in Jamie's comment #27, which does an
excellent job describing the various perspectives for the same problems.
Thanks for that Jamie.
Just a couple of points that might be useful to add:
[Jamie]
No, please see the discussion above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585806
Title:
snap remove while in /snap/foo/current/... not robust
To manage notifications about this bug go to:
As we discussed today on the channel, we should give a try at using
attributes to produce the final interface we want here. This is
supported for some time, and really not too much work compared making
the interface global.
I suggest something like this (whitespaces => underlines to make
Launchpad
Apparently the message indicates this is about uid 0, which would hint
at it being unrelated to user id mapping.
On a quick search, this issue covers the same problem:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/649917
with the relevant comment from Evan Broder:
Apparently an /e
It is only a serious problem if we find a serious bug about it.
Meanwhile it's an inconvenience which we should try to fix when the
cost-benefit pays off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
As we discussed the last time this came up, yes, that seems fine.
Handing out a token to root that provides an authorization to manipulate
the system is analogous to allowing root itself to be doing removals
without further store information, which we allow.
The necessary infrastructure for that i
Every application may already have an associated desktop file under
meta/gui/.desktop today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661590
Title:
GNOME Software only supports running one app
The bug description is misleading. There's a single name field in snaps
today, and its called "name". Summary is not a name, and description is
not a name. If gnome-software or anything else is using "summary" as a
name, that's a pretty obvious bug that would be great to see fixed.
We can discuss
Another side note: there's no special meaning to the order of commands
in snap.yaml. We can reorder it, and snapcraft can reorder it, so please
don't take it to mean something specific as that'll easily break.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Robert: what do you actually need here? We already support multiple
desktop files, and they already hold metadata. gnome-software can
already inspect to see which of these is available, I believe? What are
the missing pieces?
--
You received this bug notification because you are a member of Ubu
More food for thought on the above note: the desktop file cannot call
the real underlying command by itself! That would break confinement. It
calls the confined binary under /snap/bin instead, which is what the
"command:" attribute specifies. So, necessarily respected.
--
You received this bug no
@Mark: The command is not duplicated. The desktop file will call the
actual command defined in the snap.yaml. It may provide additional
arguments, but those will indeed be _in addition_ to the ones in
snap.yaml.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, but the discussion above also implies that we have multiple naming
fields, and that gnome-software is currently using summary as it
("Currently gnome-software is using sumary or name instead of this
field.").
We should discuss the possibility of another field, per above note, but
let's please
If gnome-software is using summary as a name, it needs to be fixed to
not do that, ASAP.
Whether to have a different field is an unrelated conversation which is
of less urgency than that. We have a name field today, and it should be
used.
--
You received this bug notification because you are a m
Sounds good. We'll add something along those lines to the API.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661590
Title:
GNOME Software only supports running one application from a snap
To manag
Indeed. We need a way to distinguish between lack of purchase and other
reasons for lack of access rights. Along similar lines, would be great
to be able to distinguish between real not found (bogus endpoint) and
semantic content not found (unknown snap).
--
You received this bug notification bec
Almost all of the logged messages are unrelated to snapd. Can you please
show "snap changes" and then "snap change" on the latest refresh
operation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/166260
Indeed. The right fix is probably a trivial change in /etc/zsh/zshenv.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640514
Title:
/snap/bin is not added to the PATH when using zsh
To manage notif
If you install/remove on a loop, this will create changes which are kept
in memory until they are pruned. This happens in the period of three
days for successful ones, and a week for unsuccessful ones (which are
aborted, and later pruned). Eventually we'll need to move to a model
where this data is
Btw, there's a "snap changes" command you can see which changes
currently exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642068
Title:
snapd memory sizes grows huge over time
To manage notif
As mentioned above, unsuccessful changes are aborted after a few days,
and pruned thereafter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642068
Title:
snapd memory sizes grows huge over time
To
@Colin, Sure it definitely needs to be improved. As I said above, this
is just a cheap way to get us going, and the proper fix is a
transactional storage on disk.
@Mark, Yes, we can prune based on number of changes as well. It's not
expensive. That's a good trick to get us going farther.
@John, 2
Did you did into that problem? I don't see the potential leak looking at
the function. All of the arguments other than *ThreadStart are allocated
in the stack, and ts is freed on threadentry which is the function
provided as the start_routine parameter of pthread_create.
What is the actual issue r
@Colin, That's what I understood previously, but thanks for confirming
it. The question was whether you had digged further to see whether that
warning made any sense, or whether you had any further data confirming
the leak to be real. I'll take your response as a no, which is fine.
--
You receive
Once more, unless we have evidence showing otherwise, there were no
leaks before either. Let's please stop pretending otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642068
Title:
snapd me
@Colin, Sorry if it sounds different, but this is not a wish of mine.
It's just about respecting the data we have. Not even Valgrind itself is
reporting this as a leak. It's saying "block possibly lost". Unless we
have either very basic empirical evidence of a leak (e.g. offending code
alone in a l
If it never stops growing, it's obviously a leak.. somewhere! If it
stabilizes after a while, then it's a side effect of Go being a non-
deterministic garbage collected language. Again, data.
If the goal is testing this particular code path, it'd be best to have a
tiny test case exercising it, rat
We should just clear config up from the state when the last revision
from the snap is going away.
That needs to be done in a careful way to take undoing into account.
Eventually we should actually migrate to a model where configuration is
keyed by (snap, revision) instead of simply (snap), so tha
It's in master now.
** Changed in: snapd
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662552
Title:
snaps don't work with NFS home
To manage notificat
Jamie's suggestion seems spot on for the time being. This is really
something for the gadget to expose, and it should be made in an explicit
way. It can be a regular expression as suggested because then you cannot
assign a particular snap plug to a particular serial port anymore.
The upcoming hot-
Sorry, it CANNOT be a regular expression. I wish Launchpad allowed
edits.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
Discussing here:
https://forum.snapcraft.io/t/allow-disabling-system-services-on-ubuntu-
core/531/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504657
Title:
ntp servers should be configurable o
Sorry, by "there" I mean in the forum Zyga mentioned above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677417
Title:
/etc/ld.so.conf.d/conjure-up.conf breaks apt on host system
To manage notifi
The bug is really in the snap. It shouldn't be doing that.
I've provided a longer rationale and a fix proposal there, where we have
more eyes watching.
I would like to close this bug as "Invalid".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yes, it does not fix the installation if it is wrecked. It fixes the
installation from getting wrecked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571721
Title:
Removing when an app is running r
Note that the unlike the bug description states, snapcraft.io is
correct.
It mentions refresh explicitly, and only talks about the install option
when the goal is to install it new.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
You don't need to remove the snap. Just use "refresh" instead.
We need to improve the error message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593213
Title:
snap install --channel=beta not wo
This is not just UX. There's an actual panic in doDisconnect. No UX
issue should result in a panic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599783
Title:
snapd is dead and panic when trying t
virtio_scsi is the obvious one. Not sure if there's anything else
necessary. Might be a good idea to catch up with the cloud image
maintainers and ask.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/160
Also virtio_net, virtio_blk, virtio_pci.. these are builtin in the
standard Ubuntu images, so probably also builtin there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600260
Title:
Support paravi
Thanks André. We'll likely need to do something along those lines, even
including the default system paths for the time being. This sounds like
a bug elsewhere in the system indeed, but we'll fix that separately
rather than waiting for it.
** Changed in: snapd (Ubuntu)
Status: Triaged => In
Looks like a missing conflict statement between snap and snapd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584398
Title:
package snap (not installed) failed to install/upgrade: se încearcă
sup
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
** Changed in: snappy
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603018
Title:
snap create-
We went back and forth on this issue a bit, but I believe the latest
agreement is actually that we want snaps of type "core" indeed. There's
no reason to keep the inconsistency of naming something "os" internally
when everything else refers to those as "core".
We'll need to support snaps with the
We are doing a last minute push to get "ubuntu-core" renamed to "core",
so that the images going out on RTM have the logic in place for testing,
but this is unrelated to the topic here. This specific bug is simply
about having the "core" snap with the "core" type, and this transition
needs to be do
This symptom is fixed in the current master code (and likely in the
latest SRU that is going in now). The umount will happen synchronously
even if there are still processes alive.
That said, please note that the old behavior was not as bad as it sounds
from the description. The snapd daemon is not
The Ubuntu Software team is already working on an alternative for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612783
Title:
snapd requires U1 account to install local packages
To manage no
Public bug reported:
Hello,
As discussed today in the sprint in The Hague, the number of available
loopback devices limits the number of snaps that may be installed on a
given system.
Would it be possible to increase the number of loopback devices to at
least 4096 or 8192, so that we can increas
Thank you very much for the test.
I heard this morning that the limit was 256 based on an error on a test
yesterday, but it must be something else then. I'll go back and ask for
more details.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification b
About where the notion came from, I've heard about this potential
problem pretty much since we considered using the current mount-based
model of snaps. Sounds like there's a wide belief that there is such a
limit, perhaps backed by actual reality:
http://askubuntu.com/questions/499131/how-to-use-m
Let's please keep the original topic as handling space issues in snapd
needs to be improved indeed.
If there's a specific request about ubuntu-image, this needs another
bug.
** Summary changed:
- ubuntu-image should add the regular 5% reserved space for root when creating
filesystem for /writab
Agreed. Let's get that fixed somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585332
Title:
Graphical snaps don't follow the window theme
To manage notifications about this bug go to:
https:
Ironically, the reason your CTRL-C + retry did not work is precisely
because it _is_ robust.
snapd was busy attempting to remove the existing snap for some reason,
and it could not because something in the middle of the process was
still using the old snap files. Once these files stopped being use
Ah, and we should also schedule an immediate retry when we find a
conflict such as the described one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585806
Title:
snap remove while in /snap/foo/curr
Changes may be aborted via "snap abort". It doesn't always work because
something may hang and render snapd unable to stop it, but otherwise it
should work.
We should probably map CTRL-C to an implicit abort.
> In other words, after the Ctrl-C and after I left the directory, snapd
did not "finish
Public bug reported:
The -F option of lsof informs the tool the output format.
For some reason the release in Xenial changed the output format so that
now "f" is always part of the output.
Even despite the obvious breakage that can occur with this change
(that's how I found it), it's really hard
We already do that today for existing interfaces. But I wonder if we
should open up a slightly wider door for name registration on the
session bus specifically (IOW, not system session, not communication),
so that applications can run even if they don't bother about interfaces.
This would unblock a
If it's a blank check, I don't see many advantages over asking for
unity7 itself. Once we want to force the declaration, we can just
introduce the actual interface.
Might also be a good thing because unity7 will eventually be deprecated,
and we might use that timeframe to deprecate the general bin
That's a very good point, Jamie. Let me sleep over that, please, to
ponder whether there's something else entirely that we could do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590679
Title:
Apps
Public bug reported:
Go 1 has been released last week, and it'd be very good to have that
included into Precise since it's the most stable release of Go yet.
Looking at http://packages.qa.debian.org/g/golang.html, it seems that
Debian hasn't been updated yet, so I guess this isn't a sync request
That's fixed in 1.16, thanks to your patch.
** Changed in: editmoin
Status: New => Fix Released
** Changed in: editmoin
Assignee: (unassigned) => Gustavo Niemeyer (niemeyer)
--
cannot pass arguments to EDITOR command
https://bugs.launchpad.net/bugs/610154
You receiv
Omer Akram reports the following pattern, which did not work for me, so
it's unclear whether it's the same issue:
1. open terminal app
2. click inside the app for the OSK to appear
3. click on the 'search' item in the top left corner
What happens:
The OSK hides and you cannot get it back even if
There seems to be two related but independent problems here.
The first one is the original problem reported in the description above:
the snap user directory is inaccessible to the snap itself. This should
indeed be fixed, and there's apparently no reason for us to move this
data out of $HOME that
As posted in juju-dev last night:
Okay, I couldn't resist investigating a bit. I've been looking at the
database dump from earlier today and it's smelling like a simpler bug
in the txn package, and I might have found the cause already.
Here is a quick walkthrough while debugging the problem, to a
Alright, the guess last night was correct, and the candidate fix as
well. I've managed to reproduce the problem by stressing out the
scenario described with 4 concurrent runners running the following two
operations, meanwhile the chaos mechanism injects random slowdowns in
various critical points:
This error should never happen on a healthy database. The only case I've
debugged with such an issue was on a system that had a corrupted
database due to an out-of-space situation.
The reason why this should never happen is clear in the code of the txn
package: before anything is ever done with re
@John, it's definitely a bad idea to have transactions in a capped
collection for that sort of reason, but as far as I can see the _txns_
collection, the one holding the transactions themselves, is not capped.
Having missing logs for a transaction would not cause this issue.
--
You received this
Looking at the logs from Adam that Nate forwarded to me, I can see the
database is being terminated and restarted over and over and over, every
few seconds. Looking at logs around it, looks like at least rsyslogd is
also being re-freshed on the same cadence.
By itself, this should not be an issue,
Public bug reported:
Can we please sync golang r60.1 from Debian unstable into Oneiric
universe?
** Affects: golang (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Changed in: juju
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/828147
Title:
Ensemble branch option needs to allow for distro pkg, ppa, and source
bra
I don't feel like this is a huge issue, but please note that if this is
changed, the message should only be touched in the very specific case
where "juju" is executed without any other arguments. It is really an
error to interrupt whatever juju was going to do and stop to print that
message.
--
Y
The behavior is still not entirely correct. HUD isn't popping up
anymore, but an ALT- sequence that is used as a shortcut (e.g.
ALT-<1-4> to change workspaces) is now being sent to the open
application in addition to change the workspace. This means that every
time I change from the browser (Chrom
Public bug reported:
Can we please sync golang r60.1 from Debian unstable into Oneiric
universe?
The release exception has been debated before the release of Oneiric,
but in this specific case it's even a minor.
** Affects: golang (Ubuntu)
Importance: Undecided
Status: New
--
You
** Description changed:
- Can we please sync golang r60.1 from Debian unstable into Oneiric
+ Can we please sync golang r60.3 from Debian unstable into Oneiric
universe?
The release exception has been debated before the release of Oneiric,
but in this specific case it's even a minor.
**
Public bug reported:
Can we please sync golang r60.3 from Debian unstable into Precise
universe?
The release notes are available here:
http://golang.org/doc/devel/release.html
** Affects: ubuntu
Importance: Undecided
Status: New
** Description changed:
- Can we please sync golang
Bug #896971 tracks the syncing of the same package onto Oneiric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897163
Title:
Please sync golang 1:60.3 (universe) from Debian unstable (main) onto
P
Filed bug #897163 to sync onto Precise.
** Summary changed:
- Please sync golang 1:60.3 (universe) from Debian unstable (main)
+ Please sync golang 1:60.3 (universe) from Debian unstable (main) onto Oneiric
** Changed in: golang (Ubuntu)
Status: Incomplete => New
--
You received this bu
This feels like a Critical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896772
Title:
Oneiric's x64 cloud image [2024] won't boot (wrong kernel, buggy
/etc/fstab, buggy /etc/network/interfac
Please don't sync it without us talking about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/803836
Title:
Please sync golang 1:57.2-1 from Debian unstable (main)
To manage notifications about t
The conversation was a bit different. You said you'd replace it next
week with a different package, and this is also a commitment to *update*
the package on the *stable* release every two months, as I explained.
If these two factors are entirely clear, please do not include this.
There's no reaso
I meant are _not_ entirely clear, sorry.
I'm at the airport at the moment, so I apologize in advance for not
replying quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/803836
Title:
Please syn
This has already been debated with several people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/803836
Title:
Please sync golang 1:57.2-1 from Debian unstable (main)
To manage notifications about
Alright.. please excuse my interruption.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/803836
Title:
Please sync golang 1:57.2-1 from Debian unstable (main)
To manage notifications about this bug g
Public bug reported:
Please sync golang r59 from Debian unstable into Oneiric universe.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Just to understand where the project is going, is there anything
officially seen as an S3 replacement including API compatibility,
Thierry?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829880
Title:
Wow, ok.. I clearly missed the AWS compatibility take there. Thanks
Jay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829880
Title:
object store doesn't like key with '/'
To manage notifications
Public bug reported:
This isn't nice:
ubuntu@ip-10-46-54-97:~$ sudo su -
To launch in a nested session, run: byobu
root@ip-10-46-54-97:~#
** Affects: byobu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
http://open.eucalyptus.com/wiki/EucalyptusStorage_v1.4
"""
Walrus is a storage service included with Eucalyptus that is interface
compatible with Amazon's S3. Walrus allows users to store persistent data,
organized as buckets and objects (see Amazon's S3 Getting Started Guide for
more informati
Public bug reported:
Binary package hint: qemu-kvm
It's been reported in the Go mailing list that lseek is failing on an
amd64 host when emulating arm.
The attached patch was recommended as a possible fix for the problem.
The full conversation may found in the following thread:
http://groups.g
** Patch added: "Patch suggested in the list to fix the problem"
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/721801/+attachment/1859926/+files/x86-64-llseek.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Description changed:
Binary package hint: qemu-kvm
- It's been reported in the Go mailing list that lseek is failing on an
+ It's been reported in the Go mailing list that llseek is failing on an
amd64 host when emulating arm.
The attached patch was recommended as a possible fix for
** Summary changed:
- lseek bug in amd64 host
+ llseek bug in amd64 host
--
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-bu
101 - 200 of 220 matches
Mail list logo
