[Dx-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Treviño]

I'm not sure if that has happened because the fix was marked as
released, however maybe something changed in gtk, but this change is
just something right to do, and I'd like to backport it to 16.04, thus
the need of fixing it in both.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to ido in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1506427

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  New

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1443052] Re: User accounts login history showing incorrect history - patch

[Nikita Yerenkov-Scott]

I have tested the packages from -proposed on both Trusty and Xenial and
I can confirm that they both solve the problem with no currently
noticeable regressions.

The package versions I tested were:

- Xenial: 0.6.40-2ubuntu11.3
- Trusty: 0.6.35-0ubuntu7.3

I tested the Xenial one in an Ubuntu GNOME 16.04.1 (GNOME 3.18) 64-bit
VM, and I tested the Trusty one in an Ubuntu (Unity) 14.04.5 64-bit VM.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
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/1443052

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Brian Murray]

While we don't see any crashes about that this from 16.10 on the Error
Tracker, shouldn't this also be fixed in that release?

** Also affects: ido (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to ido in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1506427

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  New

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1443052] Re: User accounts login history showing incorrect history - patch

[Brian Murray]

Hello Nikita, or anyone else affected,

Accepted accountsservice into xenial-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Description changed:

  Impact
  ---
  
  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.
  
  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.
  
  Test case
  --
  
  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough distance
  between them for you to tell that the timestamps are correct.
  
  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.
  
  Regression potential
  
  
  I have not encountered any regressions while testing this patch.
- 
+ [bdmurray] - What could go wrong? What should a user testing this look for?
  
  --
  
  Original description:
  
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which is
  meant to show the login history for that account), it will show you when
  you last logged in as "Session Started", but it will show that you
  "Session Ended" just before you login the next time.
  
  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I logged
  out, and then this morning I logged into my account somewhere around
  11:20, it will show this:
  
  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started
  
  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.
  
  I have attached a screenshot to show my example as I see it in the
  History GUI.
  
  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

** Changed in: accountsservice (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: accountsservice (Ubuntu Trusty)
   Status: In Progress => Fix Committed

-- 
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/1443052

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact 

[Dx-packages] [Bug 1443052] Please test proposed package

[Brian Murray]

Hello Nikita, or anyone else affected,

Accepted accountsservice into trusty-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.35-0ubuntu7.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
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/1443052

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1380702] Re: No keyboards shortcuts in QT apps

[George-t]

Related issue apparently cause by this one:

https://github.com/keepassxreboot/keepassxc/issues/73

have verified uninstalling appmenu-qt5 dissolves the problem.

@Dmitry - Can you clarify the env setting you're specifying -
specifically, should I replace "myapp" with the process name of the
application in question?  for keepassxc eg:

```UBUNTU_MENUPROXY= QT_QPA_PLATFORMTHEME=appmenu-qt5 keepassxc```

or something else?

Many thanks

** Bug watch added: github.com/keepassxreboot/keepassxc/issues #73
   https://github.com/keepassxreboot/keepassxc/issues/73

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1380702

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in appmenu-qt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1476257] Re: /usr/lib/arm-linux-gnueabihf/url-dispatcher/url-dispatcher:11:g_variant_is_trusted:g_variant_builder_add_value:g_variant_builder_close:send_to_dash:dispatcher_send_to_a

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/url-dispatcher/url-dispatcher-ubuntu-
zesty-1886

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1476257

Title:
  /usr/lib/arm-linux-gnueabihf/url-dispatcher/url-
  
dispatcher:11:g_variant_is_trusted:g_variant_builder_add_value:g_variant_builder_close:send_to_dash:dispatcher_send_to_app

Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding url-dispatcher.  This problem was most recently seen with
  version 0.1+15.10.20150612-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/64c5a23f81476af20831b29844a2abcb607d5dc6
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1476257/+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 1352656] Re: ubuntu-app-launch-invalid-appid

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/url-dispatcher/url-dispatcher-ubuntu-
zesty-1886

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1352656

Title:
  ubuntu-app-launch-invalid-appid

