[Dx-packages] [Bug 1344990] Re: Volume control jumps back and forth
Actually, this has nothing to do with Audacious, it's just that the volume control is not stable. -- 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/1344990 Title: Volume control jumps back and forth Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1) Listen to music via Audacious 2) Open volume control from Unity's panel 3) Try to change the volume What happens: - The volume control doesn't follow mouse properly and jumps back and forth What should happen: - The obvious thing I believe this is regression as didn't notice anything weird in 13.10 with exactly same setup. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jul 19 19:51:32 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1344990/+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
Re: [Dx-packages] [Bug 1331873] Re: the Ubuntu Help should be Ubuntu Kylin Help
I tested it in ubuntukylin 14.10 a short while ago ,it works well ,thank you ! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1331873 Title: the Ubuntu Help should be Ubuntu Kylin Help Status in The Session Menu: Fix Released Status in Ubuntu Kylin: Fix Committed Status in “indicator-session” package in Ubuntu: Fix Released Bug description: the Ubuntu Helpshould be Ubuntu Kuliy Help in the indicator ,since this is ubuntuKylin system. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1331873/+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 1331873] Re: the Ubuntu Help should be Ubuntu Kylin Help
** Changed in: ubuntukylin Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1331873 Title: the Ubuntu Help should be Ubuntu Kylin Help Status in The Session Menu: Fix Released Status in Ubuntu Kylin: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Bug description: the Ubuntu Helpshould be Ubuntu Kuliy Help in the indicator ,since this is ubuntuKylin system. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1331873/+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 732653] Re: Menus are hidden by default
Piedro, in the bug description I specifically said that Adding any options would not fix this bug, which is about menus being hidden *by default*. So no, this is not about adding options. (Which is why, incidentally, the purported Desired change is irrelevant to this bug.) The problem with Leonardo's comment isn't that he likes menus the way they are. The problem is that he made three empirical claims, none of them with any evidence, and all of them probably false; and that he suggested that people switch to another DE, which is gratuitously unhelpful, because most Ubuntu users don't and needn't know what a DE is. Editing bug comments is bug 80895. -- 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/732653 Title: Menus are hidden by default Status in Ayatana Design: Confirmed Status in Unity: Confirmed Status in “unity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Triaged Bug description: Ubuntu 11.04, Ubuntu 11.10, Ubuntu 12.04 1. Log in to Unity, and try to connect to a server: File Connect to Server. 2. Launch Firefox, and try to select an item from the Bookmarks menu. What happens: 1. The File menu, and the rest of Nautilus's menus, are hidden by default. - Unless you mouse over it, the menu bar is blank. - When you mouse over it, the menus appear. 2. The Bookmarks menu, and the rest of Firefox's menus, are hidden by default. - Unless you mouse over it, the menu bar contains only the text Firefox Web Browser, which isn't useful at all (especially, but not only, since the real name of the application -- Mozilla Firefox -- is already present in the window title bar). - When you mouse over it, the menus appear, partly but not completely replacing the previous text: Firefox W File Edit View…. What should happen: Menus should be visible by default, so that you can know that they exist without scrubbing the screen, and so that you can see where a menu is each time you aim for it. The current behavior has led some people (including, this week, one of my design colleagues) to conclude that Ubuntu applications don't have menus when they do. For example http://www.techrepublic.com/blog/opensource/gnome-shell-vs-ubuntu- unity-which-desktop-wins/2291: One of the most handy menu entries in GNOME (for me at least) is the Connect to Server entry in the Places menu. This allows the user to connect to nearly any type of server quickly and easily. The user can even connect to a Windows Share from here. In Unity - you won’t find that. In fact, you will be hard pressed to find any means to connect to a server in Ubuntu Unity. In bug 720424, Jono Bacon reported that when we did some developer tools usability testing last week and on some other occasions when I have had someone use Unity, I have noticed that some folks don't realize there is a menu there as it is not visible. This was confirmed by usability testing of Ubuntu 11.04, where 2 out of the 10 people who needed to use a menu item could not find the menus at all -- and of the 8 who did find them, 7 did so only when the window was maximized. https://lists.ubuntu.com/archives/ubuntu- desktop/2011-April/002970.html (Usability testing results of Ubuntu 11.10 or 12.04 have never been published, but this part of the design did not change.) Do not confuse this bug with bug 682788, which is about adding an option for visibility. Adding any options would not fix this bug, which is about menus being hidden *by default*. - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issues described in this bug and also issues described in the duplicates of this bus. Note the 'official' bug that tracks the implementation of this project is bug #682788 The following options will be added to 'System Settings/Appearance': --- Menus Location: Global/Local Visibility: Hidden/Always displayed --- More details to follow during the 12.10 cycle... ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/732653/+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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
It seems like FloatingWindow is being added to the queue with QueueObjectLayout in FloatingWindow.cpp, but might not be removed from the queue before it's deleted. Its ancestor Area has the same potential issue, as well. So, moving the RemoveObjectFromLayoutQueue call in View and Layout destructors to their common ancestor Area's destructor (as in the attached patch) should fix that issue (and this bug, unless something else is overwriting the objects in that queue). ** Patch added: nux-remove-area-from-layout-queue.patch https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337244/+attachment/4164791/+files/nux-remove-area-from-layout-queue.patch -- 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/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from
[Dx-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
Joining the me too section here as freshly new baked 14.04 user. Came here as the hud process currently eats 2,454g and system checking processes (zfswatcher) are failing due to out of memory issues. And yes, I'm a heavy user of Firefox toolbar bookmarks, too. Trying the workaround of disabling the Firefox integration now. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in The Application Menu: Confirmed Status in Unity: Won't Fix Status in “hud” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
The attachment nux-remove-area-from-layout-queue.patch seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from
[Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Trusty
I uploaded these, thanks Will. ** Changed in: gtk+3.0 (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: gtk+3.0 (Ubuntu Trusty) Assignee: (unassigned) = William Hua (attente) ** Changed in: unity-gtk-module (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: unity-gtk-module (Ubuntu Trusty) Assignee: (unassigned) = William Hua (attente) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Trusty Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Trusty: In Progress Status in “unity-gtk-module” source package in Trusty: In Progress Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === % === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1208019] Re: Eclipse menus doesn't show up in Trusty
** Branch linked: lp:unity-gtk-module/14.04 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Trusty Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Trusty: In Progress Status in “unity-gtk-module” source package in Trusty: In Progress Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === % === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 972199] Re: Attached devices doesn't show webcams or scanners
Aritchie, it's unlikely to be removed from 12.04, because it's not a high-impact bug. https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/972199 Title: Attached devices doesn't show webcams or scanners Status in The Session Menu: Won't Fix Status in “indicator-session” package in Ubuntu: Won't Fix Bug description: When I plug in a webcam or the scanner this isn't shown under attached devices as in 11.10. Only printer is shown there - which is a network printer which is connected already when I boot the PC. When I plugin the webcam before I boot I also can't see it - but the webcam works fine for example with cheese. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-session 0.3.95-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Tue Apr 3 10:00:04 2012 EcryptfsInUse: Yes SourcePackage: indicator-session UpgradeStatus: Upgraded to precise on 2012-03-21 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/972199/+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 1322769] Re: 14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with VirtualBox VMs Running
This looks similar to this bug: https://bugs.launchpad.net/unity/+bug/1305586 However - I've found that another issue is that whatever application has held on to the cursor, you will end up typing your password directly into. Google Chrome and Chromium seem to be the two most popular culprits. -- 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/1322769 Title: 14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with VirtualBox VMs Running Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: I have replicated this bug on two different laptops, one at work running mulitple monitors, one at home running a single monitor. Symptom: When the Unity System Settings Lock Screen Settings activate, and I notice the screen has gone blank and locked, I re-activate the keyboard (usually left CRTL) and the 14.04 LTS Login Screen appears. In all cases the keyboard is locked out and non-responsive, I can click on the password box for my account and anything I type no longer appears. I have to select Switch Account option with the mouse to get a new login screen for my account and I can log in. In some cases both the keyboard and the mouse input is locked out and non-responsive. I can not select Switch Account and must power off the laptop which of course is dangerous for the file systems of both Windows VMs that are running and the host/14.04 LTS file system. I have already corrupted the Windows VM file systems and had to repair while testing this bug for repeatability. Both laptops run the AMD64 version of Ubuntu 14.04 LTS. Both have built in Intel Integrated Graphics, one laptop with the older Ironlake, one with the newer ivy bridge. Both are running Oracle VirtualBox but different version: 1. Home is running the Ubuntu 14.04 Repository version of Oracle VirtualBox (Currently 4.3.10_Ubuntu r93012) 2. Work is running the Oracle downloadable AMD64 version of Oracle VirtualBox Currently 4.3.12 3. Both have the respective Oracle Virtual Box Extensions installed for 4.3.10 and 4.3.12 3. Both are running Windows 7 64 VMs Both 14.04 LTS have the following System Settings for Lock Screen: Brightness slider - All the way left Dim screen to save power - Checked Lock - Switch to ON position Lock Screen after: 5 minutes Require my password when weking form suspend - Checked I have tested this with both a VM running (no other running applications were tested) and with no apps running (fresh boot and login into 14.04 LTS unity desktops). 1. On fresh boot with no apps running the lock screen activates (after 5 min of no activity) and when I re-activate the laptops (usually pressing left CTRL on keyboard) I get the login screen and can enter my password successfully and the Unity desktop is presented. 2. On fresh boot with a Windows 7 VM running the lock screen activates (after 5 min of no activity) and when I re-activate the laptops (usually pressing the left CTRL on the keyboard) I get the login screen and the keyboard is locked and non-responsive and I can not log into my account. Variations on 2. I can not enter password but I can use CTRL-ALT-F1, etc. to switch to TTY and gain access to system. Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. the entire keyboard appears locked out, but I can use mouse and select Switch Account to force a new login screen to appear and the keyboard now works to enter password. Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. and I can not use the mouse, the entire input interfaces appear locked out and I have to power off the laptops to restart and be able to log in to Unity again. If I turn Lock: Off but leave Turn Screen off when inactive for 5 minutes set. If I have a VM running or no apps running, after 5 minutes the screen dims. I re-activate the system by pressing a key on the keyboard (usually the left CTRL key) and the Unity desktop re- appears. This bug only seems to occur when the Lock/Require Password when waking from suspend is active. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1322769/+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 1345505] Re: lock screen leaks keystrokes to window behind greeter
This seems to happen most frequently with Google Chrome and Chromium - or at least, they're two easy culprits to identify. :) Seems related to the following: https://bugs.launchpad.net/unity/+bug/1305586 I'm not sure if the fix in that bug is what caused this or if another issue arose elsewhere. -- 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/1345505 Title: lock screen leaks keystrokes to window behind greeter Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1345505/+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 1307657] Re: UBUNTU_MENUPROXY should not be set in Xfce
*** This bug is a duplicate of bug 1347272 *** https://bugs.launchpad.net/bugs/1347272 ** This bug has been marked a duplicate of bug 1347272 Several XFCE applications appear unresponsive after communicating with a daemon -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1307657 Title: UBUNTU_MENUPROXY should not be set in Xfce Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “xfce4-indicator-plugin” package in Ubuntu: Confirmed Bug description: To reproduce: either start with a fresh Ubuntu install and then install xubuntu-desktop, or start with Xubuntu and then install ubuntu-desktop - ie have both Xfce and Unity installed on the same machine. Xfce now has support for gtk3 indicators launched by upstart, but indicator-appmenu is totally broken - it will constantly crash the panel and applications. Xfce has a mechanism to hide indicators, and then the frontend UI will not be loaded in the panel, but it seems that UBUNTU_MENUPROXY is still being set in Xfce, which causes menus to disappear from applications, even though nothing is available to receive them. I discussed this with tedg and he suggested that the problem may be to do with the upstart service which sets UBUNTU_MENUPROXY, ie /usr/share/upstart/sessions/unity-gtk-module.conf We may in future get the appmenus working in Xfce, and then we would need some way to turn the menuproxy on and off depending on the user configuration. But for now, since they are broken anyway, it would be easiest to simply blacklist xubuntu desktop completely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 14 19:40:36 2014 InstallationDate: Installed on 2014-02-11 (61 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140210) PackageArchitecture: all SourcePackage: unity-gtk-module UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1307657/+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 1185065] Re: autopilot should prevent screen from locking during test runs
** Changed in: unity (Ubuntu) Status: New = Invalid ** Changed in: unity Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1185065 Title: autopilot should prevent screen from locking during test runs Status in Autopilot: Won't Fix Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: On the phone, autopilot tests get interrupted by the screen locking. Autopilot should prevent the screen from being locked while running tests. To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1185065/+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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
*** This bug is a duplicate of bug 1163041 *** https://bugs.launchpad.net/bugs/1163041 ** Also affects: nautilus Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in Nautilus: New Status in Unity: Triaged Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1170647/+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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
** Also affects: nux Importance: Undecided Status: New ** Also affects: nux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: New Status in Unity: Confirmed Status in “nux” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123
[Dx-packages] [Bug 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
** No longer affects: unity (Ubuntu) ** No longer affects: freetype (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 https://bugs.launchpad.net/bugs/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: Confirmed Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() 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/cairo/+bug/1199571/+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 1278680] Re: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property()
** Information type changed from Private Security to Public ** Also affects: indicator-bluetooth Importance: Undecided Status: New ** Changed in: indicator-bluetooth (Ubuntu) Status: Confirmed = Triaged ** Changed in: indicator-bluetooth Status: New = Confirmed ** Description changed: - No funciona mi bluetooth + My bluetooth device doesn't work at all. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 10 21:23:54 2014 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2013-06-04 (251 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: - Segfault happened at: 0x8054fd8: mov(%ebx),%eax - PC (0x08054fd8) ok - source (%ebx) (0x) not located in a known VMA region (needed readable region)! - destination %eax ok + Segfault happened at: 0x8054fd8: mov(%ebx),%eax + PC (0x08054fd8) ok + source (%ebx) (0x) not located in a known VMA region (needed readable region)! + destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: - ?? () - ?? () - ?? () - g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 - g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 + ?? () + ?? () + ?? () + g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 + g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() UpgradeStatus: Upgraded to trusty on 2014-01-07 (34 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.indicator-bluetooth.log: ** (process:2140): CRITICAL **: bluez.vala:184: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method GetProperties with signature on interface org.bluez.Adapter doesn't exist -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1278680 Title: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property() Status in Bluetooth Menu: Confirmed Status in “indicator-bluetooth” package in Ubuntu: Triaged Bug description: My bluetooth device doesn't work at all. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 10 21:23:54 2014 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2013-06-04 (251 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: Segfault happened at: 0x8054fd8: mov(%ebx),%eax PC (0x08054fd8) ok source (%ebx) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() UpgradeStatus: Upgraded to trusty on 2014-01-07 (34 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.indicator-bluetooth.log: ** (process:2140): CRITICAL **: bluez.vala:184: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method GetProperties with signature on interface org.bluez.Adapter doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1278680/+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 1345505] Re: lock screen leaks keystrokes to window behind greeter
** Description changed: - When my machine comes out of suspend, I am shown the lightdm greeter. + When my machine comes out of suspend, I am shown the unity lockscreen. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). - ProblemType: Bug - DistroRelease: Ubuntu 14.10 + ProblemType: BugDistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) - InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) - SourcePackage: lightdm + InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 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/1345505 Title: lock screen leaks keystrokes to window behind greeter Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When my machine comes out of suspend, I am shown the unity lockscreen. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: BugDistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1345505/+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 1344990] Re: Volume control jumps back and forth
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) 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/1344990 Title: Volume control jumps back and forth Status in Sound Menu: New Status in Unity: New Status in “indicator-sound” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen to music via Audacious 2) Open volume control from Unity's panel 3) Try to change the volume What happens: - The volume control doesn't follow mouse properly and jumps back and forth What should happen: - The obvious thing I believe this is regression as didn't notice anything weird in 13.10 with exactly same setup. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jul 19 19:51:32 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1344990/+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 1344990] Re: Volume control jumps back and forth
** Also affects: indicator-sound Importance: Undecided Status: New ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1344990 Title: Volume control jumps back and forth Status in Sound Menu: New Status in Unity: New Status in “indicator-sound” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen to music via Audacious 2) Open volume control from Unity's panel 3) Try to change the volume What happens: - The volume control doesn't follow mouse properly and jumps back and forth What should happen: - The obvious thing I believe this is regression as didn't notice anything weird in 13.10 with exactly same setup. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jul 19 19:51:32 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1344990/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
dovercrash: I'm having that issue with chrome as well. $ sudo apt-cache policy google-chrome-stable google-chrome-stable: Installed: 36.0.1985.125-1 Same versions of unity and compiz that you have. Tried to reproduce it with other applications (gedit, gnome-terminal, firefox), but it does only happen in Google Chrome. My workaround is to click some of the icons on the taskbar (the battery icon, or the keyboard layout selector i.e). -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 1349826] Re: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1300713 *** https://bugs.launchpad.net/bugs/1300713 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1300713, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1349826/+attachment/4165081/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1349826/+attachment/4165083/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1349826/+attachment/4165086/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1349826/+attachment/4165087/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1349826/+attachment/4165088/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1349826/+attachment/4165089/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1349826/+attachment/4165090/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1300713 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1349826 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() Status in “unity” package in Ubuntu: New Bug description: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Jul 29 15:56:18 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2014-07-10 (18 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0x7fa5a612e0fc:mov(%rdi),%rbx PC (0x7fa5a612e0fc) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349826/+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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
** Patch removed: nux-remove-area-from-layout-queue.patch https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337244/+attachment/4164791/+files/nux-remove-area-from-layout-queue.patch -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: New Status in Unity: Confirmed Status in “nux” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*)
[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
Actually, since View is FloatingWindow's indirect base class, and since InputArea (which is the only other class derived from Area besides Layout) is a direct base class of View, and InputArea objects are not put on that queue, the RemoveObjectFromLayoutQueue calls in View and Layout destructors do seem to remove all queued Area objects (including FloatingWindow objects). So, the patch wouldn't fix the bug, so I've removed it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: New Status in Unity: Confirmed Status in “nux” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in
[Dx-packages] [Bug 1163041] Re: Inconsistent behaviour with minimized Trash windows
** Changed in: unity Status: Confirmed = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1163041 Title: Inconsistent behaviour with minimized Trash windows Status in Ayatana Design: Invalid Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.2 series: Confirmed Status in “unity” package in Ubuntu: Triaged Bug description: Now with a fix for LP: #753938 being merged into raring, this presents a new usability challenge to users. The issue: When you open a trash window from the launcher and minimize it, it gets minimized into the Nautilus icon. However, a user would then expect to get the window back by clicking the icon where the window minimized into in the first place, in this case, the Nautilus icon in the launcher. Instead, it opens a new Nautilus window. The issue here is that trash windows and every other Nautilus window are only seperated logically from each other, but not visually. The fix: When minimizing the trash window, instead of minimizing into the Nautilus icon, it should minimize the window into the trash icon in the launcher. I'm purely talking about the minimize animation and triangle next to the trash icon here. Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 unity: Installiert: 6.12.0daily13.04.01-0ubuntu1 Installationskandidat: 6.12.0daily13.04.01-0ubuntu1 Versionstabelle: *** 6.12.0daily13.04.01-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.04.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Apr 2 00:23:51 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1163041/+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 1349858] [NEW] Cannot override certain key combinations involving Super
Public bug reported: When defining keyboard shortcuts in System Settings - Keyboard - Shortcuts, several combinations are never honoured. These include setting: - Launchers - Launch calculator to Super+C (launches search photos instead) - Launchers - Launch email client to Super+M (launches search music instead) - Launchers - Launch terminal to Super+T (launches Rubbish bin instead) - Launchers - Launch web browser to Super+F (launches search files folders instead) - Launchers - Search to Super+S (launches Workspace Switcher) - Navigation - Switch to workspace # to Super+# (launches the corresponding launcher icon instead) It is non-obvious that this shortcut change has not been honoured, and there is no list of keys to which this applies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-services 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jul 30 00:01:48 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1349858 Title: Cannot override certain key combinations involving Super Status in “unity” package in Ubuntu: New Bug description: When defining keyboard shortcuts in System Settings - Keyboard - Shortcuts, several combinations are never honoured. These include setting: - Launchers - Launch calculator to Super+C (launches search photos instead) - Launchers - Launch email client to Super+M (launches search music instead) - Launchers - Launch terminal to Super+T (launches Rubbish bin instead) - Launchers - Launch web browser to Super+F (launches search files folders instead) - Launchers - Search to Super+S (launches Workspace Switcher) - Navigation - Switch to workspace # to Super+# (launches the corresponding launcher icon instead) It is non-obvious that this shortcut change has not been honoured, and there is no list of keys to which this applies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-services 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jul 30 00:01:48 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349858/+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 1349761] Re: [Wishlist] Opening Launcher popup menu on mouseover after a couple of seconds
** Changed in: unity Status: New = Opinion ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = Opinion -- 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/1349761 Title: [Wishlist] Opening Launcher popup menu on mouseover after a couple of seconds Status in Unity: Opinion Status in “unity” package in Ubuntu: Opinion Bug description: Currently Unity Launcher icons elegantly display the Title on mouseover, and you need to right click to access a popup menu including any Shortcuts available, which is also very useful. However, I think it would be much more efficient and useful if this popup menu could also become visible when the mouseover action persists for a couple of seconds (making the right click action redundant), which shouldn't be too costly I guess. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349761/+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 1186181] Re: [Indicator] battery icon unreliable at low battery levels
Okay, after follow-up from Daniela it looks like for RTM we're going with option #1 from https://bugs.launchpad.net/indicator- power/+bug/1186181/comments/12 and we can revisit this after RTM as necessary. ** Changed in: ubuntu-ux Status: Triaged = Fix Committed ** Changed in: indicator-power Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1186181 Title: [Indicator] battery icon unreliable at low battery levels Status in The Power Indicator: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-power” package in Ubuntu: Triaged Bug description: Battery icon does not reliably display correct values at low battery levels. The icon works fine until you get below 30%. At 10-30% a small red icon should be displayed, and another icon should be displayed at 10%. Currently, the icon doesn't seem to change to anything smaller than the 40% icon. I have sometimes seen the red 20% icon, but it's very unreliable, and typically switches back to the 40% icon moments after resuming the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1348538] Re: Display should come on when started charging
** Changed in: ubuntu-ux Assignee: (unassigned) = Matthew Paul Thomas (mpt) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1348538 Title: Display should come on when started charging Status in Ubuntu UX bugs: New Status in “indicator-power” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “unity-system-compositor” package in Ubuntu: New Bug description: The display should be triggered to turn on for a $timeout when connected to a charger, so that users can see charging commenced. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-system-compositor (not installed) ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 09:45:42 2014 SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1348538/+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 1186181] Re: [Indicator] battery icon unreliable at low battery levels
** Branch linked: lp:~charlesk/indicator-power/lp-1186181-icon-should- match-battery-percentage -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1186181 Title: [Indicator] battery icon unreliable at low battery levels Status in The Power Indicator: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-power” package in Ubuntu: Triaged Bug description: Battery icon does not reliably display correct values at low battery levels. The icon works fine until you get below 30%. At 10-30% a small red icon should be displayed, and another icon should be displayed at 10%. Currently, the icon doesn't seem to change to anything smaller than the 40% icon. I have sometimes seen the red 20% icon, but it's very unreliable, and typically switches back to the 40% icon moments after resuming the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1348538] Re: Display should come on when started charging
** Changed in: ubuntu-ux Importance: Undecided = Low ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1348538 Title: Display should come on when started charging Status in Ubuntu UX bugs: Triaged Status in “indicator-power” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “unity-system-compositor” package in Ubuntu: New Bug description: The display should be triggered to turn on for a $timeout when connected to a charger, so that users can see charging commenced. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-system-compositor (not installed) ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 09:45:42 2014 SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1348538/+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 1334998] Re: When using Super+L keys autohide not working properly
*** This bug is a duplicate of bug 1320438 *** https://bugs.launchpad.net/bugs/1320438 ** This bug has been marked a duplicate of bug 1320438 Unity launcher auto hide fails on screen unlock using Super+L -- 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/1334998 Title: When using Super+L keys autohide not working properly Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When using the super+l keys to lock the screen, the unity panel gets stuck. This happens whenever the user first clicks on the super key and then the L key. Clicking simutaniously works as expected. The issue was also reported on Ask Ubuntu: http://askubuntu.com/questions/459585/launcher-auto-hide-not-working- ubuntu-14-04/469732?noredirect=1#comment652314_469732 There is a workaround (the user has to double tap the super key) however, this is one of those papercuts that gets rather annoying over time. I would expect the system to be a little more tolerant in terms of the sequnce of keys pressed. If I first click on the super key and then the L key, the panel will not be locked when I log back in. === Description: Ubuntu 14.04 LTS Release: 14.04 === unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages === Screenshot: http://i.imgur.com/e3AePQ8.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 27 09:23:52 2014 InstallationDate: Installed on 2014-03-16 (103 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1334998/+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 1349128] Re: Ubuntu 14.04 lock screen doesn't accept keyboard input (until using indicators)
** Summary changed: - Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators) + Ubuntu 14.04 lock screen doesn't accept keyboard input (until using indicators) -- 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/1349128 Title: Ubuntu 14.04 lock screen doesn't accept keyboard input (until using indicators) Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+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 1328537] Re: Can't find where to shut off showing the user's wallpaper in Unity locker
com.canonical.unity.unity-greeter-draw-user-backgrounds is the correct option. If it does not work please reopen the bug. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1328537 Title: Can't find where to shut off showing the user's wallpaper in Unity locker Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Sorry I could not select the unity package to report this. When the session is locked in Trusty Tahr 14.04 the background picture is the user wallpaper instead of a generic/common/local public picture. This is the same whatever the way the lockscreen is triggered, Super+L or elapsed inactivity. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1328537/+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 739469] Re: Dash search unavoidably returns offensive results
** Description changed: unity 3.6.6-0ubuntu1, Ubuntu Natty unity 3.6.8-0ubuntu3, Ubuntu Natty unity-2d 5.8.0-0ubuntu1, Ubuntu Pangolin + unity 7.2.2+14.04.20140714-0ubuntu1, Ubuntu 14.04 Example 1: 0. Be a 14-year-old girl, or a schoolteacher preparing to show a film to your class, or a businessperson preparing to give a presentation. 1. Click the Applications button. 2. Type movie to launch Movie Player. What happens: Seven applications appear, one of which is called PornView. Example 2: 0. Be a Dell representative or customer. 1. Click the Applications button. 2. Type Dell to find the Dell Recovery tool. What happens: Five applications appear, including Dopewars, a drug-dealing game. (More examples in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/883800/comments/15.) This problem cannot reasonably be solved merely by renaming or blacklisting one or two particular applications. These are just two examples, and if the Dash shows any applications that aren't installed, there is no bright line between those that should appear for everyone and those that should appear for no-one. We can't realistically expect the entire Ubuntu software library to be offense-free: as more independent applications are published, some (especially games) will be targeted at mature audiences and/or be non- worksafe, and that's fine. (We can introduce a maturity rating system inside Ubuntu Software Center for those.) But people should be able to expect that the launcher in Ubuntu's shell, of all things, *will* be offense-free. Possible solutions: * Simplest would be to restrict application search results only to those applications that are actually installed. As Mark Shuttleworth said in https://lists.launchpad.net/unity-design/msg08030.html: To launch what you know you have installed, use the Dash. To explore what may be installed, or may be available, use the Software Centre. Now, neither piece may yet be ideal, but we should improve the design of those pieces for their specific purposes, not try to make everything do everything. * Introduce a maturity ratings system https://blueprints.launchpad.net/ubuntu/+spec/foundations-software- maturity-ratings, apply it to every package in the Ubuntu archive that needs it, then set a reasonable default for Dash searches (analogous to Google's SafeSearch Moderate). This might involve adding a setting for how much filtering the Dash should do. * Ad-hoc and unconfigurable blacklisting (as proposed in duplicate bug 883800). This might result in ongoing disagreements about whether particular applications should be blacklisted. -- 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/739469 Title: Dash search unavoidably returns offensive results Status in Unity: Fix Released Status in Unity Foundations: Fix Released Status in Unity Applications Lens: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “unity-place-applications” package in Ubuntu: Fix Released Bug description: unity 3.6.6-0ubuntu1, Ubuntu Natty unity 3.6.8-0ubuntu3, Ubuntu Natty unity-2d 5.8.0-0ubuntu1, Ubuntu Pangolin unity 7.2.2+14.04.20140714-0ubuntu1, Ubuntu 14.04 Example 1: 0. Be a 14-year-old girl, or a schoolteacher preparing to show a film to your class, or a businessperson preparing to give a presentation. 1. Click the Applications button. 2. Type movie to launch Movie Player. What happens: Seven applications appear, one of which is called PornView. Example 2: 0. Be a Dell representative or customer. 1. Click the Applications button. 2. Type Dell to find the Dell Recovery tool. What happens: Five applications appear, including Dopewars, a drug-dealing game. (More examples in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/883800/comments/15.) This problem cannot reasonably be solved merely by renaming or blacklisting one or two particular applications. These are just two examples, and if the Dash shows any applications that aren't installed, there is no bright line between those that should appear for everyone and those that should appear for no-one. We can't realistically expect the entire Ubuntu software library to be offense-free: as more independent applications are published, some (especially games) will be targeted at mature audiences and/or be non- worksafe, and that's fine. (We can introduce a maturity rating system inside Ubuntu Software Center for those.) But people should be able to expect that the launcher in Ubuntu's shell, of all things, *will* be offense-free. Possible solutions: * Simplest would be to restrict application search results only to those applications that are actually installed. As Mark Shuttleworth said in
[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
However, if the parent object of an object of type InputArea is a Layout object comment at Area.cpp:603 is inaccurate (as some of the other comments there, such as the ones at :540, :576, and :596), and if InputArea objects can have HSplitter or VSplitter as parent, then they could be added to the queue at Area.cpp:521, in which case they would need to be removed from the queue in the InputArea destructor (as in the attached patch). ** Patch added: nux-remove-input-area-from-queue.patch https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337244/+attachment/4165209/+files/nux-remove-input-area-from-queue.patch -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: New Status in Unity: Confirmed Status in “nux” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) ()
[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
And since InputArea and Layout are the only classes derived directly from Area, and they would both have the same code in their destructors with the patch in #6, the removal code can be moved to the Area destructor, as in the attached patch. ** Patch added: nux-remove-area-from-layout-queue.patch https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337244/+attachment/4165234/+files/nux-remove-area-from-layout-queue.patch -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: New Status in Unity: Confirmed Status in “nux” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in
[Dx-packages] [Bug 1208019] Re: Eclipse menus don't show up in Trusty
Hello Hans, or anyone else affected, Accepted gtk+3.0 into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gtk+3.0/3.10.8-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Summary changed: - Eclipse menus doesn't show up in Trusty + Eclipse menus don't show up in Trusty ** Changed in: gtk+3.0 (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus don't show up in Trusty Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Trusty: Fix Committed Status in “unity-gtk-module” source package in Trusty: In Progress Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === % === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708)
[Dx-packages] [Bug 739469] Re: Dash search unavoidably returns offensive results
In Ubuntu 14.04, example 2 produces the results originally described. Example 1 no longer displays PornView, but instead shows QFlatBoob, QBoobmsg, and QHandJoob. -- 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/739469 Title: Dash search unavoidably returns offensive results Status in Unity: Fix Released Status in Unity Foundations: Fix Released Status in Unity Applications Lens: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “unity-place-applications” package in Ubuntu: Fix Released Bug description: unity 3.6.6-0ubuntu1, Ubuntu Natty unity 3.6.8-0ubuntu3, Ubuntu Natty unity-2d 5.8.0-0ubuntu1, Ubuntu Pangolin unity 7.2.2+14.04.20140714-0ubuntu1, Ubuntu 14.04 Example 1: 0. Be a 14-year-old girl, or a schoolteacher preparing to show a film to your class, or a businessperson preparing to give a presentation. 1. Click the Applications button. 2. Type movie to launch Movie Player. What happens: Seven applications appear, one of which is called PornView. Example 2: 0. Be a Dell representative or customer. 1. Click the Applications button. 2. Type Dell to find the Dell Recovery tool. What happens: Five applications appear, including Dopewars, a drug-dealing game. (More examples in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/883800/comments/15.) This problem cannot reasonably be solved merely by renaming or blacklisting one or two particular applications. These are just two examples, and if the Dash shows any applications that aren't installed, there is no bright line between those that should appear for everyone and those that should appear for no-one. We can't realistically expect the entire Ubuntu software library to be offense-free: as more independent applications are published, some (especially games) will be targeted at mature audiences and/or be non- worksafe, and that's fine. (We can introduce a maturity rating system inside Ubuntu Software Center for those.) But people should be able to expect that the launcher in Ubuntu's shell, of all things, *will* be offense-free. Possible solutions: * Simplest would be to restrict application search results only to those applications that are actually installed. As Mark Shuttleworth said in https://lists.launchpad.net/unity-design/msg08030.html: To launch what you know you have installed, use the Dash. To explore what may be installed, or may be available, use the Software Centre. Now, neither piece may yet be ideal, but we should improve the design of those pieces for their specific purposes, not try to make everything do everything. * Introduce a maturity ratings system https://blueprints.launchpad.net/ubuntu/+spec/foundations-software- maturity-ratings, apply it to every package in the Ubuntu archive that needs it, then set a reasonable default for Dash searches (analogous to Google's SafeSearch Moderate). This might involve adding a setting for how much filtering the Dash should do. * Ad-hoc and unconfigurable blacklisting (as proposed in duplicate bug 883800). This might result in ongoing disagreements about whether particular applications should be blacklisted. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/739469/+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 1348538] Re: [power] Display should come on when started charging
** Summary changed: - Display should come on when started charging + [power] Display should come on when started charging -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1348538 Title: [power] Display should come on when started charging Status in Ubuntu UX bugs: Triaged Status in “indicator-power” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “unity-system-compositor” package in Ubuntu: New Bug description: The display should be triggered to turn on for a $timeout when connected to a charger, so that users can see charging commenced. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-system-compositor (not installed) ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 09:45:42 2014 SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1348538/+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 1344990] Re: Volume control jumps back and forth
** Attachment added: Video clip of the problem. First without Audacious and then with it. https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1344990/+attachment/4165264/+files/bug1344990.mp4 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1344990 Title: Volume control jumps back and forth Status in Sound Menu: New Status in Unity: New Status in “indicator-sound” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen to music via Audacious 2) Open volume control from Unity's panel 3) Try to change the volume What happens: - The volume control doesn't follow mouse properly and jumps back and forth What should happen: - The obvious thing I believe this is regression as didn't notice anything weird in 13.10 with exactly same setup. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jul 19 19:51:32 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1344990/+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 1186181] Re: [Indicator] battery icon unreliable at low battery levels
** Changed in: indicator-power (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1186181 Title: [Indicator] battery icon unreliable at low battery levels Status in The Power Indicator: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-power” package in Ubuntu: Triaged Bug description: Battery icon does not reliably display correct values at low battery levels. The icon works fine until you get below 30%. At 10-30% a small red icon should be displayed, and another icon should be displayed at 10%. Currently, the icon doesn't seem to change to anything smaller than the 40% icon. I have sometimes seen the red 20% icon, but it's very unreliable, and typically switches back to the 40% icon moments after resuming the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1349953] [NEW] Screen locking issue
You have been subscribed to a public bug: After coming out of sleep mode, my keyboard cannot type to the password entry field. When I try to type to the password entry field, the computer sends my input to whatever window I had open before my computer went to sleep. This means that if I type my password and press enter, and the last window I had open was, say, a gchat, I will send my password to the person with whom I was talking. It seems like this bug only occurs when I had a text entry field selected before putting my computer to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 29 09:40:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 1800 InstallationDate: Installed on 2012-12-24 (582 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-07-23 (5 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- Screen locking issue https://bugs.launchpad.net/bugs/1349953 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1349953] Re: Screen locking issue
** Information type changed from Private Security to Public ** Package changed: gnome-screensaver (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 https://bugs.launchpad.net/bugs/1349953 Title: Screen locking issue Status in “unity” package in Ubuntu: New Bug description: After coming out of sleep mode, my keyboard cannot type to the password entry field. When I try to type to the password entry field, the computer sends my input to whatever window I had open before my computer went to sleep. This means that if I type my password and press enter, and the last window I had open was, say, a gchat, I will send my password to the person with whom I was talking. It seems like this bug only occurs when I had a text entry field selected before putting my computer to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 29 09:40:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 1800 InstallationDate: Installed on 2012-12-24 (582 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-07-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349953/+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 1349961] Re: lock screen don't get focus by closing the lid
** Information type changed from Private Security to Public -- 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/1349961 Title: lock screen don't get focus by closing the lid Status in “unity” package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 7.2.2+14.04.20140714-0ubuntu1 3) What you expected to happen After closing the lid (without moving the mouse) i expected to write my password and press enter to unlock 4) What happened instead After closing the lid and start writing the password is still being written by the open app The big security problem: i was talking in a group chat on facebook, i closed my lid, when i open it i wrote the password and clicked enter but nothing happened, after i moved the mouse and logged in, i have just sent my password to a facebook chat group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349961/+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 964673] Re: keyboard shortcut overlay needs more consistent wording
This was merged 2012-08-27 and shipped in Ubuntu 12.10, the Fix is as Released as it's going to get. ** Changed in: unity Status: Incomplete = Fix Released ** Changed in: unity (Ubuntu) Status: Incomplete = 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/964673 Title: keyboard shortcut overlay needs more consistent wording Status in Ayatana Design: New Status in Ubuntu Translations: Triaged Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: I'm submitting a merge proposal to go with this. The keyboard shortcut overlay (when you hold down the Windows key) has several wording issues: - Inconsistent verb tenses (open and opens) - Minimise (Minimize is the correct spelling in US English, which is what the C locale should use) - Super (Press) is confusing; changing the text to Super (Hold) makes it more clear that holding down the Super key will show the overlay - Cursor keys; I think a typical person calls them arrow keys This won't affect ubuntu-docs, but it does create new strings for the translators. Translators notified: https://lists.ubuntu.com/archives/ubuntu-translators/2012-April/005297.html ProblemType: BugDistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CheckboxSubmission: 201084ed41ea7548f8becd47fa4d1e6c CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Mar 25 13:19:15 2012SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/964673/+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 964673] Re: keyboard shortcut overlay needs more consistent wording
** No longer affects: ubuntu-translations -- 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/964673 Title: keyboard shortcut overlay needs more consistent wording Status in Ayatana Design: New Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: I'm submitting a merge proposal to go with this. The keyboard shortcut overlay (when you hold down the Windows key) has several wording issues: - Inconsistent verb tenses (open and opens) - Minimise (Minimize is the correct spelling in US English, which is what the C locale should use) - Super (Press) is confusing; changing the text to Super (Hold) makes it more clear that holding down the Super key will show the overlay - Cursor keys; I think a typical person calls them arrow keys This won't affect ubuntu-docs, but it does create new strings for the translators. Translators notified: https://lists.ubuntu.com/archives/ubuntu-translators/2012-April/005297.html ProblemType: BugDistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CheckboxSubmission: 201084ed41ea7548f8becd47fa4d1e6c CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Mar 25 13:19:15 2012SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/964673/+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 1313248] Re: Ctrl+[Key] Shortcuts Assigned in QtCreator Do Not Work
Same here. Any shortcut is actually broken (example: F5, ALT-T). Removing appmenu-qt5 does solve the problem, but I like having my menus in the title bar... Software that can be compiled agains qt4 work as expected. -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1313248 Title: Ctrl+[Key] Shortcuts Assigned in QtCreator Do Not Work Status in “appmenu-qt5” package in Ubuntu: Confirmed Bug description: I recompiled one of my Qt applications tonight on Ubuntu 14.04. This application uses QActions that are are set up in the mainwindow.ui file. (I originally did this with QtDesigner some two year ago, but have updated the application for Qt 5 in the mean time.) When appmenu-qt5 is installed, the Ctrl+[key] shortcuts of the actions on the main menubar do not work. If I remove appment-qt5, they do work as expected. Oddly enough, the edit actions on the edit dialog do work, but they are disabled and enabled multiple times. I tried disabling and enabling the actions on the main menubar in code which didn't help. I also tried assigning the short cut keys via code and that did not help. I am using 14.04 LTS, appmenu-qt5 0.3.0+14.04.20140415-0ubuntu1, and the Qt program found at https://github.com/Dyrcona/omiquji To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1313248/+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 1350017] Re: There is no vibration when an alarm goes off
Marking incomplete until we receive feedback from design. Will update this bug report by the end of the week. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Status: Confirmed = Incomplete ** Changed in: indicator-datetime (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350017 Title: There is no vibration when an alarm goes off Status in Clock application for Ubuntu devices: Incomplete Status in Ubuntu UX bugs: New Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: It'd be probably nice to also have vibration beside the sound alert when an alarm triggers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: telephony-service Status: New = Triaged ** Changed in: telephony-service Importance: Undecided = Medium -- 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/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: Triaged Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-network” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1348668] Re: Unity lockscreen lets applications capture keyboard input
I can confirm this too, the first time it happened I freaked out, my workaround is to change input methods in the icon in the top panel. But this should be like this, I agree that no lockscreen should behave like this. This only happens with Google Chrome. As I have the vimium extension too I find to my surprise that I was opening a web page with half of my password on it. I mean, c'mon that's not secure. -- 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/1348668 Title: Unity lockscreen lets applications capture keyboard input Status in “unity” package in Ubuntu: New Bug description: I noticed that with the Vimium extension activated in Google Chrome, I cannot unlock Unity's lockscreen because keyboard input is hijacked by Vimium. The lockscreen really should not let this happen, and it can even be considered a potential security vulnerability as it might allow applications to capture a user's password. I have noticed this before as well when using another application, though I can't remember which one it was at the moment. The workaround is to use the mouse to choose the Switch user-option, but this is really not obvious to anyone who might encounter this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1348668/+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 1350052] [NEW] Unity FTBFS - gcc 4.9
Public bug reported:
Confirmed gcc/g++ 4.9 causes this FTBFS
[ 17%] Building CXX object
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
from /home/bschaefer/src/unity/UnityCore/Model.h:107,
from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o]
Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
CMakeFiles/Makefile2:6381: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
Makefile:113: recipe for target 'all' failed
make: *** [all] Error 2
** Affects: unity
Importance: Critical
Status: Triaged
** Affects: unity (Ubuntu)
Importance: Critical
Status: Triaged
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu)
Status: New = Triaged
** Changed in: unity (Ubuntu)
Importance: Undecided = Critical
** Description changed:
+ 4.8 worked fine, upgrade to 4.9 now unity FTBFS. Ill double check gcc
+ though.
+
[ 17%] Building CXX object
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
- DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
- ^
+ DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
+ ^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
-::nux::logging::Logger logger() \
-^
+ ::nux::logging::Logger logger() \
+ ^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
- from /home/bschaefer/src/unity/UnityCore/Model.h:107,
- from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
- from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
+ from /home/bschaefer/src/unity/UnityCore/Model.h:107,
+ from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
+ from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
- DECLARE_LOGGER(logger, unity.dash.filter);
- ^
+ DECLARE_LOGGER(logger, unity.dash.filter);
+ ^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
-::nux::logging::Logger logger() \
-^
+ ::nux::logging::Logger logger() \
+ ^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: ***
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target
[Dx-packages] [Bug 1350052] Re: Unity FTBFS (Possibly gcc 4.9 issue)
** Description changed:
- 4.8 worked fine, upgrade to 4.9 now unity FTBFS. Ill double check gcc
- though.
+ Confirmed gcc/g++ 4.9 causes this FTBFS
[ 17%] Building CXX object
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
from /home/bschaefer/src/unity/UnityCore/Model.h:107,
from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: ***
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
CMakeFiles/Makefile2:6381: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
Makefile:113: recipe for target 'all' failed
make: *** [all] Error 2
** Summary changed:
- Unity FTBFS (Possibly gcc 4.9 issue)
+ Unity FTBFS - gcc 4.9
--
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/1350052
Title:
Unity FTBFS - gcc 4.9
Status in Unity:
Triaged
Status in “unity” package in Ubuntu:
Triaged
Bug description:
Confirmed gcc/g++ 4.9 causes this FTBFS
[ 17%] Building CXX object
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
from /home/bschaefer/src/unity/UnityCore/Model.h:107,
from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: ***
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
CMakeFiles/Makefile2:6381: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
Makefile:113: recipe for target 'all' failed
make: *** [all] Error 2
To manage notifications about
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: telephony-service (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: Triaged Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-network” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1292657] Re: Call back in indicator fails the indicator service with +-prefixed numbers
** Tags added: rtm14 ** Changed in: url-dispatcher (Ubuntu) Status: New = Triaged ** Changed in: url-dispatcher (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1292657 Title: Call back in indicator fails the indicator service with +-prefixed numbers Status in “telephony-service” package in Ubuntu: New Status in “url-dispatcher” package in Ubuntu: Triaged Bug description: When a +-prefixed number called you and you try to call it back using the button in the indicator, it fails with the attached .crash file, url-dispatcher tool reports: ** (process:26240): WARNING **: Unable to dispatch url 'tel:///%2B48508xx':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'tel:///%2B48508xx' is not handleable by the URL Dispatcher ProblemType: RecoverableProblem DistroRelease: Ubuntu 14.04 Package: telephony-service 0.1+14.04.20140306-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf BadURL: tel:///%2B48508xx CurrentDesktop: Unity Date: Fri Mar 14 19:06:51 2014 DuplicateSignature: url-dispatcher;bad-url;tel:///%2B48508xx ExecutablePath: /usr/bin/telephony-service-indicator ExecutableTimestamp: 1394099254 InstallationDate: Installed on 2014-03-14 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140314) LocalLibraries: /android/system/lib/libGLES_trace.so /android/system/lib/libcorkscrew.so /android/system/lib/libcutils.so /android/system/lib/libgccdemangle.so /android/system/lib/libc.so /android/system/lib/libdsyscalls.so /android/system/lib/libstlport.so /android/system/lib/libEGL.so /android/system/lib/libGLESv2.so /android/system/lib/libstdc++.so /android/system/lib/libutils.so /android/system/lib/liblog.so /android/system/lib/libm.so ProcCmdline: /usr/bin/telephony-service-indicator ProcCwd: / SourcePackage: telephony-service 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/telephony-service/+bug/1292657/+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 1290785] Re: Users with UID 60000 are invisible in login and Settings-User unless /etc/login.defs updated
This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7.1 --- accountsservice (0.6.35-0ubuntu7.1) trusty-proposed; urgency=medium * debian/patches/0018-no-max-uid.patch: - Don't have a maximum UID (LP: #1290785) -- Robert Ancell robert.anc...@canonical.com Fri, 18 Jul 2014 12:26:01 +1200 ** Changed in: accountsservice (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290785 Title: Users with UID 6 are invisible in login and Settings-User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Fix Released Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID UID_MIN. In 13.10 this was changed to UID UID_MIN or UID UID_MAX. [Test Case] 1. Create a user with a UID UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: big-uid is shown in the greeter. Once logged in big-uid is shown in system settings. Observed result: big-uid is not shown in the greeter (14.04 LTS, 14.10) big-uid is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+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 1290785] Update Released
The verification of the Stable Release Update for accountsservice has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290785 Title: Users with UID 6 are invisible in login and Settings-User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Fix Released Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID UID_MIN. In 13.10 this was changed to UID UID_MIN or UID UID_MAX. [Test Case] 1. Create a user with a UID UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: big-uid is shown in the greeter. Once logged in big-uid is shown in system settings. Observed result: big-uid is not shown in the greeter (14.04 LTS, 14.10) big-uid is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
I also have this bug with chromium: chromium-browser: Installed: 34.0.1847.116-0ubuntu2 compiz: Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1 unity: Installed: 7.2.2+14.04.20140714-0ubuntu1 A work around is to suspend and wake up the computer one more. -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 1350101] Re: Nux FTBFS - gcc 4.9
** Also affects: nux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nux (Ubuntu)
Status: New = In Progress
** Changed in: nux
Status: Triaged = In Progress
** Changed in: nux (Ubuntu)
Importance: Undecided = Critical
** Changed in: nux
Assignee: (unassigned) = Brandon Schaefer (brandontschaefer)
** Changed in: nux (Ubuntu)
Assignee: (unassigned) = Brandon Schaefer (brandontschaefer)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1350101
Title:
Nux FTBFS - gcc 4.9
Status in Nux:
In Progress
Status in “nux” package in Ubuntu:
In Progress
Bug description:
CXX libnux_core_4.0_la-Trigonometry.lo
./Object.cpp:33:6: error: 'bool
nux::{anonymous}::debug_object_allocation_stack()' defined but not used
[-Werror=unused-function]
bool debug_object_allocation_stack()
To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1350101/+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 1350101] Re: Nux FTBFS - gcc 4.9
** Branch linked: lp:~brandontschaefer/nux/lp.1350101-fix
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1350101
Title:
Nux FTBFS - gcc 4.9
Status in Nux:
In Progress
Status in “nux” package in Ubuntu:
In Progress
Bug description:
CXX libnux_core_4.0_la-Trigonometry.lo
./Object.cpp:33:6: error: 'bool
nux::{anonymous}::debug_object_allocation_stack()' defined but not used
[-Werror=unused-function]
bool debug_object_allocation_stack()
To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1350101/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
I also have this bug with google-chrome 36.0.1985.125-1, so this bug is not fixed, please someone take a look. Also workaround by clicking some of the icons on the panel. -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 1350052] Re: Unity FTBFS - gcc 4.9
** Changed in: unity
Assignee: (unassigned) = Brandon Schaefer (brandontschaefer)
** Changed in: unity (Ubuntu)
Assignee: (unassigned) = Brandon Schaefer (brandontschaefer)
** Changed in: unity
Status: Triaged = In Progress
** Changed in: unity
Status: In Progress = Won't Fix
** Changed in: unity (Ubuntu)
Status: Triaged = In Progress
--
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/1350052
Title:
Unity FTBFS - gcc 4.9
Status in Unity:
In Progress
Status in “unity” package in Ubuntu:
In Progress
Bug description:
Confirmed gcc/g++ 4.9 causes this FTBFS
[ 17%] Building CXX object
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
from /home/bschaefer/src/unity/UnityCore/Model.h:107,
from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: ***
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
CMakeFiles/Makefile2:6381: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
Makefile:113: recipe for target 'all' failed
make: *** [all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1350052/+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 1350052] Re: Unity FTBFS - gcc 4.9
** Branch linked: lp:~brandontschaefer/unity/lp.1350052-fix
--
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/1350052
Title:
Unity FTBFS - gcc 4.9
Status in Unity:
In Progress
Status in “unity” package in Ubuntu:
In Progress
Bug description:
Confirmed gcc/g++ 4.9 causes this FTBFS
[ 17%] Building CXX object
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
from /home/bschaefer/src/unity/UnityCore/Model.h:107,
from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: ***
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
CMakeFiles/Makefile2:6381: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
Makefile:113: recipe for target 'all' failed
make: *** [all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1350052/+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 1350052] Re: Unity FTBFS - gcc 4.9
urrg... hit Wont Fix on accident .. now I get a timeout error anytime I
try to change it. Yay launchpad! (Same when attempting to link the
branch to fix this...)
** Changed in: unity
Status: Won't Fix = In Progress
--
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/1350052
Title:
Unity FTBFS - gcc 4.9
Status in Unity:
In Progress
Status in “unity” package in Ubuntu:
In Progress
Bug description:
Confirmed gcc/g++ 4.9 causes this FTBFS
[ 17%] Building CXX object
UnityCore/CMakeFiles/unity-core-6.0.dir/GLibDBusProxy.cpp.o
In file included from
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:22:0:
/home/bschaefer/src/unity/UnityCore/CheckOptionFilter.cpp:28:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter.checkoption);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
In file included from /home/bschaefer/src/unity/UnityCore/Model-inl.h:23:0,
from /home/bschaefer/src/unity/UnityCore/Model.h:107,
from /home/bschaefer/src/unity/UnityCore/Filters.h:26,
from /home/bschaefer/src/unity/UnityCore/Filter.cpp:21:
/home/bschaefer/src/unity/UnityCore/Filter.cpp:35:16: error:
‘nux::logging::Logger unity::dash::{anonymous}::logger()’ defined but not used
[-Werror=unused-function]
DECLARE_LOGGER(logger, unity.dash.filter);
^
/usr/include/Nux-4.0/NuxCore/Logger.h:75:27: note: in definition of macro
‘DECLARE_LOGGER’
::nux::logging::Logger logger() \
^
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:169: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o' failed
make[2]: ***
[UnityCore/CMakeFiles/unity-core-6.0.dir/CheckOptionFilter.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1plus: all warnings being treated as errors
UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:238: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o' failed
make[2]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Filter.cpp.o] Error 1
CMakeFiles/Makefile2:6381: recipe for target
'UnityCore/CMakeFiles/unity-core-6.0.dir/all' failed
make[1]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/all] Error 2
Makefile:113: recipe for target 'all' failed
make: *** [all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1350052/+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 1349961] Re: lock screen don't get focus by closing the lid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) 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/1349961 Title: lock screen don't get focus by closing the lid Status in “unity” package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 7.2.2+14.04.20140714-0ubuntu1 3) What you expected to happen After closing the lid (without moving the mouse) i expected to write my password and press enter to unlock 4) What happened instead After closing the lid and start writing the password is still being written by the open app The big security problem: i was talking in a group chat on facebook, i closed my lid, when i open it i wrote the password and clicked enter but nothing happened, after i moved the mouse and logged in, i have just sent my password to a facebook chat group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349961/+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 1348538] Re: [power] Display should come on when started charging
** Also affects: unity-system-compositor Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1348538 Title: [power] Display should come on when started charging Status in Ubuntu UX bugs: Triaged Status in Unity System Compositor: New Status in “indicator-power” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “unity-system-compositor” package in Ubuntu: New Bug description: The display should be triggered to turn on for a $timeout when connected to a charger, so that users can see charging commenced. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-system-compositor (not installed) ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 09:45:42 2014 SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1348538/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: telephony-service (Ubuntu) Importance: Undecided = Medium -- 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/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: Triaged Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-network” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1257382] Re: Unity3d engine games all suffer from tearing even with vsync
The problem isn't limited to Unity3D. I switched over to GNOME 3 and though it improved the performance of one game (A Wizard's Lizard), 3D games tear on very capable hardware. I'm using Nvidia 331.xx. -- 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/1257382 Title: Unity3d engine games all suffer from tearing even with vsync Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: All unity3d engine games suffers from tearing because they are detecting that a compositor is running. Compiz is supposed to be disabled when fullscreen apps are running but it's not clearly working on anything that makes use of unity3d engine. The only working solution is installing openbox to my Ubuntu install and running the games from there. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1257382/+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 1292657] Re: Call back in indicator fails the indicator service with +-prefixed numbers
please test to see if still valid -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1292657 Title: Call back in indicator fails the indicator service with +-prefixed numbers Status in Telephony Service: Triaged Status in “telephony-service” package in Ubuntu: Triaged Status in “url-dispatcher” package in Ubuntu: Triaged Bug description: When a +-prefixed number called you and you try to call it back using the button in the indicator, it fails with the attached .crash file, url-dispatcher tool reports: ** (process:26240): WARNING **: Unable to dispatch url 'tel:///%2B48508xx':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'tel:///%2B48508xx' is not handleable by the URL Dispatcher ProblemType: RecoverableProblem DistroRelease: Ubuntu 14.04 Package: telephony-service 0.1+14.04.20140306-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf BadURL: tel:///%2B48508xx CurrentDesktop: Unity Date: Fri Mar 14 19:06:51 2014 DuplicateSignature: url-dispatcher;bad-url;tel:///%2B48508xx ExecutablePath: /usr/bin/telephony-service-indicator ExecutableTimestamp: 1394099254 InstallationDate: Installed on 2014-03-14 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140314) LocalLibraries: /android/system/lib/libGLES_trace.so /android/system/lib/libcorkscrew.so /android/system/lib/libcutils.so /android/system/lib/libgccdemangle.so /android/system/lib/libc.so /android/system/lib/libdsyscalls.so /android/system/lib/libstlport.so /android/system/lib/libEGL.so /android/system/lib/libGLESv2.so /android/system/lib/libstdc++.so /android/system/lib/libutils.so /android/system/lib/liblog.so /android/system/lib/libm.so ProcCmdline: /usr/bin/telephony-service-indicator ProcCwd: / SourcePackage: telephony-service 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/telephony-service/+bug/1292657/+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 1292657] Re: Call back in indicator fails the indicator service with +-prefixed numbers
** Changed in: telephony-service (Ubuntu) Status: New = Triaged ** Changed in: telephony-service (Ubuntu) Importance: Undecided = High ** Also affects: telephony-service Importance: Undecided Status: New ** Changed in: telephony-service Status: New = Triaged ** Changed in: telephony-service Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1292657 Title: Call back in indicator fails the indicator service with +-prefixed numbers Status in Telephony Service: Triaged Status in “telephony-service” package in Ubuntu: Triaged Status in “url-dispatcher” package in Ubuntu: Triaged Bug description: When a +-prefixed number called you and you try to call it back using the button in the indicator, it fails with the attached .crash file, url-dispatcher tool reports: ** (process:26240): WARNING **: Unable to dispatch url 'tel:///%2B48508xx':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'tel:///%2B48508xx' is not handleable by the URL Dispatcher ProblemType: RecoverableProblem DistroRelease: Ubuntu 14.04 Package: telephony-service 0.1+14.04.20140306-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf BadURL: tel:///%2B48508xx CurrentDesktop: Unity Date: Fri Mar 14 19:06:51 2014 DuplicateSignature: url-dispatcher;bad-url;tel:///%2B48508xx ExecutablePath: /usr/bin/telephony-service-indicator ExecutableTimestamp: 1394099254 InstallationDate: Installed on 2014-03-14 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140314) LocalLibraries: /android/system/lib/libGLES_trace.so /android/system/lib/libcorkscrew.so /android/system/lib/libcutils.so /android/system/lib/libgccdemangle.so /android/system/lib/libc.so /android/system/lib/libdsyscalls.so /android/system/lib/libstlport.so /android/system/lib/libEGL.so /android/system/lib/libGLESv2.so /android/system/lib/libstdc++.so /android/system/lib/libutils.so /android/system/lib/liblog.so /android/system/lib/libm.so ProcCmdline: /usr/bin/telephony-service-indicator ProcCwd: / SourcePackage: telephony-service 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/telephony-service/+bug/1292657/+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 1329275] Re: missed call from x-ofono-unknown
** Changed in: dialer-app (Ubuntu) Status: Incomplete = Fix Released ** No longer affects: indicator-messages (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329275 Title: missed call from x-ofono-unknown Status in “dialer-app” package in Ubuntu: Fix Released Status in “ofono” package in Ubuntu: Invalid Bug description: I have a missed call which has no name or number. It shows up as from x-ofono-unknown in the indicator and dialer-app. The call came from my local taxi company who ring 3 times when the cab is nearly at your house. So there's no number, no contact, it's just an unknown number. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ofono 1.12.bzr6868+14.10.20140513.1-0ubuntu2 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 11:22:51 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: ofono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1329275/+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 755406] Re: Mouse offset problem when using a WINE application maximized
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- 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/755406 Title: Mouse offset problem when using a WINE application maximized Status in Compiz: Expired Status in Compiz Core: Won't Fix Status in Unity: Expired Status in “compiz” package in Ubuntu: Expired Status in “unity” package in Ubuntu: Expired Bug description: When putting Picasa in fullscreen, all controls on the screen are drawn as expected (window without title bar) but the mouse has to be the size of the title bar BELOW these controls. There seems to be a y-offset of the height of the title bar. I only noticed this for Picasa for now, but I found a report from another user of this behavior there: http://answers.unity3d.com/questions/44091/mouse-input-offset-problem- in-web-fullscreen . I attached a screenshot. Please notice the mouse pointer being below the button, but the button is highlighted. Also the original title bar is shining through the slightly transparent globalmenu-bar. Picasa is 3.8 installed into the original Picasa 3.x-wine-environment from Google (picasa-package). This is on Natty with today's updates. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/755406/+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 755406] Re: Mouse offset problem when using a WINE application maximized
[Expired for Compiz because there has been no activity for 60 days.] ** Changed in: compiz Status: Incomplete = Expired -- 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/755406 Title: Mouse offset problem when using a WINE application maximized Status in Compiz: Expired Status in Compiz Core: Won't Fix Status in Unity: Expired Status in “compiz” package in Ubuntu: Expired Status in “unity” package in Ubuntu: Expired Bug description: When putting Picasa in fullscreen, all controls on the screen are drawn as expected (window without title bar) but the mouse has to be the size of the title bar BELOW these controls. There seems to be a y-offset of the height of the title bar. I only noticed this for Picasa for now, but I found a report from another user of this behavior there: http://answers.unity3d.com/questions/44091/mouse-input-offset-problem- in-web-fullscreen . I attached a screenshot. Please notice the mouse pointer being below the button, but the button is highlighted. Also the original title bar is shining through the slightly transparent globalmenu-bar. Picasa is 3.8 installed into the original Picasa 3.x-wine-environment from Google (picasa-package). This is on Natty with today's updates. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/755406/+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 755406] Re: Mouse offset problem when using a WINE application maximized
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete = Expired -- 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/755406 Title: Mouse offset problem when using a WINE application maximized Status in Compiz: Expired Status in Compiz Core: Won't Fix Status in Unity: Expired Status in “compiz” package in Ubuntu: Expired Status in “unity” package in Ubuntu: Expired Bug description: When putting Picasa in fullscreen, all controls on the screen are drawn as expected (window without title bar) but the mouse has to be the size of the title bar BELOW these controls. There seems to be a y-offset of the height of the title bar. I only noticed this for Picasa for now, but I found a report from another user of this behavior there: http://answers.unity3d.com/questions/44091/mouse-input-offset-problem- in-web-fullscreen . I attached a screenshot. Please notice the mouse pointer being below the button, but the button is highlighted. Also the original title bar is shining through the slightly transparent globalmenu-bar. Picasa is 3.8 installed into the original Picasa 3.x-wine-environment from Google (picasa-package). This is on Natty with today's updates. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/755406/+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 755406] Re: Mouse offset problem when using a WINE application maximized
[Expired for compiz (Ubuntu) because there has been no activity for 60 days.] ** Changed in: compiz (Ubuntu) Status: Incomplete = Expired -- 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/755406 Title: Mouse offset problem when using a WINE application maximized Status in Compiz: Expired Status in Compiz Core: Won't Fix Status in Unity: Expired Status in “compiz” package in Ubuntu: Expired Status in “unity” package in Ubuntu: Expired Bug description: When putting Picasa in fullscreen, all controls on the screen are drawn as expected (window without title bar) but the mouse has to be the size of the title bar BELOW these controls. There seems to be a y-offset of the height of the title bar. I only noticed this for Picasa for now, but I found a report from another user of this behavior there: http://answers.unity3d.com/questions/44091/mouse-input-offset-problem- in-web-fullscreen . I attached a screenshot. Please notice the mouse pointer being below the button, but the button is highlighted. Also the original title bar is shining through the slightly transparent globalmenu-bar. Picasa is 3.8 installed into the original Picasa 3.x-wine-environment from Google (picasa-package). This is on Natty with today's updates. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/755406/+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
