← Back to team overview

dx-packages team mailing list archive

[Bug 1195692] Re: Dash takes a long time to open when running Mir on Samsung N310 netbook with i915 graphics

 

Confirmed. I notice this is still happening with the latest saucy images
on netbooks. Generally everything works fine until you open the dash.
And then you have *minutes* of waiting.

In the past we thought this was due to graphics load. But I think more
likely is the simple issue that netbooks only have 1GB RAM usually. A
large chunk is consumed by graphics, and the rest is not big enough to
cope with Unity7's high memory consumption. So I think we're probably
just thrashing. I have yet to confirm this theory...

** Changed in: mir
       Status: Incomplete => Invalid

** Summary changed:

- Dash takes a long time to open when running Mir on Samsung N310 netbook with i915 graphics
+ Dash takes a long time to open when running Mir on a netbook with i915 graphics

** Changed in: unity
       Status: Expired => Confirmed

** Changed in: unity (Ubuntu)
       Status: Expired => Confirmed

** 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/1195692

Title:
  Dash takes a long time to open when running Mir on a netbook with i915
  graphics

Status in Mir:
  Invalid
Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I've installed Mir on an old Samsung netbook (N310) with an Atom CPU
  and onboard graphics. Everything seems to be normal, expect when I
  open the dash the following happens:

  1.) Press the Super key to open the Dash
  2.) Wait 60 seconds
  3.) A 'ghost' of the Dash appears (high alpha value)
  4.) Wait 60 more seconds
  5.) Dash is at last usable

  Closing the Dash works at the usual speed (not instant but acceptable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1195692/+subscriptions