[Dx-packages] [Bug 1915695] Re: [MIR] libayatana-appindicator
** Changed in: libayatana-appindicator (Ubuntu) Status: New => Fix Committed ** Changed in: libayatana-appindicator (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to a duplicate bug report (1770146). https://bugs.launchpad.net/bugs/1915695 Title: [MIR] libayatana-appindicator Status in libayatana-appindicator package in Ubuntu: Fix Committed Bug description: * Availability It's available on the Ubuntu supported architectures https://launchpad.net/ubuntu/+source/libayatana-appindicator/0.5.5-2 The package is in sync with Debian * Rationale The source is a community maintained replacement for our current libappindicator. Debian has transitioned and we plan to follow their lead now, demoting libappindicator to universe until we can remove it from the archive. The binary to promote is libappindicator3-1 The request is low priority, it's a target of opportunity transition, it doesn't need to land this cycle * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libayatana-appindicator https://people.canonical.com/~ubuntu-security/cve/pkg/libayatana-appindicator.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libayatana-appindicator * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libayatana-appindicator/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libayatana-appindicator The source depends on some outdated libraries but that's because there are still old applications needing it, that's already the case with our libappindicator so not a change of status The package enables upstream tests during the build but some are currently failing (and the Debian package doesn't stop the build on errors), that has been reported to Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982845 and needs to be resolved before promotion The package doesn't provide autopkgtests, which has been reported to Debian . That's not a regression compared to our current libappindicator Update, the tests issue has been resolved in Debian and Impish now * Dependencies Package: libayatana-appindicator3-1 Depends: libayatana-indicator3-7 (>= 0.6.0), libc6 (>= 2.4), libdbusmenu-glib4 (>= 0.4.2), libdbusmenu-gtk3-4 (>= 0.4.2), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.0.0) libayatana-indicator3-7 is currently in universe and bug #1915693 * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and desktop team is going to sign up for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1915695/+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 1915695] Re: [MIR] libayatana-appindicator
Thanks for looking into those, MIR ack for me then! Feel free to promote once desktop-packages is subscribed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to a duplicate bug report (1770146). https://bugs.launchpad.net/bugs/1915695 Title: [MIR] libayatana-appindicator Status in libayatana-appindicator package in Ubuntu: New Bug description: * Availability It's available on the Ubuntu supported architectures https://launchpad.net/ubuntu/+source/libayatana-appindicator/0.5.5-2 The package is in sync with Debian * Rationale The source is a community maintained replacement for our current libappindicator. Debian has transitioned and we plan to follow their lead now, demoting libappindicator to universe until we can remove it from the archive. The binary to promote is libappindicator3-1 The request is low priority, it's a target of opportunity transition, it doesn't need to land this cycle * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libayatana-appindicator https://people.canonical.com/~ubuntu-security/cve/pkg/libayatana-appindicator.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libayatana-appindicator * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libayatana-appindicator/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libayatana-appindicator The source depends on some outdated libraries but that's because there are still old applications needing it, that's already the case with our libappindicator so not a change of status The package enables upstream tests during the build but some are currently failing (and the Debian package doesn't stop the build on errors), that has been reported to Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982845 and needs to be resolved before promotion The package doesn't provide autopkgtests, which has been reported to Debian . That's not a regression compared to our current libappindicator Update, the tests issue has been resolved in Debian and Impish now * Dependencies Package: libayatana-appindicator3-1 Depends: libayatana-indicator3-7 (>= 0.6.0), libc6 (>= 2.4), libdbusmenu-glib4 (>= 0.4.2), libdbusmenu-gtk3-4 (>= 0.4.2), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.0.0) libayatana-indicator3-7 is currently in universe and bug #1915693 * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and desktop team is going to sign up for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1915695/+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 1770146] Re: [MIR] libayatana-appindicator
See https://bugs.launchpad.net/ubuntu/+source/libayatana- appindicator/+bug/1770146/comments/14. This is still invalid. Please don't reopen without a new rationale. ** Changed in: libayatana-appindicator (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1770146 Title: [MIR] libayatana-appindicator Status in libayatana-appindicator package in Ubuntu: Invalid Bug description: [Availability] * Everywhere [Rationale] * Appindicator is dead, we should move it to universe and switch to the "better" and "supported" ayatana version [Security] * No security bugs found [Quality assurance] * Strongly maintained in Debian, lots of packages in main used to have deltas to drop and switch to appindicator, I think we will save a lot of work by just syncing stuff and not maintaining appindicator anymore (at least moving it to universe) [Dependencies] * All deps in main [Standards compliance] * New compat level * Maintained in sync with Debian * It builds a python2 bind, maybe we can just not MIR all binaries there [Maintenance] * Debian maintains it, and is doing a port to ayatana of all packages. [Background information] * I think we can also just MIR libayatana-appindicator3-1 reverse-depends -c main src:libappindicator -r cosmic Reverse-Depends === * network-manager-gnome (for libappindicator3-1) * remmina (for libappindicator3-1) * transmission-gtk (for libappindicator3-1) all the three packages are now using ayatana in -proposed pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1770146/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Sure, will have a look on the directory creation permission -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in d-conf package in Ubuntu: New Status in gnome-session package in Ubuntu: Triaged Status in session-migration package in Ubuntu: Confirmed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1735929/+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 1718615] Re: Nux doesn't build proprerly in s390x arch
Removing packages from artful: libnux-4.0-0 4.0.8+17.04.20170213-0ubuntu1 in artful s390x libnux-4.0-dev 4.0.8+17.04.20170213-0ubuntu1 in artful s390x libunity-core-6.0-9 7.5.0+17.10.20170721.1-0ubuntu1 in artful s390x libunity-core-6.0-dev 7.5.0+17.10.20170721.1-0ubuntu1 in artful s390x unity 7.5.0+17.10.20170721.1-0ubuntu1 in artful s390x unity-lens-video 0.3.15+16.04.20160212.1-0ubuntu2 in artful s390x unity-lens-music 6.9.1+16.04-0ubuntu2 in artful s390x unity-lens-files 7.1.0+17.10.20170605-0ubuntu1 in artful s390x unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2 in artful s390x unity-china-music-scope 1.0.8-0ubuntu1 in artful s390x Comment: desktop isn't a target for s390x Bug #1718615 Remove [y|N]? y ** Changed in: nux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1718615 Title: Nux doesn't build proprerly in s390x arch Status in nux package in Ubuntu: Fix Released Bug description: This is due to some tests segfaulting because of impossible-to-debug (for me) issues, so it's quite safe to remove it from the archive. libnux-4.0-0 libnux-4.0-dev libunity-core-6.0-9 libunity-core-6.0-dev unity unity-lens-video unity-lens-music unity-lens-files unity-lens-applications unity-china-music-scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1718615/+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 1711085] Re: battery icon is distorded under GNOME Shell
We discussed it a couple of times with seb on #ubuntu-desktop in the past week and the current approach is to prefix icons name with unity- and have indicator-power loading them in priority. Please refrain modifying bugs that are opened for tracking without talking on IRC. This is the second time and give additional work as I have now to remove the additional components (gnome-shell and unity) you added… ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1711085 Title: battery icon is distorded under GNOME Shell Status in indicator-power package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Even if https://bugs.launchpad.net/ubuntu/+source/ubuntu- themes/+bug/1693155 is fixed, the icon is still distorded in non Hi- DPI environment. The issue is that the icons aren't really square. Let's use the upstrema indicator icons, while still preserving them in the Unity session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1711085/+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 1711085] Re: battery icon is distorded under GNOME Shell
Let's use that proven path for now and revisit later on, shall we? :) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1711085 Title: battery icon is distorded under GNOME Shell Status in indicator-power package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Even if https://bugs.launchpad.net/ubuntu/+source/ubuntu- themes/+bug/1693155 is fixed, the icon is still distorded in non Hi- DPI environment. The issue is that the icons aren't really square. Let's use the upstrema indicator icons, while still preserving them in the Unity session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1711085/+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 1698795] Re: Humanity should provide symbolic versions of custom icons for GNOME Shell
For now, let's use in the ubuntu session non symbolic icons: - our theme doesn't support them and there are few changes we'll have app symbolic icons for our default applications in 17.10. - for coherence reasons: most of branded apps outside of GNOME (firefox, chrome, thunderbird) don't have symbolic icons, and so, will appear colorized. Shipping two different experiences in the same session is weird. Let's ensure the ubuntu session don't use them by default thus. -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1698795 Title: Humanity should provide symbolic versions of custom icons for GNOME Shell Status in Ubuntu theme: New Status in gnome-shell package in Ubuntu: New Status in humanity-icon-theme package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: The app icon in top panel next to application menu entry is the default adwaita icons and don't match the current theming. It's either: - the fact that we don't provide the correct icon size in our themes, and so, the icons are defaulted - a bug in G-S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1698795/+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 1521208] Re: Disable Online Search by default in Unity 7 Dash
** No longer affects: unity ** Changed in: unity-lens-music Status: Triaged => Fix Released ** Changed in: libunity Status: Triaged => Fix Released ** Changed in: libunity (Ubuntu) Status: Triaged => Fix Committed ** Changed in: unity-lens-music (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1521208 Title: Disable Online Search by default in Unity 7 Dash Status in libunity: Fix Released Status in Music Lens: Fix Released Status in libunity package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Triaged Status in unity-lens-music package in Ubuntu: Fix Committed Status in unity-scope-audacious package in Ubuntu: Triaged Status in unity-scope-clementine package in Ubuntu: Triaged Status in unity-scope-gmusicbrowser package in Ubuntu: Triaged Status in unity-scope-gourmet package in Ubuntu: Triaged Status in unity-scope-guayadeque package in Ubuntu: Triaged Status in unity-scope-musique package in Ubuntu: Triaged Bug description: We have decided to disable online search results in the dash by default. Changes needed are as follows: 1. "Include online search results" from Security & Privacy in Systems Settings should be OFF by default. 2. Amazon & Skimlinks to remain off by default and search results to not be generated without explicitly turning on those filters. 3. Music store option to be fully removed in 16.04 and beyond. I'll take advice on what the best option is for older supported releases. 4. The following scopes to be moved to Universe: * Audacious * Clementine * gmusicbrowser * Gourmet * Guayadeque * Musique (note: unity-scope-musique) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1521208/+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 1521208] Re: Disable Online Search by default in Unity 7 Dash
Scopes are not recommended anymore by unity, demote them to universe: $ ./change-override -c universe -S unity-scope-audacious unity-scope-clementine unity-scope-gmusicbrowser unity-scope-gourmet unity-scope-guayadeque unity-scope-musique Override component to universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial: main/gnome -> universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial amd64: main/gnome/optional/100% -> universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial arm64: main/gnome/optional/100% -> universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial armhf: main/gnome/optional/100% -> universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial i386: main/gnome/optional/100% -> universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial powerpc: main/gnome/optional/100% -> universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial ppc64el: main/gnome/optional/100% -> universe unity-scope-audacious 0.1+13.10.20130927.1-0ubuntu1 in xenial s390x: main/gnome/optional/100% -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial: main/gnome -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial amd64: main/gnome/optional/100% -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial arm64: main/gnome/optional/100% -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial armhf: main/gnome/optional/100% -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial i386: main/gnome/optional/100% -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial powerpc: main/gnome/optional/100% -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial ppc64el: main/gnome/optional/100% -> universe unity-scope-clementine 0.1+13.10.20130723-0ubuntu1 in xenial s390x: main/gnome/optional/100% -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial: main/gnome -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial amd64: main/gnome/optional/100% -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial arm64: main/gnome/optional/100% -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial armhf: main/gnome/optional/100% -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial i386: main/gnome/optional/100% -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial powerpc: main/gnome/optional/100% -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial ppc64el: main/gnome/optional/100% -> universe unity-scope-gmusicbrowser 0.1+13.10.20130723-0ubuntu1 in xenial s390x: main/gnome/optional/100% -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial: main/gnome -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial amd64: main/gnome/optional/100% -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial arm64: main/gnome/optional/100% -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial armhf: main/gnome/optional/100% -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial i386: main/gnome/optional/100% -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial powerpc: main/gnome/optional/100% -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial ppc64el: main/gnome/optional/100% -> universe unity-scope-gourmet 0.1+13.10.20130723-0ubuntu1 in xenial s390x: main/gnome/optional/100% -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial: main/gnome -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial amd64: main/gnome/optional/100% -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial arm64: main/gnome/optional/100% -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial armhf: main/gnome/optional/100% -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial i386: main/gnome/optional/100% -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial powerpc: main/gnome/optional/100% -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial ppc64el: main/gnome/optional/100% -> universe unity-scope-guayadeque 0.1+13.10.20130927.1-0ubuntu1 in xenial s390x: main/gnome/optional/100% -> universe unity-scope-musique 0.1+13.10.20130723-0ubuntu1 in xenial: main/gnome -> universe unity-scope-musique 0.1+13.10.20130723-0ubuntu1 in xenial amd64: main/gnome/optional/100% -> universe unity-scope-musique 0.1+13.10.20130723-0ubuntu1 in xenial arm64: main/gnome/optional/100% -> universe unity-scope-musique 0.1+13.10.20130723-0ubuntu1 in xenial armhf: main/gnome/optional/100% -> universe unity-scope-musique 0.1+13.10.20130723-0ubuntu1 in xenial i386: main/gnome/optional/100% -> universe unity-scope-musique 0.1+13.10.20130723-0ubuntu1 in
[Dx-packages] [Bug 1521208] Re: Disable Online Search by default in Unity 7 Dash
Online music stores NBS removed from the archive $ ./remove-package -m "Not supported anymore, LP: #1521208" -b unity-scope-musicstores Removing packages from xenial: unity-scope-musicstores 6.9.0+15.04.20141219-0ubuntu1 in xenial amd64 unity-scope-musicstores 6.9.0+15.04.20141219-0ubuntu1 in xenial arm64 unity-scope-musicstores 6.9.0+15.04.20141219-0ubuntu1 in xenial armhf unity-scope-musicstores 6.9.0+15.04.20141219-0ubuntu1 in xenial i386 unity-scope-musicstores 6.9.0+15.04.20141219-0ubuntu1 in xenial powerpc unity-scope-musicstores 6.9.0+15.04.20141219-0ubuntu1 in xenial ppc64el unity-scope-musicstores 6.9.0+15.04.20141219-0ubuntu1 in xenial s390x Comment: Not supported anymore, LP: #1521208 Remove [y|N]? y 7 packages successfully removed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1521208 Title: Disable Online Search by default in Unity 7 Dash Status in libunity: Fix Released Status in Music Lens: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-scope-audacious package in Ubuntu: Fix Released Status in unity-scope-clementine package in Ubuntu: Fix Released Status in unity-scope-gmusicbrowser package in Ubuntu: Fix Released Status in unity-scope-gourmet package in Ubuntu: Fix Released Status in unity-scope-guayadeque package in Ubuntu: Fix Released Status in unity-scope-musique package in Ubuntu: Fix Released Bug description: We have decided to disable online search results in the dash by default. Changes needed are as follows: 1. "Include online search results" from Security & Privacy in Systems Settings should be OFF by default. 2. Amazon & Skimlinks to remain off by default and search results to not be generated without explicitly turning on those filters. 3. Music store option to be fully removed in 16.04 and beyond. I'll take advice on what the best option is for older supported releases. 4. The following scopes to be moved to Universe: * Audacious * Clementine * gmusicbrowser * Gourmet * Guayadeque * Musique (note: unity-scope-musique) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1521208/+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 1482181] Re: Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging
I'm getting it for a couple of releases. It was one on 10 login before. It seems recently, it's one every 4 of them, so quite high in term of frequency. monitoring and pressing a media key gives: signal time=1443171424.483295 sender=:1.28 -> destination=(null destination) serial=7116 path=/org/gnome/Shell; interface=org.gnome.Shell; member=AcceleratorActivated uint32 33 uint32 0 uint32 9782134 So, the signal is sent. I checked, and I have u-s-d running. -- 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/1482181 Title: Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've installed 15.10 and I can't open a terminal using ctrl-alt-t or use any other media keys. All system shorcuts as well don't work. Note that this started at least in 14.10. Restarting Unity "fixes" it (or logging out/logging back), so it seems a race between Unity and settings daemon at startup. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1482181/+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 1482181] Re: Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging
** Summary changed: - ctrl-alt-t doesn't open the terminal on a fresh 15.10 install + Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging ** Description changed: - I've installed 15.10 and I can't open a terminal using ctrl-alt-t. + I've installed 15.10 and I can't open a terminal using ctrl-alt-t or use + any other media keys. All system shorcuts as well don't work. + + Note that this started at least in 14.10. + + Restarting Unity fixes it (or logging out/logging back), so it seems a + race between Unity and settings daemon at startup. ** No longer affects: unity-settings-daemon ** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Triaged ** Changed in: unity-settings-daemon (Ubuntu) Status: New = Triaged -- 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/1482181 Title: Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've installed 15.10 and I can't open a terminal using ctrl-alt-t or use any other media keys. All system shorcuts as well don't work. Note that this started at least in 14.10. Restarting Unity fixes it (or logging out/logging back), so it seems a race between Unity and settings daemon at startup. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1482181/+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 969697] Re: music lens doens't find rhythmbox radios
** Changed in: unity-music-lens Status: Fix Committed = 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, dx-packages https://bugs.launchpad.net/bugs/969697 Title: music lens doens't find rhythmbox radios Status in Unity: Fix Released Status in unity-lens-music: Fix Released Status in Unity Music Lens: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Bug description: Precise 3D 64-Bit up-to-date When searching music using the music lens only local music is displayed in the music lens but no Internet radio stations. Precise will be out there for 5 years and a lot of people listen to radio streams. The music lens is a nice way to find and play music, but the lens is not complete until it find plays Internet radio stream too - IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/969697/+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 883764] Re: migrate_favorites.py crashed with OSError in _execute_child(): [Errno 5] Input/output error
** Changed in: unity (Ubuntu) Assignee: Didier Roche (didrocks) = (unassigned) ** Changed in: unity Assignee: Didier Roche (didrocks) = (unassigned) -- 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/883764 Title: migrate_favorites.py crashed with OSError in _execute_child(): [Errno 5] Input/output error Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: this was automaticvally created see summary ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: unity-common 4.22.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 CasperVersion: 1.287 CompizPlugins: Error: [Errno 5] Input/output error Date: Sun Oct 30 09:18:01 2011 ExecutablePath: /usr/lib/unity/migrate_favorites.py GconfCompiz: Error: [Errno 5] Input/output error InterpreterPath: /usr/bin/python2.7 LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/lib/unity/migrate_favorites.py ProcEnviron: PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/lib/unity/migrate_favorites.py'] SourcePackage: unity Title: migrate_favorites.py crashed with OSError in _execute_child(): [Errno 5] Input/output error UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/883764/+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 1054746] Re: [FFe] [UIFe] No easy way to disable online-fetched results in lenses
** Changed in: unity-lens-wikipedia Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1054746 Title: [FFe] [UIFe] No easy way to disable online-fetched results in lenses Status in A Unity Lens for AskUbuntu.com: Fix Released Status in Gwibber: Fix Released Status in LibUnity: Fix Released Status in Ubuntu Translations: Fix Released Status in Unity: Fix Released Status in unity-lens-music: Fix Released Status in Photos Lens: Fix Released Status in Unity Shopping Lens: Fix Released Status in Wikipedia Lens: Fix Released Status in Google Documents Lens: Fix Released Status in Unity Remote Videos scope: Fix Released Status in activity-log-manager package in Ubuntu: Fix Released Status in gwibber package in Ubuntu: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: New Status in unity-lens-help package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-photos package in Ubuntu: Fix Released Status in unity-lens-radios package in Ubuntu: Fix Released Status in unity-lens-shopping package in Ubuntu: Fix Released Status in unity-scope-gdocs package in Ubuntu: Fix Released Status in unity-scope-video-remote package in Ubuntu: Fix Released Status in activity-log-manager source package in Quantal: Fix Released Status in gwibber source package in Quantal: Fix Released Status in libunity source package in Quantal: Fix Released Status in unity-lens-music source package in Quantal: Fix Released Status in unity-lens-radios source package in Quantal: Fix Released Status in unity-lens-shopping source package in Quantal: Fix Released Status in unity-scope-video-remote source package in Quantal: Fix Released Bug description: We will add an option in the Privacy panel of System Settings. This on/off switch enables to remove all internet connexion in any lens you have installed supporting the option (which are all lenses in the ubuntu repository). All lenses components and libunity are impacted by the change, as well as gnome-control-center. A couple of new strings will be added to the latest for the option. see on comment #27 the screenshot of the privacy settings dash panel. This one is in gnome-control-center (but the source is activity-log-manager for it). The additional strings are: #: ../src/activity-log-manager.vala:57 msgid Search Results msgstr #: ../src/searchresults-widget.vala:60 #, c-format msgid When searching in the Dash: msgstr #: ../src/searchresults-widget.vala:67 #, c-format msgid Include online search results. msgstr The fact that this lens is installed by default means that users are shown commercial content as search results by default in the home screen, and that search queries are sent to an external (to the user) server. It's reasonable that one might want to turn this behaviour off. While it is possible to uninstall the package, this isn't a particularly intuitive route for most. Other lenses have a 'Filter results' item, which would solve this if on the home screen. Otherwise, an option somewhere in the control centre (privacy?) would be good. To manage notifications about this bug go to: https://bugs.launchpad.net/askubuntu-lens/+bug/1054746/+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 697678] Re: libcompizconfig try to create the config file before reading it
** Changed in: libcompizconfig (Ubuntu) Status: Triaged = Fix Released ** Changed in: libcompizconfig (Ubuntu Precise) Status: Triaged = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libcompizconfig in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/697678 Title: libcompizconfig try to create the config file before reading it Status in libcompizconfig package in Ubuntu: Fix Released Status in libcompizconfig source package in Precise: Fix Released Bug description: It's an issue when we have an apparmor profile protecting /etc/compizconfig/config as the LSM reject will make libcompizconfig loading the ini backend (not reading the config file still available for read) There is a temporary workaround in the gdm-guest-session package which should be removed once that fixed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcompizconfig/+bug/697678/+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 793278] Re: Fallback to unity-2d fails on unsupported hardware
** Changed in: unity-2d Assignee: Didier Roche (didrocks) = (unassigned) -- 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/793278 Title: Fallback to unity-2d fails on unsupported hardware Status in Unity 2D: Incomplete Status in unity-2d package in Ubuntu: Expired Bug description: Binary package hint: unity Current daily build Live defaults to Unity desktop setting for Radeon Mobility 7500. Unity 3D does not work on this video. Forums say Unity 3D isn't even on the Live .iso Live should default to Unity 2D which works. (yes bugs, but at least displays and does some things with launchers. Jerry ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 3.8.14-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: None DRM.card0.DVI.D.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: Off modes: 1024x768 800x600 848x480 720x480 640x480 edid-base64: DRM.card0.VGA.1: status: connected enabled: enabled dpms: On modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 edid-base64: AP///wAi8OsmAQEBAQITAQNoIhuM7txVo1lIniQRUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAVA4RAAAe/QAyTRhTDgAKICAgICAg/ABIUCBMMTcxMAogICAg/wAzQ1E5MDIzODlECiAgAPo= Date: Sun Jun 5 17:48:12 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] (prog-if 00 [VGA controller]) Subsystem: IBM ThinkPad T42 2373-4WU [1014:0530] LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110605) LiveMediaBuild_: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110605) LiveMediaBuild__: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110605) MachineType: IBM 23736U0 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card Socket 1: no card ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper persistent iso-scan/filename=/boot/iso/oneiric-desktop-i386.iso noprompt noeject ProcVersionSignature_: Ubuntu 2.6.39-3.10-generic 2.6.39 ProcVersionSignature__: Ubuntu 2.6.39-3.10-generic 2.6.39 Renderer: Unknown SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Configured Video Device Driver radeon EndSection dmi.bios.date: 10/13/2005 dmi.bios.vendor: IBM dmi.bios.version: 1RETDNWW (3.19 ) dmi.board.name: 23736U0 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDNWW(3.19):bd10/13/2005:svnIBM:pn23736U0:pvrThinkPadT40:rvnIBM:rn23736U0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 23736U0 dmi.product.version: ThinkPad T40 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.libdrm2: libdrm2 2.4.25-2ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/793278/+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 1422745] Re: wrong notification progress reported if volume 100% enabled in pulseaudio
It's partially fixed. This works now when using media keys for volume up and down (the reported value by the notification is the correct one). It is not fixed when using indicator-sound itself: - there is still the notification spam - this one is offset between the notification report and indicator sound slider ** Changed in: indicator-sound (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1422745 Title: wrong notification progress reported if volume 100% enabled in pulseaudio Status in indicator-sound package in Ubuntu: Confirmed Bug description: When using the option to use the volume above 100%, indicator-sounds interferes with the percentage reported in notify-osd: - enable in pulseaudio capplet for allow volume being above 100% - press volume up or down medium keys - notice that the progress reported by notify-osd isn't the correct one compared to the capplet. Also, there is a glitch (like notification progress bar going back and force) - stop indicator-sound, the progress reported is correct, and the glitch is gone as well. So, there are 2 updates occuring in a short period of time: - the one from unity-settings-daemon - the one from the indicator-sound, which doesn't send the correct value. Another consequence is if you are using the indicator and slide the volume bar, you have the notification showing on top, making it hard to see what volume you are setting it. Moving the slider is already a visual user confirmation, you shouldn't get a notification on top. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150205-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 17 15:18:19 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-28 (995 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: indicator-sound UpgradeStatus: Upgraded to vivid on 2014-10-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1422745/+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 1422745] [NEW] wrong notification progress reported if volume 100% enabled in pulseaudio
Public bug reported: When using the option to use the volume above 100%, indicator-sounds interferes with the percentage reported in notify-osd: - enable in pulseaudio capplet for allow volume being above 100% - press volume up or down medium keys - notice that the progress reported by notify-osd isn't the correct one compared to the capplet. Also, there is a glitch (like notification progress bar going back and force) - stop indicator-sound, the progress reported is correct, and the glitch is gone as well. So, there are 2 updates occuring in a short period of time: - the one from unity-settings-daemon - the one from the indicator-sound, which doesn't send the correct value. Another consequence is if you are using the indicator and slide the volume bar, you have the notification showing on top, making it hard to see what volume you are setting it. Moving the slider is already a visual user confirmation, you shouldn't get a notification on top. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150205-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 17 15:18:19 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-28 (995 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: indicator-sound UpgradeStatus: Upgraded to vivid on 2014-10-31 (109 days ago) ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1422745 Title: wrong notification progress reported if volume 100% enabled in pulseaudio Status in indicator-sound package in Ubuntu: New Bug description: When using the option to use the volume above 100%, indicator-sounds interferes with the percentage reported in notify-osd: - enable in pulseaudio capplet for allow volume being above 100% - press volume up or down medium keys - notice that the progress reported by notify-osd isn't the correct one compared to the capplet. Also, there is a glitch (like notification progress bar going back and force) - stop indicator-sound, the progress reported is correct, and the glitch is gone as well. So, there are 2 updates occuring in a short period of time: - the one from unity-settings-daemon - the one from the indicator-sound, which doesn't send the correct value. Another consequence is if you are using the indicator and slide the volume bar, you have the notification showing on top, making it hard to see what volume you are setting it. Moving the slider is already a visual user confirmation, you shouldn't get a notification on top. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150205-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 17 15:18:19 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-28 (995 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: indicator-sound UpgradeStatus: Upgraded to vivid on 2014-10-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1422745/+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 1003950] Re: launcher does not show minimized update manager while clicked
** Description changed: + Found an easy way to reproduce it during brussels sprint: + 1. start deja-dup or update-manager + 2. kill -9 compiz; metacity + 3. compiz --replace + + + === + Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. -- 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/1003950 Title: launcher does not show minimized update manager while clicked Status in Compiz: New Status in Accelerated Xorg driver for nVidia cards: New Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in binary-driver-fglrx package in Ubuntu: New Status in intel-linux-graphics-installer package in Ubuntu: New Status in unity package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in binary-driver-fglrx source package in Precise: New Status in intel-linux-graphics-installer source package in Precise: New Status in unity source package in Precise: Fix Released Status in update-manager source package in Precise: Confirmed Status in xserver-xorg-video-nouveau source package in Precise: New Status in binary-driver-fglrx source package in Quantal: Invalid Status in intel-linux-graphics-installer source package in Quantal: Invalid Status in unity source package in Quantal: Fix Released Status in update-manager source package in Quantal: Won't Fix Status in xserver-xorg-video-nouveau source package in Quantal: Invalid Bug description: Found an easy way to reproduce it during brussels sprint: 1. start deja-dup or update-manager 2. kill -9 compiz; metacity 3. compiz --replace === Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1003950/+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 1364070] Re: vivid, utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
Thanks Andrea for looking deeper into this! Opened the upstream bug for it. ** Bug watch added: GNOME Bug Tracker #744030 https://bugzilla.gnome.org/show_bug.cgi?id=744030 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=744030 Importance: Unknown Status: Unknown ** Changed in: unity Status: In Progress = Incomplete ** Changed in: unity (Ubuntu) Status: In Progress = Incomplete ** Changed in: unity Status: Incomplete = Invalid ** Changed in: unity (Ubuntu) Status: Incomplete = 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/1364070 Title: vivid, utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in The G Library - GLib: Unknown Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1364070/+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 1364070] Re: utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
** Summary changed: - utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up + utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up -- 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/1364070 Title: utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1364070] Re: utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
** Changed in: unity Milestone: None = 7.3.2 -- 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/1364070 Title: utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1364070] Re: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
** Description changed: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. + + + This was first experimented on June 2014 on IRC. -- 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/1364070 Title: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1364070] Re: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
** Description changed: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. - - This was first experimented on June 2014 on IRC. + This was first experimented on June 2014 and reported on IRC. -- 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/1364070 Title: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1001621] Re: appmenu-qt doesn't work with 32-bit apps on 64-bit system
** Changed in: unity (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity Status: Confirmed = Invalid ** Changed in: appmenu-qt Status: Triaged = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1001621 Title: appmenu-qt doesn't work with 32-bit apps on 64-bit system Status in Application menu for Qt4: Fix Released Status in Unity: Invalid Status in “appmenu-qt” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Bug description: When I run a software which it write with and build in 32bit system in a 64bit system. It can't work a global meun and the HUD. I test this in Ubuntu 12.04 64bit,and the version of unity is 5.12.0. And we can reproduce it run the little program (attachment) in 64bit sysytem which I write it with Qt and build in 32 bit system. (You may should install ia32-libs to support 32bit software in 64bit system) And this is the output information: Unable to load library icui18n Cannot load library icui18n: (libicui18n.so.48: wrong ELF class: ELFCLASS64) /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt/+bug/1001621/+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 1364070] [NEW] utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
Public bug reported: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. ** Affects: unity Importance: Undecided Status: Confirmed ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed -- 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/1364070 Title: utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364070/+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 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
I'm not working on Compiz/Unity anymore, but I agree with the bug description and the comments to where compiz/unity headed to today. We had a lot of stability problem at the time, hence this helper to reset unity (which is never used in the session itself to start unity). Stephen's team will handle it. I'm accepting the SRU nomination for trusty as well. ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1324114 Title: Unity kills running compiz, even if it belongs to a different Unity session Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Trusty: New Bug description: Hi! I'm trying to get a setup with two different Unity desktop sessions running at the same time. One for the local desktop, one for a remote desktop. This almost works, except that when starting the second Unity session, the compiz process that belongs to the first one is killed because of this code in /usr/bin/unity: # kill a previous compiz if was there (this is a hack as compiz can # sometimes get stuck and not exit on --replace) subprocess.call ([pkill, -9, compiz]) Commenting this line makes both desktop sessions work fine. This kill is far too harsh. If you want to kill compiz, you should make sure that you are killing it in the same DISPLAY as the session that you are about to start, and not just every possible compiz process that is running. Please consider either removing the kill or making it apply only to processes in the same DISPLAY. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1324114/+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 1292343] Re: notify-osd positions its top notification overlapping the panel on displays not aligned with the top of the virtual screen
I can reproduce with that setup: I have two monitors with one on top of the other one: VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 287mm LVDS1 connected primary 1366x768+0+1080 (normal left inverted right x axis y axis) 277mm x 156mm The sync notification (like volume up and down) is always overlapping the top panel of the monitor with the focused window. ** Changed in: notify-osd (Ubuntu) Status: New = Triaged ** Changed in: notify-osd (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292343 Title: notify-osd positions its top notification overlapping the panel on displays not aligned with the top of the virtual screen Status in “notify-osd” package in Ubuntu: Triaged Bug description: My monitor layout is: 1. 1366x768+0+270 2. 1680x1050+1366+0 notify-osd renders the volume/brightness notification overlapping the panel on monitor 1. This doesn't happen when the top edge of monitor 1 touches the top of the virtual screen, i.e. 1366x768+0+0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 12:08:56 2014 DesktopSession: 'ubuntu' GtkTheme: 'Ambiance' IconTheme: 'Humanity-Colors-Dark-Red' MachineType: LENOVO 2325F45 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.4-hyper1 root=UUID=274ad2d4-6566-4eb1-85d7-d22ef41b2170 ro acpi_osi=!Windows 2012 i915.i915_enable_rc6=7 i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.semaphores=1 rootflags=data=writeback splash resume=/dev/mapper/cryptostuff-swap crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-1ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 SourcePackage: notify-osd UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) dmi.bios.date: 04/30/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325F45 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: RH0005026 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2325F45:pvrThinkPadX230:rvnLENOVO:rn2325F45:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2325F45 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1292343/+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 1319983] Re: notify-osd loses pending bubble if append occurs when bubble is not yet visible
** Also affects: notify-osd (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1319983 Title: notify-osd loses pending bubble if append occurs when bubble is not yet visible Status in “notify-osd” package in Ubuntu: In Progress Status in “notify-osd” source package in Trusty: New Bug description: [Impact] When a notification specifiying x-canonical-append:true is recieved and merges with a bubble the bubble will be lost if the bubble is not yet visible. We will also update times incorrectly on any synchronous bubble. [Test Case] Running the attached scripts (play.py and play2.py) show the issue: bubbles after the first one aren't shown, because they specify x-canonical-append. The attached branch fixes that. [Regression Potential] The patch only touches code that is concerned with updating an existing notification. This is currently broken anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1319983/+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 1295122] Re: Alarms not going off reliably on recent touch images
set as critical as a promotion blocker ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Critical ** Changed in: indicator-datetime (Ubuntu) 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/1295122 Title: Alarms not going off reliably on recent touch images Status in “indicator-datetime” package in Ubuntu: New Bug description: Alarms are not reliable on recent images on touch. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/+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 1295237] Re: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing
confirming, seems a promotion blocker as well ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed ** Changed in: indicator-datetime (Ubuntu) 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/1295237 Title: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to debug: adb shell sudo -u phablet -i stop indicator-datetime G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service In a separate terminal run: adb shell powerd-cli active Steps to reproduce: Set an alarm for 3 minutes time Hit the power button Repeat until the issue triggers. At some point the alarm will sound you hit dismiss in the snap decision and the alarm doesn't stop ringing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 16:51:23 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237/+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 1255530] Re: /home/phablet/.pam_environment does not get updated on OTA upgrades
as discussed with Ogra on IRC, this should be a pam migration script itself, not session-migration but using session-migration. however, there is another bug needed to hook session-migration into upstart so that session-migration works ** Package changed: session-migration (Ubuntu) = pam (Ubuntu) -- 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/1255530 Title: /home/phablet/.pam_environment does not get updated on OTA upgrades Status in “indicator-datetime” package in Ubuntu: Invalid Status in “pam” package in Ubuntu: New Bug description: starting my phone set to german language the lock screen properly shows a 24h clock ... as aoon as the panel clock shows up, the lockscreen format (and all other places where the time is shown in the UI) is swithcing to AM/PM 12h time format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1255530/+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 1253810] Re: Messages in Incoming not always display the correct date and content
let's add the regression tag (as it's from image 27 at least) so that we can get it in our regression list (and so fixing ASAP) ** Tags added: regression -- 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/1253810 Title: Messages in Incoming not always display the correct date and content Status in The Messaging Menu: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: Sometimes SMSes are displayed with Dec 31 as a date and the content is not displayed. This happens every once in a while, in general the notifications are displayed correctly, but as I exchanged a lot of SMSes with different numbers, this problem happened a few times. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1253810/+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 1253810] Re: Messages in Incoming not always display the correct date and content
So, after talking with Saviq, it's a very old bug that was always present. They have a branch proposed to fix it but never decided on the correct resolution of this. So, targetting Unity8 and attaching the branch to that bug. (and removing both version and regression tags) ** Tags removed: r27 regression ** Project changed: indicator-messages = unity8 ** Package changed: indicator-messages (Ubuntu) = unity8 (Ubuntu) ** Branch linked: lp:~nick-dedekind/unity8/StrFTimeFormatter -- 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/1253810 Title: Messages in Incoming not always display the correct date and content Status in The Unity 8 shell: New Status in “unity8” package in Ubuntu: Confirmed Bug description: Sometimes SMSes are displayed with Dec 31 as a date and the content is not displayed. This happens every once in a while, in general the notifications are displayed correctly, but as I exchanged a lot of SMSes with different numbers, this problem happened a few times. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1253810/+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 1253804] Re: [regression] Indicator icons don't match the settings they display
** Package changed: unity (Ubuntu) = unity8 (Ubuntu) ** Changed in: unity8 (Ubuntu) Importance: Critical = Undecided -- 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/1253804 Title: [regression] Indicator icons don't match the settings they display Status in Ubuntu UX bugs: New Status in The Unity 8 shell: New Status in “unity8” package in Ubuntu: Confirmed Bug description: In the top bar I have these icons: network (mobile, wifi), bluetooth, location, incoming, battery, sound and clock. When I drop down to access the settings, the only one that shows the correct panel is Network. All the others display settings different than what the icon implies. For example, Bluetooth icon displays Incoming settings, Location displays Bluetooth, Incoming displays Battery, Battery displays Upcoming, Sound displays Location and the Clock displays Sound settings. I'm using mako, -proposed, r27, read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1253804/+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 1236249] Re: unity8 crashed with SIGSEGV in UnityMenuModelPrivate::itemState()
** Changed in: unity8 (Ubuntu) Status: Fix Committed = Fix Released ** Also affects: indicator-bluetooth (Ubuntu Saucy) Importance: Undecided Status: Confirmed ** Also affects: ubuntu-system-settings (Ubuntu Saucy) Importance: High Assignee: Charles Kerr (charlesk) Status: Fix Released ** Also affects: unity8 (Ubuntu Saucy) Importance: High Assignee: Nick Dedekind (nick-dedekind) Status: Fix Released -- 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/1236249 Title: unity8 crashed with SIGSEGV in UnityMenuModelPrivate::itemState() Status in Bluetooth Menu: Fix Committed Status in “indicator-bluetooth” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “indicator-bluetooth” source package in Saucy: Confirmed Status in “ubuntu-system-settings” source package in Saucy: Fix Released Status in “unity8” source package in Saucy: Fix Released Bug description: TEST CASE: 1. Open BT indicator and disable BT 2. Open system-settings 3. Select BT 4. Enable/Disable BT several times (max 2 or 3) = indicator doesn’t appear and eventually u-s-s and unity8 crashed ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity8 7.82+13.10.20131005-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu1 Architecture: armhf CrashCounter: 1 Date: Mon Oct 7 09:15:09 2013 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 1380974656 InstallationDate: Installed on 2013-10-05 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131005) MarkForUpload: True ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 6 SourcePackage: unity8 StacktraceTop: ?? () UnityMenuModelPrivate::itemState(_GtkMenuTrackerItem*) () from /usr/lib/arm-linux-gnueabihf/libqmenumodel.so.0 UnityMenuModel::data(QModelIndex const, int) const () from /usr/lib/arm-linux-gnueabihf/libqmenumodel.so.0 UnityMenuModel::get(int, QByteArray const) () from /usr/lib/arm-linux-gnueabihf/libqmenumodel.so.0 RootActionState::updateActionState() () from /usr/lib/arm-linux-gnueabihf/unity8/qml/Unity/Indicators/libIndicatorsQml.so Title: unity8 crashed with SIGSEGV in UnityMenuModelPrivate::itemState() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1236249/+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 1230275] Re: Bluetooth cannot be switched on/off on Nexus 4 (rfkill issues)
** Also affects: indicator-bluetooth (Ubuntu Saucy) Importance: Undecided Status: New -- 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/1230275 Title: Bluetooth cannot be switched on/off on Nexus 4 (rfkill issues) Status in Bluetooth Menu: Fix Committed Status in “indicator-bluetooth” package in Ubuntu: New Status in “indicator-bluetooth” source package in Saucy: New Bug description: When using the latest indicator-bluetooth on the Nexus 4 (mako) and Ubuntu Touch switching bluetooth on/off is impossible, as the state never changes. Same when doing it from the ubuntu-system-settings. The unity8.log upstart log has this in it: Can't open /dev/rfkill for use as a killswitch backend: Permission denied Couldn't write rfkill event: Bad file descriptor Can't open /dev/rfkill for use as a killswitch backend: Permission denied [Impact] * User has no chance to switch bluetooth on or off which can also pose a security problem when having bluetooth on all the time. [Test Case] * Try to switch BT on/off via indicator or system settings. [Regression Potential] * None really as it cannot be more broken as it is currently. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1230275/+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 1238043] Re: indicator-datetime-service is opening /etc/localtime every 5 seconds even on a totally idle system
** Also affects: indicator-datetime (Ubuntu Saucy) Importance: Medium Assignee: Charles Kerr (charlesk) Status: In Progress -- 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/1238043 Title: indicator-datetime-service is opening /etc/localtime every 5 seconds even on a totally idle system Status in “indicator-datetime” package in Ubuntu: In Progress Status in “indicator-datetime” source package in Saucy: In Progress Bug description: In an attempt to reduce unnecessary frequent periodic file access to save power, I noticed that indicator-datetime-service is opening and closing /etc/localtime every 5 seconds on my desktop and not apparently reading this file. On the ubuntu phone it is doing the same thing with /etc/writable/localtime. This seems a little excessive, especially because the TZ data doesn't change quite that frequently. It would be useful if this excessive polling on the file could be reduced if possible. [Impact] * Battery drain, wasting energy by a lot of unnecessary polling [Test Case] * Observe how often /etc/localtime or /etc/writable/localtime gets opened for reading [Regression Potential] * Possibility to not get the local time reliably To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1238043/+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 1199314] Re: compiz crashed with SIGSEGV in operator()
I use Unity on the left et Cairo dock on the ground. Cairo because it is the only way to parameter colours and brigtness on the screen. (my graphic card : ATI Radeon 4500 series A+ -- 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/1199314 Title: compiz crashed with SIGSEGV in operator() Status in “unity” package in Ubuntu: Confirmed Bug description: Changing filters in the social lens ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 19:59:31 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-22 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f155f86b76a:mov0x3c0(%rax),%rax PC (0x7f155f86b76a) ok source 0x3c0(%rax) (0x03c0) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/compiz/libunityshell.so nux::Propertybool::Set(bool const) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so nux::Button::RecvClick(int, int, unsigned long, unsigned long) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0 nux::InputArea::EmitMouseClickSignal(int, int, unsigned long, unsigned long) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0 Title: compiz crashed with SIGSEGV in nux::Propertybool::Set() 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/unity/+bug/1199314/+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