Status in url-dispatcher package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding url-dispatcher.  This problem was most recently seen with
  version 8.00+14.10.20140731.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/50ef8ac2301b5a70acb47d40d1efff412014d40b
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1352656/+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 1461496] Re: initctl start url-dispatcher-update-user does not update the protocols database

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/url-dispatcher/url-dispatcher-ubuntu-
zesty-1886

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1461496

Title:
  initctl start url-dispatcher-update-user does not update the protocols
  database

Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  I want to register a protocol for an application putting it in
  ~/.config/url-dispatcher/urls. According to Ted, after running

  $ initctl start url-dispatcher-update-user

  the url dispatcher database should be updated with the new protocol. But 
that's not working.
  It only works if I run /usr/lib/*/url-dispatcher/update-directory with the 
path or my .url-dispatcher file.

  To check the database after the update:

  echo .quit | sqlite3 -batch -csv -cmd "select urls.protocol,
  urls.domainsuffix, configfiles.name from urls, configfiles where
  urls.sourcefile = configfiles.rowid;" ~/.cache/url-
  dispatcher/urls-1.db

  Here is the branch where I'm automating this test:
  
https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/register_url_dispatcher/+merge/260923

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1461496/+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 1370008] Re: URL Dispatcher Should Prompt on Bad URL

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/url-dispatcher/url-dispatcher-ubuntu-
zesty-1886

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1370008

Title:
  URL Dispatcher Should Prompt on Bad URL

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gallery-app.  This problem was most recently seen with
  version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8
  contains more details.

  : "Whenever
  the URL dispatcher is called on to open an address of a protocol that
  it does not understand (url-dispatcher-bad-url), it should open an
  alert with the title “Unrecognized Address”, text of the form ‘Ubuntu
  can’t open addresses of type “{protocol:}”.’, and an “OK” button. To
  prevent denial of UI service, however, the alert should not open if it
  has already opened more than three times in the past minute."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370008/+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 1591342] Re: Complains about bad url on libertine scope urls

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/url-dispatcher/url-dispatcher-ubuntu-
zesty-1886

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1591342

Title:
  Complains about bad url on libertine scope urls

Status in Canonical System Image:
  In Progress
Status in libertine-scope package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  In Progress

Bug description:
  ** (process:4255): WARNING **: Unable to dispatch url
  
'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL
  Dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591342/+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 1380702] Re: No keyboards shortcuts in QT apps

[Dmitry Shachnev]

Yonathan: that may help if appmenu-qt5 is installed. Then use it as “env
UBUNTU_MENUPROXY= QT_QPA_PLATFORMTHEME=appmenu-qt5 myapp”.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1380702

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in appmenu-qt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1380702] Re: No keyboards shortcuts in QT apps

[Yonatan Yehezkeally]

@Dimitry, whether or not `appmenu-qt5` is in use in 16.10, that doesn't
tell us if running a QT5 program setting `ENV UBUNTU_MENUPROXY= `
returns the use of keyboard shortcuts. Can you confirm / deny?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1380702

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in appmenu-qt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1380702] Re: No keyboards shortcuts in QT apps

[Dmitry Shachnev]

Timo: https://codereview.qt-project.org/175494 should work for 16.04 /
appmenu-qt5 too. The second patch (for Alt+letter mnemonics) will not
apply to Qt 5.6, but that’s not what this bug is about.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1380702

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in appmenu-qt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1380702] Re: No keyboards shortcuts in QT apps

[Timo Jyrinki]

Note that it's 'appmenu-qt5', not 'app-menu-qt5'. In 16.10, appmenu-qt5
is no longer installed by default as its functionality was replaced by
better upstream implementation (even if still doesn't fix this
particular bug).

For 16.04, a fix in appmenu-qt5 would still be welcome too.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1380702

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in appmenu-qt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1380702] Re: No keyboards shortcuts in QT apps

[Timo Jyrinki]

** Also affects: appmenu-qt5 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: appmenu-qt5 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New => Invalid

** Changed in: appmenu-qt5 (Ubuntu Xenial)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1380702

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in appmenu-qt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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