saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as Won't Fix.
** Changed in: unity8 (Ubuntu Saucy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: unity8 (Ubuntu)
Status: Confirmed = 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/1219057
Title:
volume up/down key is not working anymore with the new
** No longer affects: touch-preview-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219057
Title:
volume up/down key is not working anymore with the new indicator-sound
To manage
Why do you say Bill that's not the case? It's exactly what happens under
SF now (on Mir this is broken by bug #1233245).
There's a bigger issue here where we want to allow *apps* to get the
volume up/down events to override the default system behavior (like
change the call volume when on a call,
This is not fixed.
per ricmm:
what it means is that the shell needs to mediate the volume keys. the shell
already listens to keys in a few places in Shell.qml, regardless of Mir, the
interface is independent. Mir or SF routing of events happens at a lower layer.
key events are delivered to the
This bug was fixed in the package unity8 -
7.81.3+13.10.20130919.3-0ubuntu1
---
unity8 (7.81.3+13.10.20130919.3-0ubuntu1) saucy; urgency=low
[ Michal Hruby ]
* Add support for music grid renderer to GenericScopeView.
[ Nick Dedekind ]
* Fixed the removal of messaging widget
** Changed in: touch-preview-images
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219057
Title:
volume up/down key is not working anymore with the new
** Tags added: avengers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219057
Title:
volume up/down key is not working anymore with the new indicator-sound
To manage notifications about this bug
** Branch linked: lp:~larsu/unity8/lp1219057
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219057
Title:
volume up/down key is not working anymore with the new indicator-sound
To manage
** Changed in: unity8 (Ubuntu)
Status: New = In Progress
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Lars Uebernickel (larsu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
diwic tvoss, kgunn anyway, my quick question was does it make any sense for
me to write a volume key up/down reader in PulseAudio directly and the answer
is no,
diwic because you want it to be kernel - mir - sound indicator -
pulseaudio instead
diwic right?
tvoss diwic, yup
--
You received
*** This bug is a duplicate of bug 1204434 ***
https://bugs.launchpad.net/bugs/1204434
** This bug has been marked a duplicate of bug 1204434
Volume up/down doesnt work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** This bug is no longer a duplicate of bug 1204434
Volume up/down doesnt work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219057
Title:
volume up/down key is not working anymore with the new
13 matches
Mail list logo