[Dx-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
https://bileto.ubuntu.com/#/ticket/2454 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1389336] Re: Use geoclue-2.0
Humm, the qtlocation 5.6 did land to yakkety so marking this as fixed. ** Changed in: qtlocation-opensource-src (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Fix Released Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Fix Released Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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
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
** 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
[Dx-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations
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 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma or GNOME when installed: see bug 1434516, bug 1307619. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1612767 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma or GNOME when installed: see bug 1434516, bug 1307619. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 have those working even without landing-034 PPA, so the appmenu- qt5 seems to have become broken regardless right now. New bugs should probably be filed for any next actions, whether in Unity itself or elsewhere. -- 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-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 "transmission-qt" received signal SIGSEGV, Segmentation fault. 0x7590b518 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x7590b518 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x76907c5e in copyActionToPlatformItem (action=action@entry=0x55bb9430, item=item@entry=0x55b6c690, itemsMenu=0x55b72840) at widgets/qmenu.cpp:3228 #2 0x76907861 in QMenuPrivate::syncPlatformMenu (this=0x55c2abd0) at widgets/qmenu.cpp:202 #3 0x76907977 in QMenu::setPlatformMenu (this=this@entry=0x55c28680, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x76af69f5 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55bc7020, menu=0x55c28680) at util/qsystemtrayicon.cpp:761 #5 0x76af6ad2 in QSystemTrayIconPrivate::updateMenu_sys_qpa ( this=0x55bc7020) at util/qsystemtrayicon.cpp:710 #6 0x555d5b62 in ?? () #7 0x5559afdf in ?? () #8 0x55595e9d in ?? () #9 0x74fd33f1 in __libc_start_main (main=0x55595e60, argc=1, argv=0x7fffdea8, init=, fini=, rtld_fini=, stack_end=0x7fffde98) at ../csu/libc-start.c:291 #10 0x555964e9 in ?? () Should appmenu-qt5 forced to be removed from some package instead of allowing it to be continue to be installed? -- 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-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1612767 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 causes this regression, if only it would be known. Meanwhile, the previous qtbase landing hasn't migrated to release pocket still so this is pending. -- 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-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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+dfsg/bin:$PATH -k /home/ubuntu/b/qtbase-opensource-src-5.6.1+dfsg/tests/auto/printsupport/dialogs/qabstractprintdialog/target_wrapper.sh ./tst_qabstractprintdialog make: 'tst_qabstractprintdialog' is up to date. * Start testing of tst_QAbstractPrintDialog * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20160822) PASS : tst_QAbstractPrintDialog::initTestCase() PASS : tst_QAbstractPrintDialog::getSetCheck() XFAIL : tst_QAbstractPrintDialog::setMinMax() QTBUG-22637 Loc: [tst_qabstractprintdialog.cpp(107)] PASS : tst_QAbstractPrintDialog::setMinMax() PASS : tst_QAbstractPrintDialog::setFromTo() PASS : tst_QAbstractPrintDialog::cleanupTestCase() Totals: 5 passed, 0 failed, 0 skipped, 0 blacklisted * Finished testing of tst_QAbstractPrintDialog * -- 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-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 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-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 subscriptions: dx-packages https://bugs.launchpad.net/bugs/1612767 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) It breaks other environments such as Plasma when installed: see bug 1434516. 5) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1612767] Re: Drop appmenu-qt5 from default installations
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 https://bugs.launchpad.net/bugs/1612767 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: 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::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+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 1389336] Re: Use geoclue-2.0
The switch in Qt will happen with Qt 5.6 that aims to land to yakkety before Feature Freeze in August. ** Changed in: qtlocation-opensource-src (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: In Progress Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1531516] Re: qt5/gtk integration needs to disable overlay-scrollbars since they create issues
** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1531516 Title: qt5/gtk integration needs to disable overlay-scrollbars since they create issues Status in overlay-scrollbar package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: Similar to past issues seen in Bug 1005677 & Bug 805303 Test case: open vlc > any menu item, window will be way too long hortizontally & will hang Ex. - xwininfo -all xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0x3af "Open Media" Root window id: 0xd4 (the root window) (has no name) Parent window id: 0x1016ca3 (has no name) 0 children. Absolute upper-left X: 59 Absolute upper-left Y: 366 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 16383 Height: 404 Depth: 24 Visual: 0xb1 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x3ac (not installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +59+366 --14522+366 --14522-310 +59-310 -geometry 16383x404+59+366 Bit gravity: ForgetGravity Window gravity: NorthWestGravity Backing-store hint: NotUseful Backing-planes to be preserved: 0x Backing pixel: 0 Save-unders: No Someone wants these events: KeyPress KeyRelease ButtonPress ButtonRelease EnterWindow LeaveWindow PointerMotion ButtonMotion Exposure StructureNotify FocusChange PropertyChange Do not propagate these events: Override redirection?: No Window manager hints: Client accepts input or input focus: Yes Initial state is Normal State Displayed on desktop 0 Window type: Dialog Normal Window state: Modal Process id: 305 Frame extents: 0, 0, 28, 0 Normal window size hints: User supplied location: 59, 338 User supplied size: 524309 by 404 Program supplied minimum size: 16383 by 404 Program supplied maximum size: 900 by 16383 Program supplied window gravity: StaticGravity No zoom window size hints defined No window shape defined No border shape defined If the overlay-scrollbar packages are removed menu windows open, vlc complains about module not able to be loaded & menus are not as accessible as they should be. If vlc is opened with export LIBOVERLAY_SCROLLBAR=0 && vlc then all is well. As I understand overlay-scrollbars is not going to be used or something like that, hence yet again starting bug on vlc though other packages like calibre may be affected & or the cause ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.1-5 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 6 09:37:07 2016 InstallationDate: Installed on 2015-10-25 (72 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1531516/+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 1531516] Re: qt5/gtk integration needs to disable overlay-scrollbars since they create issues
@fabianbur: it was marked as such because the bug is not in "overlay- scrollbar" package, but in "qtbase-opensource-src" instead. It will get handled latest tomorrow although the automatic QA will take an additional day or two. ** Changed in: overlay-scrollbar (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1531516 Title: qt5/gtk integration needs to disable overlay-scrollbars since they create issues Status in overlay-scrollbar package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Similar to past issues seen in Bug 1005677 & Bug 805303 Test case: open vlc > any menu item, window will be way too long hortizontally & will hang Ex. - xwininfo -all xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0x3af "Open Media" Root window id: 0xd4 (the root window) (has no name) Parent window id: 0x1016ca3 (has no name) 0 children. Absolute upper-left X: 59 Absolute upper-left Y: 366 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 16383 Height: 404 Depth: 24 Visual: 0xb1 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x3ac (not installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +59+366 --14522+366 --14522-310 +59-310 -geometry 16383x404+59+366 Bit gravity: ForgetGravity Window gravity: NorthWestGravity Backing-store hint: NotUseful Backing-planes to be preserved: 0x Backing pixel: 0 Save-unders: No Someone wants these events: KeyPress KeyRelease ButtonPress ButtonRelease EnterWindow LeaveWindow PointerMotion ButtonMotion Exposure StructureNotify FocusChange PropertyChange Do not propagate these events: Override redirection?: No Window manager hints: Client accepts input or input focus: Yes Initial state is Normal State Displayed on desktop 0 Window type: Dialog Normal Window state: Modal Process id: 305 Frame extents: 0, 0, 28, 0 Normal window size hints: User supplied location: 59, 338 User supplied size: 524309 by 404 Program supplied minimum size: 16383 by 404 Program supplied maximum size: 900 by 16383 Program supplied window gravity: StaticGravity No zoom window size hints defined No window shape defined No border shape defined If the overlay-scrollbar packages are removed menu windows open, vlc complains about module not able to be loaded & menus are not as accessible as they should be. If vlc is opened with export LIBOVERLAY_SCROLLBAR=0 && vlc then all is well. As I understand overlay-scrollbars is not going to be used or something like that, hence yet again starting bug on vlc though other packages like calibre may be affected & or the cause ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.1-5 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 6 09:37:07 2016 InstallationDate: Installed on 2015-10-25 (72 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1531516/+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 1513098] Re: The global menu isn't working properly on QtCreator.
** Changed in: appmenu-qt5 (Ubuntu) Status: Confirmed => Fix Released ** Also affects: indicator-appmenu (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-appmenu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1513098 Title: The global menu isn't working properly on QtCreator. Status in appmenu-qt5 package in Ubuntu: Fix Released Status in indicator-appmenu package in Ubuntu: Fix Released Bug description: The global menu appears properly at first. But, when I click on it, it disappears completely. Nevertheless, I still can access the menu through the Alt key and searching for the menu manually there. I am using QtCreator 3.5.1 with Qt 5.5.1 (GCC 5.2.1 20151028, 64bit). I'm using the testing repository: deb http://ppa.launchpad.net/ci- train-ppa-service/landing-012/ubuntu xenial main to test Qt 5.5. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" $ uname -a Linux vitimiti-X200MA 4.2.0-17-generic #21-Ubuntu SMP Fri Oct 23 19:56:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ unity --version unity 7.3.2 If any more information is needed, I will add it up with no problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1513098/+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 1513098] Re: The global menu isn't working properly on QtCreator.
** Tags added: qt5.5 ** Changed in: appmenu-qt5 (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- 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/1513098 Title: The global menu isn't working properly on QtCreator. Status in appmenu-qt5 package in Ubuntu: New Bug description: The global menu appears properly at first. But, when I click on it, it disappears completely. Nevertheless, I still can access the menu through the Alt key and searching for the menu manually there. I am using QtCreator 3.5.1 with Qt 5.5.1 (GCC 5.2.1 20151028, 64bit). I'm using the testing repository: deb http://ppa.launchpad.net/ci- train-ppa-service/landing-012/ubuntu xenial main to test Qt 5.5. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" $ uname -a Linux vitimiti-X200MA 4.2.0-17-generic #21-Ubuntu SMP Fri Oct 23 19:56:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ unity --version unity 7.3.2 If any more information is needed, I will add it up with no problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1513098/+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 1436211] Re: Remove GTK3 from phone images
I think this might be best assigned to Bill first, possibly to Will later for the desktop splitting parts. ** Changed in: evolution-data-server (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: canonical-devices-system-image Assignee: Timo Jyrinki (timo-jyrinki) => Bill Filler (bfiller) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-asset-pool in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436211 Title: Remove GTK3 from phone images Status in Canonical System Image: In Progress Status in address-book-service package in Ubuntu: Confirmed Status in evolution-data-server package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Invalid Status in unity-asset-pool package in Ubuntu: Confirmed Status in evolution-data-server package in Debian: New Bug description: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. ===TODO=== -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? ===DONE=== -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436211/+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 1436211] Re: Remove GTK3 from phone images
@Pat: We'd need desktop team to do the splitting they've been thinking about. seb128 was talking about the evolution-data-server, thinking it's doable. Maybe Ken could look at the ubuntu-system-settings libtimezonemap dependency larsu mentioned in comment #6. After that there'd be the theme/artwork packages which could also fall into desktop team's hands, thinking about how to relax the dependencies or split packages so that they'd be usable on Touch without bringing GTK dependencies. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-asset-pool in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436211 Title: Remove GTK3 from phone images Status in Canonical System Image: In Progress Status in address-book-service package in Ubuntu: Confirmed Status in evolution-data-server package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Invalid Status in unity-asset-pool package in Ubuntu: Confirmed Status in evolution-data-server package in Debian: New Bug description: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. ===TODO=== -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? ===DONE=== -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436211/+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 1489037] Re: Change default alarm sound to "Alarm clock.ogg"
This needs a separate landing for the vivid branch (that has diverged from wily), the current silo only has the fix for wily. ** Also affects: indicator-datetime (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: indicator-datetime (Ubuntu RTM) Assignee: (unassigned) => Charles Kerr (charlesk) -- 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/1489037 Title: Change default alarm sound to "Alarm clock.ogg" Status in Canonical System Image: In Progress Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: New Bug description: With OTA-6 (as per bug 1354370), the default alarm sound has been changed from "Suru arpeggio.ogg" to "Alarm clock.ogg". Indicator- datetime will have to set this as default on its end. Note: Clock App will set "Alarm clock.ogg" as the default alarm sound for new alarms created by the user starting with clock app v3.5.362. This bug is to ensure that the fallback alarm played by indicator- datetime is also "Alarm clock.ogg" (which is used when the user sets an invalid alarm tone). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489037/+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()
The problem always seemed to me to be lower level problem than indicator-bluetooth. That is, when it happened there was BT problems in general. -- 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 1436211] Re: Remove GTK3 from phone images
** Description changed: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. - -- gnome-control-center-signon -- - Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? + ===TODO=== -- address-book-service -- - address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. + + address-book-service depends on evolution-data-server, which depends on + GTK3. evolution-data-server further depends on libgweather-3-6 and + libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita- icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? + + ===DONE=== + -- gnome-control-center-signon -- + Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-asset-pool in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436211 Title: Remove GTK3 from phone images Status in Canonical System Image: In Progress Status in address-book-service package in Ubuntu: Confirmed Status in evolution-data-server package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Invalid Status in unity-asset-pool package in Ubuntu: Confirmed Status in evolution-data-server package in Debian: New Bug description: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. ===TODO=== -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? ===DONE=== -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436211/+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 1437192] Re: FTBFS with Qt 5.5: cannot find -linput
** Changed in: appmenu-qt5 (Ubuntu) Importance: Undecided = High ** Branch linked: lp:~timo-jyrinki/appmenu-qt5/build_dep_libinput- dev_qt55 -- 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/1437192 Title: FTBFS with Qt 5.5: cannot find -linput Status in appmenu-qt5 package in Ubuntu: New Status in qtubuntu package in Ubuntu: Fix Released Bug description: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- That is, qtubuntu and appmenu-qt5 should apparently have a build dependency on 'libinput-dev': https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting appmenu-qt5: https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1437192/+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 1436211] Re: Remove GTK3 from phone images
As a related item, GTK2 was successfully dropped starting at http://people.canonical.com/~ogra/touch-image-stats/20150521.changes -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-asset-pool in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436211 Title: Remove GTK3 from phone images Status in the base for Ubuntu mobile products: Confirmed Status in address-book-service package in Ubuntu: New Status in evolution-data-server package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Invalid Status in unity-asset-pool package in Ubuntu: New Status in evolution-data-server package in Debian: New Bug description: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436211/+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 1437192] Re: FTBFS with Qt 5.5: cannot find -linput
** Summary changed: - qtubuntu fails to build against Qt 5.5 + FTBFS with Qt 5.5: cannot find -linput ** Also affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New ** Description changed: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- - That is, qtubuntu should apparently have a build dependecy on 'libinput- - dev': https://launchpad.net/ubuntu/+source/libinput + That is, qtubuntu and appmenu-qt5 should apparently have a build + dependency on 'libinput-dev': + https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting + + + appmenu-qt5: + https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz -- 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/1437192 Title: FTBFS with Qt 5.5: cannot find -linput Status in appmenu-qt5 package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- That is, qtubuntu and appmenu-qt5 should apparently have a build dependency on 'libinput-dev': https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting appmenu-qt5: https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1437192/+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 1436211] Re: Remove GTK3 from phone images
libaccount-plugin-1.0-0 removed from images with add_package in livecd- rootfs live-build config to explicitly pull ubuntu-system-settings- online-accounts instead of the first mentioned libaccount-plugin-google in a | dependency: http://people.canonical.com/~ogra/touch-image- stats/149.changes ** Changed in: gnome-control-center-signon (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-asset-pool in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436211 Title: Remove GTK3 from phone images Status in address-book-service package in Ubuntu: New Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Invalid Status in unity-asset-pool package in Ubuntu: New Bug description: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1436211/+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 1436211] [NEW] Remove GTK3 from phone images
Public bug reported: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita- icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? ** Affects: address-book-service (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-control-center-signon (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: Invalid ** Affects: unity-asset-pool (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: address-book-service (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. - Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would - it be possible to refactor it so that it would not depend on GTK3 - bringing it on the images? + -- gnome-control-center-signon -- + Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? + + -- address-book-service -- + address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. + + Would it be possible to work with libfolks-eds25 and other libraries + alone? Or would it be possible to modify evolution-data-server building + to not depend on GTK3 since we're not using the toolkit anyway? ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New = Invalid ** Also affects: unity-asset-pool (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? + + -- themes (unity-asset-pool) -- + + humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita- + icon-theme. adwaita-icon-theme directly depends on GTK3. ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? - -- themes (unity-asset-pool) -- + -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita- icon-theme. adwaita-icon-theme directly depends on GTK3. + + -- ubuntu-system-settings -- + + ubuntu-system-settings depends on libtimezonemap1 which
[Dx-packages] [Bug 1418505] Re: QT5.4: Ciboriums scanning sdcard message is deleted but the indicator never turns off
** Description changed: STEPS: 1. install vivid on krillin 2. Add silo 5 with citrain 3. Insert an sdcard 4. Clear the message from the indicator 5. Look at the indicator 6. Let the phone sleep EXPECTED: The same behaviour as in RTM and Vivid in the indicator is cleared ACTUAL: The messaging indicator stays light up and the led flashes when the phone sleeps. + + More information about using Qt 5.4 (targeted before Feature Freeze Feb + 19) at https://wiki.ubuntu.com/Touch/QtTesting -- 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/1418505 Title: QT5.4: Ciboriums scanning sdcard message is deleted but the indicator never turns off Status in indicator-messages package in Ubuntu: New Bug description: STEPS: 1. install vivid on krillin 2. Add silo 5 with citrain 3. Insert an sdcard 4. Clear the message from the indicator 5. Look at the indicator 6. Let the phone sleep EXPECTED: The same behaviour as in RTM and Vivid in the indicator is cleared ACTUAL: The messaging indicator stays light up and the led flashes when the phone sleeps. More information about using Qt 5.4 (targeted before Feature Freeze Feb 19) at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1418505/+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 1394887] [NEW] appmenu-qt5 fails to build against Qt 5.4.0 beta
Public bug reported: appmenu-qt5 fails to build against Qt 5.4.0 beta: https://launchpad.net/~canonical- qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing- archive-extra appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 'QKdeTheme::QKdeTheme(const QString, int)' : QKdeTheme(kdeHome, kdeVersion) More information about Qt testing versions at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: appmenu-qt5 Importance: Undecided Status: New ** Affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.4 ** Also affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New -- 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/1394887 Title: appmenu-qt5 fails to build against Qt 5.4.0 beta Status in Application menu for Qt5: New Status in “appmenu-qt5” package in Ubuntu: New Bug description: appmenu-qt5 fails to build against Qt 5.4.0 beta: https://launchpad.net/~canonical- qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing- archive-extra appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 'QKdeTheme::QKdeTheme(const QString, int)' : QKdeTheme(kdeHome, kdeVersion) More information about Qt testing versions at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1394887/+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 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
** Changed in: maliit-framework (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: appmenu-qt5 (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: qtubuntu Status: New = Fix Released ** Changed in: appmenu-qt5 Status: New = Fix Released -- 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/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: Fix Released Status in Qt integration with the Mir display server: Fix Released Status in QT Ubuntu: Fix Released Status in “appmenu-qt5” package in Ubuntu: Fix Released Status in “maliit-framework” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “qtubuntu” package in Ubuntu: Fix Released Status in Debian GNU/Linux: Won't Fix Status in “qtmir” package in Ubuntu RTM: Fix Released Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+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 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
** Changed in: qtbase-opensource-src (Ubuntu) Status: New = Fix Released -- 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/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Released Status in Mir 0.4 series: Won't Fix Status in Unity: New Status in “dbus-cpp” package in Ubuntu: Fix Released Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Fix Released Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: Fix Released Status in “unity-scopes-api” package in Ubuntu: Fix Released Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+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 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
I don't think this B) option has any impact other than the 80kB library appearing on rootfs and the need to add the build dependency in affected packages. This is already done in the Qt 5.3.2 landing PPA. The mtdev is only used if evdev input driver is in use, ie. this can improve multi touch on desktop but does not affect the phone. -- 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/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: New Status in Qt integration with the Mir display server: New Status in QT Ubuntu: New Status in “appmenu-qt5” package in Ubuntu: New Status in “maliit-framework” package in Ubuntu: New Status in “qtmir” package in Ubuntu: In Progress Status in “qtubuntu” package in Ubuntu: New Status in Debian GNU/Linux: Won't Fix Status in “qtmir” package in Ubuntu RTM: In Progress Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+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 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
** Description changed: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- - This comes from QPlatformSupport stuff which creates a static library that - needs this linking. + This comes from QPlatformSupport stuff which creates a static library that needs this linking. - It also happens that QPlatformSupport is private stuff, so there is really no - way to solve this but either stop using private stuff or helping upstream to - make QPlatformSupport public (which would be really helpful). This will in - turn mean that it will become a dynamic lib and this bug can be fixed. + It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. -- 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/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: New Status in Qt integration with the Mir display server: New Status in QT Ubuntu: New Status in “appmenu-qt5” package in Ubuntu: New Status in “maliit-framework” package in Ubuntu: New Status in “qtmir” package in Ubuntu: New Status in “qtubuntu” package in Ubuntu: New Status in Debian GNU/Linux: Won't Fix Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+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 1323853] Re: No menubar for QtQuick.Controls based applications
** Also affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New -- 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/1323853 Title: No menubar for QtQuick.Controls based applications Status in Application menu for Qt5: New Status in “appmenu-qt5” package in Ubuntu: Confirmed Bug description: For QtQuick.Controls based applications no menubars are shown. The following message is printed to the console instead: appmenu-qt: handleReparent 128 The given QWindow has no QMenuBar assigned Apparently this is because QtQuick.Controls menus are built upon QQuickMenuBar and QGuiApplicationPrivate::platformTheme()-createPlatformMenuBar(); instead of QMenuBar. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1323853/+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 1357311] Re: Datetime indicator no longer shows events
** Tags added: lt-blocker lt-category-visible lt-prio-high -- 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/1357311 Title: Datetime indicator no longer shows events Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Since #189 the datetime indicator shows no events at all inside the pull-down from i-d. See screenshot Split into two bugs, related: bug 1357307 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1357311/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** 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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Status in “qtbase-opensource-src” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Invalid Status in “xorg-server” source package in Trusty: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
qtbase 5.2.1+dfsg-1ubuntu14.2 SRU for trusty is in unapproved queue now too (https://launchpad.net/ubuntu/trusty/+queue?queue_state=1queue_text=) -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Status in “qtbase-opensource-src” source package in Trusty: In Progress Status in “unity” source package in Trusty: Invalid Status in “xorg-server” source package in Trusty: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Also affects: xorg-server (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: qtbase-opensource-src (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu Trusty) Status: New = In Progress ** Changed in: qtbase-opensource-src (Ubuntu Trusty) Importance: Undecided = High ** Changed in: qtbase-opensource-src (Ubuntu Trusty) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: unity (Ubuntu Trusty) Status: New = Invalid -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Status in “qtbase-opensource-src” source package in Trusty: In Progress Status in “unity” source package in Trusty: Invalid Status in “xorg-server” source package in Trusty: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
It seems the automated message did not reach here. The updated version is now in proposed: https://launchpad.net/ubuntu/trusty/+source/unity/7.2.0+14.04.20140423-0ubuntu1 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! ** Tags added: verification-needed -- 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/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: New Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1287580] Re: hud docs fail tests with gtk-doc 1.20
** Changed in: hud Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1287580 Title: hud docs fail tests with gtk-doc 1.20 Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: Building hud fails currently, and I've tracked it down to gtk-doc update to 1.20 two weeks ago. The failure is shown as (output cut a bit): --- 7/9 Test #7: doc-libhud-check ..***Failed0.03 sec E: 1 unused documentation entries 75.0%: Checks 4, Failures: 1 Start 8: doc-libhud-client-check 8/9 Test #8: doc-libhud-client-check ...***Failed0.03 sec E: 3 undocumented or incomplete symbols 75.0%: Checks 4, Failures: 1 Start 9: doc-libhud-gtk-check 9/9 Test #9: doc-libhud-gtk-check ..***Failed0.03 sec E: 1 undocumented or incomplete symbols 50.0%: Checks 4, Failures: 2 67% tests passed, 3 tests failed out of 9 --- Downgrading to https://launchpad.net/ubuntu/+source/gtk- doc/1.19-1ubuntu1 fixes the issue. I've only tested this with Qt 5.2 installed, but I assume it'd fail to build in the archive too currently. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1287580/+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 1287580] Re: hud docs fail tests with gtk-doc 1.20
** Changed in: hud (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1287580 Title: hud docs fail tests with gtk-doc 1.20 Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: Fix Committed Bug description: Building hud fails currently, and I've tracked it down to gtk-doc update to 1.20 two weeks ago. The failure is shown as (output cut a bit): --- 7/9 Test #7: doc-libhud-check ..***Failed0.03 sec E: 1 unused documentation entries 75.0%: Checks 4, Failures: 1 Start 8: doc-libhud-client-check 8/9 Test #8: doc-libhud-client-check ...***Failed0.03 sec E: 3 undocumented or incomplete symbols 75.0%: Checks 4, Failures: 1 Start 9: doc-libhud-gtk-check 9/9 Test #9: doc-libhud-gtk-check ..***Failed0.03 sec E: 1 undocumented or incomplete symbols 50.0%: Checks 4, Failures: 2 67% tests passed, 3 tests failed out of 9 --- Downgrading to https://launchpad.net/ubuntu/+source/gtk- doc/1.19-1ubuntu1 fixes the issue. I've only tested this with Qt 5.2 installed, but I assume it'd fail to build in the archive too currently. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1287580/+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 1287580] Re: hud docs fail tests with gtk-doc 1.20
In the landing PPA now https://launchpad.net/~ci-train-ppa- service/+archive/landing-006/+packages ** Changed in: hud Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1287580 Title: hud docs fail tests with gtk-doc 1.20 Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: New Bug description: Building hud fails currently, and I've tracked it down to gtk-doc update to 1.20 two weeks ago. The failure is shown as (output cut a bit): --- 7/9 Test #7: doc-libhud-check ..***Failed0.03 sec E: 1 unused documentation entries 75.0%: Checks 4, Failures: 1 Start 8: doc-libhud-client-check 8/9 Test #8: doc-libhud-client-check ...***Failed0.03 sec E: 3 undocumented or incomplete symbols 75.0%: Checks 4, Failures: 1 Start 9: doc-libhud-gtk-check 9/9 Test #9: doc-libhud-gtk-check ..***Failed0.03 sec E: 1 undocumented or incomplete symbols 50.0%: Checks 4, Failures: 2 67% tests passed, 3 tests failed out of 9 --- Downgrading to https://launchpad.net/ubuntu/+source/gtk- doc/1.19-1ubuntu1 fixes the issue. I've only tested this with Qt 5.2 installed, but I assume it'd fail to build in the archive too currently. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1287580/+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 907640] Re: alt-backtick doesn't work properly
Jeffrey, you're correct regarding metacity if the same problem is seen outside of unity-2d, so the bug should be valid for trusty even though there are now fewer environments using it. I think ideally metacity would be in universe, but it's still depended upon by compiz packaging wise. ** Changed in: metacity (Ubuntu Trusty) Status: Invalid = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/907640 Title: alt-backtick doesn't work properly Status in Ayatana Design: New Status in The Metacity Window Manager: New Status in “metacity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Invalid Status in “metacity” source package in Precise: Triaged Status in “unity-2d” source package in Precise: Triaged Status in “metacity” source package in Trusty: Triaged Status in “unity-2d” source package in Trusty: Invalid Bug description: In Unity (and I presume unity-2d) alt-backtick (alt-grave, alt-key- above-tab) is meant to flip between the active windows of the current application. In precise unity-2d for me it shows a switcher window with 4 icons for the four windows of my current app (chrome), but repeated presses of backtick while holding alt just flip between the focussed window and the next window, not around all four. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 4.12.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5 Uname: Linux 3.2.0-5-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Dec 22 16:23:53 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) PackageArchitecture: all SourcePackage: unity-2d UpgradeStatus: Upgraded to precise on 2011-12-15 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+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 907640] Re: alt-backtick doesn't work properly
And... Thanks! I've built and successfully tested the patched metacity on trusty at ppa:timo-jyrinki/ppa :) I installed gnome-session-fallback, and with the patched metacity I was able to use alt-grave to switch between 3+ same windows (similar to Compiz/Unity), unlike without the patch. I also tested a few combinations of different apps, and I didn't find anything to complain. Debdiff looked good too. ** Branch linked: lp:~timo-jyrinki/metacity/ubuntu_fix_lp907640 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/907640 Title: alt-backtick doesn't work properly Status in Ayatana Design: New Status in The Metacity Window Manager: New Status in “metacity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Invalid Status in “metacity” source package in Precise: Triaged Status in “unity-2d” source package in Precise: Triaged Status in “metacity” source package in Trusty: Triaged Status in “unity-2d” source package in Trusty: Invalid Bug description: In Unity (and I presume unity-2d) alt-backtick (alt-grave, alt-key- above-tab) is meant to flip between the active windows of the current application. In precise unity-2d for me it shows a switcher window with 4 icons for the four windows of my current app (chrome), but repeated presses of backtick while holding alt just flip between the focussed window and the next window, not around all four. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 4.12.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5 Uname: Linux 3.2.0-5-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Dec 22 16:23:53 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) PackageArchitecture: all SourcePackage: unity-2d UpgradeStatus: Upgraded to precise on 2011-12-15 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+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 1244704] Re: Some test_hud tests fail on trusty desktop
This seems improved now. I filed a new bug of the remaining/new autopilot failures in cu2d in bug #1276569 -- 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/1244704 Title: Some test_hud tests fail on trusty desktop Status in Unity HUD: Invalid Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Last daily release run revealed several autopilot failures in the HUD stack, high above our threshold. Those are blocking the release of the HUD stack. The failures are as follows: unity.tests.test_hud.HudBehaviorTests.test_closes_then_focuses_window_on_mouse_down unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Monitor 1,Launcher autohide) unity.tests.test_hud.HudVisualTests.test_hud_icon_shows_the_focused_application_emblem(Monitor 0,Launcher autohide,Launcher on primary monitor) unity.tests.test_hud.HudVisualTests.test_hud_icon_is_shown(Monitor 1,Launcher autohide,Launcher on all monitors) unity.tests.test_hud.HudBehaviorTests.test_mouse_changes_selected_hud_button unity.tests.test_hud.HudBehaviorTests.test_keyboard_steals_focus_from_mouse unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Single Monitor,Launcher never hide) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) Not all happened on both machines at once. Some tests might be flacky on trusty right now. It is unrelated to autopilot 1.4 as we are still using autopilot 1.3 for this run. No public jenkins instance available yet: http://10.97.0.1:8080/job/autopilot-trusty-daily_release/104/ To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1244704/+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 1244704] Re: Some test_hud tests fail on trusty desktop
Kicked a new daily build of the unity stack. After that, rerunning the HUD stack's tests could yield the results. -- 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/1244704 Title: Some test_hud tests fail on trusty desktop Status in Unity HUD: Invalid Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Last daily release run revealed several autopilot failures in the HUD stack, high above our threshold. Those are blocking the release of the HUD stack. The failures are as follows: unity.tests.test_hud.HudBehaviorTests.test_closes_then_focuses_window_on_mouse_down unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Monitor 1,Launcher autohide) unity.tests.test_hud.HudVisualTests.test_hud_icon_shows_the_focused_application_emblem(Monitor 0,Launcher autohide,Launcher on primary monitor) unity.tests.test_hud.HudVisualTests.test_hud_icon_is_shown(Monitor 1,Launcher autohide,Launcher on all monitors) unity.tests.test_hud.HudBehaviorTests.test_mouse_changes_selected_hud_button unity.tests.test_hud.HudBehaviorTests.test_keyboard_steals_focus_from_mouse unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Single Monitor,Launcher never hide) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) Not all happened on both machines at once. Some tests might be flacky on trusty right now. It is unrelated to autopilot 1.4 as we are still using autopilot 1.3 for this run. No public jenkins instance available yet: http://10.97.0.1:8080/job/autopilot-trusty-daily_release/104/ To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1244704/+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 1243654] Re: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId()
** Description changed: + SRU for saucy. + + [Impact] + + A crash in certain situations. + + [Test Case] + + A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting + this. + + [Regression Potential] + + Low, a null safe guard added in three places. + ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-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-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Wed Oct 23 13:44:21 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge InstallationDate: Installed on 2012-11-10 (346 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge SegvAnalysis: Segfault happened at: 0x409b70 _ZN10BamfWindow8windowIdEv: mov 0x24(%rdi),%eax PC (0x00409b70) ok source 0x24(%rdi) (0x0024) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: BamfWindow::windowId() () BamfWindowStack::ActiveWindowChanged(QString const, QString const) () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 OrgAyatanaBamfMatcherInterface::ActiveWindowChanged(QString const, QString const) () Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() UpgradeStatus: Upgraded to saucy on 2013-10-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo upstart.hud.log: (process:1812): hudapplicationsource-WARNING **: Unable to export application 'python2' skeleton on path '/com/canonical/hud/applications/python2': An object is already exported for the interface com.canonical.hud.Application at /com/canonical/hud/applications/python2 upstart.window-stack-bridge.log: Could not get desktop file for /org/ayatana/bamf/window/75497480 -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1243654 Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: New Bug description: SRU for saucy. [Impact] A crash in certain situations. [Test Case] A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting this. [Regression Potential] Low, a null safe guard added in three places. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-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-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Wed Oct 23 13:44:21 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge InstallationDate: Installed on 2012-11-10 (346 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge SegvAnalysis: Segfault happened at: 0x409b70 _ZN10BamfWindow8windowIdEv: mov 0x24(%rdi),%eax PC (0x00409b70) ok source 0x24(%rdi) (0x0024) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: BamfWindow::windowId() () BamfWindowStack::ActiveWindowChanged(QString const, QString const) () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 OrgAyatanaBamfMatcherInterface::ActiveWindowChanged(QString const, QString const) () Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() UpgradeStatus: Upgraded to saucy on 2013-10-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo upstart.hud.log: (process:1812): hudapplicationsource-WARNING **: Unable to export application 'python2' skeleton on path '/com/canonical/hud/applications/python2': An object is already exported for the interface com.canonical.hud.Application at /com/canonical/hud/applications/python2 upstart.window-stack-bridge.log: Could not get desktop file for /org/ayatana/bamf/window/75497480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1243654/+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 1244688] Re: /usr/lib/i386-linux-gnu/hud/hud-service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call
** Description changed: + SRU for saucy. + + [Impact] + + A reported crash in certain situations. + + [Test Case] + + A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting + this. + + [Regression Potential] + + Low, doing graceful exiting instead of abort. + The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/23bafefb567e15de49e41a1fda7e468768652425 contains more details. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1244688 Title: /usr/lib/i386-linux-gnu/hud/hud- service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: New Bug description: SRU for saucy. [Impact] A reported crash in certain situations. [Test Case] A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting this. [Regression Potential] Low, doing graceful exiting instead of abort. The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/23bafefb567e15de49e41a1fda7e468768652425 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1244688/+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 1217598] Re: Another test failure
** Description changed: Another test failure is blocking quaternourly release: https://launchpadlibrarian.net/148572571/buildlog_ubuntu-saucy-amd64 .indicator- messages_13.10.1%2B13.10.20130827.6-0ubuntu1_FAILEDTOBUILD.txt.gz + + Related ones?: + + https://launchpadlibrarian.net/148595897/buildlog_ubuntu-saucy- + amd64.qmenumodel_0.2.7%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz + + https://launchpadlibrarian.net/148596254/buildlog_ubuntu-saucy-amd64 + .indicator-network_0.5.0%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz + + There was a big apparmor update yesterday + https://lists.ubuntu.com/archives/saucy-changes/2013-August/009007.html ** Summary changed: - Another test failure + Test failure in indicators stack ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Also affects: qmenumodel (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Critical ** Changed in: qmenumodel (Ubuntu) Importance: Undecided = Critical ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Importance: Undecided = Critical ** Summary changed: - Test failure in indicators stack + Multiple test failures in indicators stack ** Description changed: Another test failure is blocking quaternourly release: https://launchpadlibrarian.net/148572571/buildlog_ubuntu-saucy-amd64 .indicator- messages_13.10.1%2B13.10.20130827.6-0ubuntu1_FAILEDTOBUILD.txt.gz Related ones?: https://launchpadlibrarian.net/148595897/buildlog_ubuntu-saucy- amd64.qmenumodel_0.2.7%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz https://launchpadlibrarian.net/148596254/buildlog_ubuntu-saucy-amd64 .indicator-network_0.5.0%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz - There was a big apparmor update yesterday + There were big apparmor and dbus updates yesterday https://lists.ubuntu.com/archives/saucy-changes/2013-August/009007.html ** Description changed: Another test failure is blocking quaternourly release: https://launchpadlibrarian.net/148572571/buildlog_ubuntu-saucy-amd64 .indicator- messages_13.10.1%2B13.10.20130827.6-0ubuntu1_FAILEDTOBUILD.txt.gz Related ones?: https://launchpadlibrarian.net/148595897/buildlog_ubuntu-saucy- amd64.qmenumodel_0.2.7%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz https://launchpadlibrarian.net/148596254/buildlog_ubuntu-saucy-amd64 .indicator-network_0.5.0%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz There were big apparmor and dbus updates yesterday https://lists.ubuntu.com/archives/saucy-changes/2013-August/009007.html + + https://lists.ubuntu.com/archives/saucy- + changes/2013-August/009008.html ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Changed in: dbus (Ubuntu) Importance: Undecided = Critical ** Description changed: - Another test failure is blocking quaternourly release: + Another test failure is blocking quaternourly release of indicators + + unity stacks: https://launchpadlibrarian.net/148572571/buildlog_ubuntu-saucy-amd64 .indicator- messages_13.10.1%2B13.10.20130827.6-0ubuntu1_FAILEDTOBUILD.txt.gz Related ones?: https://launchpadlibrarian.net/148595897/buildlog_ubuntu-saucy- amd64.qmenumodel_0.2.7%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz https://launchpadlibrarian.net/148596254/buildlog_ubuntu-saucy-amd64 .indicator-network_0.5.0%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz There were big apparmor and dbus updates yesterday https://lists.ubuntu.com/archives/saucy-changes/2013-August/009007.html + https://lists.ubuntu.com/archives/saucy- changes/2013-August/009008.html -- 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/1217598 Title: Multiple test failures in indicators stack Status in “apparmor” package in Ubuntu: New Status in “dbus” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: New Status in “indicator-network” package in Ubuntu: New Status in “qmenumodel” package in Ubuntu: New Bug description: Another test failure is blocking quaternourly release of indicators + unity stacks: https://launchpadlibrarian.net/148572571/buildlog_ubuntu-saucy-amd64 .indicator- messages_13.10.1%2B13.10.20130827.6-0ubuntu1_FAILEDTOBUILD.txt.gz Related ones?: https://launchpadlibrarian.net/148595897/buildlog_ubuntu-saucy- amd64.qmenumodel_0.2.7%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz https://launchpadlibrarian.net/148596254/buildlog_ubuntu-saucy-amd64 .indicator- network_0.5.0%2B13.10.20130828-0ubuntu1_FAILEDTOBUILD.txt.gz There were big apparmor and dbus updates yesterday https://lists.ubuntu.com/archives/saucy- changes/2013-August/009007.html +
[Dx-packages] [Bug 1215180] Re: Deprecated method call causes failing quaternourly release.
Hud built now successfully with Antti's fix. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1215180 Title: Deprecated method call causes failing quaternourly release. Status in “hud” package in Ubuntu: In Progress Status in “indicator-messages” package in Ubuntu: In Progress Bug description: indicator-messages has failed to build, blocking the indicator stack from releasing. Here is the build log: http://paste.ubuntu.com/6012072/ Looks like these failures are caused by an upstream API change; please update the code to the latest non-deprecated standards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1215180/+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
