On Tue, Oct 4, 2016 at 6:25 AM Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
No - it's a new machine on which I've installed Yakkety.
Would
Public bug reported:
The wireless card in my Acer V3-372-587T suffers from firmware crashes
regularly (every 5-10mins approx).
$ lsb_release -rd
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
Checking dmesg I see:
$ dmesg | grep ath10k
** Also affects: snappy
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/bugs/1603018
Title:
snap create-user gets bad username
To manage notifications about
Assuming we don't want people to have to change usernames on SSO/LP
(sometimes not even possible, if people have packages published in PPAs
- from memory?), I don't (yet) see any other option than to use the
username with a period from SSO/LP (which is posix compliant [1]).
But can we be sure
Public bug reported:
ubuntu@dev-xenial3:~⟫ sudo snap create-user michael.nel...@canonical.com
error: bad user result: cannot create user michael.nelson: adduser failed with
exit status 1: adduser: Please enter a username matching the regular expression
configured
via the NAME_REGEX[_SYSTEM]
Interestingly, sed is happy to ignore failures on fchown itself:
$ grep chown sed/execute.c -B4 -A2
output_fd = fileno (output_file.fp);
#ifdef HAVE_FCHOWN
/* Try to set both UID and GID, but if that fails,
try to set only the GID. Ignore failure. */
if (fchown
Public bug reported:
Similar to bug 1580018, I'm not sure if the default apparmor profile is
not correct, or possibly this bug is invalid and `sed -i.bak` should be
denied.
AFAICT, the issue is that sed -i.bak tries a chown syscall on the backup
file in the $SNAP_USER_DATA directory, and the
Thanks Jamie. My ubuntu-core was out of date, but updating doesn't
change the symlinks which my snap'd app sees:
michael@dev-xenial2:~/dev/todo.txt⟫ snap list
Name Version Developer
hello-world 6.0 canonical
todo 2.1
ubuntu-core 16.04.0-24 canonical
** Description changed:
- I'm trying to snap a tool which uses awk. I checked the default apparmor
- profile for any snap, and it seems to indicate that awk is installed and
- enabled by the profile, but when checking (via a test snap),
- /usr/bin/awk symlinks to /etc/alternatives/awk symlinks to
Public bug reported:
I'm trying to snap a tool which uses awk. I checked the default apparmor
profile for any snap, and it seems to indicate that awk is installed and
enabled by the profile, but when checking (via a test snap),
/usr/bin/awk symlinks to /etc/alternatives/awk symlinks to
** Changed in: rnr-server
Status: Fix Committed => 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/1564209
Title:
Doesn't recognise own reviews
To manage notifications about this
@fgallina or @kelvin: Can you check the background for these decisions.
I'm not 100% but from memory RnR used to use the SSO (well, LP) username
when it has one for the user (as SSO users don't always have a username,
it depends whether they have an LP account), so I don't know that we can
provide
@francis-regan: I'm still getting issues with Chromium on 16.04, but I
don't see the same (fifo_underrun) error. So it's likely that it was
solved.
What I see now (only just checked the logs) are messages like:
Mar 23 08:27:11 hpmor kernel: [20182.144009] [drm] stuck on render ring
Mar 23
FWIW, I've switched back to Chromium after installing 16.04 on the same
machine, to see if I can reproduce it with the Xenial kernel, and it's
been 4 days without any such lockups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Wed, Jul 8, 2015 at 11:45 PM Chris J Arges 1336...@bugs.launchpad.net
wrote:
Hello Michael, or anyone else affected,
Hi Chris,
Unfortunately I'm not able to reproduce the original problem with the
existing 3.3.8-1ubuntu6.2 (which is different to what I originally used) .
As I mentioned in
On Wed, Jul 8, 2015 at 11:45 PM Chris J Arges 1336...@bugs.launchpad.net
wrote:
Hello Michael, or anyone else affected,
Hi Chris,
Unfortunately I'm not able to reproduce the original problem with the
existing 3.3.8-1ubuntu6.2 (which is different to what I originally used) .
As I mentioned in
Public bug reported:
After updating to vivid, I'm experiencing lockups when visiting certain
pages (not sure if it's flash-enabled) with chromium-browser.
I see the following in the syslog matching the corresponding time (but
don't know whether it's the cause):
May 5 11:11:42 michael-acer
On Fri, Feb 27, 2015 at 1:27 AM, Robie Basak 1336...@bugs.launchpad.net wrote:
We're past feature freeze for Vivid now, so I can't just update to the
latest any more, unless only bugfixes are involved or the release team
grant an exception. If you can give me backported patches though, I can
On Fri, Feb 27, 2015 at 1:27 AM, Robie Basak 1336...@bugs.launchpad.net wrote:
We're past feature freeze for Vivid now, so I can't just update to the
latest any more, unless only bugfixes are involved or the release team
grant an exception. If you can give me backported patches though, I can
Public bug reported:
See the upstream bug report for more details [1], but it seems as though
squid in trusty isn't caching any response which includes a vary header
[2]. The upstream bug was fixed in 3.3.12 [3].
Steps to reproduce:
* Setup an application returning responses with Vary:
Public bug reported:
See the upstream bug report for more details [1], but it seems as though
squid in trusty isn't caching any response which includes a vary header
[2]. The upstream bug was fixed in 3.3.12 [3].
Steps to reproduce:
* Setup an application returning responses with Vary:
** Project changed: software-center-agent = rnr-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318144
Title:
Can't edit reviews
To manage notifications about this bug go to:
The reviews server doesn't (didn't last time I checked [1]) allow a
second review for the same user, returning a 400 not allowed [2].
The other aspect is exactly right - the click reviews server only allows
creating reviews right now. It's trivial to move the other functionality across
from
+1 Thanks mvo. One small but incredible useful feature that 1.5 brings
is the ability to loop over hashes in your playbook. In juju-world, this
enables you to loop over all your relations for a specific interface
very neatly.
[1] http://docs.ansible.com/playbooks_loops.html#looping-over-hashes
On Thu, Feb 6, 2014 at 8:28 PM, John Pugh john.p...@canonical.com wrote:
From #3 above, issue #2 is not present in 13.04 and is present in
13.10+. This would lead one to believe the problem is either in the SCA
or in the software-center client (in one of the USC components).
Hi John. Yes, the
On Fri, Feb 7, 2014 at 9:07 PM, Marco Cimmino cimmino.ma...@gmail.com wrote:
Hi,
yes I think John is right, the problem is: Skype is not interested in
splitting the package into two different packages, this will make the user
confused at our web site download page and we would like to still
On Mon, Feb 10, 2014 at 7:03 PM, Marco Cimmino cimmino.ma...@gmail.com wrote:
Ultimately, I think you'd need two packages - one skype package that
is arch-independent so that you always end up with a 'skype' package
installed, and a skype-bin which installs the i386 binaries
I guess I haven't
Hi Marco,
I think you've already stated this, but this is specifically about the
skype deb package from the skype website correct? That is, the skype
debian package that is in the Ubuntu partner archive [1] seems to behave
as expected (see screenshot).
Perhaps it'd be best if whoever packaged
This issue is fixed on Ubuntu 13.10, evoluion version
3.10.3-0ubuntu3~saucy1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246624
Title:
Reminders from Google are displayed as “This is an event
Fixed released and verified. Thanks everyone for all the info, sorry for
the disruption to reviews.
Before deploy: http://paste.ubuntu.com/6745216/
After deploy: http://paste.ubuntu.com/6749235/
Verified with USC on saucy that searching for skype and viewing details
displays the reviews.
**
** Changed in: rnr-server
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268250
Title:
No reviews displayed (ValueError: time data ... does not match format)
To
Confirmed - it was a result of the upgrade to Django 1.5, the work for
which was done over 6 months ago, but it was only deployed last Friday.
Fixing now and will get deployed asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed here too. Interesting thing I noticed is that when you click
Edit, the event name is in the Summary field. Perhaps Google's
Calendar API changed and has become misaligned with what Evolution
expects.
Would love a fix or workaround!
** Attachment added: Screenshot from 2014-01-12
Surprise :/, here are the steps that I took (perhaps it'll give you some
information showing my mistake):
1) I downloaded and installed all the debs - note missing linux-tools:
https://pastebin.canonical.com/99199/
2) Tested:
$ uname -a
Linux michael-X201EP 3.11.0-12-generic #19~lp1213917v1 SMP
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201310151549 SMP Tue Oct 15
19:50:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213917
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201310091534 SMP Wed Oct 9
19:36:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good.
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201310101545 SMP Thu Oct 10
19:47:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also good (I'd
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201310011456 SMP Tue Oct 1 18:58:54
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213917
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201309181425 SMP Wed Sep 18
18:27:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213917
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201309171602 SMP Tue Sep 17
20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213917
Also, just in case it's relevant in confirming the eventual commit, I've
already mentioned above that after the first suspend and kworker going
to 100%, I can't suspend a second time (I get a complete freeze
requiring a hard power-off), but if I instead try a soft power off
rather than the second
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201309171218 SMP Tue Sep 17
16:20:31 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Bad.
Thanks Joseph
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ uname -a
Linux michael-X201EP 3.10.0-031000rc5-generic #201309121250 SMP Thu Sep 12
16:51:50 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #20130954 SMP Wed Sep 11
15:55:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good - multiple suspend/resume without kworker thread going crazy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201309101033 SMP Tue Sep 10
14:35:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good - multiple suspend/resume without kworker thread going above 5%
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Good - unable to reproduce the issue with:
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201309091524 SMP Mon Sep 9
19:25:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
(Note: I was confused at first by the change in package name and re-
tested the previous (non-rc6) version).
--
You
Thanks Joseph. I hit the issue straight after a suspend with the
3.10.0-031000.201309061430 build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213917
Title:
kworker thread 99.8 - 100% CPU after
On Thu, Aug 29, 2013 at 3:07 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
I built the next test kernel, up to the following commit:
1b375dc30710180c4b88cc59caba6e3481ec5c8b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1213917
Running
$ uname
Blueprint changed by Michael Nelson:
Whiteboard changed:
+ Note: schedule updated to 2013-08-29 14:00..15:00 in Server Cloud 2
+
[USER STORIES]
Rodrigo is a new charm writer and needs tools to solve problems other
authors have already solved in their charms.
Dora is a seasoned
On Tue, Aug 27, 2013 at 9:29 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1213917
Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on your
*** This bug is a duplicate of bug 1213917 ***
https://bugs.launchpad.net/bugs/1213917
** This bug has been marked a duplicate of bug 1213917
kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- kworker thread consuming 99.8 - 100% CPU after update
+ kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@jsalisbury I looked at reporting upstream, and have the email ready,
but I think they expect the bisect to be done also.
I checked the mainline builds and it seems to be when my machine was
updated from 3.10 to 3.11. That is, I can confirm that running
v3.10.9-saucy installed [1] I cannot
On Thu, Aug 22, 2013 at 3:21 AM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Michael Nelson, the next step would be to bisect from Precise to
Quantal, in order to identify the commit that caused this regression.
Could you please do this following
https://wiki.ubuntu.com
On Tue, Aug 20, 2013 at 1:41 PM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Michael Nelson, did this problem not occur in a release prior to Saucy?
Yes - I was not able to suspend/resume with Raring at all (it would wake
immediately). But after updating to Saucy
On Wed, Aug 21, 2013 at 10:03 AM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Michael Nelson, did this problem not occur in a release prior to Raring?
I bought the machine with Ubuntu installed (12.04 I think) and
suspend/resume worked fine. I updated to Quantal
Public bug reported:
After updating today (hadn't updated for a while), my fan won't stop and
top is showing:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
4 root 20 0 00
Public bug reported:
Suspend was working after upgrading to saucy, but failed after updating
today (I hadn't updated for a week or two).
Screen goes blank, but fan and disk keep spinning.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-2-generic 3.11.0-2.5
But works fine after a second reboot.
** Changed in: linux (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/1214071
Title:
[ASUSTeK COMPUTER INC. X201EP]
On Mon, Aug 19, 2013 at 7:27 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
Yes - although since rebooting it's not
...and fails again the third time.
** Changed in: linux (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214071
Title:
[ASUSTeK COMPUTER INC. X201EP]
I have no way currently of knowing, but just ftr, suspend is failing
whenever I try to suspend while kworker thread is near 100% cpu usage
(another bug I reported earlier - bug 1213917).
Actually, I just tested and suspend/resume works fine the first time,
but after the resume bug 1213917 starts
OK, I've just tested 3 times, and this issue seems to be triggered by
suspend/resume, which works fine the first time, but after the first
resume, the kworker CPU consumption starts and the next suspend fails
(bug 1214071).
I'll update to 3.11 and check if I can reproduce it there.
--
You
Updated to 3.11 (note, see circular dependency for linux-headers - is
that normal or am I miss-reading? [1]). It did not fix the problem.
[1] http://paste.ubuntu.com/6004055/
** Tags added: kernel-bug-exists-upstream
** Description changed:
Suspend was working after upgrading to saucy, but
** Description changed:
After updating today (hadn't updated for a while), my fan won't stop and
top is showing:
- PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
- 4 root 20
*** This bug is a duplicate of bug 1028053 ***
https://bugs.launchpad.net/bugs/1028053
** This bug has been marked a duplicate of bug 1028053
running juju status on a non bootstrapped environment gives confusing results
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1028053 ***
https://bugs.launchpad.net/bugs/1028053
** This bug has been marked a duplicate of bug 1028053
running juju status on a non bootstrapped environment gives confusing results
--
You received this bug notification because you are a member of
Thanks Christopher. I updated to the latest bios, and tried again -
resumed perfectly.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@jsalisbury
Sorry - update: After updating the bios to the latest version from Asus,
retrying with the v3.10 kernel resumed fine :) Thanks for your help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After an upgrade to 13.10, I rebooted to find a bunch of error reports
(see screenshot).
Hoping they might go away with another update, I tried that - which
resulted in the same errors [1]
[1] http://paste.ubuntu.com/5927929/
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Public bug reported:
This might be considered a dupe of bug 1157435. I upgrade to saucy for
other reasons, but saw a chance to check if suspend was working with
v3.10 kernal.
The machine suspended, but when I tried to resume, the fan span but the
screen never changed from a blank one :)
[1]
@jsalisbury
I updated to saucy (for other reasons), and tried suspend with the v3.10
kernal. It suspended, but didn't resume. Details on bug 1206625. Thanks
to the team for looking at these!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Steps to reproduce:
1) Start with an existing ubuntu installation [1] with an encrypted home
directory for 'username'
2) Create a bootable USB of 13.10, reboot to installer and choose the upgrade
your existing ubuntu installation (ie. keep the home directory)
3) When
Public bug reported:
Originally reported at http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=712819
I was using salt-minion from the salt PPA which is version 0.15.3, and
everything was fine. I then tried instead to use the 0.15.1 version
from the debian archive (well, a copy of the debian
I'm tagging this with regression-release, but the only last-working
version I can give is the precise version.
Info that I have:
* suspend was working fine with Precise (the OS the machine was purchased
with) and there are no updates at
FWIW, I had also seen this behaviour on 12.10 on my Asus F201E, but not
as often (usually after a day or two it would stop suspending). I
upgraded to 13.04 and so far it's happened every time (only just
rebooted into 13.04), as Alex described. My log is a bit different,
attaching in full.
**
Another point (thanks Anthony): although the sca fix above ensures that
buyers will no longer see a Not available for your version for
multiarch apps, when they click on the Install button:
* for i386 users, everything should work fine
* for amd64 users, they will currently see a Not found
On Wed, Sep 19, 2012 at 2:40 PM, James Westby jw+deb...@jameswestby.net wrote:
On Wed, 19 Sep 2012 08:31:45 -, Michael Nelson
1052...@bugs.launchpad.net wrote:
We also discussed on irc [1] whether sca could potentially provide a
work-around for USC's Reinstall previous purchases
** Also affects: software-center (Ubuntu)
Importance: Undecided
Status: New
** Changed in: software-center-agent
Assignee: Danny Tamez (zematynnad) = Łukasz Czyżykowski
(lukasz-czyzykowski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Alexander, I'll update the bug and see if we can get some of the
pay.ubuntu.com folk to investigate.
** Project changed: software-center-agent = canonical-payment-service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@achuni: To save a bit of back-n-forth-ing, I took a look at the pay
logs and see this:
2012-08-07 19:42:26,642 INFO NEW payment created with id
'36682a0f9f5d9e03da0a651bf832d4fb' for user with openid '' as requested by
consumer 'SCA'.
2012-08-07 19:42:26,870 WARNING Payment
@mvo: I can't see any 404s on softwarecenteragent requesting volleybrawl
:/. Here are the ones I do see: https://pastebin.canonical.com/71628/
Nick's image (thanks Nick!) is showing that, at least when he got that
error, he'd already been redirected through to pay.ubuntu.com (but I
think the
In fact, the blank screen *may* have been due to the same pay bug (bug
1033140). It may be best to check with ricardo if that is now resolved
(as the comment implies it would have been fixed yesterday).
Either way, if Nick or Alexander report back with either the URL
displaying the blank page, or
** Changed in: software-center-agent
Assignee: (unassigned) = Michael Nelson (michael.nelson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020205
Title:
add support for a click_url
Confirming that upgrading to libgtk-3-0 from proposed also allows me to
unlock using the selected layout. Thank-you to all involved!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872701
Title:
Public bug reported:
I seem to get about 1.5 songs out of Rhythm box until it freezes. I
haven't worked out the cause, only that it's consistent, and isn't
related to which music I play (although all my music is ogg).
I didn't watch to see if the following message appeared right when it
freezes,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011504
Title:
Rhythm box freezes consistently
To manage notifications about this bug go to:
** Changed in: software-center-agent
Assignee: (unassigned) = Michael Nelson (michael.nelson)
** Changed in: software-center-agent
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Another possible (?) solution mentioned by lukasz, was if Launchpad
keeps a record of merged accounts (and previous usernames), it could
include the auth details in the htpasswd for the old username as well.
This would mean no changes needed for the client at all.
--
You received this bug
@ricardo: that would be ideal if sca could subscribe to such events.
In the mean-time, sca already (attempts to [1]) update to the current LP
username the next time the user initiates a purchase (which will update
the exported deblines for all purchases). We could use this same call
@chris: I've just checked for the change you landed with r255, and see
it must have been removed at some point.
Is there a way we can have this included for apps.ubuntu.com and
software-center.ubuntu.com (or *.ubuntu.com so we can test the
functionality on our staging servers too)? Currently we
On Fri, May 18, 2012 at 4:35 AM, Natalia Bidart
912...@bugs.launchpad.net wrote:
Re opening in SCA since while brainstorming about this with my office
roommate I realized the template that checkout_complete rendes does
reload the page every a given amount of seconds. Will propose a branch
Hi Natalia - yes, the browser refresh was one of those temporary options
that stuck. The plan was to have the client handle the UI straight after
the purchase was initiated - bug 622732 - initially with the client
polling sca via an API, but ultimately removing the need to poll at all
(plenty of
Hi Jimmy and Gary. This seems to be a repeat of an issue that we also
experienced on Monday - in short, our database server is getting stuck
for period of time, in which the purchases can't be processed. The bug
for the original issue on Monday is bug 996686 - but I'll not yet mark
this as a
@mathieu-tl - Since my comment above (comment 2 on 2012-02-23) I have
not seen the original issue that I reported. There have been a few times
where I thought my machine wasn't going to connect after a resume, but
it always began animating before I'd been able to pkill nm-applet.
Is there info
Hi Fabio! Is it possible that you purchased Irukandji when you were
running Ubuntu Natty or Maverick. It seems it was available for amd64 on
those series, but is only available for i386 for Oneiric and Precise
[1].
There's a comment on the changelog that mentions this decision [2],
which was an
Apparently this has been fixed upstream in gtkplug:
https://bugzilla.gnome.org/show_bug.cgi?id=675167
** Bug watch added: GNOME Bug Tracker #675167
https://bugzilla.gnome.org/show_bug.cgi?id=675167
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Thu, May 3, 2012 at 11:00 AM, Fabio Marconi fabiomarc...@ubuntu.com wrote:
Hello Michael
I've purchased Irukandji yesterday and it was regularry proposed as a normal
software in software center.
I've never purchased this software before, and is the first time that I see
it.
Wow, so
I haven't yet found the above oops (rangpur and satsuma only have pay
oopses until 2012-04-19 currently), but the behaviour sounds as if SCA
initiate the payment via the pay API, then redirected to the payments
checkout URL (ie. HttpResponseRedirect(payment.checkout_url) ), but pay
didn't
So this is the delay from:
2012-04-12 16:36:11,789 - softwarecenter.backend - INFO -
add_repo_add_key_and_install_app()
'private-ppa.launchpad.net/commercial-ppa-uploaders/bobby/ubuntu precise main'
'1024R/75254D99' 'Bobby,bobby'
... (apparently 4 failed attempts before)...
2012-04-12
This happened again today, and it seems it's not related to apt-cache
itself (sorry). It runs slowly and consumes heaps of CPU, but so does
everything else. This time I even saw vim take over 60% cpu while
starting, as well as multiple postgres processes etc., so it seems
related to the system
1 - 100 of 262 matches
Mail list logo
