[Dx-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
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 https://discourse.ubuntu.com/t/odd-close-button-with-snaps/19392 -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1703743] Re: Subfolders Documents, Downloads , , , missing in Home folder
*** 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 Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1703743 Title: Subfolders Documents, Downloads ,,, missing in Home folder Status in indicator-session package in Ubuntu: New Bug description: Installed from: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170703) usual subfolders Documents, Downloads, Music ... are missing in Home folder. corrado@corrado-HP-aa-p4:~$ ls -a . .bashrc examples.desktop .local.stellarium .. .cache .gimp-2.8 .mozilla .sudo_as_admin_successful .bash_history .config .gnupg.profile .thumbnails .bash_logout Desktop .ICEauthority .ssh corrado@corrado-HP-aa-p4:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1703743/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
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 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in powerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1342123] Re: evolution-calendar-factory always running with high memory usage
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 support for things like ~/.config/autostart and such). -- 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/1342123 Title: evolution-calendar-factory always running with high memory usage Status in Canonical System Image: Confirmed Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: At boot the process is using over 100MB on my mako (build 129) I sync'd a fairly large set of calendar events from google previously Does this process need to be running all the time? Can we streamline it to not read so much of the data set, which it appears to be doing? With no calendar entries (i.e. removing .local/share/evolution/xxx/calendar.ics) the process still uses over 30MB (looking at RSS with ps aux --sort -rss ) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1342123] Re: evolution-calendar-factory always running with high memory usage
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. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1342123 Title: evolution-calendar-factory always running with high memory usage Status in Canonical System Image: Confirmed Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: At boot the process is using over 100MB on my mako (build 129) I sync'd a fairly large set of calendar events from google previously Does this process need to be running all the time? Can we streamline it to not read so much of the data set, which it appears to be doing? With no calendar entries (i.e. removing .local/share/evolution/xxx/calendar.ics) the process still uses over 30MB (looking at RSS with ps aux --sort -rss ) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1540457] [NEW] no notifications for events anymore
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 completely missing in the indicator: http://i.imgur.com/oFZQ3h5.png the matching calendar file is at http://people.canonical.com/~ogra/calendar.ics ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Assignee: Charles Kerr (charlesk) Status: New ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) -- 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/1540457 Title: no notifications for events anymore Status in indicator-datetime package in Ubuntu: New Bug description: 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 completely missing in the indicator: http://i.imgur.com/oFZQ3h5.png the matching calendar file is at http://people.canonical.com/~ogra/calendar.ics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1540457/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308092] Re: [desktop]"indicator-session" name is suboptimal
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 https://bugs.launchpad.net/bugs/1308092 Title: [desktop]"indicator-session" name is suboptimal Status in Ubuntu UX: Triaged Status in indicator-session package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: The session indicator has no icon in the Panel in the Unity 8 Desktop Preview session. Also, it appears in the indicator nav bar as 'indicator-session' instead of having some user-friendly title. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1308092/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1478506] Re: Apps change audio output role all the time
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. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1478506 Title: Apps change audio output role all the time Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: To reproduce, install the app Maroon in trouble from the app store and play it a little with having sound enabled. Press the volume down hardware button on the phone. It will temporarily decrease the volume. However, whenever a new item comes into the scene, it will be on 100% volume again. Setting the system volume to 0 should keep everything at 0. Please note that this app does *not* have any code to set the volume! Also this app is one of the upstream Qt QML example demo apps, so this is really how QML apps are supposed to work (in other words, it is not a badly implemented app, but really an issue in the system) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
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 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 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389761] Re: Don't show the volume overlay when changing the volume with the slider
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 stays changed for the duration of the sound.
it might be that either our interfacing of the toolkit with the back end
is broken here or the back end behaviour itself is wrong, but this kind
of supports the fact that making a UI element pick the current
default without the ability to override is the wrong approach.
what if i want to write an app that explicitly allows modification of
different volumes for different roles, i would have no way to use your
slider item at all but would have to completely create custom sliders,
since all of yours would forcefully just point to the default output.
whatever we have in the toolkit should offer to define the role it
controls (with a sane default when undefined).
all i'm asking for is a way to override the default behaviour in the
toolkit element, or if needed there could be a default volume slider
and a customizable volume slider if you prefer to not have it in the
same element.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1389761
Title:
Don't show the volume overlay when changing the volume with the slider
Status in indicator-sound package in Ubuntu:
Triaged
Status in ubuntu-system-settings package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
The overlay and the slider are redundant when the user changes the
volume with the slider and the overlay shouldn't be displayed.
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '',
[{'running': false, 'state': 'Paused'}]), 'mute': (true, '', [false]),
'phone-settings': (true, '', []), 'mic-volume': (true, '', [1.0]), 'scroll':
(true, 'i', []), 'high-volume': (true, '', [false]),
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings':
(true, '', []), 'mediaplayer-app.desktop': (true, '', [{'running': false,
'state': 'Paused'}]), 'play.mediaplayer-app.desktop': (true, '',
['Paused']), 'volume': (true, 'i', [1.0]), 'next.mediaplayer-app.desktop':
(true, '', []), 'root': (true, '', [{'title': 'Son', 'accessible-desc':
'Volume (100%)', 'icon': ('themed', ['audio-volume-high-panel',
'audio-volume-high', 'audio-volume', 'audio']), 'visible': true}]),
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '',
[false])},)
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Wed Nov 5 16:58:35 2014
InstallationDate: Installed on 2014-11-05 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf
(20141105-120036)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389761/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389761] Re: Don't show the volume overlay when changing the volume with the slider
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 app uses to play back the effect. if your slider
adjusts the active output role it will always adjust the main volume,
not the volume of your sound effect.
to visualize what i mean, perhaps do the following:
* install the OMGUbuntu app
* turn the main volume down so that the indicator icon just doesn't show any of
the curved lines in front of the speaker icon (30% or so)
* open OMGUbuntu
* keep your eyes on the indicator icon and tap a link/photo/etc in the app
(that generates a sound effect)
you will see the volume jump to full volume the moment the effect plays back,
your role just changed.
if the app had a slider in its settings for controlling the effect volume this
slider would never control the volume you actually want to control, unless the
slider element has an option to define it (this element can indeed default to
the currently active role if unset, but unless you actually want the main
control or unless your app constantly produces sound you would want a way to
override this default to point to the correct knobs suited for the application)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1389761
Title:
Don't show the volume overlay when changing the volume with the slider
Status in indicator-sound package in Ubuntu:
Triaged
Status in ubuntu-system-settings package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
The overlay and the slider are redundant when the user changes the
volume with the slider and the overlay shouldn't be displayed.
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '',
[{'running': false, 'state': 'Paused'}]), 'mute': (true, '', [false]),
'phone-settings': (true, '', []), 'mic-volume': (true, '', [1.0]), 'scroll':
(true, 'i', []), 'high-volume': (true, '', [false]),
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings':
(true, '', []), 'mediaplayer-app.desktop': (true, '', [{'running': false,
'state': 'Paused'}]), 'play.mediaplayer-app.desktop': (true, '',
['Paused']), 'volume': (true, 'i', [1.0]), 'next.mediaplayer-app.desktop':
(true, '', []), 'root': (true, '', [{'title': 'Son', 'accessible-desc':
'Volume (100%)', 'icon': ('themed', ['audio-volume-high-panel',
'audio-volume-high', 'audio-volume', 'audio']), 'visible': true}]),
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '',
[false])},)
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Wed Nov 5 16:58:35 2014
InstallationDate: Installed on 2014-11-05 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf
(20141105-120036)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389761/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389761] Re: Don't show the volume overlay when changing the volume with the slider
(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
notification goes off while the app is open ? you will suddenly adjust the
notification volume. what if your app uses a certain role that only gets
activated if you actually play a sound.
my alternate webapp container framework allows to enable haptic feedback and
click sounds for links in websites, if i enable that i can see the volume
indicator jump to full volume for the lenght of the sound. if i would want to
provide the mentioned slider to adjust the sound effect volume it would always
only point to the main system volume unless the effect is played.
the toolkit widget should have a field to define the type of role you want it
to change.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1389761
Title:
Don't show the volume overlay when changing the volume with the slider
Status in indicator-sound package in Ubuntu:
Triaged
Status in ubuntu-system-settings package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
The overlay and the slider are redundant when the user changes the
volume with the slider and the overlay shouldn't be displayed.
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '',
[{'running': false, 'state': 'Paused'}]), 'mute': (true, '', [false]),
'phone-settings': (true, '', []), 'mic-volume': (true, '', [1.0]), 'scroll':
(true, 'i', []), 'high-volume': (true, '', [false]),
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings':
(true, '', []), 'mediaplayer-app.desktop': (true, '', [{'running': false,
'state': 'Paused'}]), 'play.mediaplayer-app.desktop': (true, '',
['Paused']), 'volume': (true, 'i', [1.0]), 'next.mediaplayer-app.desktop':
(true, '', []), 'root': (true, '', [{'title': 'Son', 'accessible-desc':
'Volume (100%)', 'icon': ('themed', ['audio-volume-high-panel',
'audio-volume-high', 'audio-volume', 'audio']), 'visible': true}]),
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '',
[false])},)
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Wed Nov 5 16:58:35 2014
InstallationDate: Installed on 2014-11-05 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf
(20141105-120036)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389761/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]
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. https://bugs.launchpad.net/bugs/1473428 Title: battery indicator does not update after charge [meizu ubuntu phone] Status in indicator-power package in Ubuntu: Confirmed Bug description: Battery charge indicator does not update after phone is charged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1473428/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1461682] Re: [MX4] LED does not notify for incoming notifications
@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 subscriptions: dx-packages https://bugs.launchpad.net/bugs/1461682 Title: [MX4] LED does not notify for incoming notifications Status in Canonical System Image: Fix Released Status in indicator-messages package in Ubuntu: Invalid Status in qtubuntu package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Image r12 The notification LED on the device does not blink when a new SMS arrives. Its always static off. It however does lighten up when the button physical button is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461682/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1461682] Re: [MX4] LED does not notify for incoming notifications
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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1461682 Title: [MX4] LED does not notify for incoming notifications Status in indicator-messages package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Image r12 The notification LED on the device does not blink when a new SMS arrives. Its always static off. It however does lighten up when the button physical button is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1461682/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1445106] Re: [Notifications] turn the screen on
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 subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1445106 Title: [Notifications] turn the screen on Status in Ubuntu UX bugs: Triaged Status in indicator-messages package in Ubuntu: Confirmed Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. -UX comment- Please refer for the correct behaviour here: https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1445106] Re: [Notifications] turn the screen on
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 proximity sensor is not covered will help with that (yes, i know it wouldn't turn on then if you have a sheet of paper on top of it on your desk or some such, but isn't that a corner case (beyond the fact that you still get acoustic (and perhaps haptic) signals anyway ?) -- 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: [Notifications] turn the screen on Status in Ubuntu UX bugs: Triaged Status in indicator-messages package in Ubuntu: Confirmed Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. -UX comment- Please refer for the correct behaviour here: https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1445106] Re: Notifications turn the screen on
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: Notifications turn the screen on Status in Ubuntu UX bugs: New Status in indicator-messages package in Ubuntu: New Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1445106] Re: Notifications turn the screen on
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 https://bugs.launchpad.net/bugs/1445106 Title: Notifications turn the screen on Status in Ubuntu UX bugs: New Status in indicator-messages package in Ubuntu: New Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1445106] Re: Notifications turn the screen on
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 subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1445106 Title: Notifications turn the screen on Status in Ubuntu UX bugs: New Status in indicator-messages package in Ubuntu: New Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1439136] Re: Messages readable when phone locked..
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: dx-packages https://bugs.launchpad.net/bugs/1439136 Title: Messages readable when phone locked.. Status in Ubuntu UX bugs: New Status in indicator-messages package in Ubuntu: New Bug description: When the phone is in a locked state swiping down you are able to get access to the notification tab, from here you are able to read recent SMS messages -- which is all well and good if you want quick access to your text messages but you are also able to reply to the text message without unlocking the phone. in summary; You are able to read and send SMS messages without unlocking the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1439136/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1436801] [NEW] Volume notifications give no audible feedback for volume changes
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 changed: - Volume notifications ive no audible feedback for volume changes + Volume notifications give no audible feedback for volume changes -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436801 Title: Volume notifications give no audible feedback for volume changes Status in indicator-sound package in Ubuntu: New Bug description: 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 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1436801/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1435736] Re: snoozing an alarm causes time to freeze
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 seems affected as well. -- 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/1435736 Title: snoozing an alarm causes time to freeze Status in indicator-datetime package in Ubuntu: New Bug description: On latest vivid, snoozing an alarm causes the time in the indicator to freeze. Here's a screenshot of the phone after I snoozed an alarm today morning at 9am. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1435736/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
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 (0.108+15.04.2014-0ubuntu1) vivid; urgency=low [ Ted Gould ] * Override indicator-sound to wait for pulse audio (LP: #1389008) Date: 2014-11-12 17:47:09.485214+00:00 ** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Status in “unity8” package in Ubuntu RTM: New Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389008/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1388235] Re: Icon turns red at 30%
** 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 Title: Battery icon turns red at 30% Status in Ubuntu UX bugs: Confirmed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1382857] Re: No way to swipe away sound notification
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 ever invented on mobile OSes, i wonder if we cant do better than the others here :) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1382857 Title: No way to swipe away sound notification Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: Using RTM 5 on Mako, there is no way to swipe away the new sound notification overlay. While it doesn't last very long, this is annoying. Touching it, or swiping it away, would be a preferable way to dismiss this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1382857/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** Also affects: dbus (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: hud (Ubuntu) Status: Confirmed = Fix Released ** Also affects: ubuntu-touch-session (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-touch-session (Ubuntu RTM) 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 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 Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “dbus” package in Ubuntu RTM: Confirmed Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1296431] Re: Phone doesn't alert user of critical power situations
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 Status in “indicator-power” package in Ubuntu: In Progress Bug description: The phone doesn't currently alert the user when the battery is critical. This leads to power loss at times and the user doesn't know it's about to happen or had happened. e.g. during a call, or while listening to music. Also if the phone is sat on the desk unplugged from power connection. https://wiki.ubuntu.com/Power#Warnings: When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 1 hour or less remaining (PC) or 20% or less remaining (phone/tablet), a notification bubble should appear ... When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 30 minutes or less remaining (PC) or 10% or less remaining (phone/tablet), an alert should appear... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1296431/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1328646] Re: Clock out of sync on resume from suspend
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 both, the lock screen and indicator still show a time around 10:20 .. this is reproducable every morning for me ... -- 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/1328646 Title: Clock out of sync on resume from suspend Status in The Date and Time Indicator: New Status in The Unity 8 shell: Triaged Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: When the device is resumed by pressing the power button and the device is not connected over USB the clock is out of sync You need another system to compare the time to verify this bug report, and make sure both clocks are in sync. TEST CASE 1. Unplug the device from its USB cable 2. Press the power button to switch to suspend mode or wait until it goes to suspend 3. Wait 2 or more minutes 4. Press the power button again to resume the device 5. Compare the time on the greeter and indicator with the time on the other system EXPECTED RESULT Clocks are in sync ACTUAL RESULT Time on the device is behind by several minutes. The use case are people who use their device as a watch. You usually resume it, check the time, suspend it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.88+14.10.20140606-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Tue Jun 10 19:11:42 2014 InstallationDate: Installed on 2014-06-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140610) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317860] Re: [system] the phone should switch itself off before completely draining battery
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 switch itself off before completely draining battery Status in The Power Indicator: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: the phone should switch itself off at around ~5% remaining battery. This is to preserve a little battery for use cases such as: * turn it back on once or twice for urgent short phone calls * prevent the battery from going into a state where it can't be charged any more * have enough power to turn itself on again and trigger an alarm Desired resolution The following actions should take place as the phone/tablet runs out of battery: at 10% - Notification battery under 10% at 5% - Notification saying battery level is critical, will shutdown soon. at 1-2% - Shell fades out, animation fades in (same as startup animation), phone initiates full shutdown. The notification should be a clickable notification with the tap action mapped to dismiss. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1317860/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** 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 Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1299916] Re: Alarm Clock does not ring when phone is locked
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 https://bugs.launchpad.net/bugs/1299916 Title: Alarm Clock does not ring when phone is locked Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: TSIA. I woke up two hours late today because my alarm clock on UT failed. I need this fixed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1299916/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** 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 ** Changed in: dbus (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: dbus (Ubuntu) Status: New = Confirmed ** Changed in: hud (Ubuntu) Status: New = Confirmed -- 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 Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
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, the change to the HUD code is a trivial one liner (and you get cleanup of the messed up upstart job (duplicated pre-start script) for free with the MP) ** Branch linked: lp:~ogra/hud/new-dbus-address ** Branch linked: lp:~ogra/ubuntu-touch-session/fix-dbus-location -- 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 Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317277] Re: Don't always receive a notification of incoming SMS
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 https://bugs.launchpad.net/bugs/1317277 Title: Don't always receive a notification of incoming SMS Status in “indicator-messages” package in Ubuntu: New Bug description: This is impossibly vague, I'm sorry. I was dogfooding u2 and I got several texts over the course of a day from the same contact that did not trigger a notification at all in indicator-messages. If I opened the Messaging app, I would see the texts. I just had to check and see because indicator-messages didn't tell me. Other contacts seemed to work fine. I don't know what was wrong with this one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1317277/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317510] Re: Wrong icon for events #17 mako
** 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: Wrong icon for events #17 mako Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: I have a bunch of calendar events synced to my device, but they show as clock alarms. Previously (some images back) I had clock items with a clock icon and calendar items as calendar icon. Now they have the wrong icons. Note in the screenshot Alarm was set in the clock, the others are calendar items. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1317510/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen
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 a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308572 Title: Ubuntu 14.04: security problem in the lock screen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: affects ubuntu Hello, I am running Ubuntu 14.04 with all the packages updated. When the screen is locked with password, if I hold ENTER after some seconds the screen freezes and the lock screen crashes. After that I have the computer fully unlocked. -- Marco Agnese This bug is about the lockscreen being bypassed when unity crashes/restarts, which is a critcal security issue. The crash will be handled from bug 1308750 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308572/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
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 to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
Confirmed
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
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 Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
Confirmed
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1299806] [NEW] the hud package ships a messed up upstart session job
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: High Status: New ** Changed in: hud (Ubuntu) Importance: Undecided = High -- 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/1299806 Title: the hud package ships a messed up upstart session job Status in “hud” package in Ubuntu: New Bug description: 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/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1299806/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1299806] Re: the hud package ships a messed up upstart session job
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 on desktop-end
env HUD_SERVICE_TIMEOUT=0
export HUD_SERVICE_TIMEOUT
pre-start script
if [ -z $DBUS_SESSION_BUS_ADDRESS ]; then
echo Working around missing DBUS_SESSION_BUS_ADDRESS variable
printf DuplicateSignature\0DBusSessionAddressNotSet |
/usr/share/apport/recoverable_problem -p `pidof -s -o 1 init`
. ${HOME}/.cache/upstart/dbus-session
initctl set-env
DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS
fi
end script
exec /usr/lib/arm-linux-gnueabihf/hud/hud-service
--
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/1299806
Title:
the hud package ships a messed up upstart session job
Status in “hud” package in Ubuntu:
New
Bug description:
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/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1299806/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1185565] Re: Indicators should have Upstart jobs
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 are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Released Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Released Status in The Session Menu: Fix Released Status in Sound Menu: Fix Released Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Invalid Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1282051] [NEW] Camera app on maguro flickering degraded massively with latest Unity
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 (Ubuntu) Importance: Undecided Status: New ** Tags: r189 touch ** Package changed: unity8 (Ubuntu) = unity (Ubuntu) ** Summary changed: - Camera app on maguro flickering degraded massively with latest Unity8 + Camera app on maguro flickering degraded massively with latest Unity ** Tags added: r189 touch -- 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/1282051 Title: Camera app on maguro flickering degraded massively with latest Unity Status in “unity” package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282051/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1255530] Re: system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock starts
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 upgrade the new settings were not updated inside this config file so that parts of my settings flipped back to english. to handle this case in the future (we might have other cases where pam settings of a user need upgrading even on released images) the session- migration tool should get a backend to handle this. i am turning this into a wishlist bug against session-migration, the indicator task is solved. ** Also affects: session-migration (Ubuntu) Importance: Undecided Status: New ** Changed in: session-migration (Ubuntu) Importance: Undecided = Wishlist ** Changed in: indicator-datetime (Ubuntu) Status: New = Invalid ** Summary changed: - system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock starts + /home/phablet/.pam_environment does not get updated on OTA upgrades -- 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/1255530 Title: /home/phablet/.pam_environment does not get updated on OTA upgrades Status in “indicator-datetime” package in Ubuntu: Invalid Status in “session-migration” package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1255530/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1255530] [NEW] system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock starts
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 (Ubuntu) Importance: Medium Status: New ** Tags: avengers ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Medium ** Tags added: avengers -- 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/1255530 Title: system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock starts Status in “indicator-datetime” package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1255530/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1247401] Re: Date/Time missing from indicators and welcome screen
** 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: Date/Time missing from indicators and welcome screen Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Sometimes the clock disappears from both the indicator and the welcome screen. I don't have much running, and its only been up for 2 hours or so. alan@deep-thought:~$ adb shell system-image-cli -i current build number: 5 device name: mako channel: trusty last update: 2013-10-26 19:41:51 version version: 5 version ubuntu: 20131024 version device: 20131024 See screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+13.10.20131016.2-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Sat Nov 2 14:54:04 2013 InstallationDate: Installed on 2013-10-24 (8 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131024) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1247401/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1243143] [NEW] hud on the phone dies in backgrounded webapps after a while
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, run a bunch of webapps for a few hours and see them randomly die and come back, with and without hud on a phone ** Affects: hud Importance: Undecided Status: New ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Also affects: hud (Ubuntu) Importance: Undecided Status: New -- 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/1243143 Title: hud on the phone dies in backgrounded webapps after a while Status in Unity HUD: New Status in “hud” package in Ubuntu: New Bug description: 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, run a bunch of webapps for a few hours and see them randomly die and come back, with and without hud on a phone To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1243143/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1241130] Re: Bluetooth turned on automatically after unlocking galaxy nexus
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: indicator-bluetooth (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1241130 Title: Bluetooth turned on automatically after unlocking galaxy nexus Status in Phablet Tools: Invalid Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: everytime i locked and unlocked and / or turn off and on galaxy nexus bluetooth working automatically. when i turn it off the phone redirect me to location ( location detection GPS ) To manage notifications about this bug go to: https://bugs.launchpad.net/phablet-tools/+bug/1241130/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
