[Dx-packages] [Bug 1200750] Re: Regression: Rev 3696: Qt4 apps some others that are started or controlled from unity launcher quicklists cause extended cursor run on
You can add google-chrome quicklist options to affected ** Tags removed: amd64 apport-bug package-from-proposed raring saucy ** Tags added: trusty vivid wily -- 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/1200750 Title: Regression: Rev 3696: Qt4 apps some others that are started or controlled from unity launcher quicklists cause extended cursor run on Status in Compiz: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Minor issue but annoying, present in raring saucy Test cases: Install smplayer from software-center Add a quicklist entry - sudo nano /usr/share/applications/smplayer.desktop Paste this in at bottom, save Actions=mpc [Desktop Action mpc] Name=Smplayer-mpc Exec=smplayer -mpcgui OnlyShowIn=Unity; Start smplayer from the quicklist entry of smplayer-mpc, cursor will run on for 12-15 sec's when not over a window Install minitube-ubuntu from software-center Open, (may get cursor spin right there), search anything, start a video. From quicklist choose an option Play/Pause, cursor spins for 12-15 sec's. when not over window Also would affect a launcher icon where a quicklist entry launched a qt4 app, same deal with cursor spin, for example if one had a launcher icon whose quicklists launched media apps, all qt4 apps would get the spin on Duped bug shows other test cases not involving qt4 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jul 12 15:21:18 2013 InstallationDate: Installed on 2013-07-11 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1200750/+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 1169054] Re: Disabling then Re-Enabling login without password does remove user from nopasswdlogin group
I think this should be changed to Fix Released after your merge proposal was approved? Thanks Eric. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1169054 Title: Disabling then Re-Enabling login without password does remove user from nopasswdlogin group Status in accountsservice package in Ubuntu: Confirmed Bug description: I am using 12.04. Under System Settings, User Accounts, Passwords, Action, changing to Login without a password works as expected. On the next login, LightDM will not prompt you for a password, You can just login by hitting Enter. But, re-enabling password, or changing a password for the same user does not change LightDM behavior. LightDM does not re-enable asking for password at login. I think the problem is re-enabling password under Systems Settings does not delete user from nopasswdlogin group. You have to delete it from the command line: sudo gpasswd -d username nopasswdlogin This problem is the same ones described here: http://ubuntuforums.org/showthread.php?p=11566335 http://askubuntu.com/questions/211084/how-do-i-get-ubuntu-to-ask-me- for-at-password-at-login-again/281615#281615 http://askubuntu.com/questions/100010/no-password-asked-at-login- screen-just-start-session-button-with-lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1169054/+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 1478217] Re: can't pair bluetooth keyboard, phone doesn't show code.
Same bug as described by Hugo, Aquaris E4.5 Ubuntu edition and Logik bluetooth keyboard(LKBUBT13) -- 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/1478217 Title: can't pair bluetooth keyboard, phone doesn't show code. Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: 1) Device: Meizu MX4 Ubuntu Edition OS: Ubuntu 15.04 (r68) - armhf (20150724-020304) 2) Bluez version 4.101-0ubuntu25 indicator-bluetooth version 0.0.6+14.10.20141006-0ubuntu1 3) When trying to connect a bluetooth keyboard (SilverCrest SBT 3.0 A1), pairing doesn't follow correct procedure. On other devices (Android 5.1.1 on Nexus 10; Ubuntu 15.04 on BTO laptop) a 6 digit number is displayed, which needs to be typed on the Bluetooth keyboard, followed by pressing [Enter]. 4) On Ubuntu touch, a dialogue appears asking to enter a 4 digit PIN on the phone. Default is '' and at first the phone says the device is connected, but the phone does not respond to any input from the keyboard. After some time the phone indicates the device is not connected. All of this is similarly described in this askubuntu article: http://askubuntu.com/questions/625533/how-to-pair-external-bluetooth- keyboard-to-ubuntu-touch-bq-phone, which has not received any answers as of yet. I am willing to follow instructions and report back results. i have adb shell installed on my laptop, and Terminal app installed on the phone. Developer mode is on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1478217/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
** Summary changed: - Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10, 15.04 + Hotkeys not functional in non-latin keyboard layout -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1478075] Re: Sound indicator should only indicate ringtone volume
Per spec, if an app/game is playing sounds but not music, that is the
alert output role. As long as an alarm is not sounding, a phone call
is not in progress, and you're not playing music some other way, all
volume controls should adjust the volume of that app's sounds.
https://wiki.ubuntu.com/Sound#primary-output
In other words, if apps obey the media volume setting for things that
aren't music/video, that's probably a bug.
I just realized that when I added output roles to the spec, I updated
the design for the System Settings slider and the volume buttons, but I
neglected to update the design for the indicator slider to match. Spec
updated. https://wiki.ubuntu.com/Sound?action=diffrev2=148rev1=147
But that doesn't seem to be related to this bug report, and I still have
no reason to think that this bug report is valid.
--
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/1478075
Title:
Sound indicator should only indicate ringtone volume
Status in Canonical System Image:
New
Status in Ubuntu UX:
Incomplete
Status in indicator-sound package in Ubuntu:
Incomplete
Bug description:
On the phone, the volume indicator follows the current active stream
volume (music, alarm etc.) to show and control via slider and/or
volume buttons.
The indicator icon and slider should only ever follow the ringtone
volume. I'm not sure whether volume buttons should work for alarms.
This is somewhat related to bug #1291458.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: indicator-sound 12.10.2+15.04.20150508-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', [0.7414398193359375]),
'next.mediaplayer-app.desktop': (true, '', []), 'indicator-shown': (true, '',
[false]), 'root': (true, '', [{'title': 'Dźwięk', 'accessible-desc':
'Głośność (74%)', 'icon': ('themed', ['audio-volume-high-panel',
'audio-volume-high', 'audio-volume', 'audio']), 'visible': true}]),
'silent-mode': (true, '', [false]), 'previous.mediaplayer-app.desktop':
(true, '', [])},)
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: armhf
Date: Fri Jul 24 18:07:15 2015
InstallationDate: Installed on 2015-07-23 (1 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20150723-020304)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478075/+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 1481913] Re: UI volume warnings need revision
** Branch linked: lp:~unity-api-team/indicator-sound/lp-1481913-revised- ui-volume-warnings -- 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/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+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 1401491] Re: Bluetooth icon shows a little lock, and there's no indication of what it means
*** This bug is a duplicate of bug 1311211 *** https://bugs.launchpad.net/bugs/1311211 ** Package changed: bluez (Ubuntu) = indicator-bluetooth (Ubuntu) -- 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/1401491 Title: Bluetooth icon shows a little lock, and there's no indication of what it means Status in indicator-bluetooth package in Ubuntu: New Bug description: All of a sudden the Bluetooth icon on the top right notification area shows a little lock icon (see screenshot). By clicking on the icon, there's no way to figure out what the icon means. After turning bluetooth off and on, the lock icon disappeared. Then, no matter whether I turn bluetooth on or off, no matter whether visible or not, the lock icon never reappeared (the bluetooth icon, without a lock, greys out as expected when bluetooth is turned off). I thought the lock may mean that Receive Files via Bluetooth was turned off in Personal File Sharing settings (see also #958661: that setting should be in the Bluetooth settings), but even after enabling it, the lock was still showing up (until I turned off and on bluetooth). After disabling file reception again, the lock icon did not reappear. I suspect that the icon appeared because of an attempt to send a file to the computer which was rejected, because it appeared just after that but: 1 - if that is the case, then an indication should be given, e.g. when rolling over the icon or when unfolding the submenu. You should ALWAYS be able to know what the an icon means 2 - if that is the case, there should be a way to dismiss the notice, other than turning off and on bluetooth 3 - a toast (or whatever it is called) notification should also be shown at the moment the file is rejected If the lock is instead supposed to mean that file reception is turned off, or that visibility is turned off, then it's not working properly. If it means anything else, it is not working properly either, as I haven't changed any other setting when the lock disappeared. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 10 10:45:21 2014 InstallationDate: Installed on 2013-10-11 (424 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-05-24 (199 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:819218 acl:1083 sco:0 events:198 errors:0 TX bytes:3969 acl:103 sco:0 commands:71 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1401491/+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 1481913] Re: UI volume warnings need revision
** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Alejandro J. Cura (alecu) ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) = Xavi Garcia (xavi-garcia-mena) ** Changed in: indicator-sound (Ubuntu) Status: New = Confirmed ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Critical -- 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/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+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 1458509] Re: revoking the coupling of device remotely isn't reflected in inidcator-applet
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: indicator-bluetooth (Ubuntu) Importance: Undecided = Low ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Incomplete -- 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/1458509 Title: revoking the coupling of device remotely isn't reflected in inidcator- applet Status in indicator-bluetooth package in Ubuntu: Incomplete Bug description: The device is still displayed as if it was coupled. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-bluetooth 0.0.6+14.10.20141006-0ubuntu1 Uname: Linux 4.0.1-040001-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 25 11:51:19 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (52 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: indicator-bluetooth SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1458509/+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 1350621] Re: indicator-power battery with locked screen
Thanks, what desktop environment and ubuntu version are you using? Could you add a screenshot of the issue? ** Package changed: indicator-bluetooth (Ubuntu) = indicator-power (Ubuntu) ** Changed in: indicator-power (Ubuntu) Importance: Undecided = Low ** Changed in: indicator-power (Ubuntu) Status: New = Incomplete -- 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/1350621 Title: indicator-power battery with locked screen Status in indicator-power package in Ubuntu: Incomplete Bug description: When the screen is locked and the battery is very low the battery symbol is always white. Instead I would expect that it becomes red when is low and an exclamation mark inside when is very low (as it happens when the computer is not locked) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1350621/+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 1311211] Re: Bluetooth icon has a padlock emblem when paired with device
** Also affects: ubuntu-themes Importance: Undecided Status: New -- 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/1311211 Title: Bluetooth icon has a padlock emblem when paired with device Status in Ubuntu theme: New Status in indicator-bluetooth package in Ubuntu: Triaged Bug description: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2, Ubuntu 14.04 When a Bluetooth device is paired, the Bluetooth icon has a padlock emblem. This makes no sense. https://wiki.ubuntu.com/Bluetooth#icon: If a device is paired, a lozenge Bluetooth icon between two arrowheads, with accessible label 'Bluetooth (paired)'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1311211/+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 1385938] Re: bluetooth indicator has no option to enable file sharing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Confirmed -- 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/1385938 Title: bluetooth indicator has no option to enable file sharing Status in Bluetooth Menu: New Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: if you go to bluetooth settings via the bluetooth-indicator, you can pair with other devices such as phones, but there is no option to enable file sharing. When attempting to send a file with a paired device it silently fails. There is no prompt to confirm the file transfer. As it turns out you have to enable bluetooth filesharing in a separate menu Personal file sharing, wich is only available via the Dash. There you have the option to recieve files. This is totally not obvious and there should atleast be a link from the bluetooth indicator to this menu. This is on Ubuntu 14.04 LTS on two different laptops I have tried. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1385938/+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 1272686] Re: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property()
seems like reports stopped in newer series, unsure why since the code didn't change... -- 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/1272686 Title: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property() Status in indicator-bluetooth package in Ubuntu: Triaged Bug description: After activating bluetooth. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 25 15:02:43 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2013-12-10 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20131210) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: Segfault happened at: 0x40d880: mov(%rbx),%rdi PC (0x0040d880) ok source (%rbx) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1272686/+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 1278680] Re: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property()
seems like reports stopped in newer series, unsure why since the code didn't change... -- 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/1278680 Title: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property() Status in Bluetooth Menu: Confirmed Status in indicator-bluetooth package in Ubuntu: Triaged Bug description: My bluetooth device doesn't work at all. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 10 21:23:54 2014 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2013-06-04 (251 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: Segfault happened at: 0x8054fd8: mov(%ebx),%eax PC (0x08054fd8) ok source (%ebx) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() UpgradeStatus: Upgraded to trusty on 2014-01-07 (34 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.indicator-bluetooth.log: ** (process:2140): CRITICAL **: bluez.vala:184: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method GetProperties with signature on interface org.bluez.Adapter doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1278680/+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 1298374] Re: Bluetooth applet doesn't remember state
thanks, it's not a bug in the indicator but one in the bluez service, see bug #446657 ** Changed in: indicator-bluetooth (Ubuntu) Importance: Undecided = Low ** Changed in: indicator-bluetooth (Ubuntu) Status: Confirmed = Invalid -- 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/1298374 Title: Bluetooth applet doesn't remember state Status in indicator-bluetooth package in Ubuntu: Invalid Bug description: If I disable bluetooth from the applet, reboot and then check the state, it is enabled. So the applet fails to make the change permanent, as you expect it to do. Other settings are usually permanent across reboots so I can't see why this settings shouldn't be. It saves battery to only turn it on if you need it on a laptop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 27 14:04:54 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-26 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140325.1) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: ** (unity-control-center:3393): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1298374/+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 1350621] Re: indicator-power battery with locked screen
Hi Sebastien, I am using Ubuntu 15.04 64 bit Desktop fully updated. The desktop environment is the default one, namely Unity. My laptop is an Asus UX31A. The issue appears only when the computer is locked therefore I cannot print the screen. But simply the empty battery symbol is white instead of red. It seems inconsistent to me. Cheers, Marco. -- 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/1350621 Title: indicator-power battery with locked screen Status in indicator-power package in Ubuntu: Incomplete Bug description: When the screen is locked and the battery is very low the battery symbol is always white. Instead I would expect that it becomes red when is low and an exclamation mark inside when is very low (as it happens when the computer is not locked) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1350621/+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: [indicators] Battery icon turns red at 30%
** Changed in: ubuntu-ux Status: Triaged = Fix Released -- 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: [indicators] Battery icon turns red at 30% Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Released Status in indicator-power package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu RTM: Fix Released 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/canonical-devices-system-image/+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 1401491] [NEW] Bluetooth icon shows a little lock, and there's no indication of what it means
You have been subscribed to a public bug: All of a sudden the Bluetooth icon on the top right notification area shows a little lock icon (see screenshot). By clicking on the icon, there's no way to figure out what the icon means. After turning bluetooth off and on, the lock icon disappeared. Then, no matter whether I turn bluetooth on or off, no matter whether visible or not, the lock icon never reappeared (the bluetooth icon, without a lock, greys out as expected when bluetooth is turned off). I thought the lock may mean that Receive Files via Bluetooth was turned off in Personal File Sharing settings (see also #958661: that setting should be in the Bluetooth settings), but even after enabling it, the lock was still showing up (until I turned off and on bluetooth). After disabling file reception again, the lock icon did not reappear. I suspect that the icon appeared because of an attempt to send a file to the computer which was rejected, because it appeared just after that but: 1 - if that is the case, then an indication should be given, e.g. when rolling over the icon or when unfolding the submenu. You should ALWAYS be able to know what the an icon means 2 - if that is the case, there should be a way to dismiss the notice, other than turning off and on bluetooth 3 - a toast (or whatever it is called) notification should also be shown at the moment the file is rejected If the lock is instead supposed to mean that file reception is turned off, or that visibility is turned off, then it's not working properly. If it means anything else, it is not working properly either, as I haven't changed any other setting when the lock disappeared. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 10 10:45:21 2014 InstallationDate: Installed on 2013-10-11 (424 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-05-24 (199 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:819218 acl:1083 sco:0 events:198 errors:0 TX bytes:3969 acl:103 sco:0 commands:71 errors:0 ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- Bluetooth icon shows a little lock, and there's no indication of what it means https://bugs.launchpad.net/bugs/1401491 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. -- 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 1458491] Re: indicator-bluetooth misses controls to enable file transfer
*** This bug is a duplicate of bug 1385938 *** https://bugs.launchpad.net/bugs/1385938 ** Changed in: indicator-bluetooth (Ubuntu) Importance: Undecided = Low ** This bug has been marked a duplicate of bug 1385938 bluetooth indicator has no option to enable file sharing -- 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/1458491 Title: indicator-bluetooth misses controls to enable file transfer Status in indicator-bluetooth package in Ubuntu: New Bug description: The default settings of `indicator-bluetooth` make file transfers fail without feedback (not too great, but not the issue here). One has to install `bluemon` and enable file transfer options like ~allow read/write and ~allow trusted devices. The user expects `indicator- bluetooth` to offer a sufficient set of options to transfer file which is a quite basic task for bluetooth connections. The options should be added to sufficient hints displayed in the application (e.g. a hint that the settings aren't implemented yet and that one needs to manage the device with `bluemon` like described above). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-bluetooth 0.0.6+14.10.20141006-0ubuntu1 Uname: Linux 4.0.1-040001-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 25 10:54:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (52 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: indicator-bluetooth SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: (unity-control-center:7633): Bluetooth-WARNING **: Can't open the plugins dir: Fehler beim Öffnen des Ordners »/usr/lib/gnome-bluetooth/plugins«: Datei oder Verzeichnis nicht gefunden (unity-control-center:7633): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1458491/+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 1401491] Re: Bluetooth icon shows a little lock, and there's no indication of what it means
*** This bug is a duplicate of bug 1311211 *** https://bugs.launchpad.net/bugs/1311211 ** This bug has been marked a duplicate of bug 1311211 Bluetooth icon has a padlock emblem when paired with device -- 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/1401491 Title: Bluetooth icon shows a little lock, and there's no indication of what it means Status in indicator-bluetooth package in Ubuntu: New Bug description: All of a sudden the Bluetooth icon on the top right notification area shows a little lock icon (see screenshot). By clicking on the icon, there's no way to figure out what the icon means. After turning bluetooth off and on, the lock icon disappeared. Then, no matter whether I turn bluetooth on or off, no matter whether visible or not, the lock icon never reappeared (the bluetooth icon, without a lock, greys out as expected when bluetooth is turned off). I thought the lock may mean that Receive Files via Bluetooth was turned off in Personal File Sharing settings (see also #958661: that setting should be in the Bluetooth settings), but even after enabling it, the lock was still showing up (until I turned off and on bluetooth). After disabling file reception again, the lock icon did not reappear. I suspect that the icon appeared because of an attempt to send a file to the computer which was rejected, because it appeared just after that but: 1 - if that is the case, then an indication should be given, e.g. when rolling over the icon or when unfolding the submenu. You should ALWAYS be able to know what the an icon means 2 - if that is the case, there should be a way to dismiss the notice, other than turning off and on bluetooth 3 - a toast (or whatever it is called) notification should also be shown at the moment the file is rejected If the lock is instead supposed to mean that file reception is turned off, or that visibility is turned off, then it's not working properly. If it means anything else, it is not working properly either, as I haven't changed any other setting when the lock disappeared. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 10 10:45:21 2014 InstallationDate: Installed on 2013-10-11 (424 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-05-24 (199 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:819218 acl:1083 sco:0 events:198 errors:0 TX bytes:3969 acl:103 sco:0 commands:71 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1401491/+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 1421559] Re: [Clock][ux] Should be able to silence alarm using power button
Appears to be a device capability related bug, will flag for relevant design team member. ** Summary changed: - [Clock][ux] Should be able to silence alarm using power button + [Clock] Should be able to silence alarm using power button -- 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/1421559 Title: [Clock] Should be able to silence alarm using power button Status in Ubuntu Clock App: Incomplete Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: krillin @rtm #16 Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, press OK on alarm What should have happened: I should be able to silence the alarm using the power button. On iOS and Android power button enable snooze to prevent accidential disabling alarm. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. Also when someone forget phone in the office, then it will be no possibility to disable alarm. Related to bug 1340329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1421559/+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 1362962] Re: Calendar icon usually shows the wrong date
** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scope-click (Ubuntu) Status: New = Confirmed ** Changed in: unity-scope-click (Ubuntu) Importance: Undecided = Wishlist -- 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/1362962 Title: Calendar icon usually shows the wrong date Status in Ubuntu Calendar App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in unity-scope-click package in Ubuntu: Confirmed Bug description: Problem occurs with: Ubuntu 14.10 r203 Does not occur with: iOS, Windows Phone 1. In the clock menu, find the calendar app and launch it. 2. In the Launcher or Dash, find the Calendar app. What you see: 1. The icon always says 25, regardless of the actual date. 2. The icon always says 28, regardless of the actual date. What you should see: 1. The icon shows the current date. 2. The icon shows the current date. The equivalent for PC is bug 1362033, and for the Clock app is bug 1362964. This depends on bug 1453795 for Unity letting an app change its own icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1362962/+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 694224] Re: Synchronous notifications briefly steal focus
** Changed in: canonical-devices-system-image Importance: Medium = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/694224 Title: Synchronous notifications briefly steal focus Status in Canonical System Image: Confirmed Status in notify-osd package in Ubuntu: Confirmed Bug description: It appears synchronous notifications (at least those for volume and brightness) briefly steal focus when they appear. This is quite problematic for games and some other applications that pause as soon as they lose focus. The focus stealing does not happen with normal, asynchronous notifications. Here's a quick Python program to reproduce this: #!/usr/bin/python import gtk import time def cb (wid, ev): evtime = time.strftime (%H:%M:%S, time.localtime()) print (%s: Lost focus! % evtime) win = gtk.Window() win.connect (focus-out-event, cb) win.show_all() gtk.main() You could also just start playing Quadrapassel, then adjust your volume :) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/694224/+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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
So according to the usability test, 7/11 participants failed to interpret the meaning of blue. How many interpreted the meaning of green? Was it any better? I'd be surprised if Michael quoted above, for example, would say: I don't know why it would need to be blue ... but green, green makes sense to me. Or if Hansie would change his belief that The fact that it is present indicates there is something there for me to do merely because it was sometimes green rather than sometimes blue (if he even saw that happen). If the logic is, the menu is where we list notifications, therefore the indicator has to be there all the time, therefore we need to use visual design to distinguish new messages received or not, then maybe the premise is wrong. -- 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/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in Canonical System Image: Fix Released Status in Ubuntu theme: Fix Released Status in Ubuntu UX: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated
** Description changed: Imagine a scenario where you have a calendar event or a clock alarm to go of at 10:00. If you get a call at the same time, then obviously the call gets the highest priority and the alarm or calendar audible notification is suppressed by the system. So a phone user can actually miss the event. This can be resolved by turning the alarm icon shown in the indicator to blue similar to messages to indicate that an alarm or event was missed by the user. - --- - Desired solution: + ——— UX Comment ——— - The alarm icon turns its state to active like notification - center/messages indicator as suggested in the bug description. + I can think of two possibilities for the resolution of this bug: + + 1) We change the alarm icon in the status bar for alarm-missed icon + (https://drive.google.com/drive/u/1/folders/0BzbnWoHmYF3ablBITVByRnpzdEk + + 2) Once the incoming call event has finished or the user has acted on it + by answering the call, we fire a notification bubble (as well as it’s + associated auditory feedback) to communicate the missed event. If the + user doesn’t act on the incoming call event, the alarm goes off after + incoming call timeout. + + -- My recommendation would be to use a combination of both. ** Changed in: ubuntu-ux Status: In Progress = Opinion -- 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/1321309 Title: [Indicators] Missed calendar or alarm events need to be properly indicated Status in Indicator Date and Time: Confirmed Status in Ubuntu theme: New Status in Ubuntu UX: Opinion Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Imagine a scenario where you have a calendar event or a clock alarm to go of at 10:00. If you get a call at the same time, then obviously the call gets the highest priority and the alarm or calendar audible notification is suppressed by the system. So a phone user can actually miss the event. This can be resolved by turning the alarm icon shown in the indicator to blue similar to messages to indicate that an alarm or event was missed by the user. ——— UX Comment ——— I can think of two possibilities for the resolution of this bug: 1) We change the alarm icon in the status bar for alarm-missed icon (https://drive.google.com/drive/u/1/folders/0BzbnWoHmYF3ablBITVByRnpzdEk 2) Once the incoming call event has finished or the user has acted on it by answering the call, we fire a notification bubble (as well as it’s associated auditory feedback) to communicate the missed event. If the user doesn’t act on the incoming call event, the alarm goes off after incoming call timeout. -- My recommendation would be to use a combination of both. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1321309/+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 1458509] Re: revoking the coupling of device remotely isn't reflected in inidcator-applet
** Description changed: The device is still displayed as if it was coupled. + + Steps to reproduce: + + 1. couple with an Android 4.0.4 device + 2. revoke the coupling on the Android device + + The device is still displayed as coupled in the `indicator-bluetooth`, + but shouldn't. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-bluetooth 0.0.6+14.10.20141006-0ubuntu1 Uname: Linux 4.0.1-040001-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 25 11:51:19 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (52 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: indicator-bluetooth SystemImageInfo: - current build number: 0 - device name: - channel: daily - last update: Unknown + current build number: 0 + device name: + channel: daily + last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1458509 Title: revoking the coupling of device remotely isn't reflected in inidcator- applet Status in indicator-bluetooth package in Ubuntu: Incomplete Bug description: The device is still displayed as if it was coupled. Steps to reproduce: 1. couple with an Android 4.0.4 device 2. revoke the coupling on the Android device The device is still displayed as coupled in the `indicator-bluetooth`, but shouldn't. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-bluetooth 0.0.6+14.10.20141006-0ubuntu1 Uname: Linux 4.0.1-040001-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 25 11:51:19 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (52 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: indicator-bluetooth SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1458509/+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
** Tags added: hardware-related -- 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: 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 1329048] Re: Shouldn't stop listing events until they are over
** Description changed: Using current utopic, events are dropped from the list when they start, wouldn't it make sense to list as well the ongoing ones (if you are looking to the menu 3 minutes after a meeting started you might still be interested in joining it for example) + + + -- UX Comment -- + + I agree with Matthew suggestion: + + If an event hasn't started yet, its start time should be shown, for + example 7:00 PM; if it has started but not finished, its end time + should be shown, for example ends 9:20 PM. + + https://wiki.ubuntu.com/TimeAndDate?action=diffrev2=100rev1=99 ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Fix Committed ** Description changed: Using current utopic, events are dropped from the list when they start, wouldn't it make sense to list as well the ongoing ones (if you are looking to the menu 3 minutes after a meeting started you might still be interested in joining it for example) - -- UX Comment -- - I agree with Matthew suggestion: + I agree with Matthew's suggestion: If an event hasn't started yet, its start time should be shown, for example 7:00 PM; if it has started but not finished, its end time should be shown, for example ends 9:20 PM. https://wiki.ubuntu.com/TimeAndDate?action=diffrev2=100rev1=99 -- 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/1329048 Title: Shouldn't stop listing events until they are over Status in indicator-datetime package in Ubuntu: Fix Committed Bug description: Using current utopic, events are dropped from the list when they start, wouldn't it make sense to list as well the ongoing ones (if you are looking to the menu 3 minutes after a meeting started you might still be interested in joining it for example) -- UX Comment -- I agree with Matthew's suggestion: If an event hasn't started yet, its start time should be shown, for example 7:00 PM; if it has started but not finished, its end time should be shown, for example ends 9:20 PM. https://wiki.ubuntu.com/TimeAndDate?action=diffrev2=100rev1=99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1329048/+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 1421559] Re: [Clock] Should be able to silence alarm using power button
** Tags added: hardware-related -- 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/1421559 Title: [Clock] Should be able to silence alarm using power button Status in Ubuntu Clock App: Incomplete Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: krillin @rtm #16 Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, press OK on alarm What should have happened: I should be able to silence the alarm using the power button. On iOS and Android power button enable snooze to prevent accidential disabling alarm. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. Also when someone forget phone in the office, then it will be no possibility to disable alarm. Related to bug 1340329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1421559/+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 1350621] Re: indicator-power battery with locked screen
right, that's an unity lock screen issue ** Package changed: indicator-power (Ubuntu) = unity (Ubuntu) ** Changed in: unity (Ubuntu) Status: Incomplete = New -- 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/1350621 Title: indicator-power battery with locked screen Status in unity package in Ubuntu: New Bug description: When the screen is locked and the battery is very low the battery symbol is always white. Instead I would expect that it becomes red when is low and an exclamation mark inside when is very low (as it happens when the computer is not locked) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1350621/+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 1481913] Re: UI volume warnings need revision
** Tags added: audio -- 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/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+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
