dx-packages team mailing list archive

[Jon <launchpad.net.20120321.ws@xxxxxxxxxxx>]

System info:

lsb_release -rd
Description:	Ubuntu 14.04.3 LTS
Release:	14.04

unity --version
unity 7.2.5

Interestingly, I ran apport to get some system information, and I get
this message:

> Your system is providing 3D via software rendering rather than
hardware rendering.  This is a compatibility mode which should display
3D graphics properly but the performance may be very poor.  If the
problem you're reporting is related to graphics performance, your real
question may be why X didn't use hardware acceleration for your system.

3D acceleration is indeed turned on for this VM, and Workspaces
animation is very snappy, so as far as I've been aware it +has+ been
using hardware acceleration. I don't know if this is relevant, but
adding it anyway.

Let me know if you need any logs.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1514065

Title:
  Windows move in workspaces after a window resize event

Status in compiz-plugins-main package in Ubuntu:
  New

Bug description:
  I run Ubuntu 14.04 LTS as a VirtualBox guest (both with VB 4.3.x and
  5.x) using the default desktop. If I toggle the size of the screen
  (using Host-Right-Ctrl) from maximised to not maximised and then back
  again, the workspaces behave incorrectly. The same happens also if I
  save and restore a VirtualBox session from disk.

  Here is what goes wrong:

  - Maximised windows move between Workspaces
  - When activating the Workspaces viewer, maximised windows cannot be dragged to the Workspace they should be on
  - Unmaximising and re-maximising a window fixes the problem for that window only

  I have written a script to toggle the maximisation status of all
  windows, which resolves the problem. I will add that, and system
  information, once this report is submitted.

  I have installed a brand new Ubuntu guest using the "ubuntu-14.04.2
  -desktop-amd64.iso" image and cannot reproduce the problem. It is
  perhaps the case that the problematic machine was installed using the
  "ubuntu-14.04-desktop-amd64.iso" image (I don't know if that would
  matter).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1514065/+subscriptions