[Dx-packages] [Bug 1369737] Re: Send button does not enable until you press spacebar
As a reminder, we need to call Qt.inputMethod.commit() so the buffer gets committed and the text property is correctly set. -- 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/1369737 Title: Send button does not enable until you press spacebar Status in “indicator-messages” package in Ubuntu: New Bug description: krillin build 40, rtm image - make sure word prediction/preditive text is turned on (this is now the default) - receive a text message on your phone - pull down messaging indicator - click on the message - type Hello in the entry field Expected result: - the send button should become active as soon as you start typing Actual result: - send button stays disabled until you press the spacebar The send button should not wait until the word is committed before becoming active, but instead should listen for any change and enable the button accordingly. The messaging app does this correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1369737/+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 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
Bill debugged this issue and this is what we found: http://pastebin.ubuntu.com/8353187/ Looks more like an ofono bug to me. I will reassign. ** Project changed: telephony-service = ofono -- 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/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+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 1367270] Re: Message is lost when user replies to an SMS from the indicator without a default SIM
** Branch linked: lp:~tiagosh/telephony-service/fallback-default-account -- 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/1367270 Title: Message is lost when user replies to an SMS from the indicator without a default SIM Status in “indicator-messages” package in Ubuntu: New Bug description: TEST CASE: Pre-requisite: Dual SIM device without a default SIM selected 1. Send an SMS to the device under test 2. On notification, open the message indication 3. Tap the incoming message to show the input field 4. Type an answer and send. ACTUAL RESULT: The message is not sent and is lost. EXPECTED RESULT Either the system asks which SIM to use or replying from the indicator is locked without a default SIM. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 9 14:37:03 2014 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140909-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367270/+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 1238346] Re: on bootup wrong keyboard layout is recognized
Any news about this? This bug is incredibly annoying. -- 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/1238346 Title: on bootup wrong keyboard layout is recognized Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: This is a regression. I have two keyboard layouts activated, the Dvorak and the English US. The Dvorak should be the default keyboard. That is the way I have it set up, and it shows up in the task bar on top as En1, which is the Dvorak. However, when I start to type, it starts in QUERTY. ?? To correct this, I go to the task bar (where it shows EN1, or Dvorak), re-select the Dvorak, and then everything is fine. ?? I have another minor problem which should probably go on another bug, but happened at the same time. CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm using. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 10 21:20:39 2013 InstallationDate: Installed on 2013-08-12 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1238346/+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 1227920] Re: after suspend/resume, the Unity HUD is always open when I unlock the screen
I see this behaviour as well on my desktop. Ubuntu 13.10 64bit, nvidia graphics (binary drivers). I suspend using menu option, then resume by pressing power button. I get a password screen, enter my password, and when it drops to the desktop, the HUD is already open. -- 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/1227920 Title: after suspend/resume, the Unity HUD is always open when I unlock the screen Status in Gnome Settings Daemon: New Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: Traveling at a conference, so I'm doing a lot of suspending and resuming of my laptop. Every time I open my laptop back up after resume and unlock the desktop, the Unity dash is open. This does not happen if I lock my screen using the lock screen hotkey, and does not happen if my screen is locked by a lid close event; only when the system suspends and resumes. But it is 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,place,grid,resize,regex,mousepoll,gnomecompat,unitymtgrabhandles,vpswitch,move,animation,expo,session,wall,ezoom,staticswitcher,workarounds,fade,scale,unityshell] Date: Thu Sep 19 17:51:29 2013 InstallationDate: Installed on 2010-09-24 (1091 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-05-06 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1227920/+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
