This bug was fixed in the package indicator-appmenu -
15.02.0+16.10.20160927-0ubuntu1
---
indicator-appmenu (15.02.0+16.10.20160927-0ubuntu1) yakkety; urgency=medium
* Drop appmenu-qt5 recommendation. (LP: #1612767)
-- Dmitry Shachnev Tue, 27 Sep 2016 12:50:20
+
** Changed
> For some reason the shortcuts are not shown in menus
Thanks a lot to Albert Astals Cid who found the issue and fixed it!
https://code.launchpad.net/~aacid/libdbusmenu/fix_accelerator_not_showing/+merge/306911
We are now almost ready to getting this bug closed.
--
You received this bug notific
** Branch linked: lp:~mitya57/indicator-appmenu/drop-appmenu-qt5
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1612767
Title:
Drop appmenu-qt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-appmenu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscription
Yes the global menus seemed to be working fine both with and without
appmenu-qt5 now.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1612767
Tit
This bug was fixed in the package qtbase-opensource-src - 5.6.1+dfsg-
3ubuntu3~3
---
qtbase-opensource-src (5.6.1+dfsg-3ubuntu3~3) yakkety; urgency=medium
[ Timo Jyrinki ]
* debian/patches/QDBusServer-delay-processing-of-D-Bus-messages.patch:
- Fix DBus message processing (LP:
With the latest packages in 034 both menus and tray icons seem to work
fine.
For some reason the shortcuts are not shown in menus, but according to
dbus-monitor log, Qt is behaving correctly here (shortcuts are
exported), so this seems a regression somewhere on server side (the same
happens with a
Thank you! I've pushed a new build to silo 034. I also realize my Qt 5.6
testing involved Unity 8 on phone and desktop, and smoketesting Plasma,
LXQt etc but not really checking the appmenu functionality.
--
You received this bug notification because you are a member of DX
Packages, which is subs
What broke both configurations, with and without appmenu-qt5, was
http://code.qt.io/cgit/qt/qtbase.git/commit/?id=717ff946391233e7.
I have pushed a quick fix to our packaging Git. It cannot be forwarded
as is, but I will try to discuss this with upstream and make sure it is
fixed upstream too.
--
** Description changed:
Currently we are using appmenu-qt5 as our platform theme on desktop,
however it has many disadvantages, which make me want to get rid of it:
1) Its design is a hack: instead of the using normal QPA API for getting
the menu, it retrieves the menu bar using QWidget
What broke appmenu-qt5 may be https://git.gnome.org/browse/gnome-
session/commit/?id=971baf2e225abc5a.
In this case we probably need to backport https://git.gnome.org/browse
/gnome-session/commit/?id=ce4208add3b49d44 which fixes that issue.
However this should not affect the configuration without
Ok the crash goes away indeed with a rebuild, thanks! That should be
fine.
Can you elaborate a bit how the global menus would be supposed to be
working with these patches when running Qt applications under Unity 7
environment? I can actually see that for whatever reason current yakkety
doesn't hav
Sorry that I did not notice that earlier. It looks like we simply need a
non-change rebuild of appmenu-qt5 against new Qt.
The ABI break was introduced not in the patch adding global menu
support, but in dbusmenu_exclusive_groups.diff which is a bugfix and
affects the tray icons too.
Maybe we wil
No change in your PPA it seems.
Meanwhile, silo 34 would have the build that does pass those tests and
skips the printer related tests.
However, as reported on IRC, transmission-qt crashes on yakkety on startup when
using the silo, if not removing appmenu-qt5. Here's the backtrace:
Thread 1 "tra
The difference between my PPA and yours is that mine didn't have
-proposed archive enabled. I have now enabled -proposed and retried one
of the builds, to see if it makes any difference.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicato
Interestingly, tst_QStaticText passed just fine in my landing PPA build
for all i386 armhf amd64 running tests: https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/landing-034/+sourcepub/6845112/+listing-
archive-extra
--
You received this bug notification because you are a member of DX
Here is the stacktrace of the tst_QAbstractPrintDialog crash.
For me it happens only when libqt5printsupport5 is installed (and picked
by the testsuite), when I remove that package the test passes (hello,
the docs building hack).
** Attachment added: "bt_full.txt"
https://bugs.launchpad.net/u
I have just been able to reproduce the tst_QStaticText failure in my
pbuilder (on amd64).
I gathered the debug images from that test and submitted upstream as
https://bugreports.qt.io/browse/QTBUG-55653 (see attached file there).
The tst_QAbstractPrintDialog test crashes for me with SIGPIPE in li
I used a clean pbuilder too by manually logging in inside and apt build-
dep:ing and building, and couldn't reproduce it. I'm not sure what could
explain the difference.
I have now a successful build with those tests disabled, but it would be
useful to file a bug against the package change that ca
By "locally" I meant a pbuilder on my own server, not really locally...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1612767
Title:
Drop app
Dmitry, any idea how did you get it reproduced locally? I'm getting:
$ QT_QPA_PLATFORM=xcb xvfb-run -a -s "-screen 0 640x480x24" make check
QT_PLUGIN_PATH=~/b/qtbase-opensource-src-5.6.1+dfsg/plugins
LD_LIBRARY_PATH=~/b/qtbase-opensource-src-5.6.1+dfsg/lib
PATH=~/b/qtbase-opensource-src-5.6.1+d
Ok I've the same problem:
https://launchpadlibrarian.net/280573314/buildlog_ubuntu-yakkety-amd64
.qtbase-opensource-src_5.6.1+dfsg-3ubuntu3~1_BUILDING.txt.gz
It seems it's something new in the last two weeks in yakkety, and not
related to Qt changes. Maybe glibc 2.24 related?
--
You received th
Those don't look familiar, I wonder if they are related to new libc6 or
something. I had a successful build on Augusty 9th.
I'll try a new build myself.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching sub
Thanks Timo! I committed the changes last week.
Unfortunately I get tests failures when trying to build qtbase, but they
seem unrelated to my changes
(https://launchpad.net/~mitya57/+archive/ubuntu/test2/+build/10643352, I
get the same locally). Do you know anything about this?
** Description cha
Thanks a lot for that work! No objections, commit away but don't upload
yet since we still struggle with the proposed migration...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
** Description changed:
Currently we are using appmenu-qt5 as our platform theme on desktop,
however it has many disadvantages, which make me want to get rid of it:
1) Its design is a hack: instead of the using normal QPA API for getting
the menu, it retrieves the menu bar using QWidget
26 matches
Mail list logo
