[Dx-packages] [Bug 1591342] Re: Complains about bad url on libertine scope urls
** Changed in: url-dispatcher (Ubuntu) Assignee: (unassigned) => Larry Price (larryprice) ** Changed in: url-dispatcher (Ubuntu) Status: Triaged => In Progress -- 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/1591342 Title: Complains about bad url on libertine scope urls Status in Canonical System Image: In Progress Status in libertine-scope package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: In Progress Bug description: ** (process:4255): WARNING **: Unable to dispatch url 'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL Dispatcher To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591342/+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 1308092] Re: [desktop]"indicator-session" name is suboptimal
The desktop session now uses the same System indicator and icon as the desktop personality everywhere else. Marking as fix released. ** Changed in: unity8-desktop-session (Ubuntu) Status: Confirmed => 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/1308092 Title: [desktop]"indicator-session" name is suboptimal Status in Ubuntu UX: Triaged Status in indicator-session package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: The session indicator has no icon in the Panel in the Unity 8 Desktop Preview session. Also, it appears in the indicator nav bar as 'indicator-session' instead of having some user-friendly title. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1308092/+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 1530807] Re: Bluetooth cannot be activated on Nexus 7
Definitely happens on mako using the -pd image (r127) which renders it completely useless as a -pd image. ** Changed in: canonical-pocket-desktop Status: New => Confirmed -- 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/1530807 Title: Bluetooth cannot be activated on Nexus 7 Status in Canonical System Image: Confirmed Status in canonical-pocket-desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530807/+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 1495027] Re: unity_support_test should not write to hardcoded file in /tmp
** Changed in: nux (Ubuntu) Status: New => Triaged ** Changed in: nux (Ubuntu) Importance: Undecided => Low ** Also affects: nux Importance: Undecided Status: New ** Changed in: nux Status: New => Triaged ** Changed in: nux Importance: Undecided => Low -- 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/1495027 Title: unity_support_test should not write to hardcoded file in /tmp Status in Nux: Triaged Status in nux package in Ubuntu: Triaged Bug description: unity_support_test writes to a file called /tmp/unity_support_test.0 no matter what value is set in TMP, TMPDIR, and so on. This tool should respect user preferences and not hardcode the temporary directory. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1495027/+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 1491555] Re: Unity unnecessarily goes to low graphics mode
** Changed in: unity Status: New => Triaged ** Changed in: unity Importance: Undecided => Medium ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Triaged ** Changed in: unity (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/1491555 Title: Unity unnecessarily goes to low graphics mode Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Unity goes into low graphics mode when it detects "LLVM" in the renderer string. "LLVM" is not the right pattern to match because there are now accelerated Gallium drivers those also report "LLVM" in the render string, e.g. VMWare and Radeon. For example, this bug that showed up recently: https://bugs.freedesktop.org/show_bug.cgi?id=91747#c3 Gallium drivers may fall back to the Gallium Draw module for certain operations, and the Draw module can go down an LLVM path if necessarily and enabled. I think the original intention of this check is to catch "llvmpipe" driver, so I've attached a patch to do just that. Also, instead of matching "on softpipe", it seems that "softpipe" is sufficient. FYI, this fix can hopefully end up in Ubuntu 14.04 onwards. Unfortunately, I can't get through my company's proxy to push my branch, so instead of a merge request, please see the patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1491555/+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 1294864] Re: window snapping to the right edge is making the windows one or two pixels too narrow
** Changed in: compiz Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1294864 Title: window snapping to the right edge is making the windows one or two pixels too narrow Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Triaged Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Today is the first day I experience this. Window snapping has always worked perfectly on this machine. When snapping windows to the right side of the screen using either mouse or keyboard, any application's windows are not resized to fill up the screen to the right completely. vlc, nautilus, terminal, firefox, thundebird, chrome in rare cases, the resizing works correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,resize,regex,move,compiztoolbox,vpswitch,mousepoll,place,snap,grid,imgpng,animation,workarounds,wall,unitymtgrabhandles,session,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 19 22:13:18 2014 InstallationDate: Installed on 2013-12-24 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131220) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294864/+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 1072206] Re: [nvidia] Window content is black or transparent
** Changed in: compiz Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Released Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+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 1486498] Re: unity --reset wrongly says deprecated and fails to say what to do instead
** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = In Progress ** Changed in: unity Importance: Undecided = Low ** Changed in: unity Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity (Ubuntu) Importance: Undecided = Low ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Stephen M. Webb (bregma) -- 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/1486498 Title: unity --reset wrongly says deprecated and fails to say what to do instead Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: unity 7.2.5+14.04.20150603-0ubuntu1, Ubuntu 14.04 1. Switch to a console, for example by typing Ctrl Alt F1. 2. Enter unity --reset (without quotes). What happens: A. WARNING: no DISPLAY variable set, setting it to :0 B. ERROR: the reset option is now deprecated C. Nothing else. What's wrong with this: A. Unity rambles about no DISPLAY variable being set, despite knowing that it isn't going to use one anyway. B. reset is either deprecated, or it is an error. It can't be both. Deprecated means that something is planned to stop working sometime in the future. C. Unity exits without telling you what to use instead. What should happen: either A. unity --reset should Just Work, or B. the message should say ERROR: the reset option is no longer allowed; and C. it should tell you just to use unity by itself next time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1486498/+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 1486498] Re: unity --reset wrongly says deprecated and fails to say what to do instead
** Changed in: unity Milestone: None = 7.3.4 -- 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/1486498 Title: unity --reset wrongly says deprecated and fails to say what to do instead Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: unity 7.2.5+14.04.20150603-0ubuntu1, Ubuntu 14.04 1. Switch to a console, for example by typing Ctrl Alt F1. 2. Enter unity --reset (without quotes). What happens: A. WARNING: no DISPLAY variable set, setting it to :0 B. ERROR: the reset option is now deprecated C. Nothing else. What's wrong with this: A. Unity rambles about no DISPLAY variable being set, despite knowing that it isn't going to use one anyway. B. reset is either deprecated, or it is an error. It can't be both. Deprecated means that something is planned to stop working sometime in the future. C. Unity exits without telling you what to use instead. What should happen: either A. unity --reset should Just Work, or B. the message should say ERROR: the reset option is no longer allowed; and C. it should tell you just to use unity by itself next time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1486498/+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 1226737] Re: unity-support-test crashes on get_opengl_version()
The Nux Raring series is no longer supported.
** Changed in: nux/raring
Status: Triaged = Invalid
--
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/1226737
Title:
unity-support-test crashes on get_opengl_version()
Status in Nux:
Fix Released
Status in Nux raring series:
Invalid
Status in nux package in Ubuntu:
Fix Released
Bug description:
Bug is frequently reported on error.ubuntu.com. Looks like a pathway
with uninitialized variables can be triggered under some
circumstances.
#0 get_opengl_version (minor=0xbfdb3608, major=0xbfdb3604, version=0x1
Address 0x1 out of bounds) at unity_support_test.c:140
tmp = 0
i = 0
#1 main (argc=3, argv=0xbfdb36f4) at unity_support_test.c:760
display_name = optimized out
screen = optimized out
print = optimized out
root = 149729288
vinfos = 0x8ed51e0
display = 0x8ecb008
context = 0x0
results = {vendor = 0x0, renderer = 0x Address 0x
out of bounds, version = 0x1 Address 0x1 out of bounds, result = 1, major =
-1218692328, minor = -1076147649, indirect = 0, compiz = 0, flags = 0, error =
0x8ee0ec8 OpenGL rendering is not supported by the root visual}
resultfilename =
\004\b\344\063Z\267\003\000\000\000\000\300\004\b\\240\004\b\003\000\000\000\364\066\333\277\004\067\333\277
resultfile = 0
forcecheck = optimized out
glx_supported = optimized out
dummy0 = 169
dummy1 = 105
To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1226737/+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 1422427] Re: Nux cannot be built with clang.
** Changed in: nux Status: In Progress = Fix Committed -- 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/1422427 Title: Nux cannot be built with clang. Status in Nux: Fix Committed Status in nux package in Ubuntu: Fix Released Bug description: Would be useful allowing to build nux with clang. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1422427/+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 1050959] Re: Dash - Fix Dash scrollbar so that it does not displace Dash background texture
** Changed in: nux Milestone: 4.0.7 = None -- 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/1050959 Title: Dash - Fix Dash scrollbar so that it does not displace Dash background texture Status in Ayatana Design: Fix Committed Status in Nux: In Progress Status in Unity: Won't Fix Status in Unity 6.0 series: Won't Fix Status in nux package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Prior to building the full version of the overlay scrollbars, the most urgent fix is to stop the current scrollbar displacing the Dash background texture. Once this issue is fixed the next step is to move on to bug #608124 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1050959/+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 1111216] Re: Drop support for running without GLib event loop
** Changed in: nux Milestone: 4.0.7 = 4.0.8 -- 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/216 Title: Drop support for running without GLib event loop Status in Nux: In Progress Status in nux package in Ubuntu: In Progress Bug description: Nux has support in conditional compilation for running without the GLib event loop. This bug is about getting support for that dropped. Considering that the GLib event loop is supported on all platforms that Nux supports, there isn't much of a reason for running without it. The main reasons it should be removed are : 1. Its not used by anybody 2. Maintenance burden - every time you want to use some new event source, you have to provide support on both 3. Its completely broken from a code inspection POV: - It uses while (true) and busy-waits for new events (most of the time) - Sometimes the event retrieval sources block, sometimes they don't. - The check-for-events and dispatch-event code is in the same function for every source, which means that if one source blocks (eg XLib), and the other has pending events (Geis) then there's a potential deadlock until the first one unblocks - There's support for both Geis and XLib in the non-glib event loop, except that the Geis portion depends on compiling with GLib in order to actually retrieve events, rendering it non-functional in this mode. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/216/+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 1484039] Re: yoga 3 screen does not rotate
To be fair, this is not a problem in Unity (which handles display changes just fine) it's a problem supporting the position sensor on the Yoga 3 and integrating it with the udev system to provide feedback to the X11 server and invoke xrandr. Many devices have position sensors, and each device is different and needs bespoke software to get such rotation working. ** Changed in: unity (Ubuntu) Importance: Undecided = Wishlist ** 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/1484039 Title: yoga 3 screen does not rotate Status in unity package in Ubuntu: Confirmed Bug description: Hi Developer Team! i don't know if you have developed it as a feature or not, but Lenovo Yoga 3's screen rotates while flipping the screen back or holding it vertivalli - just like a pad. Are you about to develop this feature? I love Ubuntu! Thank you. Seal ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Aug 12 11:06:19 2015 InstallationDate: Installed on 2015-07-27 (15 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) 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/1484039/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
** Also affects: nux/trusty Importance: Undecided Status: New -- 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/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: Invalid Status in Nux: Fix Released Status in Nux trusty series: New Status in Unity: Invalid Status in nux package in Ubuntu: In Progress Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+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 1422427] Re: Nux cannot be built with clang.
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1422427 Title: Nux cannot be built with clang. Status in Nux: Fix Released Status in nux package in Ubuntu: Fix Released Bug description: Would be useful allowing to build nux with clang. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1422427/+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
** Changed in: nux
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1350101
Title:
Nux FTBFS - gcc 4.9
Status in Nux:
Fix Released
Status in nux package in Ubuntu:
Fix Released
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 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1342208 Title: Scroll wheel uses inverted logic to switch between applications/windows in the switcher Status in Nux: Fix Released Status in Nux trusty series: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in nux source package in Trusty: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] Scrolling on the Alt+Tab has invalid behavior: - Scrolling down, moves to the previous icon/window - Scrolling up, moves to the next icon/window - Scrolling left, moves to the next icon/window - Scrolling right, moves to the previous icon/window [Test case] 1. Press Alt+Tab 2. While pressing the keys, use mouse scroll wheel to scroll vertically (and, if possible, horizontally) Expected behavior: - Scrolling down, moves to the next icon/window - Scrolling up, moves to the previous icon/window - Scrolling left, moves to the previous icon/window - Scrolling right, moves to the next icon/window [Regression potential] Vertical scrolling code has not been touched by the change, so there's no possibility to regress in this sense. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1342208/+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 1342896] Re: Add support for lcov version 1.11 to fix build error
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1342896 Title: Add support for lcov version 1.11 to fix build error Status in Nux: Fix Released Status in nux package in Ubuntu: Fix Released Bug description: Nux ci is failing to build because Nux says it doesn't support lcov 1.11. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1342896/+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()
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: Fix Released Status in Nux trusty series: Fix Committed Status in nux package in Ubuntu: Fix Released Status in nux source package in Trusty: Fix Released Bug description: [Impact] Unity crashes when unlocking the session [Test case 1] 1. Lock the session 2. Unlock the session 3. No crash should happen [Test case 2] 1. Use unity in multi-monitor setup 2. Lock the session 3. Detach one of the monitors 4. Make sure the lockscreen updates (sometimes it's needed to switch to tty1 and back) 5. No crash should happen [Regression potential] None 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
[Dx-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228093 Title: Dash content flickers when the touchpad is used to scroll it. Status in Nux: Fix Released Status in Nux trusty series: Fix Committed Status in nux package in Ubuntu: Fix Released Status in nux source package in Trusty: Fix Released Bug description: [Impact] Dash content flickers when two-finger scrolling on the touchpad [Test case] 1. Enable two fingers scroll from Unity Control Center - Mouse and Touchpad 2. Open the unity dash, expand the search results and start scrolling vertically 3. Content should not flicker and should ignore horizontal scroll events [Regression potential] Scrolling on dash content does not work properly To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1228093/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: Invalid Status in Nux: Fix Released Status in Nux trusty series: New Status in Unity: Invalid Status in nux package in Ubuntu: In Progress Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+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 1363959] Re: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle()
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363959 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() Status in Nux: Fix Released Status in Nux trusty series: Fix Committed Status in nux package in Ubuntu: Fix Released Status in nux source package in Trusty: Fix Released Bug description: [Impact] An occasional unpredictable crash in the Unity shell occurs during a drag-and-drop operation. [Test Case] Unfortunately it is not possible to reproduce this bug at will. Apparently is is caused by an uninitialized pointer dereference that only occurs in a timing-dependent manner. Running a full autopilot test suite against the Unity desktop shell reveals no new regressions. [Regression Potential] The code change effectively adds a test for a null pointer. It is possible that this might introduce a regression in drag-and-drop functionality that previously relied on undefined behaviour to work when it didn't crash. [Other Info] Fix was released with Ubuntu 14.10 and no new regressions have been reported. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1363959/+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 1290900] Re: Nux should not advertise IBUS_CAP_SURROUNDING_TEXT
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290900 Title: Nux should not advertise IBUS_CAP_SURROUNDING_TEXT Status in Nux: Fix Released Status in nux package in Ubuntu: Fix Released Bug description: The surrounding text functionality in Nux' IBus input context is not implemented yet so it should not be advertised. This bug is affecting ibus-bogo [1] and many of its Vietnamese users. [1]: https://github.com/BoGoEngine/ibus-bogo-python/ To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1290900/+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 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1342731 Title: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected Status in Nux: Fix Released Status in Nux trusty series: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in libindicator package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in libindicator source package in Trusty: Fix Released Status in nux source package in Trusty: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] When scrolling on indicator-sound using the horizontal scrolling the result is the opposite to what we expect in unity (left scrolling increases the volume and right scrolling decreases it), while in general is not handled at all for indicator-ng indicators as both left and right scrolling always ends up in a +1 delta scroll. [Test case] 1. Hover Indicator-sound in unity 2. Scroll left: the volume should be reduced 3. Scroll right: the volume should be increased [Regression potential] The horizontal scroll direction might be inverted with some touchpads To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1342731/+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 1175669] Re: fcitx often fails to work in dash with Unity
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1175669 Title: fcitx often fails to work in dash with Unity Status in Nux: Fix Released Status in Unity: Invalid Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in nux source package in Saucy: Won't Fix Bug description: The input method fcitx' is supposed to work with Unity dash in raring,but it is not working well. This happens *only* when I set the launcher to hide as default. When I press Super to open the dash and begin to type characters into dash or HUD display (by pressing left alt),sometimes I can activate the input method.In more cases,there aren't any response when pressing ctrl+space.Sometimes I can't type anything into dash. I've asked a developer of fcitx (csslayer) but he said he knew nothing about it.He said it could be a bug of unity and suggested me to report the bug here. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu May 2 23:51:07 2013 InstallationDate: Installed on 2012-05-01 (365 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-04-03 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1175669/+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 1458952] Re: Memory leak in InputMethodIBus
** Changed in: nux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1458952 Title: Memory leak in InputMethodIBus Status in Nux: Fix Released Status in Nux trusty series: Triaged Status in nux package in Ubuntu: In Progress Bug description: There are two memory leaks in InputMethodIBus. One is with releasing the ibus_bus and the other being the keybinding. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1458952/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
** Changed in: nux/trusty Status: New = Triaged ** Changed in: nux/trusty Importance: Undecided = Medium -- 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/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: Invalid Status in Nux: Fix Released Status in Nux trusty series: Triaged Status in Unity: Invalid Status in nux package in Ubuntu: In Progress Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+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 1028020] Re: Performance fixes for GdkPixbuf conversions and QueueDraw calls (SRU)
** Changed in: nux Status: Fix Committed = Fix Released ** Changed in: nux (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1028020 Title: Performance fixes for GdkPixbuf conversions and QueueDraw calls (SRU) Status in Nux: Fix Released Status in Nux 2.0 series: Fix Released Status in Unity: Invalid Status in nux package in Ubuntu: Fix Released Status in nux source package in Precise: Fix Released Bug description: [Test Case] Performance fix - only way of testing is performing the benchmarking steps again to check if there is improvement. [Regression Potential] Probably only broken scrolling in nux 'widgets'. Original description: This bug has been added to keep track of 2 performance fixes that we would like having merged into lp:nux/2.0 for an upcoming precise Nux SRU. The commits that have been mentioned: http://bazaar.launchpad.net/~unity-team/nux/trunk/revision/618 http://bazaar.launchpad.net/~unity-team/nux/trunk/revision/631 To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1028020/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
** Changed in: nux Status: In Progress = Fix Committed -- 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/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: Invalid Status in Nux: Fix Committed Status in Unity: Invalid Status in nux package in Ubuntu: In Progress Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+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 1466137] Re: unity --replace kills my session
#1 is not much of a workaround because compiz --replace also kills my session. ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: Confirmed = Triaged ** Changed in: unity Importance: Undecided = High ** Changed in: unity (Ubuntu) Importance: Undecided = High -- 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/1466137 Title: unity --replace kills my session Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Running unity --replace from the HUD or Dash causes my whole session to be killed. Rather than just simply restarting the unity applications, I'm punted back to the login window and all my running apps are dead. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid dpkg --list | grep unity ii gir1.2-unity-5.0:amd64 7.1.4+14.10.20140808-0ubuntu1 amd64GObject introspection data for the Unity library ii libmeanwhile11.0.2-5 amd64open implementation of the Lotus Sametime Community Client protocol ii libunity-action-qt1:amd64 1.1.0+14.04.20140304-0ubuntu1 amd64Unity Action Qt API ii libunity-control-center1 15.04.0+15.04.20150410-0ubuntu1amd64utilities to configure the GNOME desktop ii libunity-core-6.0-9 7.3.2+15.04.20150420-0ubuntu1 amd64core library for the Unity interface ii libunity-gtk2-parser0:amd64 0.0.0+15.04.20150118-0ubuntu1 amd64GtkMenuShell to GMenuModel parser ii libunity-gtk3-parser0:amd64 0.0.0+15.04.20150118-0ubuntu1 amd64GtkMenuShell to GMenuModel parser ii libunity-misc4 4.0.5+14.04.20140115-0ubuntu1 amd64Miscellaneous functions for Unity - shared library ii libunity-protocol-private0:amd64 7.1.4+14.10.20140808-0ubuntu1 amd64binding to get places into the launcher - private library ii libunity-scopes-json-def-desktop 7.1.4+14.10.20140808-0ubuntu1 all binding to get places into the launcher - desktop def file ii libunity-settings-daemon1 15.04.1+15.04.20150408-0ubuntu1amd64Helper library for accessing settings rc libunity-webapps0 2.5.0~+14.04.20140409-0ubuntu1 amd64Web Apps integration with the Unity desktop ii libunity9:amd64 7.1.4+14.10.20140808-0ubuntu1 amd64binding to get places into the launcher - shared library ii libunityvoice1:amd64 0.1+15.04.20150416-0ubuntu1amd64client library for Unity voice service ii qtdeclarative5-unity-action-plugin:amd64 1.1.0+14.04.20140304-0ubuntu1 amd64Unity Action QML Components ii unity 7.3.2+15.04.20150420-0ubuntu1 amd64Interface designed for efficiency of space and interaction. ii unity-asset-pool 0.8.24+15.04.20141217-0ubuntu2 all Unity Assets Pool ii unity-control-center 15.04.0+15.04.20150410-0ubuntu1amd64utilities to configure the GNOME desktop ii unity-control-center-signon 0.1.7~+14.10.20140814-0ubuntu1 amd64Unity Control Center extension for single signon ii unity-greeter15.04.4-0ubuntu1 amd64Unity Greeter ii unity-gtk-module-common 0.0.0+15.04.20150118-0ubuntu1 all Common files for GtkMenuShell D-Bus exporter ii unity-gtk2-module:amd64 0.0.0+15.04.20150118-0ubuntu1 amd64GtkMenuShell D-Bus exporter ii unity-gtk3-module:amd64 0.0.0+15.04.20150118-0ubuntu1 amd64GtkMenuShell D-Bus exporter ii unity-lens-applications 7.1.0+13.10.20131011-0ubuntu2 amd64Application lens for unity ii unity-lens-files 7.1.0+13.10.20130920-0ubuntu1 amd64File lens for unity ii unity-lens-music
[Dx-packages] [Bug 1477330] Re: open new folder in tab should put new tab on top
** Package changed: unity (Ubuntu) = nautilus (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/1477330 Title: open new folder in tab should put new tab on top Status in nautilus package in Ubuntu: New Bug description: In the files menu if the user selects the option to open a folder in a new tab it seems obvious to me that the user wants to immediately start working in that folder. However the new folder is opened behind the current folder, so the user must explicitly select the new folder to work on. I cannot think of any logical situation in which after opening a new folder the user would prefer to continue working in whatever random folder currently happens to be on top. I cannot find any tweak that controls this behavior. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 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] CurrentDesktop: Unity Date: Wed Jul 22 18:15:22 2015 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1477330/+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 1475174] Re: Unity launcher badges too small for smaller icons
'Too small' is a function of screen size, pixel density, viewing distance, and user preference. For that reason, the only reasonable solution for this would be to provide a user-visible per-display configuration option with a reasonable default based on the display's scaling factor. This would make a good first project for someone looking to dive in to Unity development. ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (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/1475174 Title: Unity launcher badges too small for smaller icons Status in unity package in Ubuntu: Triaged Bug description: If, using unity-tweak, you drop the size of launcher icons down to a smaller size - say 32px - the badges that count things like unread messages are too small. This has been a bug since 14.04 and persists through 15.04. There should be a minimum size for badges so that they are always readable. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-services 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,vpswitch,unitymtgrabhandles,move,compiztoolbox,mousepoll,resize,regex,gnomecompat,place,session,wall,animation,expo,workarounds,fade,ezoom,scale,unityshell] CurrentDesktop: Unity Date: Thu Jul 16 08:12:57 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-22-generic, x86_64: installed nvidia-346-updates, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346-updates, 346.59, 3.19.0-22-generic, x86_64: installed ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3683] InstallationDate: Installed on 2015-07-11 (4 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=33ba1dec-b49f-45c6-bd17-aa4011f8abfb ro priority=low acpi=off nomodeset quiet splash nomodeset video=uvesafb:mode_option=1680x1050-32,mtrr=3,scroll=ywrap SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97X-UD3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Jul 15 20:01:29 2015 xserver.configfile: default xserver.devices: inputDasKeyboard KEYBOARD, id 6 inputDasKeyboard KEYBOARD, id 7 inputLogitech M570MOUSE, id 8 inputUVC Camera (046d:0990) KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log
[Dx-packages] [Bug 1468602] Re: Time format is wrong on clock when seconds are added
** Project changed: unity = indicator-datetime ** Package changed: unity (Ubuntu) = indicator-datetime (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1468602 Title: Time format is wrong on clock when seconds are added Status in The Date and Time Indicator: New Status in indicator-datetime package in Ubuntu: New Bug description: When enabling seconds in the top right corner on Ubuntu 14.04 the format goes from 01:23 to 01.23.45 when it should probably be 01:23:45(colon, not period). Language is set to Norwegian. I am also seeing an increase in load on compiz when seconds are enabled, this is also found by someone else in bug #1242229. Would appreciate it if someone would replace the two periods with colons. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1468602/+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 1295445] Re: Cursor size is not updated on HiDPI at intermediate UI scale levels
Setting back to NEW for further investigation. ** Changed in: unity Status: Fix Released = New ** Changed in: unity Milestone: 7.2.0 = None -- 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/1295445 Title: Cursor size is not updated on HiDPI at intermediate UI scale levels Status in Unity: New Status in unity package in Ubuntu: New Bug description: When UI scale factor is at intermediate values from 1.0-2.0 and from 2.0-3.0 the cursor size is not updated to match current settings. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295445/+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 1461864] Re: package nux-tools 0.9.48-0ubuntu1.1 failed to install/upgrade: trying to overwrite '/usr/share/apport/package-hooks/source_nux.py', which is also in package libnux-0.9-
Thanks for reporting this problem, but that particular version of Ubuntu reached its end of support over two years ago. There are no official archives to which a fix could be pushed even if one were available. ** Changed in: nux (Ubuntu) Status: New = Won't 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/1461864 Title: package nux-tools 0.9.48-0ubuntu1.1 failed to install/upgrade: trying to overwrite '/usr/share/apport/package-hooks/source_nux.py', which is also in package libnux-0.9-common 0.9.48-0ubuntu1.1 Status in nux package in Ubuntu: Won't Fix Bug description: stop work ProblemType: Package DistroRelease: Ubuntu 11.04 Package: nux-tools 0.9.48-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.38-16.67-generic-pae 2.6.38.8 Uname: Linux 2.6.38-16-generic-pae i686 Architecture: i386 Date: Thu Jun 4 13:04:01 2015 ErrorMessage: trying to overwrite '/usr/share/apport/package-hooks/source_nux.py', which is also in package libnux-0.9-common 0.9.48-0ubuntu1.1 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) InstallationMedia_: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcVersionSignature_: Ubuntu 2.6.38-16.67-generic-pae 2.6.38.8 SourcePackage: nux Title: package nux-tools 0.9.48-0ubuntu1.1 failed to install/upgrade: trying to overwrite '/usr/share/apport/package-hooks/source_nux.py', which is also in package libnux-0.9-common 0.9.48-0ubuntu1.1 UpgradeStatus: Upgraded to natty on 2015-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1461864/+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 1388648] Re: Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native
** Summary changed: - Wine shows the Unity desktop dash when an application runs in full-screen with a resolution diferent from the native + Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native ** Changed in: unity Importance: Undecided = Medium ** 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/1388648 Title: Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. In the Configure Wine application, go to the graphics tab. 2. Under the window settings section, check the three first boxes and uncheck the latest. 3. Run a Windows application in full-screen mode using a screen resolution different from the default in the desktop. EXPECTED BEHAVIOUR - The application to be presented in full-screen. REAL BEHAVIOUR - As seen in the attached screen-shot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wine 1:1.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 3 00:47:54 2014 InstallationDate: Installed on 2013-05-21 (530 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: wine1.6 UpgradeStatus: Upgraded to utopic on 2014-09-24 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1388648/+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 1450991] Re: hided launcher does not show urgent icons in 15.04
** Branch linked: lp:~azzar1/unity/fix-lp-1450991 -- 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/1450991 Title: hided launcher does not show urgent icons in 15.04 Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: When a program requests to wiggle its icons on the launcher, if the launcher is visible, it works fine and the icon shakes properly. But when it is not visible (auto-hide option is enabled), desired behavior would be that its icon should slide inside while it is shaking and then go off the screen after a short while. This behavior already hes been applied in 14.10 and older versions, but in 15.04 launcher does not show urgent animation when it is hide that it could be bug. Why this bug annoys me? I usually would use IM apps and in such apps, Pidgin for instance, when a user becomes on-line or off-line, its icon on the launcher starts to shaking and in this way informs me. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1450991/+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 1268673] Re: Unity Dash should propose terminal app when taping cmd
** 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/1268673 Title: Unity Dash should propose terminal app when taping cmd Status in GNOME Terminal: Fix Released Status in Unity: Invalid Status in gnome-terminal package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Hi This is not a pure bug, but an idea to made life of lot of people simpler. More of that I'm not sure this is more related to Gnome Terminal than Unity). But it's for me an ergonomy bug. I explain : In my job I have to use Windows terminal a lot. As I do with 'term' in unity, to open it I usually press Windows / Super Key and enter 'CMD'. Here is the problem : each time (very often) I come back on Ubuntu I try to search 'CMD' in the dash to open gnome-terminal. Of course : no result ! The idea is to have Gnome terminal (and probably other terminal app installed on the system) being found when searching cmd. This would avoid people like me to every time make the mistake, and newcomers to Ubuntu (student in Network/Telecoms/Programming...) would find what they search instantly what they search : better first impression of being home when first days on the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Jan 13 18:46:16 2014 InstallationDate: Installed on 2014-01-12 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1268673/+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 1313597] Re: Shortcut overlay cannot be closed by clicking the close button in 14.04
I can verify this appears to work in the SRU. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1313597 Title: Shortcut overlay cannot be closed by clicking the close button in 14.04 Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Due to an input handling race, the first time users log into Unity on their system, the shortcut overlay may not close when clicking the X in the corner. This leads to a poor user experience. [ Test Case ] 1. Remove ~/.config/unity/first_run.stamp. 2. Log into Unity. 3. Shortcut hints overlay should be shown. 4. Click on X in the corner. [ Regression Potential ] This is a workaround for a race, so some users may never see the race to begin with. That said, no regression should be observed as in worse case, the shortcut hints still cannot be closed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff --- Original Description: In 14.04, the shortcut overlay would pop-out automatically on first boot. Although there is a close button on the top-left corner, it cannot be closed by clicking it. (it could be dismissed by the super key, or open a new window) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313597/+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 1459121] Re: phone unlock screen
** Package changed: unity (Ubuntu) = unity8 (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/1459121 Title: phone unlock screen Status in unity8 package in Ubuntu: New Bug description: ubuntu 15.04 for phones beta r.223 (bq aquaris ubuntu edition) Since r.222 upgrade i noticed that sometimes I cant unlock the phone. When i push unlock button (one time) looks like nothing happens, screen doesn't woke up. If i press a second time screen woke up for half second showing unlock screen. When it happens, i know that the OS is running because when i push the unlock button(first time), i can make a screen shot pushing up volume and down volume at same time it also reproduce the sound. Looks that the only problem is to wakeup the screen. It began to happen without install any program, just upgrades. When it happened to me I think that I haven't opened any app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1459121/+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 926979] Re: compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool const) from unity::dash::DashView::AnalyseLensURI(std::string const) from unity::dash::DashView::OnA
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/926979 Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool const) from unity::dash::DashView::AnalyseLensURI(std::string const) from unity::dash::DashView::OnActivateRequest(_GVariant*) Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.0 series: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Certain cases when clicking on Dash items may cause a crash. [ Test Case ] It's not entirely clear how the crash is triggered, but no crash should be observed when clicking on Dash entries. [ Regression Potential ] The change is small and no regressions should be observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Clicked dash, Internet applications. Opened a new bug as the others appear to suggest a fix is released for those bugs. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.0.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4 Uname: Linux 3.2.0-3-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sun Feb 5 14:51:39 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7eff5ff51d10 _ZN3nux8PropertyIbEaSERKb+32: mov 0x18(%rdi),%rdi PC (0x7eff5ff51d10) ok source 0x18(%rdi) (0x03f0) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: nux::Propertybool::operator=(bool const) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::AnalyseLensURI(std::string const) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::OnActivateRequest(_GVariant*) () from /usr/lib/compiz/libunityshell.so unity::UBusManager::OnCallback(_GVariant*, void*) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=() UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo usrp video To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/926979/+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 1458952] Re: Memory leak in InputMethodIBus
** Also affects: nux/trusty Importance: Undecided Status: New ** Changed in: nux/trusty Importance: Undecided = Medium ** Changed in: nux/trusty Status: New = Triaged -- 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/1458952 Title: Memory leak in InputMethodIBus Status in Nux: Fix Committed Status in Nux trusty series: Triaged Status in nux package in Ubuntu: In Progress Bug description: There are two memory leaks in InputMethodIBus. One is with releasing the ibus_bus and the other being the keybinding. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1458952/+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 886478] Re: New Alt + tab switcher doesn't follow system font
Verified this works as documented on 14.04. Marking the SRU as verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/886478 Title: New Alt + tab switcher doesn't follow system font Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Users who switch the system font and then use Alt+Tab will see a jarring effect when the Ubuntu font is displayed. This can also lead to not fully supported language issues. [ Test Case ] 1. Switch the system font to something else besides Ubuntu. 2. Use Alt+Tab. 3. Observe any fonts displayed in Alt+Tab follow the system font. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff -- Original Description: In my laptop, I have to change from default ubuntu font to droid font because the default one doesn't fully support vietnamese. Let it sit there will make the overall system feel awkward. And now, while the whole system is in droid, only the switcher is still using the ubuntu font. Plz make the switcher follow the system font or at least, make a way to configure its appearance. -- Desired solution: - Alt+tab switcher should use the system font - This change should result in ZERO change to the appearance of the font in Alt+Tab on a fresh installation of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/886478/+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 1302883] Re: Ubuntu 14.04: Moving a window when Workspace Switcher is active does not release cursor
** Package changed: ubuntu = unity (Ubuntu) ** Changed in: unity (Ubuntu) Importance: Undecided = High ** Also affects: unity 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/1302883 Title: Ubuntu 14.04: Moving a window when Workspace Switcher is active does not release cursor Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Upgraded to Ubuntu 14.04 (beta 2) from 13.10 (via: sudo update-manager -d) - 64bit version. After logging in (GUI) and pressing [SUPER / Windows key]-S (or by clicking on the icon on the launcher bar) to bring up Workspace Switcher, then left-clicking-and-keep-pressing on an app's window and keeping left mouse button pressed while dragging it, moves that window, with the mouse cursor being changed to a hand (sometimes to an up-arrow). Upon release of the left mouse button to stop dragging the window, the mouse cursor is not being changed back, the window keeps its last position when the left mouse button was released, yet upon pressing [SUPER / Windows key] the previously dragged window jumps to the new location of the mouse cursor, and the hand cursor stays. Left-clicking on any of the workspaces does nothing. Pressing [SUPER / Windows key]-S switches the mouse cursor back to the default pointer and the previously dragged window drops at that point in time to the cursor's position and the mouse functions again as usual. Sometimes this happens right away, sometimes this happens only after moving a window around a bit (several drag'n drop attempts). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302883/+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 1441487] Re: Running any Java program produces messages in the terminal
Removing upstream Unity project again, since I linked the correct upstream Jayatana project to the Ubuntu packages ** Changed in: unity (Ubuntu) Status: Confirmed = Invalid ** No longer affects: unity (Ubuntu) ** No longer affects: unity -- 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/1441487 Title: Running any Java program produces messages in the terminal Status in One Hundred Papercuts: Triaged Status in jayatana package in Ubuntu: Triaged Bug description: I just installed Ubuntu 15.04 and was surprised to discover that when running a Java based program from the terminal in Unity, the following message appears: Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar. I tried several programs and it is all the same. Some Java programs with enabled Java security produce even some error messages and crash. If I press Ctrl+Alt+F1 to start a new terminal session without a GUI and run a Java program (without a GUI), I don't experience this problem. Back in Unity, if I unset JAVA_TOOL_OPTIONS in the terminal and run a Java program, it works fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 10:11:10 2015 InstallationDate: Installed on 2015-03-30 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1441487/+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 1390625] Re: mouse cursor gets corrupted
Since this problem occurs without Unity and is solved by installing a newewr xorg-server package, I'm marking it as invalid for Unity. ** Changed in: unity (Ubuntu) Status: Confirmed = 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1264795] Re: Alt+Tab Switcher randomly activates itself
Unfortunately no, you can not use Ginn to preemptively grab the 3-finger taps because the shell already has a grab on the root window for 3-finger taps. -- 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/1264795 Title: Alt+Tab Switcher randomly activates itself Status in Unity: Triaged Status in compiz package in Ubuntu: Incomplete Status in unity package in Ubuntu: Confirmed Bug description: I am running Ubuntu 13.10 on my Macbook Pro 2009 laptop. I cannot find a report on this bug when googling it. So I thought I would file the bug. Literally, the switcher randomly just activates itself, and then the icons show in the middle of the screen as per usual. The stranger behavior is what happens next: 1) The switcher might automatically switch to a seemingly random app from the selection. 2) The switcher will just be displayed, but I cannot actually make it go away by clicking on one of the app icons. Instead, it just displays for however long it 'feels like,' typically ~5 seconds. So.. That's it. Hope I can get some help :D ^___^ 3 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1264795/+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 1448775] Re: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
demesg contains several dups of the following error. [ 637.133657] traps: compiz[5430] trap invalid opcode ip:7fe2bd6f05f5 sp:7fff0b63f0b8 error:0 [ 868.799930] traps: compiz[6021] trap invalid opcode ip:7f0fab07c5f5 sp:7fff64019268 error:0 It would be helpful if a stacktrace of compiz could be obtained. -- 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/1448775 Title: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash Status in unity package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After upgrade from working machine with 14.10 to 15.10 I'm unable to login. Right after password screen I see loading of desktop and I'm returned to password prompt again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell] Date: Sun Apr 26 23:07:55 2015 DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26: added EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71] InstallationDate: Installed on 2014-11-07 (170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA SATELLITE C670-10V ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: TKBSC dmi.board.vendor: TOSHIBA dmi.board.version: 1.40 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SATELLITE C670-10V dmi.product.version: PSC3QE-00700JPL dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 26 23:07:32 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448775/+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 1406802] Re: Vivid Unity Wallpaper horizontally hashed
** Project changed: unity = nautilus ** Package changed: unity (Ubuntu) = nautilus (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/1406802 Title: Vivid Unity Wallpaper horizontally hashed Status in Nautilus: Confirmed Status in Ubuntu MATE: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Standard wallpaper selection distorted badly cut and displaced sideways. See screenshot. Lenovo Desktop Dual processor: processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 23 model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz Standard dropdown windows like terminal, internet etc. normal. DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION=Ubuntu Vivid Vervet (development branch) Linux Lenovo2 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:37:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) jerry@Lenovo2:~$ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Dec 31 14:06:16 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo Device [17aa:3048] InstallationDate: Installed on 2014-10-27 (65 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141026) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=81fa31d4-972b-409f-9b0b-d34528ec9238 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Dec 31 14:04:58 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1406802/+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 1072206] Re: [nvidia] Window content is black or transparent
** Changed in: compiz/0.9.11 Status: In Progress = Fix Committed -- 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/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Committed Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Released Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+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 1446256] Re: Default out of the box menu option should be set to Global Menus
** Changed in: unity (Ubuntu)
Status: New = In Progress
** Changed in: unity (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/1446256
Title:
Default out of the box menu option should be set to Global Menus
Status in Unity:
In Progress
Status in unity package in Ubuntu:
In Progress
Bug description:
Change request: the default out of the box menu option should be
global menus ('menus in the menu bar')
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1446256/+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 1446256] Re: Default out of the box menu option should be set to Global Menus
** Changed in: unity (Ubuntu)
Importance: Medium = Critical
--
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/1446256
Title:
Default out of the box menu option should be set to Global Menus
Status in Unity:
In Progress
Status in unity package in Ubuntu:
In Progress
Bug description:
Change request: the default out of the box menu option should be
global menus ('menus in the menu bar')
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1446256/+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 798445] Re: can't discern between two files or folder with identical names
The status change indicates this bug requires input from the Ayatana design team before and more progress can be made in the Unity desktop shell software. -- 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/798445 Title: can't discern between two files or folder with identical names Status in Ayatana Design: New Status in Unity: Incomplete Status in Unity Files Lens: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Binary package hint: dash 1. create two folders/files with the same name (in two different locations). 2. press the BFB (Big Freakin Button aka Home Button) and search for that folder/file name see that there is no way to tell which folder/file is which. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: dash 0.5.5.1-7.2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Jun 16 17:50:38 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dash UpgradeStatus: Upgraded to natty on 2011-04-21 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/798445/+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 1108956] Re: The dash closes when trying to switch from Command lens to home lens
** Changed in: unity Status: In Progress = Fix Committed -- 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/1108956 Title: The dash closes when trying to switch from Command lens to home lens Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When I open the command lens by pressing ALT+F2, if I press Super the dash is closed. It should not be closed, it should switch to the home lens instead. This is the suite of the bug 1019457 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1108956/+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 1435830] Re: AP test failure: unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single Monitor)
** Changed in: unity
Status: In Progress = Fix Committed
--
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/1435830
Title:
AP test failure:
unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single
Monitor)
Status in Unity:
Fix Committed
Status in unity package in Ubuntu:
Fix Released
Bug description:
AP test fails consistently on every run.
FAIL:
unity.tests.launcher.test_keynav.LauncherKeyNavTests.test_launcher_keynav_changes_panel(Single
Monitor)
--
/var/log/syslog: {{{
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: login
finished
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Got
token: ya29.OwFvVwItMuU7CMLyfIe22KhPBBlD_v62HgletZAa1aS8K5U1WNfqY6QL
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Search
changed to: 'Has'
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Searching
for: Has
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Search
changed to: 'HasFocus'
Mar 19 16:18:46 xt2-14 com.canonical.Unity.Scope.File.Gdrive[1599]: Searching
for: HasFocus
}}}
unity-log: {{{
DEBUG 2015-03-19 16:18:41 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Compiz active now true
DEBUG 2015-03-19 16:18:41 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Terminal active now false
DEBUG 2015-03-19 16:18:52 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Compiz active now false
DEBUG 2015-03-19 16:18:52 unity.launcher.icon.application
ApplicationLauncherIcon.cpp:173 Terminal active now true
}}}
Traceback (most recent call last):
File
/usr/lib/python2.7/dist-packages/unity/tests/launcher/test_keynav.py, line
247, in test_launcher_keynav_changes_panel
self.assertThat(self.unity.panels.get_active_panel().title,
Eventually(Equals(Search your computer and online sources)))
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 423, in
assertThat
raise mismatch_error
MismatchError: After 10.0 seconds test on MenuView.panel_title failed: !=:
reference = u'Search your computer and online sources'
actual= u''
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1435830/+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 1294864] Re: window snapping to the right edge is making the windows one or two pixels too narrow
** Changed in: compiz Status: In Progress = Fix Committed ** Changed in: compiz/0.9.11 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/1294864 Title: window snapping to the right edge is making the windows one or two pixels too narrow Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Triaged Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Today is the first day I experience this. Window snapping has always worked perfectly on this machine. When snapping windows to the right side of the screen using either mouse or keyboard, any application's windows are not resized to fill up the screen to the right completely. vlc, nautilus, terminal, firefox, thundebird, chrome in rare cases, the resizing works correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,resize,regex,move,compiztoolbox,vpswitch,mousepoll,place,snap,grid,imgpng,animation,workarounds,wall,unitymtgrabhandles,session,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 19 22:13:18 2014 InstallationDate: Installed on 2013-12-24 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131220) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294864/+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 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds
I verified this on an old, slow machine where the described phenomenon was more easily observed and it indeed no longer occurs. There is still a whole-screen flicker as Compiz starts up but that's an unrelated issue. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. [TEST CASE] (1) Configure the desktop to use a non-default wallpaper. (2) Log in to a Unity session and observe the area behind the Launcher. [REGRESSION POTENTIAL] The solution to this problem was to eliminate the animation of the BFB icon on initial startup. Potentially this could cause the animation to not run at other times, although even if this did occur, it is unlikely to be noticed. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+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 1390625] Re: mouse cursor gets corrupted
Given that this problem seems to occur regardless of the presence of the Unity desktop shell on a system or not, and that it seems to disappear with a kernel update, I'm going to go out on a limb here and say it has nothing to do with the Unity desktop shell. ** Changed in: unity Status: Confirmed = 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1401911] Re: When the screen is locked edge barriers should be deactivated.
Works like a charm for me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1401911 Title: When the screen is locked edge barriers should be deactivated. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] If the screen is locked, launcher/panel edge barriers at the moment are active. [Test Case] In a multi-monitor environment, lock the screen and move the mouse between monitors. There should be no sticky edge between the monitors. [Regression Potential] Code in the paths that handle the edge barriers was changed. Potentially this could impact the reveal of a hidden Launcher if there were errors introduced in these code paths. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1401911/+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 1441914] Re: lua:socket settimeout does not work
** Package changed: unity (Ubuntu) = luasocket (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/1441914
Title:
lua:socket settimeout does not work
Status in luasocket package in Ubuntu:
New
Bug description:
Ubuntu Version: Ubuntu 14.04.2 LTS
package lua-socket:i386 3.0~rc1-3
On Ubuntu 14.04, lua socket settimeout does not work as expected. On a tcp
socket, it causes the next receive to close the connection immediately.
It works correctly on Ubuntu 12.04 and debian 7.
To reproduce:
install packages lua5.1 and lua-socket
Take the echo server example from the introduction to luasocket:
http://w3.impa.br/~diego/software/luasocket/introduction.html
Put it in a file echo.lua and run it with lua echo.lua
From another window, use telnet localhost {port} to connect to the echo server
Result: Immediately after connecting, the server closes the connection.
Expected Result: The server should wait 10 seconds for input, then close the
connection.
package version that works correctly in debian 7: lua-socket:i386 2.0.2-8
-
A copy of the example (echo.lua):
-- load namespace
local socket = require(socket)
-- create a TCP socket and bind it to the local host, at any port
local server = assert(socket.bind(*, 0))
-- find out which port the OS chose for us
local ip, port = server:getsockname()
-- print a message informing what's up
print(Please telnet to localhost on port .. port)
print(After connecting, you have 10s to enter a line to be echoed)
-- loop forever waiting for clients
while 1 do
-- wait for a connection from any client
local client = server:accept()
-- make sure we don't block waiting for this client's line
client:settimeout(10)
-- receive the line
local line, err = client:receive()
-- if there was no error, send it back to the client
if not err then client:send(line .. \n) end
-- done with client, close the object
client:close()
end
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/luasocket/+bug/1441914/+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 1441819] Re: The unity sound settings is a bit cluttered
** Package changed: unity (Ubuntu) = indicator-sound (Ubuntu) -- 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/1441819 Title: The unity sound settings is a bit cluttered Status in indicator-sound package in Ubuntu: Confirmed Bug description: The best is to view the added screen-shot, in the attachmentst, and my proposed 'fix'. This is an revised image of the one in the attachment: http://i.stack.imgur.com/o0Jd1.png Please ignore the one in the attachments, its slightly off, of what I meant ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 8 21:12:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-331, 331.113, 3.16.0-33-generic, x86_64: installed nvidia-331-uvm, 331.113, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. Device [1043:124d] InstallationDate: Installed on 2015-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=e4df7d74-dffc-4deb-9ea1-b7653d90c4c6 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 8 19:32:08 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1441819/+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 777140] Re: launcher doesn't hide on its own after gesture reveal
Still definitely happens in Ubuntu 15.04 ** Changed in: unity (Ubuntu) Status: Expired = Triaged ** Changed in: unity Status: Incomplete = 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/777140 Title: launcher doesn't hide on its own after gesture reveal Status in Ayatana Design: Invalid Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: When i show the launcher with a 4 finger drag, it stays open until I manually dismiss it. It should go away on its own at some point. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/777140/+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 1440560] Re: please convert the session-migration scripts to Python3
** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Stephen M. Webb (bregma) -- 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/1440560 Title: please convert the session-migration scripts to Python3 Status in unity package in Ubuntu: In Progress Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. please convert the session-migration scripts to Python3. There is also a missing dependency on python3-gi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1440560/+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 1241972] Re: Drag and drop from Dash to Desktop doesn't work
** Changed in: unity/7.1 Milestone: 7.1.2 = None -- 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/1241972 Title: Drag and drop from Dash to Desktop doesn't work Status in Chromium Browser: New Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.1 series: Won't Fix Status in Unity 7.2 series: Triaged Status in nautilus package in Ubuntu: Triaged Status in unity package in Ubuntu: Confirmed Bug description: When you try to drag and drop an app from Dash (both from app lens and home lens) to Desktop, system display an error and the shortcut isn't created. The error is: Error while copying - There was an error getting information about /. More details: The specified location is not supported Then there are four buttons: Cancel - Skip all - Skip - Retry. Way to reproduce: - Open the dash - Drag an app icon and drop on desktop What happend: - An error is raised What expected: - A shortcut is created With file, music and photo is all ok. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1241972/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
@Seb is there a way to manually reset the configuration (ie what is the dconf setting)? I saw the problem fixed after an upgrade without any manual intervention and can no longer reproduce on my test systems, but I am willing to believe my tests systems house gremlins that like to fool me on a regular basis. -- 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/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
Do you guys who are still experiencing this problem have an errant .desktop file in ~/.local/share/applications/ by any chance? -- 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/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1308265] Re: First password letter not registered in lockscreen if screen off
** Changed in: unity Status: In Progress = Fix Committed -- 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/1308265 Title: First password letter not registered in lockscreen if screen off Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 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/1308265/+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 1029114] Re: With autohide and the HUD enabled the launcher can appear at incorrect times
** Changed in: unity Status: In Progress = Fix Committed -- 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/1029114 Title: With autohide and the HUD enabled the launcher can appear at incorrect times Status in Unity: Fix Committed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Hi What Happened: 1) Turn on launcher auto hide 2) Display the HUD (tap Alt) 3) Move the mouse to the left side of the screen (as if you are showing the launcher) 4) Note the launcher is not displayed 5) Now hide the HUD (either tap Alt or select the X in the top left corner) 6) Note that the launcher is now displayed, after the HUD closes. What I expected to happen: - I expected that the launcher is not displayed at step 6. I expected for the launcher to not be displayed at step 6 because the user could have the HUD displayed for a long period of time then decide that they don't need the HUD. The launcher is then suddenly revealed to them as they moved their cursor to the left side of the screen a few minutes a ago. This could then confuse the user to why the launcher has appeared when all they did was close the HUD. Hope this can be fixed soon. Andy ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview] ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,compiztoolbox,snap,resize,move,grid,imgpng,mousepoll,place,unitymtgrabhandles,wall,gnomecompat,session,regex,resizeinfo,animation,expo,fade,scale,ezoom,workarounds,unityshell] CrashDB: unity Date: Wed Jul 25 21:19:17 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1029114/+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 1432231] Re: compiz crashed with SIGSEGV in XGetSelectionOwner()
** Changed in: unity Status: In Progress = Fix Committed -- 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/1432231 Title: compiz crashed with SIGSEGV in XGetSelectionOwner() Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: Running updated current Vivid, on systemd and using Intel Haswell video. Crash happened using Unity Tweak Tool after clicking Window Manager-General-Hardware Acceleration-Texture (dropdown). Screen. mouse and keyboard froze for several seconds, screen flashed off and on, mouse and keyboard were functional. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 14 16:01:38 2015 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2015-03-14 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f04575688dc XGetSelectionOwner+12:mov 0x968(%rdi),%rax PC (0x7f04575688dc) ok source 0x968(%rdi) (0x3f803f4ce1ff) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6 unity::XdndStartStopNotifierImp::OnTimeout() () from /usr/lib/compiz/libunityshell.so unity::glib::Source::SourceCallback(void*) () from /usr/lib/libunity-core-6.0.so.9 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: compiz crashed with SIGSEGV in XGetSelectionOwner() 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/unity/+bug/1432231/+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 1301394] Re: Launcher damange the left-monitor area also if it's hidden
** Changed in: unity Status: In Progress = Fix Committed -- 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/1301394 Title: Launcher damange the left-monitor area also if it's hidden Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: When in auto-hide mode the launcher damages the area that it would fill when shown, also when hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1301394/+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 926979] Re: compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool const) from unity::dash::DashView::AnalyseLensURI(std::string const) from unity::dash::DashView::OnA
** Changed in: unity Status: In Progress = Fix Committed -- 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/926979 Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool const) from unity::dash::DashView::AnalyseLensURI(std::string const) from unity::dash::DashView::OnActivateRequest(_GVariant*) Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.0 series: Invalid Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Clicked dash, Internet applications. Opened a new bug as the others appear to suggest a fix is released for those bugs. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.0.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4 Uname: Linux 3.2.0-3-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sun Feb 5 14:51:39 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7eff5ff51d10 _ZN3nux8PropertyIbEaSERKb+32: mov 0x18(%rdi),%rdi PC (0x7eff5ff51d10) ok source 0x18(%rdi) (0x03f0) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: nux::Propertybool::operator=(bool const) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::AnalyseLensURI(std::string const) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::OnActivateRequest(_GVariant*) () from /usr/lib/compiz/libunityshell.so unity::UBusManager::OnCallback(_GVariant*, void*) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=() UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo usrp video To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/926979/+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 1436095] Re: AP test failure: unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
** Changed in: unity
Status: In Progress = Fix Committed
--
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/1436095
Title:
AP test failure:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
Status in Unity:
Fix Committed
Status in unity package in Ubuntu:
Fix Released
Bug description:
The following two AP tests consistently ERROR during regular Unity
testing.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 13:43:02 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
128, in test_scaled_window_closes_on_middle_click
self.assertWindowIsScaledEquals(target_xid, False)
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
68, in assertWindowIsScaledEquals
self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 421, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 471, in
_matchHelper
mismatch = matcher.match(matchee)
File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py,
line 113, in match
wait_fun(self.matcher, self.timeout)
File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py,
line 129, in _callable_wait_for
new_value = refresh_fn()
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
67, in lambda
refresh_fn = lambda: xid in [w.xid for w in
self.unity.screen.scaled_windows]
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 520, in __getattr__
self.refresh_state()
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 474, in refresh_state
_, new_state = self.get_new_state()
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 564, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
StateNotFoundError: Object not found with name 'Window' and properties {'id':
148832}.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 14:00:34 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
148, in test_scaled_window_closes_on_close_button_click
self.assertWindowIsScaledEquals(target_xid, False)
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
68, in assertWindowIsScaledEquals
self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 421, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 471, in
_matchHelper
mismatch = matcher.match(matchee)
File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py,
line 113, in match
wait_fun(self.matcher, self.timeout)
File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py,
line 129, in _callable_wait_for
new_value = refresh_fn()
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
67, in lambda
refresh_fn = lambda: xid in [w.xid for w in
self.unity.screen.scaled_windows]
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 520, in __getattr__
self.refresh_state()
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 474, in refresh_state
_, new_state = self.get_new_state()
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 564, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
StateNotFoundError: Object not found with name 'Window' and properties {'id':
224517}.
==
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1436095/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to :
[Dx-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal
No, there has been no actual fix released because no one has been able to reproduce the problem. It does not appear to be a software problem in Unity, so we can not release a modification to the software to fix it. the bugs has been marked as Fix Released because of comment 10. -- 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/1432484 Title: ctrl+alt+t hot key doesn't open terminal Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: 1) Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) unity: Installed: 7.3.1+15.04.20150227-0ubuntu1 Candidate: 7.3.1+15.04.20150227-0ubuntu1 Version table: *** 7.3.1+15.04.20150227-0ubuntu1 0 500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) ctrl+alt+t should open terminal 4) nothing happens ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 21:55:08 2015 DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3662] InstallationDate: Installed on 2014-04-21 (329 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 15 21:49:49 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8 inputDarfon Wireless Keyboard Mouse KEYBOARD, id 9 inputDarfon Wireless Keyboard Mouse KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-0 DisplayPort-0 HDMI-0 product id9896 vendor HWP xserver.version: 2:1.17.1-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1432484/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe :
[Dx-packages] [Bug 1428837] Re: AP tests fail because of upstream Nautilus .desktop file rename
** Changed in: unity Status: In Progress = Fix Committed -- 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/1428837 Title: AP tests fail because of upstream Nautilus .desktop file rename Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: New AP test failures are occurring after an upstream Nautilus .desktop file rename. The failures are caused by the Nautilus windows not being closed on request. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1428837/+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 1313597] Re: Shortcut overlay cannot be closed by clicking the close button in 14.04
** Changed in: unity Status: In Progress = Fix Committed -- 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/1313597 Title: Shortcut overlay cannot be closed by clicking the close button in 14.04 Status in Unity: Fix Committed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: In 14.04, the shortcut overlay would pop-out automatically on first boot. Although there is a close button on the top-left corner, it cannot be closed by clicking it. (it could be dismissed by the super key, or open a new window) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313597/+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 1246891] Re: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher
** Changed in: unity Status: In Progress = Fix Committed -- 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/1246891 Title: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: 1) Press Alt+F1 2) Press right-key 3) Press left-key Expected result: 3) The launcher goes back to keynav mode and unfolds completely. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1246891/+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 1430784] Re: FTBFS using GCC-5
** Changed in: unity
Status: In Progress = Fix Committed
--
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/1430784
Title:
FTBFS using GCC-5
Status in Unity:
Fix Committed
Status in unity package in Ubuntu:
Fix Released
Bug description:
Unity fails to build from source using GCC 5.0 or later.
An excerpt from the failing build log follows.
/build/buildd/unity-7.3.1+15.04.20150126/hud/HudController.cpp:160:96:
required from here
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:89:30: error: no
match for call to '(sigc::bound_mem_functor1void, unity::hud::Controller,
bool) (std::nullptr_t)'
{ return functor_(_A_arg1); }
^
In file included from
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:9:0,
from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7,
from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
from /usr/include/sigc++-2.0/sigc++/signal.h:8,
from /usr/include/Nux-4.0/NuxCore/Object.h:30,
from /usr/include/Nux-4.0/NuxCore/NuxCore.h:730,
from /usr/include/Nux-4.0/Nux/Nux.h:26,
from
/build/buildd/unity-7.3.1+15.04.20150126/hud/pch/hud_pch.hh:28:
/usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1855:12: note: candidate:
T_return sigc::bound_mem_functor1T_return, T_obj, T_arg1::operator()(typename
sigc::type_traitT_arg3::take) const [with T_return = void; T_obj =
unity::hud::Controller; T_arg1 = bool; typename sigc::type_traitT_arg3::take
= const bool] near match
T_return operator()(typename type_traitT_arg1::take _A_a1) const
^
/usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1855:12: note: conversion
of argument 1 would be ill-formed:
In file included from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7:0,
from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
from /usr/include/sigc++-2.0/sigc++/signal.h:8,
from /usr/include/Nux-4.0/NuxCore/Object.h:30,
from /usr/include/Nux-4.0/NuxCore/NuxCore.h:730,
from /usr/include/Nux-4.0/Nux/Nux.h:26,
from
/build/buildd/unity-7.3.1+15.04.20150126/hud/pch/hud_pch.hh:28:
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:89:30: error:
converting to 'bool' from 'std::nullptr_t' requires direct-initialization
[-fpermissive]
{ return functor_(_A_arg1); }
^
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:89:30: error:
return-statement with a value, in function returning 'void' [-fpermissive]
hud/CMakeFiles/hud-lib.dir/build.make:103: recipe for target
'hud/CMakeFiles/hud-lib.dir/HudController.cpp.o' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1430784/+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 1433648] Re: u-s-d needs timestamp to run commands
** Changed in: unity Status: In Progress = Fix Committed -- 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/1433648 Title: u-s-d needs timestamp to run commands Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity source package in Trusty: Triaged Status in unity-settings-daemon source package in Trusty: Triaged Bug description: That's needed for https://git.gnome.org/browse/gnome-settings- daemon/commit/?id=487a936e61766f0306772c1269e2ff437fc53a46 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1433648/+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 1346355] Re: 14.04 power-cog does not turn red when restart is needed
Thanks for taking an interest in the design of the Ubuntu user interface, but even if the Ubuntu design team hadn't already declared this issue closed, it is still not an issue of the Unity shell but of the Session Menu. Reverting for a status of 'Invalid' for the Unity shell. ** 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/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in unity package in Ubuntu: Invalid Bug description: Bug = a popup-dialog asking the user to reboot the system after an update should not repeat (popup again) at a later time if the user chooses not to reboot. Instead, the power-cog should turn the color red and no further popup-dialogs should present at any time. In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+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 1303846] Re: compiz crashed with SIGSEGV in _int_malloc()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug is no longer a duplicate of private bug 1283564 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1303846 Title: compiz crashed with SIGSEGV in _int_malloc() Status in unity package in Ubuntu: New Bug description: stopped right after I ran Bleach(not as root) and search your computer and online sources. Just made the box with nothing in it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 10:00:14 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff7debbcd71 _int_malloc+689: mov %r14,0x10(%r9) PC (0x7ff7debbcd71) ok source %r14 ok destination 0x10(%r9) (0xf8a337efb7c8) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_malloc (av=0x7ff7deefb760 main_arena, bytes=256) at malloc.c:3489 __GI___libc_malloc (bytes=256) at malloc.c:2891 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in _int_malloc() 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/1303846/+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 1293860] Re: compiz crashed with SIGSEGV in _int_malloc()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug is no longer a duplicate of private bug 1283564 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1293860 Title: compiz crashed with SIGSEGV in _int_malloc() Status in unity package in Ubuntu: New Bug description: If you don't know what it means from the message above, I'm going to be of no help. It crashed, I sent the report. End of story. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 20:01:54 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-03-09 (373 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130308) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd4948bdbc1 _int_malloc+689: mov %r14,0x10(%r9) PC (0x7fd4948bdbc1) ok source %r14 ok destination 0x10(%r9) (0x21017fd494bfc7c8) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_malloc (av=0x7fd494bfc760 main_arena, bytes=256) at malloc.c:3489 __GI___libc_malloc (bytes=256) at malloc.c:2891 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 pixman_glyph_cache_insert () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 Title: compiz crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to trusty on 2014-03-17 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1293860/+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 1304949] Re: compiz crashed with SIGSEGV in _int_malloc()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1304949 Title: compiz crashed with SIGSEGV in _int_malloc() Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Fresh installation of Trusty, only updated via apt-get upgrade. After reboot, and using the starter, the system freezed and this failure was submitted. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 11:47:28 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-09 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140331) ProcCmdline: compiz ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f4d83248d71 _int_malloc+689: mov %r14,0x10(%r9) PC (0x7f4d83248d71) ok source %r14 ok destination 0x10(%r9) (0x9e63d014) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_malloc (av=0x7f4d83587760 main_arena, bytes=128) at malloc.c:3489 __GI___libc_malloc (bytes=128) at malloc.c:2891 operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 unity::dash::PlacesVScrollBar::UpdateTexture() () from /usr/lib/compiz/libunityshell.so unity::dash::PlacesVScrollBar::PostLayoutManagement(long) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in _int_malloc() 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/unity/+bug/1304949/+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 1272751] Re: u1404 beta - Asus X401A - compiz crashed with SIGSEGV in _int_malloc()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1272751 Title: u1404 beta - Asus X401A - compiz crashed with SIGSEGV in _int_malloc() Status in Unity: New Status in unity package in Ubuntu: New Bug description: compiz crashed during install of google chrome ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 25 19:53:26 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-01-25 (0 days ago) InstallationMedia: It ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7fa08fd50ed1 _int_malloc+625: add %al,(%rax) PC (0x7fa08fd50ed1) ok source %al ok destination (%rax) (0x4000) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_malloc (av=0x7fa090090760 main_arena, bytes=24) at malloc.c:3399 __GI___libc_malloc (bytes=24) at malloc.c:2850 operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::listCompWindow*, std::allocatorCompWindow* ::operator=(std::listCompWindow*, std::allocatorCompWindow* const) () from /usr/lib/compiz/libopengl.so PrivateGLScreen::paintOutputRegion(GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in _int_malloc() 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/unity/+bug/1272751/+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 1283477] Re: compiz crashed with SIGSEGV in _int_malloc()
** Changed in: unity Importance: Undecided = High ** Changed in: unity (Ubuntu) Importance: Undecided = High -- 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/1283477 Title: compiz crashed with SIGSEGV in _int_malloc() Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Was searching for mail in unity, then it hungs for several seconds (20 secs maybe) and crashed. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `compiz': free(): corrupted unsorted chunks: 0x7f8224d65f10 *** CurrentDesktop: Unity Date: Sat Feb 22 10:58:06 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8267d42f11 _int_malloc+689: mov %r14,0x10(%r9) PC (0x7f8267d42f11) ok source %r14 ok destination 0x10(%r9) (0xffa1574c4cfa8488) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_malloc (av=0x7f822420, bytes=56) at malloc.c:3446 __GI___libc_malloc (bytes=56) at malloc.c:2855 _dl_map_object_deps (map=map@entry=0x7f8268a5b000, preloads=preloads@entry=0x0, npreloads=npreloads@entry=0, trace_mode=trace_mode@entry=0, open_mode=open_mode@entry=-2147483648) at dl-deps.c:511 dl_open_worker (a=a@entry=0x7f8219c0f778) at dl-open.c:272 _dl_catch_error (objname=objname@entry=0x7f8219c0f768, errstring=errstring@entry=0x7f8219c0f770, mallocedp=mallocedp@entry=0x7f8219c0f760, operate=operate@entry=0x7f826886b880 dl_open_worker, args=args@entry=0x7f8219c0f778) at dl-error.c:177 Title: compiz crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283477/+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 1213742] Re: compiz crashed with SIGSEGV in _int_free()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1213742 Title: compiz crashed with SIGSEGV in _int_free() Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: I was searching for an ODT document, and accidentally opened the preview for it, but then when I went the close the preview, Unity froze, and then after about 5 secs, crashed and restarted. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130816.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Mon Aug 19 08:58:36 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-02-05 (194 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd116c07289 _int_free+217:mov 0x8(%rdx),%esi PC (0x7fd116c07289) ok source 0x8(%rdx) (0x10007) not located in a known VMA region (needed readable region)! destination %esi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_free (av=0x7fd116f47740 main_arena, p=0x7d9da60, have_lock=0) at malloc.c:3832 XDestroyRegion () from /usr/lib/x86_64-linux-gnu/libX11.so.6 CompRegion::intersects(CompRegion const) const () from /usr/lib/libcompiz_core.so.ABI-20130125 unity::UnityScreen::compizDamageNux(CompRegion const) () from /usr/lib/compiz/libunityshell.so unity::UnityScreen::preparePaint(int) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in _int_free() UpgradeStatus: Upgraded to saucy on 2013-08-13 (5 days ago) UserGroups: adm cdrom dip games lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1213742/+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 1207951] Re: compiz assert failure: *** Error in `compiz': free(): invalid next size (fast): 0x0000000003f5de50 ***
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1207951 Title: compiz assert failure: *** Error in `compiz': free(): invalid next size (fast): 0x03f5de50 *** Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Freeze when using Unity. And Compiz crashed. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `compiz': free(): invalid next size (fast): 0x03f5de50 *** CrashCounter: 1 Date: Tue Jul 23 22:53:56 2013 ExecutablePath: /usr/bin/compiz ExecutableTimestamp: 1366264808 InstallationDate: Installed on 2013-01-22 (182 days ago) InstallationMedia: This MarkForUpload: True ProcCmdline: compiz ProcCwd: /home/aneesh Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f42a9235860 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x3f5de50, str=0x7f42a9235a00 free(): invalid next size (fast), action=3) at malloc.c:4902 _int_free (av=optimized out, p=0x3f5de40, have_lock=0) at malloc.c:3758 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 Title: compiz assert failure: *** Error in `compiz': free(): invalid next size (fast): 0x03f5de50 *** UpgradeStatus: Upgraded to saucy on 2013-07-04 (19 days ago) UserGroups: adm autopilot cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1207951/+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 1031186] Re: compiz crashed with SIGSEGV in _int_malloc() from cairo_fill() from unity::dash::Style::FocusOverlay()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1031186 Title: compiz crashed with SIGSEGV in _int_malloc() from cairo_fill() from unity::dash::Style::FocusOverlay() Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Crash while using Unity. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: compiz-core 1:0.9.8+bzr3249-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Mon Jul 30 20:00:13 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb7452681:mov0x4(%ecx),%esi PC (0xb7452681) ok source 0x4(%ecx) (0x01aa00cb) not located in a known VMA region (needed readable region)! destination %esi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 malloc () from /lib/i386-linux-gnu/libc.so.6 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in malloc() 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/unity/+bug/1031186/+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 1378495] Re: compiz crashed with SIGSEGV in FT_Outline_Decompose()
*** This bug is a duplicate of bug 1231798 *** https://bugs.launchpad.net/bugs/1231798 ** This bug is no longer a duplicate of private bug 1284844 ** This bug has been marked a duplicate of private bug 1231798 -- 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/1378495 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() Status in unity package in Ubuntu: New Bug description: Opened dash, ad started typing, when it crashed. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 Uname: Linux 3.17.0-haswell x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Oct 7 21:18:56 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-04-27 (892 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f672967059f:cmp%rdx,(%rax) PC (0x7f672967059f) ok source %rdx ok destination (%rax) (0x00058a00) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() UpgradeStatus: Upgraded to utopic on 2013-05-12 (513 days ago) UserGroups: adm bumblebee cdrom dip docker lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378495/+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 1310837] Re: compiz crashed with SIGSEGV
*** This bug is a duplicate of bug 1231798 *** https://bugs.launchpad.net/bugs/1231798 ** This bug is no longer a duplicate of bug 1289798 compiz crashed with SIGSEGV in gray_find_cell() ** This bug has been marked a duplicate of private bug 1231798 -- 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/1310837 Title: compiz crashed with SIGSEGV Status in unity package in Ubuntu: New Bug description: Using Ubuntu 14.04 LTS 64bit. Unity version: unity 7.2.0+14.04.20140416-0ubuntu1 After booting into ubuntu and updating linux-headers-generic linux- image-generic and linux-generic from 3.13.0.24.28 to 3.13.0.24.29 tried to open terminal several times with ctrl+alt+t, nothing happened. So went into dash to search for terminal but froze as I started typing, eventually the error message appeared with Ubuntu 14.04 experienced internal error. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Apr 21 22:09:18 2014 ExecutablePath: /usr/bin/compiz ExecutableTimestamp: 1397083158 InstallationDate: Installed on 2013-05-21 (335 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: compiz ProcCwd: /home/laurenceubuntu ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8f1c0b33ce:mov%rcx,(%rsi) PC (0x7f8f1c0b33ce) ok source %rcx ok destination (%rsi) (0x0da0) not located in a known VMA region (needed writable region)! 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 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV UpgradeStatus: Upgraded to trusty on 2014-04-18 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1310837/+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 1298329] Re: compiz crashed with SIGSEGV in malloc_consolidate()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug is no longer a duplicate of private bug 1193715 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1298329 Title: compiz crashed with SIGSEGV in malloc_consolidate() Status in unity package in Ubuntu: New Bug description: I rapidly typing in the search box in unity dashboard. and this crash happend ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 27 22:47:14 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-12-10 (472 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f10fe2f4702 malloc_consolidate+258: mov 0x8(%rbx),%rax PC (0x7f10fe2f4702) ok source 0x8(%rbx) (0x002d) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: malloc_consolidate (av=av@entry=0x7f109420) at malloc.c:4149 _int_malloc (av=0x7f109420, bytes=5928) at malloc.c:3423 __GI___libc_malloc (bytes=5928) at malloc.c:2891 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298329/+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 1289798] Re: compiz crashed with SIGSEGV in gray_find_cell()
*** This bug is a duplicate of bug 1231798 *** https://bugs.launchpad.net/bugs/1231798 ** This bug has been marked a duplicate of private bug 1231798 -- 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/1289798 Title: compiz crashed with SIGSEGV in gray_find_cell() Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Was searching in the dash when compiz restarted and this showed up. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140305-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 8 10:09:26 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2011-09-24 (895 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/zsh SegvAnalysis: Segfault happened at: 0x7f18b083034f:cmp%rcx,(%rax) PC (0x7f18b083034f) ok source %rcx ok destination (%rax) (0x0201) 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() UpgradeStatus: Upgraded to trusty on 2013-12-20 (78 days ago) UserGroups: adm admin cdrom dialout kismet lpadmin plugdev sambashare wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1289798/+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 1231798] Re: compiz crashed with SIGSEGV in gray_find_cell()
** Information type changed from Private 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/1231798 Title: compiz crashed with SIGSEGV in gray_find_cell() Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: I just install Ubuntu 13.10 beta 2 and try to switch between input method engines. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 27 12:41:20 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-09-27 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=zh_TW: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=zh_TW.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb527b7ed6f:cmp%rcx,(%rax) PC (0x7fb527b7ed6f) ok source %rcx ok destination (%rax) (0x32dc) 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() 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/unity/+bug/1231798/+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 1299710] Re: compiz crashed with SIGSEGV in FT_Outline_Decompose()
*** This bug is a duplicate of bug 1231798 *** https://bugs.launchpad.net/bugs/1231798 ** This bug is no longer a duplicate of private bug 1284844 ** This bug has been marked a duplicate of private bug 1231798 -- 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/1299710 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() Status in unity package in Ubuntu: New Bug description: He was writing in the search bar and froze for a few seconds. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 30 06:03:58 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-30 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f297c59d3af:cmp%rcx,(%rax) PC (0x7f297c59d3af) ok source %rcx ok destination (%rax) (0x005e) 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() 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/1299710/+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 1292915] Re: compiz crashed with SIGSEGV in FT_Outline_Decompose()
*** This bug is a duplicate of bug 1231798 *** https://bugs.launchpad.net/bugs/1231798 ** This bug is no longer a duplicate of bug 1289798 compiz crashed with SIGSEGV in gray_find_cell() ** This bug has been marked a duplicate of private bug 1231798 -- 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/1292915 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() Status in unity package in Ubuntu: New Bug description: Happened while opening the Dash ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 15 16:35:48 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc6b8a4b3af:cmp%rcx,(%rax) PC (0x7fc6b8a4b3af) ok source %rcx ok destination (%rax) (0xfff8) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() 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/1292915/+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 1303362] Re: compiz crashed with SIGSEGV in FT_Outline_Decompose()
*** This bug is a duplicate of bug 1231798 *** https://bugs.launchpad.net/bugs/1231798 ** This bug is no longer a duplicate of private bug 1284844 ** This bug has been marked a duplicate of private bug 1231798 -- 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/1303362 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() Status in unity package in Ubuntu: New Bug description: Using unity to search for an application, and the screen became unresonsive ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 14:06:41 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f8ce05a03af:cmp%rcx,(%rax) PC (0x7f8ce05a03af) ok source %rcx ok destination (%rax) (0x0100) 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303362/+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 1238123] Re: compiz crashed with SIGSEGV in malloc_consolidate()
*** This bug is a duplicate of bug 1283477 *** https://bugs.launchpad.net/bugs/1283477 ** This bug is no longer a duplicate of private bug 1199799 ** This bug has been marked a duplicate of bug 1283477 compiz crashed with SIGSEGV in _int_malloc() -- 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/1238123 Title: compiz crashed with SIGSEGV in malloc_consolidate() Status in unity package in Ubuntu: New Bug description: It crashes on trying to click a program icon in the dash. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Thu Oct 10 18:01:15 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-10-10 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta i386 (20131010.1) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb7437880 malloc_consolidate+128: cmp 0xc(%eax),%edi PC (0xb7437880) ok source 0xc(%eax) (0x100c) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: malloc_consolidate (av=av@entry=0xb7570440 main_arena) at malloc.c:4102 _int_malloc (av=av@entry=0xb7570440 main_arena, bytes=bytes@entry=1824) at malloc.c:3379 __GI___libc_malloc (bytes=1824) at malloc.c:2859 ?? () from /usr/lib/i386-linux-gnu/libgraphite2.so.3 gr_make_font_with_ops () from /usr/lib/i386-linux-gnu/libgraphite2.so.3 Title: compiz crashed with SIGSEGV in malloc_consolidate() 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/1238123/+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 1293509] Re: compiz crashed with SIGSEGV in FT_Outline_Decompose()
*** This bug is a duplicate of bug 1231798 *** https://bugs.launchpad.net/bugs/1231798 ** This bug is no longer a duplicate of private bug 1284844 ** This bug has been marked a duplicate of private bug 1231798 -- 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/1293509 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() Status in unity package in Ubuntu: New Bug description: Using Dash to search for an application. UI froze and Compiz restarted. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 19:49:41 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-07-12 (247 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f74b11e23af:cmp%rcx,(%rax) PC (0x7f74b11e23af) ok source %rcx ok destination (%rax) (0x001b) 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() UpgradeStatus: Upgraded to trusty on 2014-03-11 (5 days ago) UserGroups: adm cdrom debian-tor dip lp lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1293509/+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 1181367] Re: Alt+Tab switches between incorrect windows after some time of activity
** Changed in: unity/7.0 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1181367 Title: Alt+Tab switches between incorrect windows after some time of activity Status in Unity: Fix Released Status in Unity 7.0 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Raring: Fix Released Bug description: [Impact] Due to overflow, alt+tab between the same application becomes impossible] [Test Case] 1) Keep two windows of an app (say terminal) opened for some time, and another window of a different app 2) Focus one window terminal keeping the other terminal window below it 3) Press Alt+Tab Expected behavior 4) The other terminal window is focused Actual behavior: 4) Other opened application is selected instead. [Regression Potential] Low, types extended from int to long long. The code affected is the alt tab functionality. Due to an overflow, after some time of activity it's impossible to alt+tab between two windows of the same application. 1) Keep two windows of an app (say terminal) opened for some time, and another window of a different app 2) Focus one window terminal keeping the other terminal window below it 3) Press Alt+Tab Expected behavior 4) The other terminal window is focused Actual behavior: 4) Other opened application is selected instead. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1181367/+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 1064155] Re: [SRU Regression] Launcher and Global Menu are completely black after exiting fullscreen from certain apps
** Changed in: unity/7.0 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1064155 Title: [SRU Regression] Launcher and Global Menu are completely black after exiting fullscreen from certain apps Status in Unity: Fix Released Status in Unity 5.0 series: Fix Committed Status in Unity 7.0 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Raring: Fix Released Bug description: [Impact] Regression in launcher / global menu drawing. [Test Case] Exit fullscreen mode from programs such as VirtualBox and KRDC the Unity Launcher on the left of the screen and the Global Menu at the top screen both disappear, and come back after clicking with a mouse. Expected result would be that they do not disappear. [Regression Potential] None known, draws the menus when full screen app is minimized. Automatic tests included. --- UPDATE: I have uninstalled the customized version of unity (ikarosdev-unity-revamped) using the following command: sudo apt-get purge unity unity-services unity-common libunity-core-5.0-5 I then removed the custom unity ppa from my system and proceeded to install the official version of unity 5.6. I AM STILL EXPERIENCING THE SAME ISSUES WHICH ARE DESCRIBED BELOW: After upgrading to Unity 5.6 on Ubuntu 12.04 32-bit, now when I exit fullscreen mode from programs such as VirtualBox and KRDC the Unity Launcher on the left of the screen and the Global Menu at the top screen both disappear. All I have to do to get them to reappear is click anywhere on the screen, which seems entirely unnecessary... I did not experience this behavior with Unity 5.4. Also I am experiencing this behavior on two different laptops that are both running 12.04 32-bit with different hardware and software configurations. Screenshot is attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 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] CompositorRunning: compiz Date: Mon Oct 8 21:18:01 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.0, 3.2.0-31-generic-pae, i686: installed vboxhost, 4.2.0, 3.5.0-17-generic, i686: installed vboxhost, 4.2.0, 3.6.0-994-generic, i686: installed vboxhost, 4.2.0, 3.6.0-l840, i686: installed GraphicsCard: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb50] InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) MachineType: TOSHIBA Satellite L840 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic-pae root=UUID=526d8ee5-709c-4635-aa7c-ba40c46cab5c ro quiet splash i915.semaphores=1 vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd06/26/2012:svnTOSHIBA:pnSatelliteL840:pvrPSK8GU-08S00D:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L840 dmi.product.version: PSK8GU-08S00D dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.libdrm2: libdrm2 2.4.39-0ubuntu1.0~ppa1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.8-0ubuntu2.1~precise2
