> On 2 Aug 2021, at 19:26, Daniel van Vugt <124...@bugs.launchpad.net> wrote:
>
> It might die soon:
>
> https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1840
Fair enough. Only took 14 years. Better late than never… :-)
--
You received this bug notification because you are a member of
The bug that won’t die…
Michi.
> On 2 Aug 2021, at 19:05, Daniel van Vugt <124...@bugs.launchpad.net> wrote:
>
> ** Tags removed: groovy
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/124440
>
> Title:
>
+1!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1621002
Title:
Mediascanner2 test failure on yakkety/{armhf,arm64,ppc64el} with
latest dbus-cpp
To manage notifications
Good catch!
I've seen this in the past due to uninitialised variables. With
optimisation, the compiler gets more aggressive about register re-use,
so a bug can manifest under optimisation when the uninitialised variable
ends up in a register that had a previous value in it. (In debug mode,
the
*** This bug is a duplicate of bug 1609602 ***
https://bugs.launchpad.net/bugs/1609602
Public bug reported:
Happened during dist-upgrade from xenial.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: systemd 231-1
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux
** Changed in: unity-scopes-api (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1481240
Title:
Can't get correct location
Just saw this happen to me with xenial. 100% CPU consumption by yelp.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/872114
Title:
Yelp causes 100% CPU usage
To manage notifications
Scopes-api is innocent here. I just passes the location info it gets
from the shell without touching or caching it. Adding the shell and
location-service to the bug.
** Also affects: location-service (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity-scopes-shell
** Also affects: gstreamer1.0 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gstreamer0.10 (Ubuntu)
** Changed in: gstreamer1.0 (Ubuntu)
Importance: Undecided = Critical
** Also affects: gstreamer (Ubuntu)
Importance: Undecided
Status: New
** Changed
I'm also seeing this on my Nexus 4. Except here, gstreamer hangs and
makes the process unkillable.
Here is a bit of trace from our code:
thumbnailer-service: [06:53:02.902] timeout, state = 2
thumbnailer-service: [06:53:02.902] killing process 12806
thumbnailer-service: [06:53:02.902] calling
** Changed in: gstreamer0.10 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1466273
Title:
gstreamer fails intermittently
To manage
See the linked branch for more discussion. We are back to the original
internal.location setting now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1393438
Title:
Enable
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1393438
Title:
Enable location data string
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) = Michi Henning (michihenning)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1393438
Title:
Enable
OK, the linked branch should fix this. To make the transition easier, I
have *added* a new settings definition called
internal.location.precision. It's an enum with values None,
Approximate, and Precise. The old internal.location boolean setting
is still there. The idea is to make the transition
One more note: while fixing this, I found a bug in our code: for
settings of enum type, if the settings schema was created from a .ini
file, the VariantMap returned by the registry metdata() method returned
the enumerators in a field named displayValues. However, when the
settings schema was
Who the hell decided to close this? Ubuntu is unusable with some brands
of mice. And we go and just put it into the I don't care basket?
Who is in charge of this project? Can we please talk about this?
michi.henn...@canonical.com
--
You received this bug notification because you are a member of
17 matches
Mail list logo
