there are various forum and askubuntu threads about this issue already
as well:
https://forum.snapcraft.io/t/ui-glitch-after-recent-update/15133
https://forum.snapcraft.io/t/some-snaps-app-have-weird-looking-window-
control-and-fonts/17859
https://askubuntu.com/q/1206868/66509
*** This bug is a duplicate of bug 1708569 ***
https://bugs.launchpad.net/bugs/1708569
** This bug has been marked a duplicate of bug 1708569
Installer on latest image fails to create a complete $HOME directory
--
You received this bug notification because you are a member of DX
it was closed as invalid for indicator-power because the problem is in
powerd ... so a new task against powerd was opened
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1483427
hmm, this bug seems ot have been dragged away from the actual topic by
the audience, please note that this bug talks about phone and tablet
installs (as the "Canonical System Image" task implies) where we use a
reduced and slightly different installation compared to desktops (and
definitely no
if you have issues with evolution-data-server on a desktop install your
chances are way higher to have some desktop people look at it if you
file a new bug.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Public bug reported:
it recently started for me that i do not get any notifications for
calendar events anymore and random entries in the indicator are missing
while they show up in the calendar app.
http://i.imgur.com/6GbGpHy.png the snappy meetings in this calendar screenshot
... are
i assume this is for pocket desktop which uses the phone UI but in
desktop context by default
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
If we would have a volume-slider Qt/QML element that allows you to pick the
role it manages you could have a volume control in the app (like i described in
bug #1389761) ...
that would indeed not fix indicator sound (or volume button) behaviour unless
you limit its focus to certain roles.
--
funny, this bug was fixed for the 4.5 a while ago, seems the vegeta also
needs the same fix of the brightness xml file.
** Summary changed:
- Possible to manually set display brightness to 0 on Ubuntu Touch
+ Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
--
You
if you refer to indicator-sound with volume UI then yes ... note that
the apps i mentioned above only use the implementation from
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/QtMultimedia.SoundEffect/
... the role changes from the default immediately when the play()
function is used, and
hmm, you don't seem to understand... unless i have an app that
constantly plays back something (game or music player) the role used to
play back my sound is never activated. in case of sound effects in an
app the volume control points 99% of the time to the main system volume,
not to the role your
(b) automatically reflect, and adjust, the system volume for the
active output role, without the app having to do anything at all;
i dont think that works, the item should have a way to select for which role
you want the volume change since we auto-change roles all the time. what if a
is that after updating to the new OTA ? including the output of:
system-image-cli -i
helps a lot to identify which image this issue was seen on ;)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
@George: note that this has not been released yet, we usually keep bugs
in Fix Committed state until the actual OTA was released to the
endusers ...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching
echo 1 /sys/class/leds/mx-led/blink
(as root) makes the led blink
echo 0 /sys/class/leds/mx-led/blink
stops teh blinking
the triggers are rather for specific use cases ...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages
i assume IOS also locks down all kinds of input while the device is
locked ... we dont really do that currently, so you can still slide the
indicator bar or the launcher causing unexpected results ...
--
You received this bug notification because you are a member of DX
Packages, which is
do either of android, IOS or windows phone use the proximity sensor to
check if they are in a pocket to not trigger any button presses on the
notifications ? that is IMHO the only sane solution to this problem,
your pocket should not be able to generate any input, only turning on
the screen if the
the proximity sensor would only help if you had very very wide pockets
;)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1445106
Title:
just follow this bug, the ubuntu-ux task should be enough to have the
design team take a look.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
adding an Ubuntu UX task, this needs design team decision
** Package changed: indicator-messages (Ubuntu) = ubuntu-ux
** Also affects: indicator-messages (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is
this is definitely by design, there has been discussion before which
resulted in the privacy options for messages and launcher ...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions:
Public bug reported:
On the desktop we have an audible pling sound if you adjust the
volume, on the phone this seems to be missing.
https://wiki.ubuntu.com/Sound#notification defines it though ...
** Affects: indicator-sound (Ubuntu)
Importance: Undecided
Status: New
** Summary
i see the same with calendar notifications (which only fire off once
without snoozing ability) ... my clock was stuck at 17:30 (time of my
last meeting and calendar notification) the whole evening yesterday
which i only noticed around midnight and could only fix with a reboot
... the greeter clock
reverted in RTM due to issues with first boot ...
ubuntu-touch-session (0.108+15.04.2014-0ubuntu2) 14.09;
urgency=medium
* revert the former override change since it was found to be not working on
first boot on fresh installs during milestone testing.
ubuntu-touch-session
** Changed in: ubuntu-ux
Status: New = Confirmed
** Changed in: indicator-power (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1388235
We should at least consider to not show it at all on fullscreen video
playback (not to mention it uses the currently hardcoded shell rotation
so it comes up in portrait mode while playing video in landscape). pop-
over volume notification that you cant swipe away is one of the most
annoying things
)
Status: New = Confirmed
** Changed in: dbus (Ubuntu RTM)
Status: New = Confirmed
** Changed in: dbus (Ubuntu RTM)
Assignee: (unassigned) = Oliver Grawert (ogra)
** Changed in: ubuntu-touch-session (Ubuntu RTM)
Assignee: (unassigned) = Oliver Grawert (ogra)
--
You received
i just filed bug 1360162 which is a far cousin of this one
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1296431
Title:
Phone doesn't alert user of critical power situations
i must say that you are very lucky only getting teh clock being off by a few
minutes ...
*every* morning when i go to the landing meeting which starts at 10:30 for me
the notification for that particular meeting goes off at 10:40 or 10:45 ...
when the screen turns on with the notification
android does warn when it goes below 15% ... i wonder if we should not
do teh same here ...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1317860
Title:
[system] the phone should
** Tags added: rtm
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1316978
Title:
ubuntu-touch-session needs to be able to start even if the homedir is
filled to 100%
Status in Ubuntu CI
use the ubuntu-touch/devel channel when flashing ... this has always the
latest tested image
--
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
** Also affects: hud (Ubuntu)
Importance: Undecided
Status: New
** Changed in: hud (Ubuntu)
Importance: Undecided = Critical
** Changed in: hud (Ubuntu)
Assignee: (unassigned) = Oliver Grawert (ogra)
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
as i understood the removal of the gesture is only temporary until an
alternative is found ...
also doesnt the search function in the panel use the HUD as backend still ?
generally i'm just trying to move the dbus-session file to
$XDG_RUNTIME_DIR and adjust all consumers to read it from there,
looks like fallout of bug 1292306
please test with a newer image again, i suppose it is fixed now.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
** Changed in: indicator-datetime (Ubuntu)
Status: New = 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/1317510
Title:
Just a sidenote: Unlike what the sensationalist article at heise.de from
today suggests (which links here), this bug was fixed in a heroc effort
over night *before* final release, the fix is on the 14.04 image that
was released to end users.
--
You received this bug notification because you are
how about you make the indicator (ab)use upstart for this, it has file
watchers already and could send an event the indicator could pick up
(hoping that systemd offers something equivalent indeed)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed
what i meant is that the upstart file watcher is running anyway ... so
you could as well just use it and not have the indicator duplicate the
file watching functionality
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in
Public bug reported:
going through the session upstart jobs on image 268 i found that the
hud.conf upstart session job carries its pre-start script twice and
generally looks a bit disordered (paste error or some such ?)
http://paste.ubuntu.com/7179957/
** Affects: hud (Ubuntu)
Importance:
below a a fixed version:
--- snip ---
# Currently started by the dbus service file
# start on dbus-activation com.canonical.hud
description Unity HUD
start on started dbus and ((xsession SESSION=ubuntu-touch) or (xsession
SESSION=ubuntu-touch-surfaceflinger) or (xsession SESSION=ubuntu))
stop
seems indicator-messages was forgotten (it significantly sticks out on the
Ubuntu Touch bootcharts).
i added a task for it so it can be fixed before 14.40
** Also affects: indicator-messages (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
After an update of libunity-core-6.0-8 to libunity-core-6.0-9 the
already existing flickering in the camera-app on maguro degraded so much
that the app got unusable (looks like a strobe now). Seemingly the
rendering frequency was raised with this update.
** Affects: unity
obviously going to the settings app, switching my language setting back
and forth and rebooting fixes it. my clock is now properly staying at
24h time.
seemingly we now set more variables in /home/phablet/.pam_environment than we
did at the time i was firstly setting up the image.
during OTA
Public bug reported:
starting my phone set to german language the lock screen properly shows
a 24h clock ...
as aoon as the panel clock shows up, the lockscreen format (and all
other places where the time is shown in the UI) is swithcing to AM/PM
12h time format.
** Affects: indicator-datetime
** Changed in: indicator-datetime (Ubuntu)
Status: New = 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/1247401
Title:
Public bug reported:
using a few webapps (5 or 6) at the same time at some point these seem
to get SIGKILLed in the bakground by the OOM watcher. if they get re-
initalized they seem to come up without any hud support (before the hud
has back/forward/reload, after the hud is empty)
to reproduce,
i can confirm ths behavior on a mako (nexus 4) too
** Also affects: indicator-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: phablet-tools
Status: New = Invalid
** Changed in: indicator-bluetooth (Ubuntu)
Status: New = Confirmed
** Changed in:
48 matches
Mail list logo
