** Changed in: zeitgeist (Ubuntu)
Importance: Undecided => Low
** Changed in: zeitgeist (Ubuntu)
Status: Confirmed => In Progress
** Changed in: zeitgeist (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: zeitgeist (Ubuntu Trusty)
Importance: Undecid
> Devices that report a wrong time remaining need to be blacklisted,
just like any other misbehaving hardware device.
Even if this means most devices will need to be blacklisted? Wouldn't it
require an extreme amount of effort to start blacklisting every mouse
that doesn't work with this feature?
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Status: New => In Progress
** Changed in: unity/7.2
Importance: Undecided => Medium
** Changed in: unity/7.2
Assignee: (unassigned) => Stephen M. Webb (bregma)
** Changed in: unity/7.2
** Changed in: systemd-shim (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start u
Just to play devil's advocate a bit here:
The logic taken in this bug (that we should show the device that will
run out of power first) seems perfectly sound, but it makes a very large
assumption, which I suspect will often be untrue: that reporting of time
remaining on mice will always be complet
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-sound (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: d
** Bug watch removed: Ubuntu.com Bugzilla [Obsoleted by Launchpad] #4360
http://bugzilla.ubuntu.com/show_bug.cgi?id=4360
--
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.launc
** Project changed: gnome-utils => gnome-panel
** Package changed: gnome-utils (Ubuntu) => gnome-panel (Ubuntu)
--
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/bu
*** This bug is a duplicate of bug 1275524 ***
https://bugs.launchpad.net/bugs/1275524
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1275524, so is being marked as such.
I've come across this or a similar bug in 14.10 which runs unity 7.3.1.
I'm on a DELL XPS 15 with a 240 dpi screen. This looks best with a
scaling factor of 2 or 2.5. The mouse in most applications (firefox,
terminal) is the proper size but on the desktop and in nautilus windows
it is very tiny.
-
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Status: New => In Progress
** Changed in: unity/7.2
Importance: Undecided => High
** Changed in: unity/7.2
Assignee: (unassigned) => Stephen M. Webb (bregma)
** Changed in: unity/7.2
** Changed in: ubuntu-calendar-app
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1320880
Title:
C
As a workaround, restarting unity should work (i.e. open a terminal or
alt+f2 and launch "unity" or "compiz --replace").
It looks that these settings aren't picked at the right time...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in
** Changed in: media-hub (Ubuntu)
Assignee: (unassigned) => Canonical Phone Foundations
(canonical-phonedations-team)
** No longer affects: media-hub (Ubuntu RTM)
** Changed in: canonical-devices-system-image
Milestone: ww11-2015 => ww13-2015
--
You received this bug notification beca
** Changed in: canonical-devices-system-image
Milestone: ww11-2015 => ww13-2015
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1387691
Title:
Media Player should not be visible
** Changed in: unity
Milestone: 7.3.2 => None
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1423855
Title:
Unity can't show the global m
Also verified Panel opacity works correctly with the Ambiance, Radiance,
and High Contrast themes in the 5 series of Unity.
--
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.launc
Thank you, that worked! However, on reboot it's all back to how it was.
At least I know there's a workaround and don't have to carry on
searching through settings trying to get it to work.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => Fix Released
** Changed in: canonical-devices-system-imag
Verified that Panel transparency is 100% controllable on the Adwaita,
Ambience, Radiance, and High Contrast themes in Unity 7 or later.
Marking as fixed for those series.
** Changed in: unity
Status: Incomplete => Fix Released
** Changed in: unity
Milestone: 7.3.2 => None
--
You rece
Public bug reported:
This issue was raised in discussion with mzanetti, who would like
reminders (created with reminder-app) to be shown in the drop-down menu
with that app's icon.
datetime currently is implemented with "everything is either a clock-app
alarm or a calendar-app event", which is no
** Summary changed:
- i-dt should support ical's "url" property for launching related apps
+ Need a mechanism for specifying what happens when an ical menuitem is clickced
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in
** Changed in: indicator-datetime (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1431384
Title:
nik90, what I mean is that the necessary information you're referring to
would be encoded in the URL that is provided by clock-app (or by the
alarm controls in ubuntu-ui-toollkit, depending on where that logic
lives).
So I'd like to replace the current implentation
('url_dispatch("appid://com.ubun
This might be an IDO bug rather than a datetime bug; I'll need to triage
more to know for certain.
seb128 is able to repeat this for 2015.03.29 in vivid with french locale
larsu's also seeing it for 2015.03.29 in en_US
I'm not able to trigger it on that date, but Laney and I are both seeing
it o
I am extremely surprised and disappointed at how this bug continues to
persist for so long with no hope in sight for a fix. Window shading has
been a fundamental function present in X11 window managers for 20+
years. This feature has critically broken in Unity somewhere between
12.04 and 14.04 ye
Oh of course, the 8th and the 29th are a giveaway aren't they... those
are the dates for US and European DST changes
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs
I'm with you Paarvai. This is a terrible lack of support. I frequently find
bug complaints are passed over
Nooo laddie, not an iThing. It's a Samsung Galaxy.
On Mar 12, 2015 10:55 AM, "Paarvai Naai" wrote:
> I am extremely surprised and disappointed at how this bug continues to
> persist for so
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New => Confirmed
--
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://b
*** This bug is a duplicate of bug 1358238 ***
https://bugs.launchpad.net/bugs/1358238
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1358238, so is being marked as such.
Public bug reported:
A stop gap workaround has been put in place for bug #1313597, but the
proper fix is to use the input::Monitor when it merges. See
https://code.launchpad.net/~3v1n0/unity/lockscreen-grabbing
** Affects: unity
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v
** Information type changed from Private to Public
--
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/1358238
Title:
compiz crashed with signal 5 in _XReply()
32 matches
Mail list logo