[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7
** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: In Progress Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: In Progress Status in unity-gtk-module source package in Xenial: In Progress Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package mediaplayer-app - 0.20.5+17.04.20161124.1-0ubuntu1 --- mediaplayer-app (0.20.5+17.04.20161124.1-0ubuntu1) zesty; urgency=medium * Use platform content share. (LP: #1629009) * Run on desktop mode when running on untiy8 snap session. -- Renato Araujo Oliveira FilhoThu, 24 Nov 2016 18:54:49 + ** Changed in: mediaplayer-app (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-transfer in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: Fix Released Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package messaging-app - 0.1+17.04.20161124.2-0ubuntu1 --- messaging-app (0.1+17.04.20161124.2-0ubuntu1) zesty; urgency=medium * Append "SNAP" path into the base application path, when that var is set. (LP: #1629009) -- Renato Araujo Oliveira FilhoThu, 24 Nov 2016 18:55:09 + -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-transfer in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: Fix Released Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package dialer-app - 0.1+17.04.20161124-0ubuntu1 --- dialer-app (0.1+17.04.20161124-0ubuntu1) zesty; urgency=medium * Append "SNAP" path into the base application path, when that var is set. (LP: #1629009) -- Renato Araujo Oliveira FilhoThu, 24 Nov 2016 18:54:52 + ** Changed in: dialer-app (Ubuntu) Status: In Progress => Fix Released ** Changed in: messaging-app (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-transfer in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: Fix Released Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package address-book-service - 0.1.2+17.04.20161124.1-0ubuntu1 --- address-book-service (0.1.2+17.04.20161124.1-0ubuntu1) zesty; urgency=medium [ Michael Terry ] * Handle running inside of a snap by respecting the $SNAP variable and not using hard coded paths. (LP: #1629009) [ Renato Araujo Oliveira Filho ] * Use the service as DBUS activated. -- Renato Araujo Oliveira FilhoThu, 24 Nov 2016 18:54:54 + -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-transfer in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: In Progress Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: In Progress Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: In Progress Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package address-book-app - 0.2+17.04.20161124.2-0ubuntu1 --- address-book-app (0.2+17.04.20161124.2-0ubuntu1) zesty; urgency=medium * Use 'SNAP_PATH' to import files if available. (LP: #1629009) -- Renato Araujo Oliveira FilhoThu, 24 Nov 2016 18:54:55 + ** Changed in: address-book-service (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-transfer in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: In Progress Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: In Progress Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: In Progress Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package gallery-app - 0.0.67+17.04.20161129-0ubuntu1 --- gallery-app (0.0.67+17.04.20161129-0ubuntu1) zesty; urgency=medium * Set Import dir based on "SNAP" env var. (LP: #1629009) * Make use of ubuntu-app-platform. -- Renato Araujo Oliveira FilhoTue, 29 Nov 2016 18:42:11 + ** Changed in: gallery-app (Ubuntu) Status: In Progress => Fix Released ** Changed in: address-book-app (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-transfer in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: In Progress Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: In Progress Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: In Progress Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7
** Description changed: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. + /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - + before unity-gtk-module.conf is started - so dbus activated services + miss the GTK_MODULES environment variable. Update unity-gtk-module.conf + to set it in the dbus activation environment. + [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. + + Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user- session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user- session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Confirmed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: In Progress Status in unity-gtk-module source package in Xenial: In Progress Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7
Both uploaded. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Confirmed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: In Progress Status in unity-gtk-module source package in Xenial: In Progress Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7
unity-gtk-module needs to update the systemd environment now too ** Description changed: + [ Description ] + + In Xenial, when dbus-user-session is installed, dbus' upstart job still + starts a new bus. Things get confused about which bus to talk to. + + [ Fix ] + + Already fixed in Yakkety. Cherry-pick the upstart job. On top of + Yakkety's version, call `dbus-update-activation-environment --verbose + --systemd GTK_MODULES', because Xenial does not have the change in + upstart to automatically publish to the systemd activation environment. + + [ QA ] + + Install dbus-user-session, press print screen. It should be delayed if + you are experiencing this bug, and not delayed otherwise. + + Remove dbus-user-session, make sure the session still works properly - + the global menu works, everything launches properly, etc. + + [ Regression potential ] + + This change alters the way that the session bus is launched, even if you + aren't using dbus-user-session. Even though this same change is deployed + in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user- + session by default, so the case where you don't have it isn't as well + tested. I would suggest focusing some testing on the non dbus-user- + session case. + + [ Original report ] + After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop ** Also affects: unity-gtk-module (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-gtk-module (Ubuntu) Status: New => Fix Released ** Changed in: unity-gtk-module (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Confirmed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: In Progress Status in unity-gtk-module source package in Xenial: In Progress Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
** Tags removed: verification-neededd ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: Fix Committed Status in ido source package in Yakkety: Fix Committed Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
As xenial-release and yakkety-release have the same ido version, I forward-copied the xenial SRU to yakkety. This needs to be verified too, so that both can eventually be released. Otherwise x would have a higher version than y. ** Also affects: ido (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: ido (Ubuntu Yakkety) Status: New => Fix Committed ** Tags removed: verification-done wily ** Tags added: verification-done-xenial verification-neededd -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: Fix Committed Status in ido source package in Yakkety: Fix Committed Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp