Hello,
I think there is a similar issue with Digikam 5.3 using Ubuntu Desktop
16.04 up to date with multiscreen (2 x 1920x1080).
libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
Ubuntu 4.4.0-49-generic
Logs are :
--
0x48bc490 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
Thanks for testing!
I'll try to get that patch included in the next Qt upload. Also
submitted upstream: https://codereview.qt-project.org/170467.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu.
Sorry for the noise. After fixing my change the local menus are gone.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1604009
Title:
Empty menus in global app-menu
User error indeed - I did #if 0 instead of #if 1. Rebuilding now, but
because of my lack of experience with debuild I am stuck in a full build
again.
By the way, lots of test cases fail after the change. I disabled them
in debian/rules locally.
--
You received this bug notification because
The patch fixes double menus for KDE apps for me (Quassel, Konsole).
I tried VirtualBox, and it looks like menu doesn't get exported at all
(I only get local menu, not the global one).
Which exactly change did you apply? Was it removing the #if and #endif
lines in QMenuBar::setVisible code (but
I rebuilt Qt5 with that change but do not see any difference. Might be
user error of course. I downloaded with apt-get source, made the
change, rebuilt with debuild binary and (for simplicity) installed all
resulting .deb files with dpkg -i.
--
You received this bug notification because you
The remaining issue looks like
https://bugreports.qt.io/browse/QTBUG-54793. It can be fixed by a simple
two-line patch (maybe I’ll propose it for review soon).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu-qt in
Not sure if you want to include the double menu issue here or if you
prefer to treat the bug as fixed. As a reminder, the double menu issue
seemed to happen with appmenu-qt because it simply hid the local menus
but did not intercept hide and show requests from the application.
--
You received
I can confirm though that the global menu now works for the second
window.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1604009
Title:
Empty menus in global
Removed appmenu-qt5 and checked that I am on 5.6.1+dfsg-3ubuntu3~3, but
still no joy. I would not rule out user error though (and I have not
yet rebooted since upgrading from 16.04, so there might be something
stale in memory).
--
You received this bug notification because you are a member of
Yes, please remove appmenu-qt5 or unset QT_QPA_PLATFORMTHEME env
variable.
This needs today’s qtbase 5.6.1+dfsg-3ubuntu3~3 which may be not yet
available on your mirrors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Just did a quick test after upgrading to 16.10. I (still) see double
menus (both local and global) in a single window machine. Should I
remove appmenu-qt* and try again?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
FWIW, I am going to get rid of appmenu-qt5 in 16.10, that work is
tracked in bug 1612767.
We will be using upstream Qt code instead, which is not based on
libdbusmenu-qt and so should not have this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I got in touch with Aurélien, who wrote the original libdbusmenu-qt
code, in case he has any ideas. This is a bit tricky for me, as I can
only justify spending a limited time on it (my main area is graphics
driver work), and while I could probably fix something up that would
work for me, I don't
By the way the commit which fixed that KDE bug is:
http://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu-
qt/trunk/revision/189
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu.
Michael, thanks for the investigation!
That check looks related, and links to
https://bugs.kde.org/show_bug.cgi?id=254066. Do you have any idea how to
fix your issue and not introduce regressions for that bug?
I do not know if there is any active maintainer for libdbusmenu-qt, but
I'm
16 matches
Mail list logo
