Public bug reported:
Charged my Meizu ubuntuphone all night. As I woke up this morning power
was still at 2%. After restarting ubuntuphone power was at 98% without
charging any more.
** Affects: indicator-power (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Power
Just to update, I removed the "screen->focusDefaultWindow ();" line and
recompiled compiz and I've been using it for more than a month and this
solved the problem and I could not observe any side effect. So I think
this code could probably be removed at least when using unity.
--
You received thi
** Tags added: patch
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1491542
Title:
libunity ftbfs in wily
Status in libunity package in Ubuntu:
New
The attachment "LLVM fix" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for a
elementaryOS Freya here and this bug still occurs.
Intel Haswell HD4600
kernel 3.16.0-46
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1390625
Title:
m
** Tags added: ftbfs
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1491542
Title:
libunity ftbfs in wily
Status in libunity package in Ubuntu:
New
** Changed in: unity
Status: New => Triaged
** Changed in: unity
Importance: Undecided => Medium
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu)
Status: New => Triaged
** Changed in: unity (Ubuntu)
Importance: Undecid
The attached patch gets past the compilation problems, but the test
suite still fails:
TEST: test-vala... (pid=6684)
/Unit/ResultsSynchronizer: OK
/Unit/IO/AsyncDesktopFile: OK
/Unit/IO/AsyncOpenFromDataDirs:
Public bug reported:
libunity seems to no longer be buildable in wily. This is a problem
because it must be rebuilt for Python 3.5, but it is failing for
unrelated reasons. Here's an excerpt of the build log from a local
build using the current wily source package:
/usr/bin/glib-compile-resourc
I gave this a shot by modifying notify-osd to take device scale into
account. Please give the attached branch a go if you own a hidpi
display.
** Branch linked: lp:~larsu/notify-osd/crisper-on-hidpi
** Changed in: notify-osd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: notify-
A couple of notes:
- this is fixed upstream in GLib already
- watching dbus for the signal is fine, but you should not use dbus to
read the property in the first place. This will result in activation of
the datetime service, which is expensive.
--
You received this bug notification because y
End of bug - please close this one. But please consider making it a
Unity wishlist item. No one I was in contact with could repeat the
problem. I downloaded the latest daily-build of Wily, and tried
everything I could in the live session to break Unity.
I conclude that the problem occurred duri
12 matches
Mail list logo
