date:20141007

[Dx-packages] [Bug 1103961] Re: nux::IOpenGLShaderProgram::Begin crashes on nVidia 10de:00fd

2014-10-07 Thread Sergio Gelato

I've upgraded the OS on the affected computer to trusty and found that
the problem is still present in trusty's version of nux. Same symptoms,
and my patch still applies.

** Tags added: precise trusty

-- 
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/1103961

Title:
  nux::IOpenGLShaderProgram::Begin crashes on nVidia 10de:00fd

Status in “nux” package in Ubuntu:
  New

Bug description:
  After upgrading to precise and activating nvidia-173 (173.14.35) on a
  machine with the following graphics card:

  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV37GL
  [Quadro PCI-E Series] [10de:00fd] (rev a2)

  /usr/bin/compiz started to crash with the exact same symptoms as in
  bug #768178. (I'm filing a new bug since that one is marked as a
  duplicate of a quite different bug that is itself marked as invalid.)
  This isn't too surprising since the graphics card is a close relative
  of the GeForce FX series, various flavours of which are already
  blacklisted in nux.

  Forcing Unity 2D works around the problem, so I've applied the
  attached patch on top of nux 2.14.1-0ubuntu1. Maybe one could set
  _use_glsl_shaders = false in NuxGraphics/GraphicsEngine.cpp instead
  but I don't have the time to test this conjecture.
  glGetString(GL_RENDERER) returns Quadro PCI-E Series/PCI/SSE2 for
  this card and driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1103961/+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 1367916] Re: Phone freezes when trying to active the dialer app from the messaging menu

2014-10-07 Thread Michał Sawicz

I can confirm the fact that it launches in emergency mode instead of
showing the lockscreen, will file a separate bug as this one is fixed
now.

** Changed in: unity8 (Ubuntu)
   Status: New = Fix Released

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

Title:
  Phone freezes when trying to active the dialer app from the messaging
  menu

Status in The Messaging Menu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce
  ==

  1 - Make sure that you have a missing call/voice message in your messaging 
indicator
  2 - Launch the dialer app
  3 - Lock your phone
  4 - From the lock screen open the messaging menu
  5 - Click to expand the message
  6 - Click on the icon in the top right

  Expected
  ==

  The dialer app appears with the phone pre-populated

  Current
  ===

  The phone freezes and stop to accept any input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-messages/+bug/1367916/+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 1367916] Re: Phone freezes when trying to active the dialer app from the messaging menu

2014-10-07 Thread Michał Sawicz

Filed as bug #1378218

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

Title:
  Phone freezes when trying to active the dialer app from the messaging
  menu

Status in The Messaging Menu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce
  ==

  1 - Make sure that you have a missing call/voice message in your messaging 
indicator
  2 - Launch the dialer app
  3 - Lock your phone
  4 - From the lock screen open the messaging menu
  5 - Click to expand the message
  6 - Click on the icon in the top right

  Expected
  ==

  The dialer app appears with the phone pre-populated

  Current
  ===

  The phone freezes and stop to accept any input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-messages/+bug/1367916/+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 1363015] Re: App icons require shaping at every callsite

2014-10-07 Thread Christian Dywan

Do we have some code examples? Where do app icons come from? I don't
know how consistent the path is… doing magic on arbitrary path names may
or may not make it even more confusing when the outcome changes
depending on the image.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New = Incomplete

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

Title:
App icons require shaping at every callsite

Status in “notify-osd” package in Ubuntu:
New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
Incomplete

Bug description:
In list items, showing an app icon in the correct Ubuntu shape requires
shaping it when you are using it: ListItem.Standard{IconFrame: True}.

http://developer.ubuntu.com/api/devel/ubuntu-13.04/qml/ui-toolkit/qml-ubuntu-components-listitems0-standard.html

That property is set to True by default, but it's not obvious why it
should be, and list items aren't the only place that app icons get
used.

The result is that several times now, app updates have ended up without the
appropriate frame:
- in the System Settings Updates list (bug 1354478)
- in the Notifications screen
- in the Launcher the frame is unintentionally different (bug 1332119).

Conversely, non-app icons have ended up *with* the frame by mistake:
- Display language (bug 1288866)
- Orientation Lock (bug 1365450)
- Ubuntu updates (bug 1367136).

In notification bubbles, the opposite applies -- you have to set a hint to
use an *unshaped* icon: notify_notification_set_hint_string(m_notification,
x-canonical-non-shaped-icon, true).
https://wiki.ubuntu.com/Touch/Notifications#Elements_of_a_Notification

Predictably, this has resulted in cases of icons having frames when they
shouldn't:
- Wi-Fi network authentication (bug 1346904)
- alarms (bug 1346925)
- Remove Account (bug 1350282).

On the API design quality scale, both of these are roughly Read the
implementation and you'll get it right. http://sweng.the-
davies.net/Home/rustys-api-design-manifesto Worse, they have opposite
defaults.

I suggest that the toolkit move all the way up to It's impossible to
get wrong, by always shaping an icon when it is an app icon, and
never otherwise. Whether an icon is an app icon could (I assume) be
detected by its path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1363015/+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

57 matches

Mail list logo