[Dx-packages] [Bug 1308037] Re: No results from application scope
** Also affects: unity-lens-applications Importance: Undecided Status: New ** Changed in: unity-lens-applications Status: New => 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/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in Unity Applications Lens: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for "spotify", which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+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 1308037] Re: No results from application scope
So from looking at the log: 23.19s - Unity queries applications masterscope 26.37s - apps scope appears on bus 43.49s - BAMF query for running apps 43.58s - Search invoked on apps scope 48.20s - Search inside apps masterscope timed out, sent no-results reply 52.30s - Search in apps scope finishes So on your machine it took the apps scope ~20 seconds to initialize and start processing requests, and then another ~9 seconds to process the first request, which is pretty bad, cause the dbus timeout is 25seconds. Although from the log it's also visible that the apps scope did respond to further searches, I assume the case where it doesn't work at all is when the initial initialization itself takes more than 25 seconds. All in all, I'd attribute bad IO performance to this issue, but clearly the apps scope should handle that better. -- 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/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for "spotify", which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+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 1308037] Re: No results from application scope
@Mateusz: Your dbus log is pretty much the same as Pawel's, it says that activation of the application scope timed out, but doesn't provide any indication why. The bustle log captured only the first 30 seconds of the startup process (as the upstart script tells it to), and in that time scopes didn't even begin starting up. You could try bumping the timeout to 90 seconds, and that might provide more data, but I'm afraid it still won't point to why is the apps scope startup taking that long. -- 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/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for "spotify", which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+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 1308037] Re: No results from application scope
@pstolowski, from the bustle log it's visible that there's a query to .../masterscope/applications with subscope_filter=['applications- applications.scope', 'applications-scopes.scope'], so not filter related. -- 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/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for "spotify", which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+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 1308037] Re: No results from application lens
Unfortunately the bustle log just shows that the home scope doesn't query the applications scope, but it's not known why. It would be useful if bustle was run earlier, so the initial query (and reason it presumably? failed) to the applications scope would be visible. ** Also affects: libunity Importance: Undecided Status: New ** Changed in: libunity Status: New => Confirmed ** Summary changed: - No results from application lens + No results from application scope ** Description changed: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for "spotify", which I've got installed, and got 0 results. + + The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) -- 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/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for "spotify", which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+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 1308615] Re: unity dash not finding apps
*** This bug is a duplicate of bug 1308037 *** https://bugs.launchpad.net/bugs/1308037 ** This bug has been marked a duplicate of bug 1308037 No results from application lens -- 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/1308615 Title: unity dash not finding apps Status in “unity” package in Ubuntu: New Bug description: I just install Trusty Desktop 64-bit from this daily ISO: 0a884e0fe10f703493a4f8ff993be5fd *trusty-desktop-amd64.iso After booting into the new desktop, I'm not able to search and find any apps. In particular, I'm searching for "terminal", trying to launch a Gnome Terminal. I'm offered The Terminator movie, for sale, but there's no terminal app returned. In a separate issue, I search for Gimp, and I receive some not-safe- for-work results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308615/+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 1295908] Re: Sometimes applications stop showing up in the Dash
*** This bug is a duplicate of bug 1308037 *** https://bugs.launchpad.net/bugs/1308037 ** This bug has been marked a duplicate of bug 1308037 No results from application lens -- 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/1295908 Title: Sometimes applications stop showing up in the Dash Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes when I use Unity, and I search for an application in the Dash the results just shows Files and Folders; no applications. I don't know how to reproduce this bug. I'm using the stock Unity Packages in Ubuntu 13.10. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 21 19:12:19 2014 InstallationDate: Installed on 2013-10-05 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-12-10 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295908/+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 1274669] Re: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va()
** Also affects: unity-scope-manpages Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274669 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() Status in Unity Manpages Scope: New Status in “libunity” package in Ubuntu: Confirmed Bug description: Typed "disks" in the dash and the crash occured shortly after opening disks. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-scopes-runner 7.1.3+14.04.20131106-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 30 21:20:26 2014 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-08-30 (153 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s code/manpages.scope Signal: 5 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() UpgradeStatus: Upgraded to trusty on 2014-01-30 (0 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-manpages/+bug/1274669/+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 1280759] Re: Shortcuts are defined via keyboard layout, not the keys
** Package changed: libunity (Ubuntu) => unity (Ubuntu) -- 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/1280759 Title: Shortcuts are defined via keyboard layout, not the keys Status in “unity” package in Ubuntu: New Bug description: There are shortcuts to open lenses in Unity, for example "Super + A" for App Lens, or "Super + F" for Files Lens, etc. There are also shortcuts in the Launcher "Super + 1 to 9" to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator --> Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press "Super + F". WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press "Ctrl + S" (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press "Ctrl + S" while Persian layout is active, I am typing "Ctrl + س". But keyboard-wise, I am always pressing the same keyboard binding. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1280759/+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 1277924] Re: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1281538 *** https://bugs.launchpad.net/bugs/1281538 ** This bug is no longer a duplicate of private bug 1277982 ** This bug has been marked a duplicate of bug 1281538 unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1277924 Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “libunity” package in Ubuntu: New Bug description: NA ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.3+14.04.20131106-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 8 10:36:34 2014 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2013-06-10 (242 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcCmdline: /usr/bin/unity-scope-loader music/mediascanner.scope video/mediascanner.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: libunity StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 unity_scope_module_load_scopes () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-mediascanner.so Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to trusty on 2014-02-04 (3 days ago) UserGroups: adm androiddev cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1277924/+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 1277880] Re: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1281538 *** https://bugs.launchpad.net/bugs/1281538 ** This bug is no longer a duplicate of private bug 1277982 ** This bug has been marked a duplicate of bug 1281538 unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1277880 Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “libunity” package in Ubuntu: New Bug description: ??? ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.3+14.04.20131106-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 8 15:20:46 2014 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2014-02-05 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/bin/unity-scope-loader music/mediascanner.scope video/mediascanner.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 Signal: 6 SourcePackage: libunity StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 unity_scope_module_load_scopes () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-mediascanner.so Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to trusty on 2014-02-07 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1277880/+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 1281081] Re: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1281538 *** https://bugs.launchpad.net/bugs/1281538 ** This bug is no longer a duplicate of private bug 1277982 ** This bug has been marked a duplicate of bug 1281538 unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1281081 Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “libunity” package in Ubuntu: New Bug description: Trying Unity8 ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 17 13:13:50 2014 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2014-02-14 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214) ProcCmdline: /usr/bin/unity-scope-loader music/mediascanner.scope video/mediascanner.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 Signal: 6 SourcePackage: libunity StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 unity_scope_module_load_scopes () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-mediascanner.so Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() 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/libunity/+bug/1281081/+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 1250134] Re: RemoteContent field should be mandatory in .scope file
** Also affects: libunity Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1250134 Title: RemoteContent field should be mandatory in .scope file Status in LibUnity: New Status in “libunity” package in Ubuntu: Confirmed Bug description: If a .scope file has no RemoteContent field, the default is to assume "false". The RemoteContent field should be mandatory, to ensure that scope authors aren't ignoring the privacy setting by mistake. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1250134/+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 1239710] Re: indicator-datetime or -session missing ~10% of the time
** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Fix Committed -- 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, dx-packages https://bugs.launchpad.net/bugs/1239710 Title: indicator-datetime or -session missing ~10% of the time Status in The Date and Time Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Committed Status in “indicator-session” package in Ubuntu: Fix Committed Status in “indicator-datetime” source package in Saucy: Fix Committed Status in “indicator-session” source package in Saucy: Fix Committed Bug description: Impact: sometime indicator-session or datetime go missing in unity Test Case: start sessions until that happens (or not) Regression potential: the change is a one liner workaround for a glib lock, shouldn't create issue, just check that those indicators keep working as they should --- Indicator-datetime is not showing in the indicator bar today on image 96. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Mon Oct 14 16:00:26 2013 InstallationDate: Installed on 2013-10-14 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131014) MarkForUpload: True 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/indicator-datetime/+bug/1239710/+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 1239710] Re: indicator-datetime or -session missing ~10% of the time
** Changed in: indicator-datetime (Ubuntu) Status: Fix Released => Confirmed -- 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, dx-packages https://bugs.launchpad.net/bugs/1239710 Title: indicator-datetime or -session missing ~10% of the time Status in The Date and Time Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: Fix Committed Status in “indicator-datetime” source package in Saucy: Fix Committed Status in “indicator-session” source package in Saucy: Fix Committed Bug description: Impact: sometime indicator-session or datetime go missing in unity Test Case: start sessions until that happens (or not) Regression potential: the change is a one liner workaround for a glib lock, shouldn't create issue, just check that those indicators keep working as they should --- Indicator-datetime is not showing in the indicator bar today on image 96. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Mon Oct 14 16:00:26 2013 InstallationDate: Installed on 2013-10-14 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131014) MarkForUpload: True 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/indicator-datetime/+bug/1239710/+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 1050026] Re: install service to pkglibexecdir rather than libexecdir
Can you please provide more information what's needed for libunity? The library itself it already being installed in the /usr/lib/[arch- triplet]. ** Changed in: libunity Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sync in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1050026 Title: install service to pkglibexecdir rather than libexecdir Status in Application Indicators: New Status in The Sync Menu: Fix Released Status in LibUnity: Incomplete Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Bug description: * The service should be installed into $pkglibexecdir instead of $libexecdir (this is an upstream issue, not a debian packaging one) In other words, rather than /usr/lib/, the service binary should be installed to /usr/lib//indicator-sync/. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1050026/+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 1240141] Re: List of client scopes is not up-to-date
** Branch linked: lp:~mhr3/libunity/update-scopes-definitions -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240141 Title: List of client scopes is not up-to-date Status in LibUnity: Fix Committed Status in “libunity” package in Ubuntu: Fix Released Bug description: The list of scopes in /usr/share/unity/client-scopes.json is not up- to-date with that's provided by the packages, there's just three differences, but we should still fix it, so the server gets correct information. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1240141/+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 1212307] Re: SearchContext.search_metadata is empty when creating it from python.
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1212307 Title: SearchContext.search_metadata is empty when creating it from python. Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: When a Unity.SearchContext is created from python, the search_metadata is always empty. Code to reproduce the issue: http://paste.ubuntu.com/5985211/ To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1212307/+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 1199715] Re: unity-scope-home crashed with signal 5 in g_wakeup_new()
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1199715 Title: unity-scope-home crashed with signal 5 in g_wakeup_new() Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “unity-scope-home” package in Ubuntu: Invalid Bug description: Not sure what happened here, just started my session. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scope-home 6.8.1+13.10.20130705-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Wed Jul 10 10:44:49 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home Signal: 5 SourcePackage: unity-scope-home StacktraceTop: g_wakeup_new () at /build/buildd/glib2.0-2.37.3/./glib/gwakeup.c:163 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x1ae22b0, pollfd=pollfd@entry=0x7f2580a21b20) at /build/buildd/glib2.0-2.37.3/./gio/gcancellable.c:402 socket_source_new (cancellable=0x1ae22b0, condition=(G_IO_IN | G_IO_ERR | G_IO_HUP), socket=0x1b09130) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3264 g_socket_create_source (socket=0x1b09130, condition=condition@entry=(G_IO_IN | G_IO_ERR | G_IO_HUP), cancellable=cancellable@entry=0x1ae22b0) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3329 _g_socket_read_with_control_messages (socket=0x1b09130, buffer=0x7f2580589f10, count=16, messages=0x1b0cb00, num_messages=0x1b0cb08, io_priority=, cancellable=0x1ae22b0, callback=0x7f258b2a6160 <_g_dbus_worker_do_read_cb>, user_data=0x1b0ca70) at /build/buildd/glib2.0-2.37.3/./gio/gdbusprivate.c:201 Title: unity-scope-home crashed with signal 5 in g_wakeup_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1199715/+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 1170810] Re: unity.deps contains unnecessary API dependencies
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1170810 Title: unity.deps contains unnecessary API dependencies Status in Geary: Fix Committed Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: The unity.deps file (required for Vala compilation) includes gee-1.0 as a dependency. However, libgee is not used by the vapi and therefore should not be included. To quote from the Vala upstream bindings guide (from https://live.gnome.org/Vala/UpstreamGuide ) "The only other file that should be distributed is a deps file, which lists pkg-config names of any dependencies exposed in the public API." In other words, if there are no libgee symbols in the API, libgee shouldn't be included in the deps file. It's quite possible some of the other libraries aren't needed for the API as well, I haven't checked. This is a problem for us as it means we can't link against both libunity and libgee 0.8, since libunity's deps file causes Vala to pull in symbols for libgee 0.6, which causes the compiler to error out with a symbol conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/geary/+bug/1170810/+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 1222828] Re: unity-scope-loader doesn't handle missing modules correctly
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1222828 Title: unity-scope-loader doesn't handle missing modules correctly Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: unity-scope-loader doesn't correctly handle return value of GLib.Module.open(). If module is missing, it fails at a later stage when checking module version, which produces assertion errors on module != NULL and a misleading error about missing get_version function. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1222828/+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 1235342] Re: libunity-tool doesn't parse scope files correctly
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1235342 Title: libunity-tool doesn't parse scope files correctly Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: Scope files that are using current GroupName and DBusName in their .scope files do not work with libunity-tool as it doesn't use the protocol library. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1235342/+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 1220733] Re: OEM scope customization isn't working properly
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: unity-scope-home Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1220733 Title: OEM scope customization isn't working properly Status in LibUnity: Fix Released Status in Unity Home Scope: Fix Released Status in “unity-lens-applications” package in Ubuntu: Fix Released Status in “unity-scope-home” package in Ubuntu: Fix Released Bug description: Currently if an OEM wants to customize which scopes are displayed and queried on the device, the only possibility for customization is to add a scope as a separate page, due to a bug in how home-scope discovers scopes. Also, we need a simple way for removing scopes without actually deleting them from the filesystem image. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1220733/+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 923727] Re: Unity lenses protocol causes excessive context switching
The latest protocol already has an option to use private connections, although they're not enabled for all channels by default, only the dash to master scope channel isn't using private connection. ** Changed in: libunity (Ubuntu) Status: Triaged => Fix Released ** Changed in: libunity Status: Triaged => Fix Released ** Changed in: unity Status: Triaged => 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 https://bugs.launchpad.net/bugs/923727 Title: Unity lenses protocol causes excessive context switching Status in LibUnity: Fix Released Status in Unity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: Updating DeeModels is currently done over DBus which causes extra copies from lenses' processes to dbus-daemon and then to unity(-2d). Dee now supports private connections which allow us to skip the copy to dbus-daemon, we should use these for the lenses' models to get the issue under control. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/923727/+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 1219792] Re: libunity-tool crashes when it can't connect to the bus
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1219792 Title: libunity-tool crashes when it can't connect to the bus Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: libunity-tool crashes when it can't connect to session bus (which is fairly often when ssh-ing into the device and forgetting to set the dbus envvar). To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1219792/+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 1231390] Re: Creating SearchContext from python no longer accepts None for metadata
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1231390 Title: Creating SearchContext from python no longer accepts None for metadata Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: As this is a regression and breaks quite a few users, we should fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1231390/+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 902242] Re: Unity should provide an "active" signal on a per lens basis
Marking as invalid since the latest scope API doesn't have a active property, plus together with TTL of result set this should be considered fixed. ** No longer affects: unity ** Changed in: libunity (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libunity Status: Confirmed => 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 https://bugs.launchpad.net/bugs/902242 Title: Unity should provide an "active" signal on a per lens basis Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: The current notify::active signal is sent when the dash is opened, closed or when any lens is displayed. Lens developers using remote APIs need to be cautious with the number of API calls they send. When they need to display a default set of results when a lens is opened, they use this signal despite of it being sent a lot more than needed and triggering a lot of unwanted API calls. Unity should provide an "active" signal on a per lens basis. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/902242/+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 1170712] Re: Left and Right clicking on “More Suggestions” should open a preview
** No longer affects: libunity (Ubuntu Raring) ** No longer affects: unity-lens-video (Ubuntu Raring) ** No longer affects: libunity (Ubuntu) ** Changed in: unity-lens-video (Ubuntu) Status: New => 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 https://bugs.launchpad.net/bugs/1170712 Title: Left and Right clicking on “More Suggestions” should open a preview Status in LibUnity: Fix Released Status in Unity: Fix Released Status in Unity Videos Lens: Fix Released Status in Unity Home Scope: Fix Released Status in “unity-lens-video” package in Ubuntu: Fix Released Bug description: Left (and Right ) clicking on any item in “More Suggestions” (in any Lens) should open a preview. This applies to Home, Music, Videos and Apps Lenses. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1170712/+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 1171567] Re: Incorrect scope files/ids of some of the default scopes
** No longer affects: unity-lens-video (Ubuntu Raring) ** No longer affects: unity-lens-music (Ubuntu Raring) ** No longer affects: unity-lens-files (Ubuntu Raring) ** No longer affects: libunity (Ubuntu Raring) ** Changed in: unity-lens-files (Ubuntu) Status: New => Fix Released ** Changed in: unity-lens-music (Ubuntu) Status: New => Fix Released ** Changed in: libunity (Ubuntu) Status: New => Fix Released ** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: unity-lens-music Status: Fix Committed => Fix Released ** Changed in: unity-lens-video Status: Fix Committed => Fix Released ** Changed in: unity-lens-files Status: Fix Committed => Fix Released ** Changed in: unity-lens-video (Ubuntu) Status: New => 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 https://bugs.launchpad.net/bugs/1171567 Title: Incorrect scope files/ids of some of the default scopes Status in LibUnity: Fix Released Status in Unity: Invalid Status in Unity Files Lens: Fix Released Status in unity-lens-music: Fix Released Status in Unity Videos Lens: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “unity-lens-files” package in Ubuntu: Fix Released Status in “unity-lens-music” package in Ubuntu: Fix Released Status in “unity-lens-video” package in Ubuntu: Fix Released Bug description: Scope (.scope) files of some of the default scopes have incorrect names, leading to scope ids such as video-video-local.scope. Files that have this issue are files/files-local.scope music/music-rhythmbox.scope music/music-banshee.scope video/video-local.scope video/video-remote.scope To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1171567/+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 1195807] Re: Unity dash previews won't load
Previews are now loaded correctly with latest 13.10, therefore marking as Fix released. ** Changed in: libunity (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libunity Status: New => 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 https://bugs.launchpad.net/bugs/1195807 Title: Unity dash previews won't load Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: I have this error in Ubuntu 13.04 and 13.10 (I also had it back in 12.10). Under the "more suggestions" in the video lens , the previews never load and it's just a spinning wheel for hours. A bug report window also pops up after about 10 seconds, and I'm finally reporting it. For Ubuntu 13.10, this same thing happens often for the smart scopes. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.4daily13.06.24-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7 Uname: Linux 3.10.0-0-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Jun 28 10:42:00 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-06-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130627) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/soundcloud/unity_soundcloud_daemon.py ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f84f4f7311e:cmpq $0x4c,(%rax) PC (0x7f84f4f7311e) ok source "$0x4c" ok destination "(%rax)" (0x0009) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so PyEval_EvalFrameEx () PyEval_EvalCodeEx () PyEval_EvalFrameEx () Title: scope-runner-dbus.py crashed with SIGSEGV in PyEval_EvalFrameEx() 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/libunity/+bug/1195807/+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 1204310] Re: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString()
Looks like a transient issue from older version of python-gobject. Please re-open if you experience this crash again. ** Changed in: libunity (Ubuntu) Status: Triaged => 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 https://bugs.launchpad.net/bugs/1204310 Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() Status in “libunity” package in Ubuntu: Fix Released Bug description: Error reported by apport on login ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130723-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Jul 23 18:13:29 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-06-17 (36 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130616) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s news/googlenews.scope ProcCwd: /home/jerome ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f544cca2711:movdqu (%rdi),%xmm1 PC (0x7f544cca2711) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 PyUnicode_FromString () pyglib_error_marshal () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 pyglib_error_check () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1204310/+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 1201526] Re: Unity.ScopeLoader crashed with SIGSEGV in g_object_ref()
** Summary changed: - scope-runner-dbus.py crashed with SIGSEGV in g_object_ref() + Unity.ScopeLoader crashed with SIGSEGV in g_object_ref() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1201526 Title: Unity.ScopeLoader crashed with SIGSEGV in g_object_ref() Status in “libunity” package in Ubuntu: Confirmed Bug description: , ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.7+13.10.20130703.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Sun Jul 14 20:47:06 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/launchpad/unity_launchpad_daemon.py SegvAnalysis: Segfault happened at: 0xb70c00e8 : mov(%esi),%eax PC (0xb70c00e8) ok source "(%esi)" (0x7273752f) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_object_ref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libunity.so.9 unity_scope_loader_export_scopes () from /usr/lib/i386-linux-gnu/libunity.so.9 ?? () from /usr/lib/i386-linux-gnu/libunity.so.9 unity_scope_loader_load_module () from /usr/lib/i386-linux-gnu/libunity.so.9 Title: scope-runner-dbus.py crashed with SIGSEGV in g_object_ref() UpgradeStatus: Upgraded to saucy on 2013-03-21 (115 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1201526/+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 1207434] Re: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString()
*** This bug is a duplicate of bug 1204310 *** https://bugs.launchpad.net/bugs/1204310 ** This bug is no longer a duplicate of bug 1206661 scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() ** This bug has been marked a duplicate of bug 1204310 scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1207434 Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() Status in “libunity” package in Ubuntu: New Bug description: help ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130723-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Jul 27 14:04:40 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py ExecutableTimestamp: 1374563432 InstallationDate: Installed on 2013-07-04 (22 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s news/googlenews.scope ProcCwd: /home/angel SegvAnalysis: Segfault happened at: 0x7ff4ab3c3c51:movdqu (%rdi),%xmm1 PC (0x7ff4ab3c3c51) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 PyUnicode_FromString () pyglib_error_marshal () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 pyglib_error_check () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() UpgradeStatus: Upgraded to saucy on 2013-07-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1207434/+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 1206661] Re: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString()
*** This bug is a duplicate of bug 1204310 *** https://bugs.launchpad.net/bugs/1204310 Looks like a transient issue from older version of python-gobject. Please re-open if you experience this crash again. ** Changed in: libunity (Ubuntu) Status: Confirmed => Invalid ** This bug has been marked a duplicate of bug 1204310 scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1206661 Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() Status in “libunity” package in Ubuntu: Invalid Bug description: help ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130723-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Jul 27 14:04:40 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py ExecutableTimestamp: 1374563432 InstallationDate: Installed on 2013-07-04 (22 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s news/googlenews.scope ProcCwd: /home/angel SegvAnalysis: Segfault happened at: 0x7ff4ab3c3c51:movdqu (%rdi),%xmm1 PC (0x7ff4ab3c3c51) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 PyUnicode_FromString () pyglib_error_marshal () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 pyglib_error_check () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() UpgradeStatus: Upgraded to saucy on 2013-07-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1206661/+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 1209346] Re: Crashed of scope-runner-dbus.py with python2
** Summary changed: - scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call() + Crashed of scope-runner-dbus.py with python2 ** Summary changed: - Crashed of scope-runner-dbus.py with python2 + Crashes of scope-runner-dbus.py with python2 ** Tags added: scopes-s -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1209346 Title: Crashes of scope-runner-dbus.py with python2 Status in “libunity” package in Ubuntu: Confirmed Bug description: Periodically crashing running the canonical directory scope ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130729-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.12-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Wed Aug 7 13:55:59 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2011-10-11 (665 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python2 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/canonicaldirectory/unity_canonicaldirectory_daemon.py ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_US LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x80e1306 :mov 0xc(%edx),%ecx PC (0x080e1306) ok source "0xc(%edx)" (0x000c) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: PyObject_CallObject () _pyglib_handler_marshal () from /usr/lib/libpyglib-2.0-python2.7.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with SIGSEGV in PyObject_CallObject() UpgradeStatus: Upgraded to saucy on 2013-08-05 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1209346/+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 1206678] Re: scope-runner-dbus.py crashed with SIGSEGV in auth_session_state_changed_cb()
** Package changed: libunity (Ubuntu) => unity-scope-gdrive (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1206678 Title: scope-runner-dbus.py crashed with SIGSEGV in auth_session_state_changed_cb() Status in “unity-scope-gdrive” package in Ubuntu: Confirmed Bug description: Searching something using unity dash, I got this crash from scope- runner. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130729-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.11-0ubuntu1 Architecture: i386 CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912 CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e Date: Tue Jul 30 22:40:57 2013 Dependencies: EcryptfsInUse: Yes ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/gdrive.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fr_FR:en PATH=(custom, user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0xb5149836:cmp%edi,(%eax) PC (0xb5149836) ok source "%edi" ok destination "(%eax)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libsignon-glib.so.1 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic (closure=0x8f800a0, return_gvalue=0x0, n_param_values=3, param_values=0x8fc6dc0, invocation_hint=0xbf9c1d6c, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454 g_closure_invoke (closure=0x8f800a0, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0x8fc6dc0, invocation_hint=invocation_hint@entry=0xbf9c1d6c) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777 Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: Upgraded to saucy on 2013-05-25 (65 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-gdrive/+bug/1206678/+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 1204272] Re: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV()
*** This bug is a duplicate of bug 1194465 *** https://bugs.launchpad.net/bugs/1194465 ** This bug is no longer a duplicate of private bug 1201917 ** This bug has been marked a duplicate of private bug 1194465 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1204272 Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV() Status in “libunity” package in Ubuntu: New Bug description: Crash when searching "Synaptic" in Unity Dashboard. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.7+13.10.20130703.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.11-0ubuntu1 Architecture: i386 CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912 CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e Date: Tue Jul 23 23:05:00 2013 Dependencies: EcryptfsInUse: Yes ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/gdrive/unity_gdrive_daemon.py ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fr_FR:en PATH=(custom, user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0xb5162756:cmp%edi,(%eax) PC (0xb5162756) ok source "%edi" ok destination "(%eax)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libsignon-glib.so.1 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic (closure=0x880f1a0, return_gvalue=0x0, n_param_values=1, param_values=0x86eae20, invocation_hint=0xbff88bbc, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454 g_closure_invoke (closure=0x880f1a0, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0x86eae20, invocation_hint=invocation_hint@entry=0xbff88bbc) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777 Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: Upgraded to saucy on 2013-05-25 (58 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1204272/+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 1223933] Re: sometimes the dash home list "no result matching your query" string
** Tags added: scopes-s ** Changed in: libunity Status: New => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223933 Title: sometimes the dash home list "no result matching your query" string Status in LibUnity: Triaged Status in “libunity” package in Ubuntu: New Status in “unity-scope-home” package in Ubuntu: New Bug description: That's happening in saucy in my current session: - open the dash, I get an empty screen with the "no result matching the query" string (the wording is not exact, I'm using a french locale and doing the approximate translation) - type something, results get listed - type backspace a few times to clear the entry, apps get listed sometimes clearly the query (either with backspace or esc) leads to the empty screen again To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1223933/+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 1224621] Re: Removing libunity9 also removes nautilus and other packages
Nautilus and other packages are patched to support integration with Unity launcher, that's why they link with libunity. ** Changed in: libunity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1224621 Title: Removing libunity9 also removes nautilus and other packages Status in “libunity” package in Ubuntu: Invalid Bug description: $ apt-get -s remove libunity9 The following packages will be REMOVED: brasero brasero-cdrkit deja-dup deja-dup-backend-gvfs deja-dup-backend-ubuntuone empathy indicator-appmenu indicator-sound libbrasero-media3-1 libunity9 mcp-account-manager-uoa nautilus nautilus-sendto nautilus-sendto-empathy nautilus-share rhythmbox-plugin-cdrecorder shotwell telepathy-indicator xchat-indicator ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libunity9 6.90.2daily13.04.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 Date: Thu Sep 12 20:05:10 2013 InstallationDate: Installed on 2011-10-21 (692 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: libunity UpgradeStatus: Upgraded to raring on 2013-01-20 (234 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1224621/+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 1237301] Re: scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call()
** Package changed: libunity (Ubuntu) => unity-scope-gdrive (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1237301 Title: scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call() Status in “unity-scope-gdrive” package in Ubuntu: Confirmed Bug description: I was using the Canonical Employee Directory scope and this occurred, but fwiw the scope worked. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.1.2+13.10.20131003-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 9 10:29:40 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-01-26 (256 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python2 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/canonicaldirectory/unity_canonicaldirectory_daemon.py SegvAnalysis: Segfault happened at: 0x53bef0 : mov 0x18(%rcx),%esi PC (0x0053bef0) ok source "0x18(%rcx)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: PyEval_CallObjectWithKeywords () _pyglib_handler_marshal () from /usr/lib/libpyglib-2.0-python2.7.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with SIGSEGV in PyEval_CallObjectWithKeywords() UpgradeStatus: Upgraded to saucy on 2013-06-07 (123 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-gdrive/+bug/1237301/+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 1235541] Re: unity-scope-loader crashed with SIGSEGV in cached_dir_invoke_monitors()
** Package changed: libunity (Ubuntu) => unity-lens-applications (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235541 Title: unity-scope-loader crashed with SIGSEGV in cached_dir_invoke_monitors() Status in “unity-lens-applications” package in Ubuntu: Confirmed Bug description: crashed while attempting to install the game limbo by terminal ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: libunity9 7.1.2+13.10.20131003-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 4 19:52:19 2013 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2013-10-04 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope applications/runningapps.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7fe0567f57e0:mov(%rbx),%rax PC (0x7fe0567f57e0) ok source "(%rbx)" (0x2d706f746b736564) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/libgnome-menu-3.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 unity_scope_dbus_connector_run () from /usr/lib/x86_64-linux-gnu/libunity.so.9 Title: unity-scope-loader crashed with SIGSEGV in g_main_context_dispatch() 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-lens-applications/+bug/1235541/+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 1229758] Re: No screenshot available for webbrowser app
** No longer affects: unity-lens-applications (Ubuntu) ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No screenshot available for webbrowser app + No screenshot available for non-click apps ** No longer affects: unity8 (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1229758 Title: No screenshot available for non-click apps Status in Camera App: New Status in Unity Click Scope: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-scope-click” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Committed Bug description: On unity8, the webbrowser is installed as a debian package, which means the scope doesn't display an application preview image. One possible discussed solution is to add hints into the webbrowser desktop file for it to find an image to preview from instead of picking it up from the store. This would avoid the fake click package that would bring in a dual desktop file problem and not much added benefit. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-lens-applications 7.1.0+13.10.20130919.3-0ubuntu2 Uname: Linux 3.0.0-3-maguro armv7l ApportVersion: 2.12.4-0ubuntu1 Architecture: armhf Date: Tue Sep 24 14:09:38 2013 InstallationDate: Installed on 2013-09-23 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130923) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: unity-lens-applications UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1229758/+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 1237257] Re: Running applications scope should be disabled
** Changed in: unity-lens-applications Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1237257 Title: Running applications scope should be disabled Status in Unity Applications Lens: Fix Released Status in “unity-lens-applications” package in Ubuntu: Fix Released Bug description: Since 'running applications' scope has been shelved for now (on the phone) and it's useless (not really hooked up), it should be disabled in the scope loader and removed from "Source" filters in Home Scope. Please note, since "Source" filters in Home are fully dynamic and partially populated from Smart Scopes on the server, I think this change doesn't need UIFE. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/1237257/+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 1238104] Re: unity-scope-loader crashed with SIGABRT in raise()
** Information type changed from Private to Public ** Package changed: libunity (Ubuntu) => unity-scope-mediascanner (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1238104 Title: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “unity-scope-mediascanner” package in Ubuntu: Confirmed Bug description: mediascanner scope crashed with a c++ exception ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: libunity9 Uname: Linux 3.0.0-3-maguro armv7l ApportVersion: 2.12.5-0ubuntu1 Architecture: armhf Date: Thu Oct 10 15:53:24 2013 ExecutablePath: /usr/bin/unity-scope-loader ExecutableTimestamp: 1381364606 InstallationDate: Installed on 2013-10-10 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131010) MarkForUpload: True ProcCmdline: /usr/bin/unity-scope-loader music/mediascanner.scope video/mediascanner.scope ProcCwd: / Signal: 6 SourcePackage: libunity StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 Title: unity-scope-loader crashed with SIGABRT in raise() 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/ubuntu/+source/unity-scope-mediascanner/+bug/1238104/+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 1238056] Re: unity scope loader crash
** Package changed: libunity (Ubuntu) => unity-scope-mediascanner (Ubuntu) ** Also affects: unity-scope-mediascanner Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1238056 Title: unity scope loader crash Status in Unity Media Scanner Scope: New Status in “unity-scope-mediascanner” package in Ubuntu: New Bug description: Crash on phone image #90 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-mediascanner/+bug/1238056/+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 1210357] Re: FTBFS
** Branch linked: lp:~mhr3/unity-lens-music/fix-1210357 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1210357 Title: FTBFS Status in unity-lens-music: Confirmed Status in “unity-lens-music” package in Ubuntu: Confirmed Bug description: The lens itself is quite troubled, maybe you all are getting rid of? (no dev since june error - GEN unity_music_daemon.vala.stamp simple-scope.vala:134.33-134.59: error: The name `FLOW' does not exist in the context of `Unity.CategoryRenderer' Unity.CategoryRenderer.FLOW); ^^^ daemon.vala:37.11-37.33: warning: unhandled error `GLib.Error' banshee.scope.export (); ^^^ daemon.vala:48.11-48.28: warning: unhandled error `GLib.Error' rb.scope.export (); ^^ Compilation failed: 1 error(s), 2 warning(s) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-lens-music 6.9.0daily13.06.21-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Thu Aug 8 22:20:05 2013 InstallationDate: Installed on 2013-08-07 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130803) MarkForUpload: True SourcePackage: unity-lens-music UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-music/+bug/1210357/+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 1229758] Re: No screenshot available for webbrowser app
Height is set to 22gu, width can be variable, but should have aspect ratio of the phone. (1gu is 18px on mako) Also nothing bad will happen if the screenshot is higher res than that. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1229758 Title: No screenshot available for webbrowser app Status in Unity Click Scope: Fix Committed Status in “unity-lens-applications” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: New Bug description: On unity8, the webbrowser is installed as a debian package, which means the scope doesn't display an application preview image. One possible discussed solution is to add hints into the webbrowser desktop file for it to find an image to preview from instead of picking it up from the store. This would avoid the fake click package that would bring in a dual desktop file problem and not much added benefit. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-lens-applications 7.1.0+13.10.20130919.3-0ubuntu2 Uname: Linux 3.0.0-3-maguro armv7l ApportVersion: 2.12.4-0ubuntu1 Architecture: armhf Date: Tue Sep 24 14:09:38 2013 InstallationDate: Installed on 2013-09-23 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130923) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: unity-lens-applications UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-click/+bug/1229758/+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 1229758] Re: No screenshot available for webbrowser app
The apps scope will now look for "X-Screenshot=/path/to/png" in the .desktop file, please use that. ** Also affects: unity-scope-click Importance: Undecided Status: New ** Changed in: unity-scope-click Assignee: (unassigned) => Michal Hruby (mhr3) ** Changed in: unity-scope-click Importance: Undecided => High ** Changed in: unity-scope-click Status: New => In Progress ** Branch linked: lp:~mhr3/unity-scope-click/handle-non-click -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1229758 Title: No screenshot available for webbrowser app Status in Unity Click Scope: In Progress Status in “unity-lens-applications” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: New Bug description: On unity8, the webbrowser is installed as a debian package, which means the scope doesn't display an application preview image. One possible discussed solution is to add hints into the webbrowser desktop file for it to find an image to preview from instead of picking it up from the store. This would avoid the fake click package that would bring in a dual desktop file problem and not much added benefit. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-lens-applications 7.1.0+13.10.20130919.3-0ubuntu2 Uname: Linux 3.0.0-3-maguro armv7l ApportVersion: 2.12.4-0ubuntu1 Architecture: armhf Date: Tue Sep 24 14:09:38 2013 InstallationDate: Installed on 2013-09-23 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130923) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: unity-lens-applications UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-click/+bug/1229758/+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 1229793] Re: FTS extension should be disabled for Ubuntu Touch
** Branch linked: lp:~unity-team/zeitgeist/disable-fts-on-touch -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1229793 Title: FTS extension should be disabled for Ubuntu Touch Status in “zeitgeist” package in Ubuntu: New Bug description: The zeitgeist-core package includes also the FTS extension that uses Xapian to index and search data indexed by zeitgeist, but we have different solution on the touch images (mediascanner) and the xapian- based DB just unnecessarily hogs up CPU and RAM. Therefore we should disable the extension for the touch images. Attached a branch with tiny patch that does this (hopefully without breaking other derivatives), we should provide proper package split in the 14.04 cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1229793/+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 1229793] [NEW] FTS extension should be disabled for Ubuntu Touch
Public bug reported: The zeitgeist-core package includes also the FTS extension that uses Xapian to index and search data indexed by zeitgeist, but we have different solution on the touch images (mediascanner) and the xapian- based DB just unnecessarily hogs up CPU and RAM. Therefore we should disable the extension for the touch images. Attached a branch with tiny patch that does this (hopefully without breaking other derivatives), we should provide proper package split in the 14.04 cycle. ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1229793 Title: FTS extension should be disabled for Ubuntu Touch Status in “zeitgeist” package in Ubuntu: New Bug description: The zeitgeist-core package includes also the FTS extension that uses Xapian to index and search data indexed by zeitgeist, but we have different solution on the touch images (mediascanner) and the xapian- based DB just unnecessarily hogs up CPU and RAM. Therefore we should disable the extension for the touch images. Attached a branch with tiny patch that does this (hopefully without breaking other derivatives), we should provide proper package split in the 14.04 cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1229793/+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 1229681] Re: Unity7: Application appear twice in the dash home page
The issue here seems to be that unpinning an app pushes a zeitgeist event with application scheme and full path to the desktop file. If a desktop file is present in the standard XDG directories, the full path should be omitted and only desktop id (as per fdo menu spec) should be used - ie instead of "application:///usr/share/applications/foo/bar.desktop", "application ://foo-bar.desktop" should be used. This will ensure that the event is correctly grouped with all the other events that we get from elsewhere about the application. ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Status: New => 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/1229681 Title: Unity7: Application appear twice in the dash home page Status in Unity: Confirmed Status in “unity” package in Ubuntu: New Bug description: I'm porting the commercial apps from Raring to Saucy and noticed apps were appearing twice in the home dash. Steps to reproduce: 1. Open Software center 2. Click on the small arrow next to all software and select "for purchase" 3. Install a 0$ app from that section 4. Wait for the app to install 5. Launch the application 6. Close the application 7. Remove the application from the launcher 8. Open the dash note the app appears twice in the home page ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Sep 24 12:30:15 2013 InstallationDate: Installed on 2013-09-04 (19 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130903) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1229681/+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 1224643] Re: Some TestIconLoader unit tests intermittently fail during Jenkins CI
Fwiw IconLoader doesn't use nor need DBus, so the error is something completely unrelated. -- 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/1224643 Title: Some TestIconLoader unit tests intermittently fail during Jenkins CI Status in Unity: Fix Committed Status in “unity” package in Ubuntu: New Bug description: During Jenkins Continuous Integration, we get intermittent TestIconLoader unit test failures. It's usually one or more of the following tests: TestIconLoader.TestGetOneIcon TestIconLoader.TestGetAnnotatedIcon TestIconLoader.TestGetColorizedIcon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1224643/+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 1209346] Re: scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call()
Most scopes processes will now quit after a while of inactivity (to save resources), of course they're respawned once there's a query directed at them. Also, by default searches in a python scope run in different threads, so this is likely connected to a threading issue. (looks like py3 doesn't have these issues though) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1209346 Title: scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call() Status in “libunity” package in Ubuntu: Confirmed Bug description: Periodically crashing running the canonical directory scope ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130729-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.12-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Wed Aug 7 13:55:59 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2011-10-11 (665 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python2 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/canonicaldirectory/unity_canonicaldirectory_daemon.py ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_US LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x80e1306 :mov 0xc(%edx),%ecx PC (0x080e1306) ok source "0xc(%edx)" (0x000c) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: PyObject_CallObject () _pyglib_handler_marshal () from /usr/lib/libpyglib-2.0-python2.7.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with SIGSEGV in PyObject_CallObject() UpgradeStatus: Upgraded to saucy on 2013-08-05 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1209346/+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 1209346] Re: scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call()
Is this only affecting the canonical directory scope, or is this a problem with different scopes as well? -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1209346 Title: scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call() Status in “libunity” package in Ubuntu: Confirmed Bug description: Periodically crashing running the canonical directory scope ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130729-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.12-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Wed Aug 7 13:55:59 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2011-10-11 (665 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python2 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/canonicaldirectory/unity_canonicaldirectory_daemon.py ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_US LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x80e1306 :mov 0xc(%edx),%ecx PC (0x080e1306) ok source "0xc(%edx)" (0x000c) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: PyObject_CallObject () _pyglib_handler_marshal () from /usr/lib/libpyglib-2.0-python2.7.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with SIGSEGV in PyObject_CallObject() UpgradeStatus: Upgraded to saucy on 2013-08-05 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1209346/+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 1225391] Re: Installed Applications is blank after doing a search
That's hard to confirm without actual steps to reproduce, but unity will display the expander only if there are >6 results in the model, so it's more than likely that the backend model is fine. What happens when you get this bug and try to expand the category? ** Changed in: unity8 Status: Confirmed => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1225391 Title: Installed Applications is blank after doing a search Status in Unity Applications Lens: Confirmed Status in The Unity 8 shell: Incomplete Status in “unity-lens-applications” package in Ubuntu: Confirmed Bug description: Steps: 1. Search for applications in the home scope 2. Dismiss the search Result: sometimes the Installed Applications section is then blank (see attached screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/1225391/+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 1223933] Re: sometimes the dash home list "no result matching your query" string
** Also affects: libunity Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223933 Title: sometimes the dash home list "no result matching your query" string Status in LibUnity: New Status in “libunity” package in Ubuntu: New Status in “unity-scope-home” package in Ubuntu: New Bug description: That's happening in saucy in my current session: - open the dash, I get an empty screen with the "no result matching the query" string (the wording is not exact, I'm using a french locale and doing the approximate translation) - type something, results get listed - type backspace a few times to clear the entry, apps get listed sometimes clearly the query (either with backspace or esc) leads to the empty screen again To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1223933/+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 855735] Re: scope factory has improper search path if prefix is not set at configure time
** Changed in: libunity Status: Confirmed => Fix Released ** Changed in: libunity Milestone: None => 6.14.0 ** Changed in: libunity Milestone: 6.14.0 => 7.0.0 ** Changed in: unity Status: Confirmed => Fix Released ** Changed in: unity Milestone: None => 7.0.1 ** No longer affects: unity-2d ** No longer affects: libunity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/855735 Title: scope factory has improper search path if prefix is not set at configure time Status in LibUnity: Fix Released Status in Unity: Fix Released Bug description: if one doesn't set the --prefix at configure time, the path to search for remote scopes gets set to NONE/share/unity/lenses/ disabling unity from loading remote scopes. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/855735/+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 1189616] Re: libunity doesn't built against vala-0.20
** Changed in: libunity Status: New => Confirmed ** Also affects: vala (Ubuntu) Importance: Undecided Status: New ** Changed in: libunity Status: Confirmed => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1189616 Title: libunity doesn't built against vala-0.20 Status in LibUnity: Incomplete Status in “libunity” package in Ubuntu: New Status in “vala” package in Ubuntu: New Bug description: libunity currently builds against vala-0.18 but that version of vala has been removed from Debian and will (probably) be removed from Saucy. libunity currently fails to build against the current default vala in Saucy (vala-0.20). Please update libunity to build against vala-0.20 and change your build-depends from valac-0.18 (>= 0.16) to just valac (>= 0.16) to make future transitions easier. libunity does build against valac-0.16 but 0.16 will be removed as soon as packages in Ubuntu don't need it any more. GEN unity.deps GICOMP Unity-6.0.gir Unity-6.0.gir:100:81: warning: element annotation from state 9 is unknown, ignoring Unity-6.0.gir:3263:52: warning: element annotation from state 9 is unknown, ignoring make[4]: Leaving directory `/«PKGBUILDDIR»/src' make[3]: Leaving directory `/«PKGBUILDDIR»/src' Making all in extras make[3]: Entering directory `/«PKGBUILDDIR»/extras' GEN libunity_extras_la_vala.stamp make all-am make[4]: Entering directory `/«PKGBUILDDIR»/extras' CC libunity_extras_la-unity-extra-preview-player-client.lo CC libunity_extras_la-unity-extra-utils.lo CCLD libunity-extras.la GICOMP UnityExtras-6.0.gir UnityExtras-6.0.gir:-1: In PreviewPlayer: error: type reference 'ExtrasPreviewPlayerClass' not found make[4]: *** [UnityExtras-6.0.typelib] Error 1 make[4]: Leaving directory `/«PKGBUILDDIR»/extras' ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libunity9 7.0.2daily13.06.06.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Mon Jun 10 16:18:19 2013 MarkForUpload: True SourcePackage: libunity UpgradeStatus: Upgraded to saucy on 2013-05-07 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1189616/+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 1160876] Re: Previews for majority of the 100 scopes don't work
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.1.0 ** Changed in: libunity (Ubuntu) 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 https://bugs.launchpad.net/bugs/1160876 Title: Previews for majority of the 100 scopes don't work Status in LibUnity: Fix Released Status in Unity: Invalid Status in “libunity” package in Ubuntu: Fix Released Bug description: Previews for the majority of 100 scopes don't work from Home lens view. Right-clicking an item such as a "Code" coming from local launchpad scope gives a completely empty preview in the Dash. While it's expected that most of the 100 scopes don't provide a useful preview, we should get a generic preview instead (which is transparently handled by libunity now), but for some reason it's not happening. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1160876/+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 1199961] Re: test-gtest-dbus fails and crashes when running TestScope* tests
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1199961 Title: test-gtest-dbus fails and crashes when running TestScope* tests Status in LibUnity: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Running test-gtest-dbus leads to this crash and failures http://pastebin.ubuntu.com/5862732/ To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1199961/+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 1159677] Re: Unity/Libunity unit tests broken by latest glib
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.0.0 -- 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/1159677 Title: Unity/Libunity unit tests broken by latest glib Status in LibUnity: Fix Released Status in Unity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “libunity” source package in Raring: Fix Released Status in “unity” source package in Raring: Fix Released Bug description: Latest glib brought https://git.gnome.org/browse/glib/commit/?id=f641699299ed2713cf247e3465bb1a21612b36f7 which broke some tests in the chroot due to the Exec= keys for desktop files we are testing against not being installed. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1159677/+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 892756] Re: Lenses get confused if scope names are too similar
** Changed in: libunity Status: Incomplete => Fix Released ** Changed in: libunity Milestone: 5.4.0 => 6.14.0 -- 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/892756 Title: Lenses get confused if scope names are too similar Status in LibUnity: Fix Released Status in Unity: Expired Status in “libunity” package in Ubuntu: Expired Status in “unity” package in Ubuntu: Expired Bug description: If scopes in different lenses have names that are too similar to each other, results from one lens can show up incorrectly under another one. This can be most easily noticed in the home lens, but can occur under individual lenses as well. For example, installing the Bliss lens (lp:unity-lens-bliss) and the Books lens (lp:unity-lens-books) can lead to results from the Bliss lens (applications) showing up under both Bliss's applications category and the Books category when a global search is done. A screenshot is attached to demonstrate this The screenshot contains results for the default applications lens, the Bliss lens and the Books lens, with Firefox showing up under all three. It should not show up under Books. This happens due to the fact that the local scope in the Bliss lens dbus path is named: ''/net/launchpad/unitylensbliss/scope/main" and Books one is named "/net/launchpad/lens/books/scope/main". Using D-Feet to view dbus introspection data, it appears that the details for both net.launchpad.UnityLensBliss.Lens and net.launchpad.Lens.Books show /com/canonical/dee/model/com/canonical/Unity/Scope/main/T1321723498/Results in their introspection data. Note that 'main' appears as the final part of the scope's dbus path and the scope definition lens's introspection data. A workaround for this is to ensure that the last part of the dbus path of a scope is unique. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/892756/+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 1170712] Re: Left and Right clicking on “More Suggestions” should open a preview
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.1.0 ** Changed in: unity-lens-video Status: Fix Committed => Fix Released ** Changed in: unity-scope-home 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 https://bugs.launchpad.net/bugs/1170712 Title: Left and Right clicking on “More Suggestions” should open a preview Status in LibUnity: Fix Released Status in Unity: Fix Released Status in Unity Videos Lens: Fix Released Status in Unity Home Scope: Fix Released Status in “libunity” package in Ubuntu: New Status in “unity-lens-video” package in Ubuntu: New Status in “libunity” source package in Raring: New Status in “unity-lens-video” source package in Raring: New Bug description: Left (and Right ) clicking on any item in “More Suggestions” (in any Lens) should open a preview. This applies to Home, Music, Videos and Apps Lenses. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1170712/+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 1193096] Re: Unity: no icon for app and app cannot be launched
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.1.0 ** Changed in: touch-preview-images Status: Confirmed => 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 https://bugs.launchpad.net/bugs/1193096 Title: Unity: no icon for app and app cannot be launched Status in LibUnity: Fix Released Status in Touch Preview Images: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: In saucy-19 on Nexus and Nexus 4 searching for applications shows many with no icon, and these cannot be launched. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1193096/+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 1212246] Re: Can't pass a URI like "application://" to an ActivationResponse
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.1.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1212246 Title: Can't pass a URI like "application://" to an ActivationResponse Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: When creating an ActivationResponse, the URI provided is not passed back, instead it's always overwritten by the URI that invoked the request. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1212246/+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 1062099] Re: libunity9 now depends on unity-common which depends on compiz
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1062099 Title: libunity9 now depends on unity-common which depends on compiz Status in LibUnity: Fix Released Status in libunity 6.0 series: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “libunity” source package in Quantal: New Bug description: [Test Case] Ensure that libunity9 can be installed without the need of installing compiz-gnome. [Regression Potential] Errors/warnings due to missing schemas. Original description: Originally reported at http://ubuntuforums.org/showpost.php?p=12278363&postcount=45 To fix bug 1055019, libunity 9 now depends on unity-common. This is a serious issue for the Ubuntu GNOME Remix because core apps like deja-dup, empathy, nautilus, and shotwell depend on libunity9. unity-common depends on compiz but we do not ship compiz. http://paste.ubuntu.com/1261477/ If we take into account bug 1036752, shipping GNOME Classic with Compiz means that the GNOME Classic session is broken. (That is also a critical bug for Edubuntu). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libunity9 6.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 03:58:23 2012 SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1062099/+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 973518] Re: Build failure: be tolerant of missing GSettings
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.1.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/973518 Title: Build failure: be tolerant of missing GSettings Status in LibUnity: Fix Released Status in libunity 6.0 series: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “libunity” source package in Quantal: New Bug description: [Test Case] 1. Open a terminal 2. Run `XDG_DATA_DIRS=/home python -c "from gi.repository import Unity; print Unity.LauncherFavorites.get_default();"` -> Verify there is no crash, just warnings [Regression Potential] Schema related errors. Original description: Discovered while setting up a Jenkins build in a clean env: if the lib isn't already installed, tests fail due to missing GSettings schemas. Ted suggests either setting up GSettings to use the local schemas or make the lib tolerant of finding none. Upping priority as this build will appear broken until fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/973518/+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 1029949] Re: unity-webapps-context-daemon crashed with SIGSEGV in g_closure_invoke()
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.1.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1029949 Title: unity-webapps-context-daemon crashed with SIGSEGV in g_closure_invoke() Status in LibUnity: Fix Released Status in libunity 6.0 series: Fix Released Status in WebApps: libunity: Invalid Status in “libunity” package in Ubuntu: Fix Released Status in “libunity” source package in Quantal: Fix Released Bug description: [Impact] A common crash seen for example while closing Chromium from Launcher. [Test case] Run automated tests or try to reproduce the crash manually by closing Chromium. [Regression potential] Low, fixes a segfault from non-null terminated array. --- ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity-webapps-service 1.8.0-0quantal2 [origin: LP-PPA-webapps-preview] ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 ApportVersion: 2.4-0ubuntu5 Architecture: amd64 CrashCounter: 1 CrashDB: libunity_webapps Date: Fri Jul 27 19:14:29 2012 ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-context-daemon InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcCmdline: /usr/lib/libunity-webapps/unity-webapps-context-daemon Launchpad launchpad.net icon://launchpad [Invalid\ UTF-8] SegvAnalysis: Segfault happened at: 0x7fbf5dd2ded6:movlpd (%rdi),%xmm1 PC (0x7fbf5dd2ded6) ok source "(%rdi)" (0x000b) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity-webapps StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ThirdParty: True Title: unity-webapps-context-daemon crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to quantal on 2012-07-24 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1029949/+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 1214125] Re: unity-scope-mock stopped working after libunity r276
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: libunity Milestone: None => 7.1.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1214125 Title: unity-scope-mock stopped working after libunity r276 Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: Sorry for filing this under libunity, but we don't have bugs for the mock lens/scope. I suspect the culprit to be r276, which changed how ScopeResult objects are instantiated. The scope complains as follows: > unbound method scope_result_create() must be called with ScopeResult instance as first argument (got unicode instance instead) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1214125/+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 1063300] Re: unity-applications-daemon crashed with SIGSEGV in g_strdup()
** Changed in: libunity 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 https://bugs.launchpad.net/bugs/1063300 Title: unity-applications-daemon crashed with SIGSEGV in g_strdup() Status in LibUnity: Fix Released Status in libunity 6.0 series: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “libunity” source package in Quantal: Fix Released Bug description: [Impact] - possible crash of lenses in some rare cases [Testcase] - as the crash is very rare (and probably depends on timing), there's no clear test case for this exact issue, please make sure that lenses still work as expected [Regression potential] - unity crashes when it is (re-)started, or when a lens is restarted Original description: = Happened after every logon so far. ( Fresh install of Ubuntu 12.10 daily build ) ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity-lens-applications 6.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Sun Oct 7 17:52:35 2012 ExecutablePath: /usr/lib/unity-lens-applications/unity-applications-daemon InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20121007) ProcCmdline: /usr/lib/unity-lens-applications/unity-applications-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0xb6db66b6:movdqu (%edi),%xmm1 PC (0xb6db66b6) ok source "(%edi)" (0x0072) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-lens-applications StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 g_strdup () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libunity.so.9 unity_protocol_lens_service_activate_with_hints () from /usr/lib/i386-linux-gnu/libunity/libunity-protocol-private.so.0 ?? () from /usr/lib/i386-linux-gnu/libunity.so.9 Title: unity-applications-daemon crashed with SIGSEGV in g_strdup() 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/libunity/+bug/1063300/+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 1213999] Re: Provide easy way for OEMs to override default settings
Closing as Invalid as a different solution will be used.
** Changed in: d-conf (Ubuntu)
Status: New => Invalid
--
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/1213999
Title:
Provide easy way for OEMs to override default settings
Status in “d-conf” package in Ubuntu:
Invalid
Bug description:
Part of the requirements is to allow the OEMs to be able to override
some settings that are stored in dconf (for example which lens pages
in the dash are visible by default). Usually we'd just add a new
.override file into /usr/share/glib-2.0/schemas, but this will not be
possible for the OEMs as any changes they make will not change the
base Ubuntu image.
A solution that we agreed upon is to extend our XDG_DATA_DIRS (we'll
prepend a new "/custom" path to the dirs where the OEM's overlay will
be mounted), but since dconf doesn't support this type of layering
(real schema in /usr/share/glib-2.0/schemas and possible defaults
overrides in /custom/...), we decided to add a symlink in
/usr/share/glib-2.0/schemas/xyz-oem-gschema.override which will point
to the override file in the OEM overlay ("/custom/..." - TBD).
Once we have the override file in place, we need to recompile the
schemas (by invoking glib-compile-schemas), to make sure the new
defaults are accounted for, although this will have to be done in a
boot script (ideally with a stamp file so we don't unnecessarily
recompile it on each boot).
With this solution we allow the operators to change default settings,
while still being able to upgrade the base image and change the
shipped schemas (but keeping the OEM overrides in place). Plus if the
operator ships applications that have their own schemas, this is still
possible by compiling a separate set of schemas in the overlay. And on
top of everything we don't need to change our apps/daemons to check
special OEM schemas that might and might not be installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1213999/+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
