I don't know which app you're testing this with, but I suspect it
needs to add a StartupWMClass entry in its .desktop file
On 28 September 2017 at 03:49, Merlijn Sebrechts
wrote:
> ** Tags added: artful
>
> ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Importance: Undecided
>
bamfdaemon is a unity thing, i believe
On 28 September 2017 at 08:24, Merlijn Sebrechts
wrote:
> Easy to test with keepassx, both available in software center (keepassx)
> and as a snap (keepassx-elopio)
>
>
> I can confirm that setting `StartupWMClass=keepassx-elopio_keepassx` in
> `/var/lib/sna
@Merlijn, I don't think there's a way for snapd to know the WMClass of
an app in a snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718942
Title:
running favorited snap shows two icons in Ubuntu
*** This bug is a duplicate of bug 1581713 ***
https://bugs.launchpad.net/bugs/1581713
** This bug has been marked a duplicate of bug 1581713
Ubuntu Software always asks for an Ubuntu Single Sign-On account when
installing or removing a snap package
--
You received this bug notification
Oliver, the argument that ~/snap/ is “not just simply a
configuration dir” isn't particularly good, I think, as the same could
be said about the triple XDG directories for data, config and cache (all
of which default to be hidden).
It is the nature of the confinement that we build that these direc
If we're doing this, we should have a core config as to what locales to
generate. That way on small core devices we just generate what's needed
(often: nothing). On non-core we can make that unsettable and proxy to
whatever the host uses for the 'get' step.
--
You received this bug notification b
Hello again! Sorry for the delay.
With
$ uname -a
Linux flimsy 4.14.0-16-generic #19-Ubuntu SMP Mon Jan 8 17:50:31 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
no dice.
Thank you,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Hello!
With
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ConfigDesignware SMP Tue Feb 6
20:11:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
still no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Hello,
I tried with
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342DESIGNWAREConfigsV2 SMP Wed Feb 7
20:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
and the bug is still there.
Sorry...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
flimsy:~$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ConfigHAVEGENERICRCUGUP SMP Thu Feb
8 16:13:18 UTC x86_64 x86_64 x86_64 GNU/Linux
flimsy:~$
still nope.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748627
Title:
`snap` should provide functionality to show files, which are included
Note that, because snaps are self-contained, the answer to "list files
in installed snap" is simply to find /snap/ Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748627
Title:
`snap` should
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748628
Title:
`snap` sh
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748630
Title:
`snap` sh
Disappointing news I'm afraid: with the bottom half,
Linux flimsy 4.13.0-041300rc1-generic #201707151931LP1745342BottomHalfV1
SMP Fri Feb 9 21:01:09 UTC 20 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen didn't work; with the top half,
Linux flimsy 4.13.0-041300rc1-generic #201707151931LP1745342T
Nice hypothesis! Sadly, with
Linux flimsy 4.15.0-9-generic #10~lp1745342 SMP Mon Feb 12 16:02:41 CST 2018
x86_64 x86_64 x86_64 GNU/Linux
it didn't work, but there's chatter in dmesg about it: Attaching in case it's
useful.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+sour
** Attachment added: "udevadm_info"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5053648/+files/udevadm_info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5053649/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscree
I just tried suspending with the 4.15 kernel, the touchscreen does not
work after resume either.
It does work after resume with the 4.12 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
I put the two configs on http://people.canonical.com/~john/lp1745342/
Including a diff at
http://people.canonical.com/~john/lp1745342/config-4.12.0-13_to_4.13.0-041300rc1.html
HTH,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
With
Linux flimsy 4.15.0-9-generic #10~lp1745342+2 SMP Tue Feb 13 01:54:54
CST 2018 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen didn't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
https://people.canonical.com/~john/lp1745342/4.15.0-9.10~lp1745342+2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful with 4.12 no longer works with 4.
I'll try that in a moment.
For what it's worth I've also got a 7140, running 16.04. That one's
running 4.13.0-32 just fine. If there's anything you want me to try on
it, just let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
[ +0.00] Linux version 4.15.0-9-generic (root@Ryzen) (gcc version
7.2.0 (Ubuntu 7.2.0-18ubuntu2)) #10~lp1745342+3 SMP Wed Feb 14 00:02:23
CST 2018
it worked!
I also suspended it, and it comes back fine from a short suspend; I'll
leave it for a while to see if it also comes back ok from a lon
** Attachment added: "/sys/firmware/acpi/tables/DSDT for 7140"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5054509/+files/DSDT.7140.feuille
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
The 7139 came back from suspend ~20 minutes later just fine.
** Attachment added: "/sys/firmware/acpi/tables/DSDT for 7139"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5054510/+files/DSDT.7139.flimsy
--
You received this bug notification because you are a member
@redx dmesg from after re-plugging the keyboard a few times might help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that worked in artful with 4.12 no longer works with
Kai, I don't use the 7139 with a keyboard dock. I have a keyboard dock
on my 7140, and I can use it with my 7139 to test. I'll do that this
evening and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
I have a Dell Venue 11 Pro 7139, and when I installed artful on it
(before release) it worked fine. Recently (over the xmas break I think
but I'm not sure; this is not a machine I intended to pay too much
attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
ha
$ uname -a
Linux flimsy 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 02:31:37 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
** 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.la
With
john@flimsy:~$ uname -a
Linux flimsy 4.13.0-041300rc1-generic #201707151931 SMP Sat Jul 15 23:32:39 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen does not work.
With
john@flimsy:~$ uname -a
Linux flimsy 4.12.14-041214-generic #201709200843 SMP Wed Sep 20 12:46:23 UTC
2017 x86_6
Linux flimsy 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Title:
touchscreen that
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261443 SMP Fri Jan 26 14:46:56 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745342
Titl
Sorry for the delay :-) was at the doc's.
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261650 SMP Fri Jan 26 16:51:44 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261837 SMP Fri Jan 26 18:39:35 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801302050 SMP Tue Jan 30 21:06:17 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
$ uname -a
Linux flimsy 4.12.0-041200-generic #201801302226 SMP Tue Jan 30 22:28:18 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311413 SMP Wed Jan 31 14:14:46 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
At some point somebody will figure out how to do newton-raphson instead
of bisect.
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311623 SMP Wed Jan 31 16:25:11 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Can't be much further now...
--
You received this bug notification
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311805 SMP Wed Jan 31 18:06:52 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
What's the significance of the "rc5" in this last batch? I would've
thought these were prior to the known-good 4.12 final.
--
You received this bug not
$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311949 SMP Wed Jan 31 19:50:53 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201801312121 SMP Wed Jan 31 21:23:03 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
did _not_ work...
also plymouthd crashed, but that might be unrelated :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I just confirmed that
$ uname -a
Linux flimsy 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
works, and that
$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201801312242 SMP Wed Jan 31 22:44:06 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
does
Happy February!
With
$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201802010156 SMP Thu Feb 1 01:58:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
it didn't work either.
Would it be possible to do a 4.12 final build in the same way you're
doing the bisect builds? I'm starting to worry it's some
With the kernel in the 4.12 directory,
~$ uname -a
Linux flimsy 4.12.0-041200-generic #201802011529 SMP Thu Feb 1 15:34:08 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen did not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
with the one from 4.12/zesty-remote,
~$ uname -a
Linux flimsy 4.12.0-041200-generic #201802011737 SMP Thu Feb 1 17:43:21 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
it works.
I get the impression this is not good news.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Linux flimsy 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
works;
Linux flimsy 4.13.0-10-generic #11-Ubuntu SMP Sun Sep 10 23:39:40 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
does not.
--
You received this bug notification because you are a member of
** Attachment added: "lspci-working.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5047588/+files/lspci-working.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745
Here you go.
** Attachment added: "dmesg-working.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5047589/+files/dmesg-working.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
There seem to be two kernels there, so I tried them both: the
touchscreen didn't work with either of them.
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ConfigChange SMP Fri Feb 2 22:13:41
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
and
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp17453
How do other polkit-using projects do the translation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747272
Title:
Polkit dialogs of snapd are not translatable
To manage notifications about this b
Um.
By removing hal, you're removing users ability to watch Amazon video, or
any other flash drm-based video (the only kind of for-pay commercial
video available on Ubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
Another one...
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
And again.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i68
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
And another.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i
Public bug reported:
There you go.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.12.1-0ubuntu3
Architec
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
Yup.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
.tmp
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
I seem to be getting a lot of these. Not sure if they're all the same
though.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubu
Public bug reported:
still more lockups
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.12.1-0ubuntu3
Arc
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
These are probably all the same bug. How would I know?
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
These are probably all the same bug. How would I know? I don't know.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 3.11.
Public bug reported:
moar lockups
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.12.1-0ubuntu3
Architect
Public bug reported:
these are probably all the same bug
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
These are probably all the same bug. How would I know? I don't know. So
I'll just keep plugging away. Hopefully there's something automated that
will pick this up.
ProblemType: Crash
D
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
These are probably all the same bug. How would I know? I don't know. So
I'll just keep plugging away.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
P
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
Ooooh, look, another one.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.
*** This bug is a duplicate of bug 1222579 ***
https://bugs.launchpad.net/bugs/1222579
Public bug reported:
These are probably all the same bug. How would I know? I don't know. So
I'll just keep plugging away. Hopefully there's something automated that
will pick this up. I hope this isn't rui
Public bug reported:
The latest chromium update is broken.
It has no chrome: no location bar, no bookmarks, you can't open new tabs
by hand. It starts multiple copies of itself (and fails to grab the
profile lock, and fails to realise it, and only complains about not
being able to log in to the a
Despite Ctrl+T not opening a tab, Ctrl+N opens a new window, and this
new window does have all the chrome on it. This new window is also
picked up by the launcher as being chromium, so if I then close the
other chromeless window(s) I have only one chromium icon in the
launcher. I can then go into s
I think I had the temerity of hitting "fullscreen" on a youtube video.
On Tue, Sep 10, 2013 at 12:53 AM, Chris Wilson wrote:
> That's a seriously confused command buffer. Do you remember what you
> were doing at the time?
>
> --
> You received this bug notification because you are subscribed to t
It happens when running from a terminal, yes. Didn't try with
--temp-profile, but did try with starting in a guest session (it looks
the same). By “chrome” I mean the tab bar, the
back/forward/reload/location/preferences bar, the bookmarks bar.
Glad you could reproduce it :-)
On Tue, Sep 10, 2013
** Description changed:
Client should exp backoff reconnect even when connect was successful.
This would protect us from some situations (already arisen: a server bug
that disconnects us hard, after accepting the connection).
+
+ [Impact]
+
+ ubuntu-push-client reattempts connection in a l
** No longer affects: whoopsie
** Summary changed:
- Returns null string during session start
+ Work around whoopsie returning null string during session start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Description changed:
During session startup, the call to whoopsie_identifier_generate will on
some devices leave both buffer and error as NULL.
In particular, running http://pastebin.ubuntu.com/7268480/ on mako (and
presumably on manta) as a *session* upstart job, with the upstart sc
** Description changed:
- Client isn't checking cert; fix before release.
+ [Impact]
+
+ * the client isn't checking the ssl certificate
+
+ [Test Case]
+
+ You need:
+
+ * a computer capable of running the ubuntu push server.
+ * at device using the stable image and that can talk to the comp
** Description changed:
Ubuntu Push client should ensure it only runs once per session.
+
+ [Impact]
+
+ * if two push clients connect with the same id, the last one to connects
disconnects the previous ones
+ * a "live" client will attempt to reconnect
+
+ thus if for whatever reason two
** Description changed:
During session startup, the call to whoopsie_identifier_generate will on
some devices leave both buffer and error as NULL.
In particular, running http://pastebin.ubuntu.com/7268480/ on mako (and
presumably on manta) as a *session* upstart job, with the upstart sc
** Description changed:
Clean flashed my phone and got a popup telling me there was a system update.
It had "[34]" in the notification which seemed spurious.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-push-client 0.2+14.04.20140411-0ubuntu1
Uname: Linux 3.4.0-5-mak
ecided
Assignee: John Lenton (chipaca)
Status: New
** Also affects: ubuntu-push
Importance: Undecided
Status: New
** Changed in: ubuntu-push
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: ubuntu-push (Ubuntu)
Assignee: (unassigned)
** 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/1309231
Title:
Client should exp backoff reconnect even when connect was successfu
** Description changed:
During session startup, the call to whoopsie_identifier_generate will on
some devices leave both buffer and error as NULL.
In particular, running http://pastebin.ubuntu.com/7268480/ on mako (and
presumably on manta) as a *session* upstart job, with the upstart sc
** 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/1309237
Title:
Work around whoopsie returning null string during session start
To
We're shutting down the service over the weekend top stop the battery
drain. Have been tracking this one down all day, but didn't realise
(didn't stop to think!) how bad an impact on cpu usage / battery it
would have.
After the weekend we'll be able to get workarounds in place.
--
You received t
Yikes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
So, there's two client-side bugs. One is that, once a connection is
successful, it resets the exponential back-off mechanism, so the server
dropping the connection hard every time gets it in a spinlock. That's
lp:1309231.
The other is that the whoopsie identifier we get is nil for the first
~10 se
Into a spin, not a spinlock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage notifications about this bug go to:
https://
** Also affects: ubuntu-push
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/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage
** Also affects: ubuntu-push (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-push (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: ubuntu-push (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-push (Ubuntu)
Statu
** Changed in: ubuntu-push
Status: In Progress => Fix Committed
** Also affects: ubuntu-push (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-push (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-push (Ubuntu)
Assignee: (unassigned) =
This has been worked around on the server until we can release a client
that works around the timing issue with the library.
** Changed in: ubuntu-push
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: ubuntu-push
Importance: Undecided => Critical
** Changed in:
h (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: ubuntu-push (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309231
Title:
** Package changed: ubuntu => ubuntu-push (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297969
Title:
Check cert
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
** Changed in: ubuntu-push
Status: In Progress => Fix Committed
** Changed in: ubuntu-push (Ubuntu)
Status: Confirmed => 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/1308145
** Package changed: ubuntu-push-client (Ubuntu) => ubuntu-push (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage n
** 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/1628612
Title:
prefer "core" rather than "ubuntu-core" if installed
To manage not
To test:
* start with an empty state
* snap install ubuntu-core
* snap install hello-world
* hello-world
reset state, repeat with core. If it fails at the "snap install core" step,
your snapd is too old; check that and *start over* (i.e. make sure things still
work with ubuntu-core and the up
** Description changed:
- Thanks to John Lenton for finding this.
+ Thanks to Christian Ehrhardt (paelzer) for finding it, and John Lenton
+ (chipaca) for boiling it down into a digestible mulch.
$ cd /tmp
$ mkdir foo
$ hello-world.sh # from snap install hello-world
bash-4.3$ touch foo
By "nuke the alternatives" I mean, as part of the image build process,
iterate over the alternatives and just point the symlink to the
alternative, instead of to /etc/alternatives/whatever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Can't we nuke alternatives in core? In what situation is it useful to
still have that in the core image?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580018
Title:
ubuntu-core image missing awk
T
401 - 500 of 966 matches
Mail list logo
