date:20140203

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity-greeter (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1057437

Title:
  login UI is prone to exposing password

Status in Ayatana Design:
  New
Status in “unity-greeter” package in Ubuntu:
  Confirmed

Bug description:
  The Unity login screen employs a single field that is used for both
  login name and password entry.  It's fairly easy to get confused as to
  the current mode and enter your password when login name is expected,
  thereby exposing your password to onlookers.

  Here are some scenarios leading to this confusion:

  * password re-entry (for general login) -- upon unsuccessful
  password attempt, the user might assume that only password is being
  reprompted, when actually the login name must be entered again.

  * enumerated vs. general login -- the user may typically use his
  enumerated login (where username selected and only password is typed)
  and fail to notice that general login has been selected (perhaps by
  another person tampering with the login screen).  He'll type his
  password when login name is expected.

  For security reasons the login UI needs to be very explicit about what
  fields are used for password.  Textual indicators (e.g. grayed
  Password placeholder in field) don't seem to be a distinctive enough
  cue-- my guess is people don't pay attention to login screen text
  beyond their first encounter.  A spacial separation is warranted.
  Using a single, modal field for both login and password appears
  especially error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1057437/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1057437] Re: login UI is prone to exposing password

2014-02-03 Thread Margarita Manterola

I've seen several users be affected by this (me included).  It's
particularly common for users to just expect to enter their password
because that's what they normally do, while for some unknown reason the
greeter is asking for the username instead (the enumerated vs general
case above).

This is a security issue, not only because other people watching the
screen might see the password being typed, but also because the failed
username is logged to syslog in cleartext.

Please make it much more clearer when asking username vs password.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1057437

Title:
  login UI is prone to exposing password

Status in Ayatana Design:
  New
Status in “unity-greeter” package in Ubuntu:
  Confirmed

Bug description:
  The Unity login screen employs a single field that is used for both
  login name and password entry.  It's fairly easy to get confused as to
  the current mode and enter your password when login name is expected,
  thereby exposing your password to onlookers.

  Here are some scenarios leading to this confusion:

  * password re-entry (for general login) -- upon unsuccessful
  password attempt, the user might assume that only password is being
  reprompted, when actually the login name must be entered again.

  * enumerated vs. general login -- the user may typically use his
  enumerated login (where username selected and only password is typed)
  and fail to notice that general login has been selected (perhaps by
  another person tampering with the login screen).  He'll type his
  password when login name is expected.

  For security reasons the login UI needs to be very explicit about what
  fields are used for password.  Textual indicators (e.g. grayed
  Password placeholder in field) don't seem to be a distinctive enough
  cue-- my guess is people don't pay attention to login screen text
  beyond their first encounter.  A spacial separation is warranted.
  Using a single, modal field for both login and password appears
  especially error prone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1057437/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 967229] Re: Text mode shown briefly with various cryptic texts when logging out or shutting down

2014-02-03 Thread Dimitri John Ledkov

** Changed in: plymouth (Ubuntu)
 Assignee: Steve Langasek (vorlon) = Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/967229

Title:
  Text mode shown briefly with various cryptic texts when logging out
  or shutting down

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “plymouth” package in Ubuntu:
  Triaged

Bug description:
  Text mode hits in for about a half a second every time one logs out or
  shuts down the computer. UPDATE: log out part fixed in lightdm in
  Ubuntu 13.04 -, shut down problem still there.

  The attached video Text-mode in logout and shutdown.webm is a
  combination of two clips showing this on one of my computers. This one
  has slightly more text output than my other machines, but on every
  machine it catches attention by being ugly and I'd guess cryptic or
  suspicious for ordinary people in the otherwise smooth experience
  starting from the bootup ubuntu logo.

  Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook,
  Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop
  machine. The video is from the sandy bridge one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.95-0ubuntu1
  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]
  CompositorRunning: compiz
  Date: Wed Mar 28 18:25:44 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic 
root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 
i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  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.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  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.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/967229/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272679] Re: gvfsd-trash hits assertions on (dir-monitor == NULL)

2014-02-03 Thread Martin Pitt

** Changed in: gvfs (Ubuntu)
   Status: Triaged = Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1272679

Title:
  gvfsd-trash hits assertions on (dir-monitor == NULL)

Status in GVFS:
  New
Status in “gvfs” package in Ubuntu:
  Fix Committed

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  gvfs:
Instalado: 1.19.4+git20140116-0ubuntu1
Candidato: 1.19.4+git20140116-0ubuntu1
Tabela de versão:
   *** 1.19.4+git20140116-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gvfs-daemons 1.19.4+git20140116-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Jan 25 10:59:17 2014
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2014-01-16 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131115)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 
/org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-trash crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272679] Re: gvfsd-trash hits assertions on (dir-monitor == NULL)

** Branch linked: lp:ubuntu/trusty-proposed/gvfs

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1272679

Title:
  gvfsd-trash hits assertions on (dir-monitor == NULL)

Status in GVFS:
  New
Status in “gvfs” package in Ubuntu:
  Fix Committed

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  gvfs:
Instalado: 1.19.4+git20140116-0ubuntu1
Candidato: 1.19.4+git20140116-0ubuntu1
Tabela de versão:
   *** 1.19.4+git20140116-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gvfs-daemons 1.19.4+git20140116-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Jan 25 10:59:17 2014
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2014-01-16 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131115)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 
/org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-trash crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1265239] Re: Security and Privacy in System Settings is too big

** Changed in: activity-log-manager (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: activity-log-manager (Ubuntu)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1265239

Title:
  Security and Privacy in System Settings is too big

Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  Just a minor bug here but I noticed that the Security and Privacy
  application in the System Settings is too large compared to all of the
  other system settings. This is purely a cosmetic issue but it could
  present a problem for people using a small display. I am running a
  fully up to date 14.04 x64 install.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 31 16:41:18 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-12-29 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-12-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1265239/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275540] Re: Problems with likes

2014-02-03 Thread Robert Bruce Park

Friends doesn't update the like count after initially downloading the
message, so it's not wrong, just stale.

As for the error, that just looks like a network issue to me. It sends
the like to facebook but then dbus times out waiting for the response to
come back.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to friends in Ubuntu.
https://bugs.launchpad.net/bugs/1275540

Title:
  Problems with likes

Status in “friends” package in Ubuntu:
  New

Bug description:
  The displayed like count is often wrong.  E.g. friends show 2 people
  like this when in fact 15 like it.

  Also when I try to like a post I sometimes get the following error:
  ** (process:27031): CRITICAL **: file 
/build/buildd/libfriends-0.1.2+14.04.20131108.1/src/dispatcher.vala: line 146: 
uncaught error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not 
receive a reply (timeout by message bus) (g-dbus-error-quark, 4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1275540/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1265239] Re: Security and Privacy in System Settings is too big

** Branch linked: lp:~robert-ancell/activity-log-manager/panel-width

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1265239

Title:
  Security and Privacy in System Settings is too big

Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  Just a minor bug here but I noticed that the Security and Privacy
  application in the System Settings is too large compared to all of the
  other system settings. This is purely a cosmetic issue but it could
  present a problem for people using a small display. I am running a
  fully up to date 14.04 x64 install.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 31 16:41:18 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-12-29 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-12-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1265239/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1230091] Re: [enhancement] Window reparenting (required for appstore app trust model)

2014-02-03 Thread rosa maria

** Changed in: unity-mir
 Assignee: (unassigned) = rosa maria (rprosamaria383)

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: (unassigned) = rosa maria (rprosamaria383)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1230091

Title:
  [enhancement] Window reparenting (required for appstore app trust
  model)

Status in Content sharing/picking infrastructure and service:
  New
Status in Mir:
  Triaged
Status in Unity Mir:
  Triaged
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Confirmed
Status in “signon” package in Ubuntu:
  Confirmed
Status in “unity-mir” package in Ubuntu:
  Confirmed
Status in “signon” source package in Saucy:
  Won't Fix
Status in “unity-mir” source package in Saucy:
  Won't Fix
Status in “signon” source package in Trusty:
  Confirmed
Status in “unity-mir” source package in Trusty:
  Confirmed

Bug description:
  (I'm filing this as a bug in order to be able to point other people to
  it, and to track its progress; if there's a blueprint containing this
  task, please let me know)

  Some components (such as the Online Accounts trusted helper) need to
  be able to pop-up a window (typically, a dialog) on top of the running
  application. Such windows should be modal to the application, that is
  the user should not be able to interact with the application while the
  modal window is displayed on top of them. This also means that in the
  task switcher one shouldn't see two windows, but only the topmost
  modal window (and parts of the application window, in case the modal
  window on top is a non-fullscreen dialog).

  For developers, this API already exists in Qt: see 
https://qt-project.org/doc/qt-5.1/qtgui/qwindow.html#fromWinId
  It needs to be implemented in the QPA plugin, so feel free to add the 
relevant projects to the bug report.

  From jdstrand
  This is a hard requirement for application confinement because of our trust 
model-- permission to access sensitive data by AppStore apps is typically 
granted or denied at the time of access (caching the result for later use as 
appropriate), so users have a context for the access being requested. We do 
this instead of throwing up a permissions prompt at installation. However, for 
it to work, trusted helpers like online accounts and location require this 
functionality from unity-mir. A trust-store is also being implemented so other 
services like calendar and contacts can do the same. Because this feature is 
not implemented, the implementation for online accounts, location and the 
trust-store is blocked and appstore apps are therefore able to access these 
services without the user knowing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/content-hub/+bug/1230091/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1274779] Re: [ivb] hang on pageflip (IPEHR: 0x0a000001)

2014-02-03 Thread Bruce Pieterse

Just got the same error a couple of minutes ago. I have this in my dmesg
log:

[ 5069.629929] [drm] stuck on render ring
[ 5069.629932] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 5069.629933] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[ 5069.629934] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI - DRM/Intel
[ 5069.629935] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[ 5069.629936] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[ 5069.978334] atl1c :0e:00.0: vpd r/w failed.  This is likely a firmware 
bug on this device.  Contact the card vendor for a firmware update.
[ 5070.070446] atl1c :0e:00.0: vpd r/w failed.  This is likely a firmware 
bug on this device.  Contact the card vendor for a firmware update.

dmesg and crash dump from /sys/class/drm/card0/error attached.

Out of curioristy would the constant flickering of my cursor (sometimes
hidden for few seconds before returning) be a result of this bug or
caused by something else?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1274779

Title:
  [ivb] hang on pageflip (IPEHR: 0x0a01)

Status in X.org xf86-video-intel:
  Incomplete
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  False GPU lockup  IPEHR: 0x0a01

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  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 Jan 29 23:32:19 2014
  DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: GPU lockup  IPEHR: 0x0a01 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f4]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:21f4]
  InstallationDate: Installed on 2013-05-30 (245 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 2342CTO
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor 
acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu7
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: False GPU lockup  IPEHR: 0x0a01
  UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago)
  UserGroups:
   
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET73WW (2.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2342CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2342CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Thu Jan 30 20:19:46 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load

[Desktop-packages] [Bug 1274779] Re: [ivb] hang on pageflip (IPEHR: 0x0a000001)

2014-02-03 Thread Bruce Pieterse

** Attachment added: dmesg and gpu crash log
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1274779/+attachment/3967368/+files/gpu-hang.tar.bz2

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1274779

Title:
  [ivb] hang on pageflip (IPEHR: 0x0a01)

Status in X.org xf86-video-intel:
  Incomplete
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  False GPU lockup  IPEHR: 0x0a01

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  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 Jan 29 23:32:19 2014
  DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: GPU lockup  IPEHR: 0x0a01 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f4]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:21f4]
  InstallationDate: Installed on 2013-05-30 (245 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 2342CTO
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor 
acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu7
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: False GPU lockup  IPEHR: 0x0a01
  UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago)
  UserGroups:
   
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET73WW (2.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2342CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2342CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Thu Jan 30 20:19:46 2014
  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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8510 
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1274779/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272679] Re: gvfsd-trash hits assertions on (dir-monitor == NULL)

This bug was fixed in the package gvfs - 1.19.5-0ubuntu1

---
gvfs (1.19.5-0ubuntu1) trusty; urgency=medium

  * New upstream release
  * Add 00git_fix_trash_assertion.patch: Fix race condition in gvfsd-trash
causing assertions (LP: #1272679)
 -- Martin Pitt martin.p...@ubuntu.com   Mon, 03 Feb 2014 11:08:28 +0100

** Changed in: gvfs (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1272679

Title:
  gvfsd-trash hits assertions on (dir-monitor == NULL)

Status in GVFS:
  New
Status in “gvfs” package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  gvfs:
Instalado: 1.19.4+git20140116-0ubuntu1
Candidato: 1.19.4+git20140116-0ubuntu1
Tabela de versão:
   *** 1.19.4+git20140116-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gvfs-daemons 1.19.4+git20140116-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Jan 25 10:59:17 2014
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2014-01-16 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131115)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 
/org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-trash crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272311] Re: Add support for AMD Kaveri graphics chipsets

This bug was fixed in the package fglrx-installer-experimental-13 -
2:13.300-0ubuntu0.0.1

---
fglrx-installer-experimental-13 (2:13.300-0ubuntu0.0.1) precise-proposed; 
urgency=low

  * New upstream release (LP: #1272311):
- Added support for the following products:
  AMD A10-7850K Desktop APU with AMD Radeon R7 Series graphics
  AMD A10-7700K Desktop APU with AMD Radeon R5 Series graphics
  * debian/fglrx.postinst.in:
Select the discrete card on first installation on intel+amd.
  * debian/dkms.conf.in,
debian/dkms/patches/buildfix_kernel_3.12.patch,
debian/dkms/patches/buildfix_kernel_3.13.patch:
- Add support for Linux 3.11-3.13 (LP: #1262238).
- Drop replace_old_procfs_calls.patch.
  * debian/fglrx-experimental-13.dirs.in:
- Add /usr/share/applications
  * debian/substvars:
- Add support for X ABI 14 and xserver-xorg-core-lts-saucy.
 -- Alberto Milone alberto.mil...@canonical.com   Fri, 24 Jan 2014 16:30:19 
+0100

** Changed in: fglrx-installer-experimental-13 (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1272311

Title:
  Add support for AMD Kaveri graphics chipsets

Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-pxpress” package in Ubuntu:
  In Progress
Status in “jockey” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-pxpress” source package in Precise:
  Fix Released
Status in “jockey” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  fglrx-pxpress
  jockey
  fglrx-installer-experimental-13

  [Rationale]
  This is the result of the HWE effort to enable AMD Kaveri GPUs, and systems 
with more than one AMD GPU. This will become more common now that AMD APUs can 
be combined with AMD GPUs.

  [Impact]
  Without this work, AMD Kaveri GPUs won't work properly and users won't be 
able to make use of all the AMD GPUs in their system.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single AMD card: there won't be any change except
  that Kaveri GPUs will be detected and will work properly.

  * Systems with two or more AMD GPUs: fglrx-pxpress will try to enable
  all the available AMD GPUs and will also detect and reconfigure X when
  users remove one of the cards.

  [Regression Potential]
  Low. fglrx-installer-experimental-13 is not automatically installed, and 
fglrx-pxpress is installed only when dealing with a multi GPU system. 
Furthermore the change in Jockey is minimal, and only extends what we mean by 
hybrid graphics, so as to make sure that fglrx-pxpress is installed also when 
dealing with systems with multiple AMD GPUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-13/+bug/1272311/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272311] Re: Add support for AMD Kaveri graphics chipsets

This bug was fixed in the package jockey - 0.9.7-0ubuntu7.13

---
jockey (0.9.7-0ubuntu7.13) precise-proposed; urgency=low

  * jockey/xorg_driver.py, tests/hybridgraphics.py:
- Add support for systems with two or more AMD GPUs.
  This is very useful now that AMD's APUs have been
  released (LP: #1272311).
- Adjust the tests so that they no longer fail when
  dealing with systems with multiple AMD GPUs (now
  dealt with by the fglrx-pxpress package).

jockey (0.9.7-0ubuntu7.12) precise-proposed; urgency=low

  * data/handlers/nvidia.py:
- Add support for nvidia-331 and nvidia-331-updates
  (LP: #1259237).
 -- Alberto Milone alberto.mil...@canonical.com   Fri, 24 Jan 2014 17:09:25 
+0100

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1272311

Title:
  Add support for AMD Kaveri graphics chipsets

Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-pxpress” package in Ubuntu:
  In Progress
Status in “jockey” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-pxpress” source package in Precise:
  Fix Released
Status in “jockey” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  fglrx-pxpress
  jockey
  fglrx-installer-experimental-13

  [Rationale]
  This is the result of the HWE effort to enable AMD Kaveri GPUs, and systems 
with more than one AMD GPU. This will become more common now that AMD APUs can 
be combined with AMD GPUs.

  [Impact]
  Without this work, AMD Kaveri GPUs won't work properly and users won't be 
able to make use of all the AMD GPUs in their system.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single AMD card: there won't be any change except
  that Kaveri GPUs will be detected and will work properly.

  * Systems with two or more AMD GPUs: fglrx-pxpress will try to enable
  all the available AMD GPUs and will also detect and reconfigure X when
  users remove one of the cards.

  [Regression Potential]
  Low. fglrx-installer-experimental-13 is not automatically installed, and 
fglrx-pxpress is installed only when dealing with a multi GPU system. 
Furthermore the change in Jockey is minimal, and only extends what we mean by 
hybrid graphics, so as to make sure that fglrx-pxpress is installed also when 
dealing with systems with multiple AMD GPUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-13/+bug/1272311/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1262238] Update Released

The verification of the Stable Release Update for fglrx-installer has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1262238

Title:
  [SRU] Add support for the lts-saucy stack

Status in “fglrx-installer” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-installer-updates” package in Ubuntu:
  Invalid
Status in “fglrx-installer” source package in Precise:
  Fix Released
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-installer-updates” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept fglrx and fglrx-updates into precise-proposed.

  [Rationale]
  The packages need to be compatible with the lts-saucy stack in 12.04.4.

  [Impact]
  Without this work, the packages won't build against Linux 3.11 and won't be 
installable when using the backported X stack.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * without the lts-saucy stack

  * with the lts-saucy stack installed

  [Regression Potential]
  Low. The non -updates flavour is the same driver that we shipped in Saucy. As 
for the -updates flavour, users expect to receive new drivers if they chose 
that package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1262238] Re: [SRU] Add support for the lts-saucy stack

This bug was fixed in the package fglrx-installer-experimental-13 -
2:13.300-0ubuntu0.0.1

---
fglrx-installer-experimental-13 (2:13.300-0ubuntu0.0.1) precise-proposed; 
urgency=low

  * New upstream release (LP: #1272311):
- Added support for the following products:
  AMD A10-7850K Desktop APU with AMD Radeon R7 Series graphics
  AMD A10-7700K Desktop APU with AMD Radeon R5 Series graphics
  * debian/fglrx.postinst.in:
Select the discrete card on first installation on intel+amd.
  * debian/dkms.conf.in,
debian/dkms/patches/buildfix_kernel_3.12.patch,
debian/dkms/patches/buildfix_kernel_3.13.patch:
- Add support for Linux 3.11-3.13 (LP: #1262238).
- Drop replace_old_procfs_calls.patch.
  * debian/fglrx-experimental-13.dirs.in:
- Add /usr/share/applications
  * debian/substvars:
- Add support for X ABI 14 and xserver-xorg-core-lts-saucy.
 -- Alberto Milone alberto.mil...@canonical.com   Fri, 24 Jan 2014 16:30:19 
+0100

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1262238

Title:
  [SRU] Add support for the lts-saucy stack

Status in “fglrx-installer” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-installer-updates” package in Ubuntu:
  Invalid
Status in “fglrx-installer” source package in Precise:
  Fix Released
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-installer-updates” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept fglrx and fglrx-updates into precise-proposed.

  [Rationale]
  The packages need to be compatible with the lts-saucy stack in 12.04.4.

  [Impact]
  Without this work, the packages won't build against Linux 3.11 and won't be 
installable when using the backported X stack.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * without the lts-saucy stack

  * with the lts-saucy stack installed

  [Regression Potential]
  Low. The non -updates flavour is the same driver that we shipped in Saucy. As 
for the -updates flavour, users expect to receive new drivers if they chose 
that package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272311] Update Released

The verification of the Stable Release Update for fglrx-installer-
experimental-13 has completed successfully and the package has now been
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1272311

Title:
  Add support for AMD Kaveri graphics chipsets

Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-pxpress” package in Ubuntu:
  In Progress
Status in “jockey” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-pxpress” source package in Precise:
  Fix Released
Status in “jockey” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  fglrx-pxpress
  jockey
  fglrx-installer-experimental-13

  [Rationale]
  This is the result of the HWE effort to enable AMD Kaveri GPUs, and systems 
with more than one AMD GPU. This will become more common now that AMD APUs can 
be combined with AMD GPUs.

  [Impact]
  Without this work, AMD Kaveri GPUs won't work properly and users won't be 
able to make use of all the AMD GPUs in their system.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single AMD card: there won't be any change except
  that Kaveri GPUs will be detected and will work properly.

  * Systems with two or more AMD GPUs: fglrx-pxpress will try to enable
  all the available AMD GPUs and will also detect and reconfigure X when
  users remove one of the cards.

  [Regression Potential]
  Low. fglrx-installer-experimental-13 is not automatically installed, and 
fglrx-pxpress is installed only when dealing with a multi GPU system. 
Furthermore the change in Jockey is minimal, and only extends what we mean by 
hybrid graphics, so as to make sure that fglrx-pxpress is installed also when 
dealing with systems with multiple AMD GPUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-13/+bug/1272311/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1262238] Re: [SRU] Add support for the lts-saucy stack

This bug was fixed in the package fglrx-installer -
2:13.101-0ubuntu0.0.1

---
fglrx-installer (2:13.101-0ubuntu0.0.1) precise-proposed; urgency=low

  * New upstream release:
- Add support for AMD A10, A8, A6, and A4 Series APUs.
- Add GLX_EXT_buffer_age extension support.
- Add Xserver 1.14 Support.
- [371937] Fix black screen while entering Team
  Fortress 2  under cinnamon desktop environment.
- [366812] Fix tearing for some OpenGL applications
  with VSYNC on or off.
- [373575] Fix taskbar missing after UVD playback
  on Ubuntu 12.04.
- [370955] Fix corruption in Team Fortress 2 when
  running Dustbowl map.
- [377199] Fix the error for APL initialization
  failure.
- [378086] Fix screen corruption when kill X on
  Ubuntu 13.04.
- [374657] Fix some WebGL conformance test
  failures.
- [377379] Fix the regression of performance drop
  with XBMC for UVD playback.
  * debian/substvars:
- Add support for X ABI up to 14 and xservers up to
  xserver-xorg-core-lts-saucy.
  * debian/rules:
- Sign the driver to remove the watermark.
  * debian/dkms.conf.in, buildfix_kernel_3.12.patch:
- Add support for Linux 3.12.
- Add proper support for Linux 3.11 (LP: #1262238).
 -- Alberto Milone alberto.mil...@canonical.com   Wed, 18 Dec 2013 17:50:31 
+0100

** Changed in: fglrx-installer (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1262238

Title:
  [SRU] Add support for the lts-saucy stack

Status in “fglrx-installer” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-installer-updates” package in Ubuntu:
  Invalid
Status in “fglrx-installer” source package in Precise:
  Fix Released
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-installer-updates” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept fglrx and fglrx-updates into precise-proposed.

  [Rationale]
  The packages need to be compatible with the lts-saucy stack in 12.04.4.

  [Impact]
  Without this work, the packages won't build against Linux 3.11 and won't be 
installable when using the backported X stack.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * without the lts-saucy stack

  * with the lts-saucy stack installed

  [Regression Potential]
  Low. The non -updates flavour is the same driver that we shipped in Saucy. As 
for the -updates flavour, users expect to receive new drivers if they chose 
that package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272311] Re: Add support for AMD Kaveri graphics chipsets

This bug was fixed in the package fglrx-pxpress - 0.6~hybrid0.0.1

---
fglrx-pxpress (0.6~hybrid0.0.1) precise-proposed; urgency=low

  * debian/control:
- Build only for i386 and amd64.
  * debian/amd-config.conf:
- Add upstart job to deal with configuration changes.
- Add support for AMD+AMD configurations (LP: #1272311).
  * debian/postinst.in:
- Deal with hexadecimal numbers properly.
- Do not change anything if detection fails. It is
  possible to override laptop detection by creating an
  empty file in /etc/force-pxpress.
  * debian/postrm.in:
- Remove /etc/last_boot_gfx on package removal.
 -- Alberto Milone alberto.mil...@canonical.com   Fri, 24 Jan 2014 17:22:42 
+0100

** Changed in: fglrx-pxpress (Ubuntu Precise)
   Status: Fix Committed = Fix Released

** Changed in: jockey (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1272311

Title:
  Add support for AMD Kaveri graphics chipsets

Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-pxpress” package in Ubuntu:
  In Progress
Status in “jockey” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-pxpress” source package in Precise:
  Fix Released
Status in “jockey” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  fglrx-pxpress
  jockey
  fglrx-installer-experimental-13

  [Rationale]
  This is the result of the HWE effort to enable AMD Kaveri GPUs, and systems 
with more than one AMD GPU. This will become more common now that AMD APUs can 
be combined with AMD GPUs.

  [Impact]
  Without this work, AMD Kaveri GPUs won't work properly and users won't be 
able to make use of all the AMD GPUs in their system.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single AMD card: there won't be any change except
  that Kaveri GPUs will be detected and will work properly.

  * Systems with two or more AMD GPUs: fglrx-pxpress will try to enable
  all the available AMD GPUs and will also detect and reconfigure X when
  users remove one of the cards.

  [Regression Potential]
  Low. fglrx-installer-experimental-13 is not automatically installed, and 
fglrx-pxpress is installed only when dealing with a multi GPU system. 
Furthermore the change in Jockey is minimal, and only extends what we mean by 
hybrid graphics, so as to make sure that fglrx-pxpress is installed also when 
dealing with systems with multiple AMD GPUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-13/+bug/1272311/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4

This bug was fixed in the package jockey - 0.9.7-0ubuntu7.13

---
jockey (0.9.7-0ubuntu7.13) precise-proposed; urgency=low

  * jockey/xorg_driver.py, tests/hybridgraphics.py:
- Add support for systems with two or more AMD GPUs.
  This is very useful now that AMD's APUs have been
  released (LP: #1272311).
- Adjust the tests so that they no longer fail when
  dealing with systems with multiple AMD GPUs (now
  dealt with by the fglrx-pxpress package).

jockey (0.9.7-0ubuntu7.12) precise-proposed; urgency=low

  * data/handlers/nvidia.py:
- Add support for nvidia-331 and nvidia-331-updates
  (LP: #1259237).
 -- Alberto Milone alberto.mil...@canonical.com   Fri, 24 Jan 2014 17:09:25 
+0100

** Changed in: jockey (Ubuntu)
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1259237

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  Fix Released
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Committed
Status in “screen-resolution-extra” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1051935] Re: Fails with SystemError when too many files are open

This bug was fixed in the package python-apt - 0.8.3ubuntu7.2

---
python-apt (0.8.3ubuntu7.2) precise; urgency=medium

  * Cherry-pick fixes from 0.8.8ubuntu1 to close apt.Cache and free
file-descriptors. (LP: #1051935).
  * Update list of mirrors from launchpad, using pre-build.sh hook.
 -- Dimitri John Ledkov x...@ubuntu.com   Fri, 24 Jan 2014 12:19:45 +

** Changed in: python-apt (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to oneconf in Ubuntu.
https://bugs.launchpad.net/bugs/1051935

Title:
  Fails with SystemError when too many files are open

Status in “gdebi” package in Ubuntu:
  Fix Released
Status in “oneconf” package in Ubuntu:
  Fix Released
Status in “python-apt” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Fix Released
Status in “gdebi” source package in Precise:
  Confirmed
Status in “oneconf” source package in Precise:
  Confirmed
Status in “python-apt” source package in Precise:
  Fix Released
Status in “ubiquity” source package in Precise:
  Fix Committed
Status in “gdebi” source package in Saucy:
  Fix Released
Status in “oneconf” source package in Saucy:
  Fix Released
Status in “python-apt” source package in Saucy:
  Fix Released
Status in “ubiquity” source package in Saucy:
  Won't Fix

Bug description:
  [Impact]

   * Failure to complete installation.

  [Test Case]

   * At times, apt cache can run out of file descriptors as seen in this bug 
and its duplicates.
   * There is no clear-cut way to reproduce it in ubiquity, but there is a 
significant amount of crash reports submit, which dropped off after the 
proposed fix has been applied.

  [Regression Potential]

   * The proposed fix has been well tested in trusty both automated 
  manual testing and does not regress on any configuration.

  [Other Info]

  This error occurs each time I try to install a .deb file with Gdebi in
  Ubuntu 12.10, after the deb installation finishes.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gdebi 0.8.5build1
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 17 15:33:34 2012
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120914)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive 
/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', 
'/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb']
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1051935/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1051935] Update Released

The verification of the Stable Release Update for python-apt has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to oneconf in Ubuntu.
https://bugs.launchpad.net/bugs/1051935

Title:
  Fails with SystemError when too many files are open

Status in “gdebi” package in Ubuntu:
  Fix Released
Status in “oneconf” package in Ubuntu:
  Fix Released
Status in “python-apt” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Fix Released
Status in “gdebi” source package in Precise:
  Confirmed
Status in “oneconf” source package in Precise:
  Confirmed
Status in “python-apt” source package in Precise:
  Fix Released
Status in “ubiquity” source package in Precise:
  Fix Committed
Status in “gdebi” source package in Saucy:
  Fix Released
Status in “oneconf” source package in Saucy:
  Fix Released
Status in “python-apt” source package in Saucy:
  Fix Released
Status in “ubiquity” source package in Saucy:
  Won't Fix

Bug description:
  [Impact]

   * Failure to complete installation.

  [Test Case]

   * At times, apt cache can run out of file descriptors as seen in this bug 
and its duplicates.
   * There is no clear-cut way to reproduce it in ubiquity, but there is a 
significant amount of crash reports submit, which dropped off after the 
proposed fix has been applied.

  [Regression Potential]

   * The proposed fix has been well tested in trusty both automated 
  manual testing and does not regress on any configuration.

  [Other Info]

  This error occurs each time I try to install a .deb file with Gdebi in
  Ubuntu 12.10, after the deb installation finishes.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gdebi 0.8.5build1
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 17 15:33:34 2012
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120914)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive 
/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', 
'/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb']
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1051935/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1262238] Re: [SRU] Add support for the lts-saucy stack

This bug was fixed in the package fglrx-installer-updates -
2:13.125-0ubuntu0.0.1

---
fglrx-installer-updates (2:13.125-0ubuntu0.0.1) precise-proposed; urgency=low

  * New upstream release:
- Add support for AMD A10, A8, A6, and A4 Series APUs.
- Add GLX_EXT_buffer_age extension support.
- Add Xserver 1.14 Support.
- [371937] Fix black screen while entering Team
  Fortress 2  under cinnamon desktop environment.
- [366812] Fix tearing for some OpenGL applications
  with VSYNC on or off.
- [373575] Fix taskbar missing after UVD playback
  on Ubuntu 12.04.
- [370955] Fix corruption in Team Fortress 2 when
  running Dustbowl map.
- [377199] Fix the error for APL initialization
  failure.
- [378086] Fix screen corruption when kill X on
  Ubuntu 13.04.
- [374657] Fix some WebGL conformance test
  failures.
- [377379] Fix the regression of performance drop
  with XBMC for UVD playback.
- [384861] Ultra slow dota2 fps.
- [383176] System hang when startx after enable Eyefinity.
- [383109] System hang when run Unigine Heaven 4.0.
- [382494] Screen corruption when run C4Engine with
  GL_ARB_texture_array enabled.
- [384193] Fix the procfs permission issue on kernel 3.10
  and later.
- [373812] System hang when run some OpenGL stress test.
- [383430] Glxtest failed with force AA.
- [383372] Fail to launch cairo-dock.
- [384509] glClientWaitSync is waiting even when timeout
  is 0.
- [383573] AC/DC switching is broken.
- [384194] Tear-Free Desktop sets V-Sync to 30Hz instead
  of 60Hz.
- [385123] CrossFire aspect observed in CCCLE where it
  should not.
- [385414] Steam crashes and games hang on a black screen
  when Force AA is on.
- [387027] Glxtest failed on SLED11 SP3.
- [382079] MARI crash with weird stack.
- [387797] X crash when kill X with Xserver 1.13 and 1.14.
- [389431] Screens are distorted when connecting an
  external monitor on some PowerXpress platform with Intel
  Haswell.
- [389728] Segfault after disabling display on re-launch
  of CCCLE.
- [387573] Soft hang and error observed on BasicDebug
  sample for OpenCL when run on x86.
- [385704] Black window when run glxgears with TWM.
- [376115] Display corruption when using rotation.
  * debian/control:
- Add transitional packages for experimental flavours 9, 12,
  and 13.
  * debian/substvars:
- Add support for X ABI 14 and xserver-xorg-core-lts-saucy.
  * debian/dkms.conf.in, buildfix_kernel_3.12.patch:
- Add support for Linux 3.12.
- Add proper support for Linux 3.11 (LP: #1262238).
  * debian/dkms/patches/replace_acpi_table_handler.patch:
- Fix build issues with Linux = 3.9.1 (only required
  by driver 13.125).
 -- Alberto Milone alberto.mil...@canonical.com   Fri, 20 Dec 2013 12:45:08 
+0100

** Changed in: fglrx-installer-updates (Ubuntu Precise)
   Status: Fix Committed = Fix Released

** Changed in: fglrx-installer-experimental-13 (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1262238

Title:
  [SRU] Add support for the lts-saucy stack

Status in “fglrx-installer” package in Ubuntu:
  Invalid
Status in “fglrx-installer-experimental-13” package in Ubuntu:
  Invalid
Status in “fglrx-installer-updates” package in Ubuntu:
  Invalid
Status in “fglrx-installer” source package in Precise:
  Fix Released
Status in “fglrx-installer-experimental-13” source package in Precise:
  Fix Released
Status in “fglrx-installer-updates” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept fglrx and fglrx-updates into precise-proposed.

  [Rationale]
  The packages need to be compatible with the lts-saucy stack in 12.04.4.

  [Impact]
  Without this work, the packages won't build against Linux 3.11 and won't be 
installable when using the backported X stack.

  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * without the lts-saucy stack

  * with the lts-saucy stack installed

  [Regression Potential]
  Low. The non -updates flavour is the same driver that we shipped in Saucy. As 
for the -updates flavour, users expect to receive new drivers if they chose 
that package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1259237

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  Fix Released
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Committed
Status in “screen-resolution-extra” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 952401] Re: Shutting the lid interrupts laptop suspend

2014-02-03 Thread Christopher M. Penalver

Bryan Eastin, you need to ensure xdiagnose is installed and you hit Yes
for additional debugging attachments.

** Tags removed: apport-collected

** Description changed:

  When I select Turn off the screen as the action to be performed when
  my laptop lid is closed I get the following behavior:  If I direct the
  computer to suspend (sleep) and then close lid of the laptop before it's
  finished going to sleep then the suspend process never completes.  I
  think the laptop ought to go to sleep regardless of how quickly I close
  the lid.
  
  I believe this issue is related to the bugs reported at
  https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/859178 and
  https://bugs.launchpad.net/hundredpapercuts/+bug/387553, though I was
  unable to reproduce these bugs.  (It is presumably also related to the
  fact that when I had Sleep selected as the action to be performed when
  my laptop lid was closed putting the laptop to sleep and then closing
  the lid too fast would result in two suspends.  That is, the laptop
  would suspend, but when I woke it it, it would suspend a second time.)
  
  This is not a pressing issue for me since I have discovered that
  selecting Do nothing as the action to be performed when my laptop lid
  is closed results in the correct behavior and turning my screen off when
  the lid is closed but the computer is still on is not a huge priority.
  Nevertheless, it would be nice to fix this.
  
  WORKAROUND: Wait until suspend initiated via command line or GUI to
  finish before closing the lid.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7.1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Mar 11 11:15:38 2012
  InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
- ApportVersion: 2.0.1-0ubuntu17.6
- Architecture: amd64
- DistroRelease: Ubuntu 12.10
- InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
- MarkForUpload: True
- Package: xorg 1:7.6+12ubuntu2
- PackageArchitecture: amd64
- ProcEnviron:
-  LANGUAGE=
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
- Tags:  quantal
- Uname: Linux 3.2.0-58-generic x86_64
- UpgradeStatus: Upgraded to quantal on 2014-01-30 (4 days ago)
- UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/952401/+attachment/3966975/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/952401

Title:
  Shutting the lid interrupts laptop suspend

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  When I select Turn off the screen as the action to be performed when
  my laptop lid is closed I get the following behavior:  If I direct the
  computer to suspend (sleep) and then close lid of the laptop before
  it's finished going to sleep then the suspend process never completes.
  I think the laptop ought to go to sleep regardless of how quickly I
  close the lid.

  I believe this issue is related to the bugs reported at
  https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/859178 and
  https://bugs.launchpad.net/hundredpapercuts/+bug/387553, though I was
  unable to reproduce these bugs.  (It is presumably also related to the
  fact that when I had Sleep selected as the action to be performed
  when my laptop lid was closed putting the laptop to sleep and then
  closing the lid too fast would result in two suspends.  That is, the
  laptop would suspend, but when I woke it it, it would suspend a second
  time.)

  This is not a pressing issue for me since I have discovered that
  selecting Do nothing as the action to be performed when my laptop
  lid is closed results in the correct behavior and turning my screen
  off when the lid is closed but the computer is still on is not a huge
  priority.  Nevertheless, it would be nice to fix this.

  WORKAROUND: Wait until suspend initiated via command line or GUI to
  finish before closing the lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7.1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Mar 11 11:15:38 2012
  InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To

[Desktop-packages] [Bug 1275703] [NEW] unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main()

2014-02-03 Thread Till Kamppeter

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-greeter 14.04.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
Date: Mon Feb  3 11:57:23 2014
ExecutablePath: /usr/sbin/unity-greeter
InstallationDate: Installed on 2013-06-05 (242 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
ProcCmdline: /usr/sbin/unity-greeter
Signal: 5
SourcePackage: unity-greeter
StacktraceTop:
 atspi_dbus_connection_setup_with_g_main () from 
/usr/lib/x86_64-linux-gnu/libatspi.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 ?? () 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: unity-greeter crashed with signal 5 in 
atspi_dbus_connection_setup_with_g_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace third-party-packages trusty

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1275703

Title:
  unity-greeter crashed with signal 5 in
  atspi_dbus_connection_setup_with_g_main()

Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-greeter 14.04.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Mon Feb  3 11:57:23 2014
  ExecutablePath: /usr/sbin/unity-greeter
  InstallationDate: Installed on 2013-06-05 (242 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
  ProcCmdline: /usr/sbin/unity-greeter
  Signal: 5
  SourcePackage: unity-greeter
  StacktraceTop:
   atspi_dbus_connection_setup_with_g_main () from 
/usr/lib/x86_64-linux-gnu/libatspi.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
   ?? () 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: unity-greeter crashed with signal 5 in 
atspi_dbus_connection_setup_with_g_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1275703/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1054081] Update Released

The verification of the Stable Release Update for libsoup2.4 has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1054081

Title:
  gvfsd-http crashed with signal 5 in g_cancellable_make_pollfd()

Status in GVFS:
  Invalid
Status in “gvfs” package in Ubuntu:
  Invalid
Status in “libsoup2.4” package in Ubuntu:
  Fix Released
Status in “gvfs” source package in Saucy:
  New
Status in “libsoup2.4” source package in Saucy:
  Fix Released

Bug description:
  * Impact: gvfs leaks fds which leads to segfault and issues with the
  unity Dash

  * Test case:
  - use the unity dash and look at the number of fds in use
  or
  - watch if reports on 
https://errors.ubuntu.com/problem/16193ad82fb29994e9821e3bd67933b10b5aa15e 
reduce/stop with the update

  * Regression potential:
  check that http browsing in nautilus/gvfs keeps working correctly (Unity dash 
uses it to display the icon for remote content, e.g music or videos)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1274779] Re: [ivb] hang on pageflip (IPEHR: 0x0a000001)

2014-02-03 Thread Chris Wilson

It is unlikely to explain the cursor flicker - the hang here is quite
rare. But a regular GPU hang could produce the symptoms you describe if
the hang coincided with the cursor being hidden itself by software (the
command to show the cursor will then need to wait for the hangcheck to
be detected in some extreme case). Given that it requires a combination
of unlikely situations, I doubt it actually explains the cursor
flickering (and if it was a constant hang, the kernel will declare the
hardware as wedged).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1274779

Title:
  [ivb] hang on pageflip (IPEHR: 0x0a01)

Status in X.org xf86-video-intel:
  Incomplete
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  False GPU lockup  IPEHR: 0x0a01

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  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 Jan 29 23:32:19 2014
  DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: GPU lockup  IPEHR: 0x0a01 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f4]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:21f4]
  InstallationDate: Installed on 2013-05-30 (245 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 2342CTO
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor 
acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu7
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: False GPU lockup  IPEHR: 0x0a01
  UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago)
  UserGroups:
   
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET73WW (2.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2342CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2342CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Thu Jan 30 20:19:46 2014
  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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8510 
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1274779/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   :

[Desktop-packages] [Bug 1054081] Re: gvfsd-http crashed with signal 5 in g_cancellable_make_pollfd()

This bug was fixed in the package libsoup2.4 - 2.42.3.1-0ubuntu1

---
libsoup2.4 (2.42.3.1-0ubuntu1) saucy; urgency=low

  * New upstream bug fix version, fixes some hangs and ld leaks issues,
that should resolve the issues where gvfsd-http ends up segfaulting
(which happens often with the Unith dash) (lp: #1054081)
 -- Sebastien Bacher seb...@ubuntu.com   Fri, 15 Nov 2013 13:16:49 +0100

** Changed in: libsoup2.4 (Ubuntu Saucy)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1054081

Title:
  gvfsd-http crashed with signal 5 in g_cancellable_make_pollfd()

Status in GVFS:
  Invalid
Status in “gvfs” package in Ubuntu:
  Invalid
Status in “libsoup2.4” package in Ubuntu:
  Fix Released
Status in “gvfs” source package in Saucy:
  New
Status in “libsoup2.4” source package in Saucy:
  Fix Released

Bug description:
  * Impact: gvfs leaks fds which leads to segfault and issues with the
  unity Dash

  * Test case:
  - use the unity dash and look at the number of fds in use
  or
  - watch if reports on 
https://errors.ubuntu.com/problem/16193ad82fb29994e9821e3bd67933b10b5aa15e 
reduce/stop with the update

  * Regression potential:
  check that http browsing in nautilus/gvfs keeps working correctly (Unity dash 
uses it to display the icon for remote content, e.g music or videos)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275223] Re: nvidia-settings seems to need python-gtk2 when using nvidia-prime

2014-02-03 Thread Alberto Milone

** Also affects: screen-resolution-extra (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: screen-resolution-extra (Ubuntu)
   Status: New = Triaged

** Changed in: screen-resolution-extra (Ubuntu)
   Importance: Undecided = Medium

** Changed in: screen-resolution-extra (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: nvidia-settings (Ubuntu)
   Status: Triaged = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to screen-resolution-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1275223

Title:
  nvidia-settings seems to need python-gtk2 when using nvidia-prime

Status in “nvidia-settings” package in Ubuntu:
  Invalid
Status in “screen-resolution-extra” package in Ubuntu:
  Triaged

Bug description:
  Hello,

  On a fresh and updated install of Kubuntu 14.04 LTS (developpement
  version) with yesterday's CD image on a computer which has nVidia
  Optimus, I installed the nvidia proprietary driver with the jockey-kde
  graphical user interface. It did install nvidia-settings. However,
  when trying to switch between graphic cards with the Prime settings
  from the nvidia-settings interface, it printed a Traceback relative to
  some gtk dependency missing. Installing the python-gtk2 package solved
  the problem.

  Maybe python-gtk2 should be a dependency of nvidia-xsettings?

  Cheers,
  Raphaël.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1275223/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272321] Re: Network Manager should only request new secrets during the initial connection for wired interfaces

2014-02-03 Thread Mathieu Trudel-Lapierre

I haven't forgotten about this, just having some issues with the build
for armhf, tests aren't passing...

This makes me think however, isn't that going to break the case where
the secrets expire for the wired connection? What happens if you need to
change to a different password, either because it is an 802.1x network
secured with RADIUS, say with an RSA Securid token.

That would affect wifi too, of course...

I'm only saying this to keep a trace somewhere, since it's already
upstream it would be a matter of filing a bug if there is ever a major
issue caused by these changes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1272321

Title:
  Network Manager should only request new secrets during the initial
  connection for wired interfaces

Status in “network-manager” package in Ubuntu:
  In Progress

Bug description:
  Hi everyone,

  Network Manager received a patch so that it only requests new secrets during 
the initial connection for WiFi connections in 2012:
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=30fe3e18766367d159dfb16d7ca5559d7dc58b9a

  This patch has been ported for wired connections:
  https://bugzilla.gnome.org/show_bug.cgi?id=720265
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6b5d31954fa655b47a9928f61d34ca74f92a953e

  Can we include the upstream patch for wired connections in Trusty?
  (The patch for WiFi connections is already present)

  Best,

  Michael Schaller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1272321/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275347] Re: Facebook replies have invalid url

2014-02-03 Thread Robert Bruce Park

Please find the offending message with tools/debug_slave.py and show me
the raw contents of 'message' field.

Is it all facebook replies or just one?

I seem to recall there was some confusion about this URL at the time
this was implemented (eg, facebook wasn't giving it to us so I was
trying to construct the URL based on the ID alone). entirely possible
that I got it wrong, or that they changed it since I wrote it.

At any rate if it's a reply message, it should link to the parent
message that was replied to, probably. shouldn't be hard to fix if you
give me some more details.

** Changed in: friends (Ubuntu)
   Status: New = Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to friends in Ubuntu.
https://bugs.launchpad.net/bugs/1275347

Title:
  Facebook replies have invalid url

Status in “friends” package in Ubuntu:
  Incomplete

Bug description:
  When I click them I just end up on a white page. Maybe just set the
  url to the empty string?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1275347/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1207812] Re: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu

2014-02-03 Thread John Flores

I can confirm that libimobiledevice4_1.1.6-git20140105_amd64.deb fixes
the issue in my Xubuntu 13.10 64-bit.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libimobiledevice in Ubuntu.
https://bugs.launchpad.net/bugs/1207812

Title:
  [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu

Status in “libimobiledevice” package in Ubuntu:
  Incomplete

Bug description:
  -*Please read this first before making a comment*-
  If you think you are affected by this bug, and in order to ensure all the the 
different devices are indeed fix, please file a new report with your USB device 
plugged in via a terminal:
  ubuntu-bug linux

  Please do not make a Me too! comment as this is not helpful, and
  just spamming everyone subscribed to this report. Thank you.

  When plugging in an iPhone with iOS 7 - Currently BETA 4 I receive the 
following message on Ubuntu 13.04 :
  The Device Nick's iPhone is locked. Enter the passcode on the device and 
click Try again.

  The iPhone reporting Trust the currently connected computer? Trust/Don't 
Trust.
  This then happens in a continous loop when clicking Trust.

  ---
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nrawlins   2068 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb
  InstallationDate: Installed on 2013-08-15 (3 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Sony Corporation VGN-SR29XN_S
  MarkForUpload: True
  Package: linux 3.8.0.27.45
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1130Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR29XN_S
  dmi.product.version: C6017UKK
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1274779] Re: [ivb] hang on pageflip (IPEHR: 0x0a000001)

2014-02-03 Thread Bruce Pieterse

This is the first time I've had this hang, and it might have been
introduced by the 3.13.0-6-generic kernel which I upgraded to today.
When the gpu hang occurred my mouse cursor was hidden for about five
seconds.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1274779

Title:
  [ivb] hang on pageflip (IPEHR: 0x0a01)

Status in X.org xf86-video-intel:
  Incomplete
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  False GPU lockup  IPEHR: 0x0a01

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu2
  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 Jan 29 23:32:19 2014
  DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: GPU lockup  IPEHR: 0x0a01 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f4]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:21f4]
  InstallationDate: Installed on 2013-05-30 (245 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 2342CTO
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic 
root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor 
acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu7
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: False GPU lockup  IPEHR: 0x0a01
  UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago)
  UserGroups:
   
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET73WW (2.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2342CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2342CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Thu Jan 30 20:19:46 2014
  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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8510 
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1274779/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1264611] Re: package nvidia-prime not installed failed to install/upgrade: subprocess installed post-removal script returned error exit status 127

This bug was fixed in the package nvidia-prime - 0.5~hybrid0.0.2

---
nvidia-prime (0.5~hybrid0.0.2) precise-proposed; urgency=low

  * debian/control:
- Add alternative dependency on gdm and kdm.
  * debian/preinst.in:
- Set the lightdm configuration bits only if lightdm is the
  default display manager (LP: #1262068).
  * debian/postrm.in, debian/rules:
- Avoid calling dpkg-architecture (LP: #1264611).
  * prime-xconfig:
- Format hexadecimal parameters properly (LP: #1252667).

nvidia-prime (0.5~hybrid0.0.1) precise-proposed; urgency=low

  * New upstream release:
- Add support for power management (LP: #1259237).
  * debian/control:
- Depend on upstart, bbswitch, lsb-release, lightdm = 1.2.3-0ubuntu2.4,
  screen-resolution-extra (= 0.14ubuntu2.1).
- Build only for i386 and amd64.
 -- Alberto Milone alberto.mil...@canonical.com   Mon, 13 Jan 2014 16:32:47 
+0100

** Changed in: nvidia-prime (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1264611

Title:
  package nvidia-prime  not installed  failed to install/upgrade:
  subprocess installed post-removal script returned error exit status
  127

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  Hi, I want to do 
  apt-get purge nvidia-prime and failed in ubuntu12.04 ,so I have to reinstall 
it 
  now this problem ocurred...

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Fri Dec 27 11:39:48 2013
  DuplicateSignature: package:nvidia-prime:(not installed):subprocess installed 
post-removal script returned error exit status 127
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 127
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 
(20130820.1)
  MarkForUpload: True
  SourcePackage: nvidia-prime
  Title: package nvidia-prime (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1264611/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1264611] Update Released

The verification of the Stable Release Update for nvidia-prime has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1264611

Title:
  package nvidia-prime  not installed  failed to install/upgrade:
  subprocess installed post-removal script returned error exit status
  127

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  Hi, I want to do 
  apt-get purge nvidia-prime and failed in ubuntu12.04 ,so I have to reinstall 
it 
  now this problem ocurred...

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Fri Dec 27 11:39:48 2013
  DuplicateSignature: package:nvidia-prime:(not installed):subprocess installed 
post-removal script returned error exit status 127
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 127
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 
(20130820.1)
  MarkForUpload: True
  SourcePackage: nvidia-prime
  Title: package nvidia-prime (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1264611/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1262068] Re: nvidia-prime should support gdm also

This bug was fixed in the package nvidia-prime - 0.5~hybrid0.0.2

---
nvidia-prime (0.5~hybrid0.0.2) precise-proposed; urgency=low

  * debian/control:
- Add alternative dependency on gdm and kdm.
  * debian/preinst.in:
- Set the lightdm configuration bits only if lightdm is the
  default display manager (LP: #1262068).
  * debian/postrm.in, debian/rules:
- Avoid calling dpkg-architecture (LP: #1264611).
  * prime-xconfig:
- Format hexadecimal parameters properly (LP: #1252667).

nvidia-prime (0.5~hybrid0.0.1) precise-proposed; urgency=low

  * New upstream release:
- Add support for power management (LP: #1259237).
  * debian/control:
- Depend on upstart, bbswitch, lsb-release, lightdm = 1.2.3-0ubuntu2.4,
  screen-resolution-extra (= 0.14ubuntu2.1).
- Build only for i386 and amd64.
 -- Alberto Milone alberto.mil...@canonical.com   Mon, 13 Jan 2014 16:32:47 
+0100

** Changed in: nvidia-prime (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1262068

Title:
  nvidia-prime should support gdm also

Status in Ubuntu GNOME:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  On Ubuntu GNOME we ship gdm by default, however nvidia-prime depends
  on lightdm. This means that

  1. Anyone installing nvidia binary drivers will pull in nvidia-prime and 
subsequently lightdm. As a consequence of this they are also going to get the 
potentially confusing dconf pop-up asking them to choose a DM.
  2. nvidia-prime probably won't work when using gdm

  I haven't looked to closely at how deeply integrated this is with
  lightdm, however we particularly don't want #1 happening, and it would
  be nice if #2 worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 18 16:56:19 2013
  InstallationDate: Installed on 2012-09-23 (451 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1262068/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4

This bug was fixed in the package nvidia-prime - 0.5~hybrid0.0.2

---
nvidia-prime (0.5~hybrid0.0.2) precise-proposed; urgency=low

  * debian/control:
- Add alternative dependency on gdm and kdm.
  * debian/preinst.in:
- Set the lightdm configuration bits only if lightdm is the
  default display manager (LP: #1262068).
  * debian/postrm.in, debian/rules:
- Avoid calling dpkg-architecture (LP: #1264611).
  * prime-xconfig:
- Format hexadecimal parameters properly (LP: #1252667).

nvidia-prime (0.5~hybrid0.0.1) precise-proposed; urgency=low

  * New upstream release:
- Add support for power management (LP: #1259237).
  * debian/control:
- Depend on upstart, bbswitch, lsb-release, lightdm = 1.2.3-0ubuntu2.4,
  screen-resolution-extra (= 0.14ubuntu2.1).
- Build only for i386 and amd64.
 -- Alberto Milone alberto.mil...@canonical.com   Mon, 13 Jan 2014 16:32:47 
+0100

** Changed in: nvidia-prime (Ubuntu Precise)
   Status: Fix Committed = Fix Released

** Changed in: lightdm (Ubuntu)
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1259237

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  Fix Released
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released
Status in “screen-resolution-extra” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4

This bug was fixed in the package lightdm - 1.2.3-0ubuntu2.4

---
lightdm (1.2.3-0ubuntu2.4) precise-proposed; urgency=low

  [ Robert Ancell ]
  * debian/patches/06_config_directory.patch:
- Backport conf.d configuration support (LP: #1190425)

  [ Alberto Milone ]
  * debian/patches/07_add_display-stopped-script.patch:
- Backport support for the display-stopped-script entry
  in the configuration file (LP: #1259237)
 -- Alberto Milone alberto.mil...@canonical.com   Wed, 18 Dec 2013 14:31:49 
+0100

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1259237

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  Fix Released
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released
Status in “screen-resolution-extra” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1262068] Update Released

The verification of the Stable Release Update for nvidia-prime has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1262068

Title:
  nvidia-prime should support gdm also

Status in Ubuntu GNOME:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  On Ubuntu GNOME we ship gdm by default, however nvidia-prime depends
  on lightdm. This means that

  1. Anyone installing nvidia binary drivers will pull in nvidia-prime and 
subsequently lightdm. As a consequence of this they are also going to get the 
potentially confusing dconf pop-up asking them to choose a DM.
  2. nvidia-prime probably won't work when using gdm

  I haven't looked to closely at how deeply integrated this is with
  lightdm, however we particularly don't want #1 happening, and it would
  be nice if #2 worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 18 16:56:19 2013
  InstallationDate: Installed on 2012-09-23 (451 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1262068/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1190425] Re: lightdm should allow packages to override defaults in /etc/lightdm/lightdm.conf

This bug was fixed in the package lightdm - 1.2.3-0ubuntu2.4

---
lightdm (1.2.3-0ubuntu2.4) precise-proposed; urgency=low

  [ Robert Ancell ]
  * debian/patches/06_config_directory.patch:
- Backport conf.d configuration support (LP: #1190425)

  [ Alberto Milone ]
  * debian/patches/07_add_display-stopped-script.patch:
- Backport support for the display-stopped-script entry
  in the configuration file (LP: #1259237)
 -- Alberto Milone alberto.mil...@canonical.com   Wed, 18 Dec 2013 14:31:49 
+0100

** Changed in: lightdm (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190425

Title:
  lightdm should allow packages to override defaults in
  /etc/lightdm/lightdm.conf

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.6 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Precise:
  Fix Released

Bug description:
  [Impact]
The /etc/lightdm/lightdm.conf file is a conffile, which means that packages 
are not allowed to modify it. 

As a result, if any package is modifying /etc/lightdm/lightdm.conf
  on installation to set 'greeter-show-manual-login=true', will cause
  users of this package to have conffile prompts on future upgrades.

  It would be helpful if lightdm had some supported mechanism for
  packages to override the defaults in /etc/lightdm/lightdm.conf - such
  as an /etc/lightdm/lightdm.conf.d directory .

  [Test Case]
* Create autologin file, as shown below. This will fail on precise, but 
work fine on saucy/trusty.

$ cat  /etc/lightdm/lightdm.conf.d/10-ubuntu.conf
[SeatDefaults]
autologin-user=ubuntu-or-any-other-user-on-system

  [Regression Potential]
* none that I could see, and is backport from upstream

  [Other Info]
* Has been tested, and works.
* Merge https://code.launchpad.net/~lightdm-team/lightdm/1.2 against precise

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1252667] Update Released

The verification of the Stable Release Update for nvidia-prime has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1252667

Title:
  package nvidia-prime 0.4.2~ubuntu13.10.1 failed to install/upgrade: le
  sous-processus script post-installation installé a retourné une erreur
  de sortie d'état 1

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  internet

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-prime 0.4.2~ubuntu13.10.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov 19 10:15:42 2013
  DuplicateSignature: package:nvidia-prime:0.4.2~ubuntu13.10.1:le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2013-08-17 (93 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  Title: package nvidia-prime 0.4.2~ubuntu13.10.1 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to saucy on 2013-09-26 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1252667/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1252667] Re: package nvidia-prime 0.4.2~ubuntu13.10.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

This bug was fixed in the package nvidia-prime - 0.5~hybrid0.0.2

---
nvidia-prime (0.5~hybrid0.0.2) precise-proposed; urgency=low

  * debian/control:
- Add alternative dependency on gdm and kdm.
  * debian/preinst.in:
- Set the lightdm configuration bits only if lightdm is the
  default display manager (LP: #1262068).
  * debian/postrm.in, debian/rules:
- Avoid calling dpkg-architecture (LP: #1264611).
  * prime-xconfig:
- Format hexadecimal parameters properly (LP: #1252667).

nvidia-prime (0.5~hybrid0.0.1) precise-proposed; urgency=low

  * New upstream release:
- Add support for power management (LP: #1259237).
  * debian/control:
- Depend on upstart, bbswitch, lsb-release, lightdm = 1.2.3-0ubuntu2.4,
  screen-resolution-extra (= 0.14ubuntu2.1).
- Build only for i386 and amd64.
 -- Alberto Milone alberto.mil...@canonical.com   Mon, 13 Jan 2014 16:32:47 
+0100

** Changed in: nvidia-prime (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1252667

Title:
  package nvidia-prime 0.4.2~ubuntu13.10.1 failed to install/upgrade: le
  sous-processus script post-installation installé a retourné une erreur
  de sortie d'état 1

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  internet

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: nvidia-prime 0.4.2~ubuntu13.10.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov 19 10:15:42 2013
  DuplicateSignature: package:nvidia-prime:0.4.2~ubuntu13.10.1:le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2013-08-17 (93 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  Title: package nvidia-prime 0.4.2~ubuntu13.10.1 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to saucy on 2013-09-26 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1252667/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1051935] Re: Fails with SystemError when too many files are open

This bug was fixed in the package ubiquity - 2.10.29

---
ubiquity (2.10.29) precise; urgency=low

  [ Dimitri John Ledkov ]
  * Show labels in automatic side-by-side installation. Fixed by removing
all cairo styling from partition boxes in automatic partitioning,
instead use simple bg styling. (LP: #947107, #1240532)
  * Automatic update of included source packages: grub-installer
1.68ubuntu5.3.

  [ Brian Murray ]
  * Use the apt cache with with so that we close the cache when we are done
with it. (LP: #1051935)

  [ Hao-Ran Liu (Joseph Liu) ]
  * src/wallpaper/wallpaper.c: Cropping wallpaper image instead of
stretching it if image's aspect ratio doesn't match monitor's aspect
ratio (LP: #1207249)

  [ Colin Watson ]
  * Update translations from Launchpad.
 -- Dimitri John Ledkov x...@ubuntu.com   Wed, 22 Jan 2014 14:35:56 +

** Changed in: ubiquity (Ubuntu Precise)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to oneconf in Ubuntu.
https://bugs.launchpad.net/bugs/1051935

Title:
  Fails with SystemError when too many files are open

Status in “gdebi” package in Ubuntu:
  Fix Released
Status in “oneconf” package in Ubuntu:
  Fix Released
Status in “python-apt” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Fix Released
Status in “gdebi” source package in Precise:
  Confirmed
Status in “oneconf” source package in Precise:
  Confirmed
Status in “python-apt” source package in Precise:
  Fix Released
Status in “ubiquity” source package in Precise:
  Fix Released
Status in “gdebi” source package in Saucy:
  Fix Released
Status in “oneconf” source package in Saucy:
  Fix Released
Status in “python-apt” source package in Saucy:
  Fix Released
Status in “ubiquity” source package in Saucy:
  Won't Fix

Bug description:
  [Impact]

   * Failure to complete installation.

  [Test Case]

   * At times, apt cache can run out of file descriptors as seen in this bug 
and its duplicates.
   * There is no clear-cut way to reproduce it in ubiquity, but there is a 
significant amount of crash reports submit, which dropped off after the 
proposed fix has been applied.

  [Regression Potential]

   * The proposed fix has been well tested in trusty both automated 
  manual testing and does not regress on any configuration.

  [Other Info]

  This error occurs each time I try to install a .deb file with Gdebi in
  Ubuntu 12.10, after the deb installation finishes.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gdebi 0.8.5build1
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 17 15:33:34 2012
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120914)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive 
/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', 
'/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb']
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1051935/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1190425] Update Released

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190425

Title:
  lightdm should allow packages to override defaults in
  /etc/lightdm/lightdm.conf

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.6 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Precise:
  Fix Released

Bug description:
  [Impact]
The /etc/lightdm/lightdm.conf file is a conffile, which means that packages 
are not allowed to modify it. 

As a result, if any package is modifying /etc/lightdm/lightdm.conf
  on installation to set 'greeter-show-manual-login=true', will cause
  users of this package to have conffile prompts on future upgrades.

  It would be helpful if lightdm had some supported mechanism for
  packages to override the defaults in /etc/lightdm/lightdm.conf - such
  as an /etc/lightdm/lightdm.conf.d directory .

  [Test Case]
* Create autologin file, as shown below. This will fail on precise, but 
work fine on saucy/trusty.

$ cat  /etc/lightdm/lightdm.conf.d/10-ubuntu.conf
[SeatDefaults]
autologin-user=ubuntu-or-any-other-user-on-system

  [Regression Potential]
* none that I could see, and is backport from upstream

  [Other Info]
* Has been tested, and works.
* Merge https://code.launchpad.net/~lightdm-team/lightdm/1.2 against precise

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272653] Re: software-center uses first installed version of ubuntu for partner repository after upgrade

2014-02-03 Thread Matthew Paul Thomas

** Package changed: software-center (Ubuntu) = software-properties
(Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1272653

Title:
  software-center uses first installed version of ubuntu for partner
  repository  after upgrade

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  After upgrading from raring to saucy using do-release-upgrade and then
  enabling partner repository in software-center GUI,
  /etc/apt/sources.list has:

  deb http://archive.canonical.com/ubuntu raring partner

  Manually editing sources.list changing to saucy fixes this.

  $ apt-cache policy software-center
  software-center:
Installed: 13.10-0ubuntu1
Candidate: 13.10-0ubuntu1
Version table:
   *** 13.10-0ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Also seen on a computer that had been upgraded oneiric - precise - quantal 
- raring - saucy,  sources.list still had oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1272653/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1265239] Re: Security and Privacy in System Settings is too big

This bug was fixed in the package activity-log-manager - 0.9.7-0ubuntu8

---
activity-log-manager (0.9.7-0ubuntu8) trusty; urgency=medium

  * debian/patches/06_panel_width.patch:
  * debian/patches/03_use_libwhoopsie-preferences.patch:
- Stop control center panel from expanding too wide (LP: #1265239)
 -- Robert Ancell robert.anc...@canonical.com   Mon, 03 Feb 2014 10:46:11 
+

** Branch linked: lp:ubuntu/trusty-proposed/activity-log-manager

** Changed in: activity-log-manager (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1265239

Title:
  Security and Privacy in System Settings is too big

Status in “activity-log-manager” package in Ubuntu:
  Fix Released

Bug description:
  Just a minor bug here but I noticed that the Security and Privacy
  application in the System Settings is too large compared to all of the
  other system settings. This is purely a cosmetic issue but it could
  present a problem for people using a small display. I am running a
  fully up to date 14.04 x64 install.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 31 16:41:18 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-12-29 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-12-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1265239/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4

** Branch linked: lp:ubuntu/precise-updates/lightdm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1259237

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  Fix Released
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released
Status in “screen-resolution-extra” source package in Precise:
  Fix Released

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1190425] Re: lightdm should allow packages to override defaults in /etc/lightdm/lightdm.conf

** Branch linked: lp:ubuntu/precise-updates/lightdm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190425

Title:
  lightdm should allow packages to override defaults in
  /etc/lightdm/lightdm.conf

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.6 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Precise:
  Fix Released

Bug description:
  [Impact]
The /etc/lightdm/lightdm.conf file is a conffile, which means that packages 
are not allowed to modify it. 

As a result, if any package is modifying /etc/lightdm/lightdm.conf
  on installation to set 'greeter-show-manual-login=true', will cause
  users of this package to have conffile prompts on future upgrades.

  It would be helpful if lightdm had some supported mechanism for
  packages to override the defaults in /etc/lightdm/lightdm.conf - such
  as an /etc/lightdm/lightdm.conf.d directory .

  [Test Case]
* Create autologin file, as shown below. This will fail on precise, but 
work fine on saucy/trusty.

$ cat  /etc/lightdm/lightdm.conf.d/10-ubuntu.conf
[SeatDefaults]
autologin-user=ubuntu-or-any-other-user-on-system

  [Regression Potential]
* none that I could see, and is backport from upstream

  [Other Info]
* Has been tested, and works.
* Merge https://code.launchpad.net/~lightdm-team/lightdm/1.2 against precise

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272321] Re: Network Manager should only request new secrets during the initial connection for wired interfaces

2014-02-03 Thread Michael Schaller

Mathieu, that is an excellent question that Dan Williams covered in his commit 
for WiFi connections:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=30fe3e18766367d159dfb16d7ca5559d7dc58b9a
Otherwise we assume the secrets good; if they aren't, the user should change 
them through a configuration editor.

Looking at the Network Manager code itself it doesn't have much choice
as currently it doesn't get any error information from WPA supplicant.
In fact the way how Network Manager handles WPA supplicant errors is not
good at all. Basically Network Manager gives WPA supplicant 25 seconds
to finish the authentication. Without these two patches Network Manager
just assumes on timeout that the secret was bad and asks repeatedly to
correct the secret. But this behavior is frustrating for the users as
there are of course a lot more issues than just a bad secret that can
cause WPA supplicant to fail... These two commits change the behavior so
that Network Manager only asks to correct the secret if the connection
wasn't successful so far. I personally think that the new behavior is
still not good but at least it is a bit better than the previous
behavior.

IMHO to fix this issue one would need to change WPA supplicant to
properly export errors via its D-Bus interface and then Network Manager
needs to be changed to react properly depending on the actual WPA
supplicant error.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1272321

Title:
  Network Manager should only request new secrets during the initial
  connection for wired interfaces

Status in “network-manager” package in Ubuntu:
  In Progress

Bug description:
  Hi everyone,

  Network Manager received a patch so that it only requests new secrets during 
the initial connection for WiFi connections in 2012:
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=30fe3e18766367d159dfb16d7ca5559d7dc58b9a

  This patch has been ported for wired connections:
  https://bugzilla.gnome.org/show_bug.cgi?id=720265
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6b5d31954fa655b47a9928f61d34ca74f92a953e

  Can we include the upstream patch for wired connections in Trusty?
  (The patch for WiFi connections is already present)

  Best,

  Michael Schaller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1272321/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 944919] Re: repeate feature not working and incorrect playing status of song after that

2014-02-03 Thread Bug Watch Updater

** Changed in: banshee
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/944919

Title:
  repeate feature not working and incorrect playing status of song after
  that

Status in Banshee Music Player:
  Confirmed
Status in “banshee” package in Ubuntu:
  Triaged

Bug description:
  Repeate feature not works like infinite repeate in case of repeate all
  and shuffle mode.

  How to reproduce:
  The mode is shuffle by song and repeate all.
  Press next as much times, the playback will stop.
  Now select a song (single click)
  Now play another song. The selected song will start playing.
  But status of selected becomes playing.

  @next song the status The indication on the playlist becomes correct.
  But infinite repeate still doesn't work.It'll stop playback after pressing 
Next key number of times...

  The play status depends i think on next song.
  The attachment contain screenshots.
  The Trumpets song is played by double clicking but Thé à la menthe is seen as 
being played.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: banshee 2.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Fri Mar  2 21:17:15 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: Upgraded to oneiric on 2011-12-20 (73 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275726] [NEW] [gen4 sna] Font corruption

2014-02-03 Thread Joseph Maillardet

*** This bug is a duplicate of bug 1098334 ***
https://bugs.launchpad.net/bugs/1098334

Public bug reported:

I noticed that graphical glitches appeared in the letters on many
application (Firefox, Empathy, Evolution, ...). Sometime letter
completly disappear. I regulary need to select the text to be able to
read it.

I'm using Ubuntu-Gnome with ppa:gnome3-team/gnome3 PPA.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Feb  3 13:51:05 2014
DistUpgraded: 2013-11-08 15:12:12,947 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:024f]
   Subsystem: Dell Device [1028:024f]
InstallationDate: Installed on 2012-05-11 (632 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MachineType: Dell Inc. Latitude E6500
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=cba25369-7dc1-452f-9e21-7917e844f5ba ro quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to saucy on 2013-11-08 (86 days ago)
dmi.bios.date: 12/06/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A27
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd12/06/2011:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Mon Feb  3 11:40:00 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17015 
 vendor AUO
xserver.version: 2:1.14.5-1ubuntu2~saucy1

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug gnome3-ppa saucy third-party-packages ubuntu

** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu)

** This bug has been marked a duplicate of bug 1098334
   [gen4 sna] Font corruption

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1275726

Title:
  [gen4 sna] Font corruption

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  I noticed that graphical glitches appeared in the letters on many
  application (Firefox, Empathy, Evolution, ...). Sometime letter
  completly disappear. I regulary need to select the text to be able to
  read it.

  I'm using Ubuntu-Gnome with ppa:gnome3-team/gnome3 PPA.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  3 13:51:05 2014
  DistUpgraded: 2013-11-08 15:12:12,947 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:024f]
 Subsystem: Dell Device [1028:024f]
  InstallationDate: Installed on 2012-05-11 (632 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: Dell Inc. Latitude E6500
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1275727] [NEW] [ENH] Add pt-BR spell grammar check as full package

2014-02-03 Thread Olivier Hallot

Public bug reported:

As for English, Hungarian and Russian, add Brazilian Portuguese package
for grammar and spell checks in Ubuntu/Debian.

For en, hu, and ru, there ase the packages:

libreoffice-lightproof-en
libreoffice-lightproof-hu
libreoffice-lightproof-ru-ru

I am asking to add
libreoffice-lightproof-pt-BR

This will avoid many user question on where is the grammar and spell
checker of pt-BR in my linux?.

Source code is in

dictionary/pt-BR/

Information on the spell check and grammar chek of LibreOffice for pt-BR
are in (but in portuguese)

http://pt-br.libreoffice.org/projetos/projeto-vero-verificador-
ortografico/

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1275727

Title:
  [ENH] Add pt-BR spell  grammar check as full package

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  As for English, Hungarian and Russian, add Brazilian Portuguese
  package for grammar and spell checks in Ubuntu/Debian.

  For en, hu, and ru, there ase the packages:

  libreoffice-lightproof-en
  libreoffice-lightproof-hu
  libreoffice-lightproof-ru-ru

  I am asking to add
  libreoffice-lightproof-pt-BR

  This will avoid many user question on where is the grammar and spell
  checker of pt-BR in my linux?.

  Source code is in

  dictionary/pt-BR/

  Information on the spell check and grammar chek of LibreOffice for pt-
  BR are in (but in portuguese)

  http://pt-br.libreoffice.org/projetos/projeto-vero-verificador-
  ortografico/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1275727/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275736] [NEW] /usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

2014-02-03 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding activity-log-manager.  This problem was most recently seen
with version 0.9.7-0ubuntu7, the problem page at
https://errors.ubuntu.com/problem/4df7a9bed6c62438921a131ef7b0794e15f00f73
contains more details.

** Affects: activity-log-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1275736

Title:
  /usr/bin/gnome-control-
  
center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding activity-log-manager.  This problem was most recently seen
  with version 0.9.7-0ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/4df7a9bed6c62438921a131ef7b0794e15f00f73
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1275736/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275736] Re: /usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

** Changed in: activity-log-manager (Ubuntu)
 Assignee: (unassigned) = Robert Ancell (robert-ancell)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1275736

Title:
  /usr/bin/gnome-control-
  
center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding activity-log-manager.  This problem was most recently seen
  with version 0.9.7-0ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/4df7a9bed6c62438921a131ef7b0794e15f00f73
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1275736/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275736] Re: /usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

To reproduce:
1. Open GNOME control center
2. Select Security and Privacy
3. Select All Settings
4. Select Security and Privacy
5. Select Diagnostics
6. Select Send error reports to Canonical

Observed result:
- Crash

Expected result:
- Checkbox is toggled

Crash is due to the DBus proxy object from the time the panel is created
in step 2 being accessed after it was destroyed due to the configuration
change.

** Changed in: activity-log-manager (Ubuntu)
Status: New = Triaged

** Changed in: activity-log-manager (Ubuntu)
Importance: Undecided = Medium

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1275736

Title:
/usr/bin/gnome-control-

center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

Status in “activity-log-manager” package in Ubuntu:
Triaged

Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding activity-log-manager. This problem was most recently seen
with version 0.9.7-0ubuntu7, the problem page at
https://errors.ubuntu.com/problem/4df7a9bed6c62438921a131ef7b0794e15f00f73
contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1275736/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275736] Re: /usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

** Branch linked: lp:~robert-ancell/activity-log-manager/proxy-unref

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1275736

Title:
  /usr/bin/gnome-control-
  
center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding activity-log-manager.  This problem was most recently seen
  with version 0.9.7-0ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/4df7a9bed6c62438921a131ef7b0794e15f00f73
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1275736/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 998001] Re: Have to confirm certificate on every connection

2014-02-03 Thread Garami Gábor

I think it would be better if remmina should provide an option something
Don't ask anymore. This would be more user-friendly than writing some
howto. Importing certificates is something what programs can
automatically do without any user interaction except confirmation.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/998001

Title:
  Have to confirm certificate on every connection

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  Every time I connect to a server it asks me to confirm the fingerprint
  of the certificate is correct. Whilst being quite useless as humans
  generally can't read hexadecimal very well, I suppose I could cross
  reference it the first time I connect. The fingerprint should be saved
  and the user should not be bothered on repeat connections.

  This is a security issue because it is impractical for the user to
  check the fingerprint every time they connect, especially considering
  how easy it would be for Remmina to cache. This dialog will simply be
  ignored and encourage the user to blindly accept every dialog they
  see, defeating the point of it to begin with.

  Ubuntu 12.04 32-bit / 0.9.99.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/998001/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275736] Re: /usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

** Branch linked: lp:ubuntu/trusty-proposed/activity-log-manager

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1275736

Title:
  /usr/bin/gnome-control-
  
center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding activity-log-manager.  This problem was most recently seen
  with version 0.9.7-0ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/4df7a9bed6c62438921a131ef7b0794e15f00f73
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1275736/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1175479] Re: Using PAC file does not set http_proxy env variable

2014-02-03 Thread Domen Puncer

Chromium uses auto_proxy variable with .pac URL. Maybe some other
application also follows the same scheme.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1175479

Title:
  Using PAC file does not set http_proxy env variable

Status in “libproxy” package in Ubuntu:
  New

Bug description:
  I have a moderately complicated (66 line) PAC file, configured in the
  Network Settings applet using the automatic method with a HTTP URL.
  I've seen the same/similar behaviour on previous versions of Ubuntu.

  This doesn't set the http_proxy environment variable, so I am unable
  to access the internet as all applications try to connect directly.
  I'm attaching an obfuscated version of the PAC file, and I'm keen to
  help debug this issue.

  I've worked around the problem to gain internet access by setting the
  proxy manually, but this doesn't set up the exceptions specified by
  the PAC.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libproxy1 0.4.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 07:55:08 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-04-27 (369 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  MarkForUpload: True
  SourcePackage: libproxy
  UpgradeStatus: Upgraded to raring on 2013-04-26 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1175479/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275760] [NEW] low graphics mode due to possible race condition on precise

2014-02-03 Thread Gordon Ball

Public bug reported:

Precise 12.04.4 x86_64, kernel 3.2.0-58-generic.

lspci reports:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev 
a1)

dpkg -l 'nvidia*' | grep '^ii' reports:
ii  nvidia-304 304.116-0ubuntu0.0.1
ii  nvidia-319-updates 331.20-0ubuntu0.0.1
ii  nvidia-331-updates 331.20-0ubuntu0.0.1
ii  nvidia-common  1:0.2.44.2
ii  nvidia-current 304.116-0ubuntu0.0.1
ii  nvidia-settings331.20-0ubuntu0.0.1
ii  nvidia-settings-304331.20-0ubuntu0.0.1
ii  nvidia-settings-319-updates331.20-0ubuntu0.0.1

ii xorg 1:7.6+12ubuntu2

Since installation, this system has periodically fallen to the running
in low graphics mode prompt on boot. This can always be resolved by
logging into a TTY and restarting LightDM: sudo service lightdm restart.
Recently (sorry I can't say precisely - probably the last month or so)
the frequency of this event has increased to ~90% of boots.

Sample Xorg.0.log attached, but the key lines appear to be
[ 3.364] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. 
Please see the
[ 3.364] (EE) NVIDIA(0): system's kernel log for additional error 
messages and
[ 3.364] (EE) NVIDIA(0): consult the NVIDIA README for details.
[ 3.364] (EE) NVIDIA(0):  *** Aborting ***

While `dmesg | grep nvidia` shows
[2.737764] nvidia: module license 'NVIDIA' taints kernel.
[3.658332] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[3.658338] nvidia :01:00.0: setting latency timer to 64

From the timestamps, it looks like Xorg attempts to load the nvidia
drivers 300ms before the kernel has actually loaded/initialised them,
and hence fails. This certainly looks like a race condition. By the time
I log into a TTY, lsmod shows the `nvidia` module to be loaded and
restarting lightdm succeeds.

Is there any way for either Xorg to check and if necessary wait for
kernel module loading, or the low graphics dialog at least include a
better option for dealing with this situation?

** Affects: nvidia-graphics-drivers (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: Xorg.0.log
   https://bugs.launchpad.net/bugs/1275760/+attachment/3967555/+files/Xorg.0.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1275760

Title:
  low graphics mode due to possible race condition on precise

Status in “nvidia-graphics-drivers” package in Ubuntu:
  New

Bug description:
  Precise 12.04.4 x86_64, kernel 3.2.0-58-generic.

  lspci reports:
  01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] 
(rev a1)

  dpkg -l 'nvidia*' | grep '^ii' reports:
  ii  nvidia-304 304.116-0ubuntu0.0.1
  ii  nvidia-319-updates 331.20-0ubuntu0.0.1
  ii  nvidia-331-updates 331.20-0ubuntu0.0.1
  ii  nvidia-common  1:0.2.44.2
  ii  nvidia-current 304.116-0ubuntu0.0.1
  ii  nvidia-settings331.20-0ubuntu0.0.1
  ii  nvidia-settings-304331.20-0ubuntu0.0.1
  ii  nvidia-settings-319-updates331.20-0ubuntu0.0.1

  ii xorg 1:7.6+12ubuntu2

  Since installation, this system has periodically fallen to the
  running in low graphics mode prompt on boot. This can always be
  resolved by logging into a TTY and restarting LightDM: sudo service
  lightdm restart. Recently (sorry I can't say precisely - probably the
  last month or so) the frequency of this event has increased to ~90% of
  boots.

  Sample Xorg.0.log attached, but the key lines appear to be
  [ 3.364] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. 
Please see the
  [ 3.364] (EE) NVIDIA(0): system's kernel log for additional error 
messages and
  [ 3.364] (EE) NVIDIA(0): consult the NVIDIA README for details.
  [ 3.364] (EE) NVIDIA(0):  *** Aborting ***

  While `dmesg | grep nvidia` shows
  [2.737764] nvidia: module license 'NVIDIA' taints kernel.
  [3.658332] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
  [3.658338] nvidia :01:00.0: setting latency timer to 64

  From the timestamps, it looks like Xorg attempts to load the nvidia
  drivers 300ms before the kernel has actually loaded/initialised them,
  and hence fails. This certainly looks like a race condition. By the
  time I log into a TTY, lsmod shows the `nvidia` module to be loaded
  and restarting lightdm succeeds.

  Is there any way for either Xorg to check and if necessary wait for
  kernel module

[Desktop-packages] [Bug 1274613] Re: module-bluetooth-discover does not load on login

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pulseaudio (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1274613

Title:
  module-bluetooth-discover does not load on login

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  The following lines appear in /etc/pulse/default.pa, which I have not
  modified:

  .ifexists module-bluetooth-discover.so
  load-module module-bluetooth-discover
  .endif

  Expected: module-bluetooth-discover is loaded on login, as configured.

  Observed: pulseaudio's module-bluetooth-discover does not load on
  login. My system does not detect and set up sinks when I connect to
  Bluetooth devices (including an A2DP speaker and a headset).

  If I issue, in a terminal window:

  $ pactl load-module module-bluetooth-discover 
  24

  …then the devices are detected and sinks set up correctly.

  $ lsb_release -rd  apt-cache policy pulseaudio-module-bluetooth
  Description:Ubuntu 13.10
  Release:13.10
  pulseaudio-module-bluetooth:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
   *** 1:4.0-0ubuntu6 0
  500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  khaeru 2051 F pulseaudio
  Date: Thu Jan 30 12:18:50 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-10-29 (457 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago)
  dmi.bios.date: 05/15/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 085VR5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1275736] Re: /usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

This bug was fixed in the package activity-log-manager - 0.9.7-0ubuntu9

---
activity-log-manager (0.9.7-0ubuntu9) trusty; urgency=medium

  * debian/patches/07_proxy_unref.patch:
- Fix crash opening and closing security panel (LP: #1275736)
 -- Robert Ancell robert.anc...@canonical.com   Mon, 03 Feb 2014 13:46:50 
+

** Changed in: activity-log-manager (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1275736

Title:
  /usr/bin/gnome-control-
  
center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

Status in “activity-log-manager” package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding activity-log-manager.  This problem was most recently seen
  with version 0.9.7-0ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/4df7a9bed6c62438921a131ef7b0794e15f00f73
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1275736/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1223506] Re: gnome-control-center crashed with SIGSEGV in on_properties_changed()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1223506

Title:
  gnome-control-center crashed with SIGSEGV in on_properties_changed()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  saucy 13.10
  kernel 3.11.0.6

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
  Uname: Linux 3.11.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  Date: Tue Sep 10 20:06:42 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-01-09 (243 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0xa64634ef:mov0x0(%ebp),%eax
   PC (0xa64634ef) ok
   source 0x0(%ebp) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   ?? () from 
/usr/lib/i386-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to saucy on 2013-02-15 (207 days ago)
  UserGroups: audio fuse lp netdev plugdev sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1223506/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1225434] Re: gnome-control-center crashed with SIGSEGV in on_properties_changed()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1225434

Title:
  gnome-control-center crashed with SIGSEGV in on_properties_changed()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  While navigating system settings, system settings window greyed, then
  closed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic i686
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  Date: Sat Sep 14 16:11:03 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-01-02 (254 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121228)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0xa6a7d4ef:mov0x0(%ebp),%eax
   PC (0xa6a7d4ef) ok
   source 0x0(%ebp) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   ?? () from 
/usr/lib/i386-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to saucy on 2013-07-27 (49 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1225434/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1215422] Re: gnome-control-center crashed with SIGSEGV in on_properties_changed()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1215422

Title:
  gnome-control-center crashed with SIGSEGV in on_properties_changed()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  automatic report

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  Date: Thu Aug 22 09:52:57 2013
  ExecutablePath: /usr/bin/gnome-control-center
  MarkForUpload: True
  ProcCmdline: gnome-control-center region layouts
  SegvAnalysis:
   Segfault happened at: 0xabaf54ef:mov0x0(%ebp),%eax
   PC (0xabaf54ef) ok
   source 0x0(%ebp) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   ?? () from 
/usr/lib/i386-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to saucy on 2013-07-12 (40 days ago)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo vboxusers 
video www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1215422/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1218517] Re: gnome-control-center crashed with SIGSEGV in on_properties_changed()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1218517

Title:
  gnome-control-center crashed with SIGSEGV in on_properties_changed()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  automatic report

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  Date: Thu Aug 22 09:52:57 2013
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1377103397
  MarkForUpload: True
  ProcCmdline: gnome-control-center region layouts
  ProcCwd: /home/phoenix
  SegvAnalysis:
   Segfault happened at: 0xabaf54ef:mov0x0(%ebp),%eax
   PC (0xabaf54ef) ok
   source 0x0(%ebp) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   ?? () from 
/usr/lib/i386-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to saucy on 2013-07-12 (40 days ago)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo vboxusers 
video www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1218517/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1223842] Re: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** This bug is no longer a duplicate of bug 1223506
   gnome-control-center crashed with SIGSEGV in on_properties_changed()
** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1223842

Title:
  gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  ubuntu 13.10
  3.11.0.6

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
  Uname: Linux 3.11.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  Date: Tue Sep 10 20:06:42 2013
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1378742723
  InstallationDate: Installed on 2013-01-09 (243 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcCwd: /home/patricia
  SegvAnalysis:
   Segfault happened at: 0xa64634ef:mov0x0(%ebp),%eax
   PC (0xa64634ef) ok
   source 0x0(%ebp) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   ?? () from 
/usr/lib/i386-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to saucy on 2013-02-15 (207 days ago)
  UserGroups: audio fuse lp netdev plugdev sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1223842/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1229130] Re: gnome-control-center crashed with SIGSEGV in g_param_spec_object@plt()

** Information type changed from Private to Public

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1229130/+attachment/3836194/+files/CoreDump.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1229130

Title:
  gnome-control-center crashed with SIGSEGV in g_param_spec_object@plt()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  Just clicked on the privacy icon in gnome-control-center.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 23 12:22:50 2013
  Disassembly: = 0x40: Cannot access memory at address 0x40
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-02-16 (218 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x40:  Cannot access memory at address 0x40
   PC (0x0040) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_param_spec_object@plt ()
   ?? ()
  Title: gnome-control-center crashed with SIGSEGV in g_param_spec_object@plt()
  UpgradeStatus: Upgraded to saucy on 2013-09-19 (3 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin monetdb plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1229130/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1198546] Re: remote-content-search preference should be binary not string

** Changed in: activity-log-manager (Ubuntu)
   Importance: Undecided = Wishlist

** Changed in: activity-log-manager (Ubuntu)
   Status: New = Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1198546

Title:
  remote-content-search preference should be binary not string

Status in Privacy Manager for Zeitgeist:
  New
Status in Unity:
  Triaged
Status in Unity Tweak Tool:
  Triaged
Status in “activity-log-manager” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  New
Status in “unity-tweak-tool” package in Ubuntu:
  Triaged

Bug description:
  The gsettings com.canonical.Unity.Lenses remote-content-search has
  only two valid values: 'none' and 'all'.

  Please replace this with a binary setting instead as this is easier
  for tweak tools to implement and makes more sense for someone working
  with dconf-editor/gsettings manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jul  6 17:27:34 2013
  InstallationDate: Installed on 2013-06-14 (22 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/activity-log-manager/+bug/1198546/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1198724] Re: Don't show Presentations Spreadsheets in Include list

** Changed in: activity-log-manager (Ubuntu)
   Status: New = Triaged

** Changed in: activity-log-manager (Ubuntu)
   Importance: Undecided = Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1198724

Title:
  Don't show Presentations  Spreadsheets in Include list

Status in Privacy Manager for Zeitgeist:
  New
Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  Instead of showing separate toggles for Documents, Presentations, and
  Spreadsheets in the Include list, let's just show Documents and have
  that toggle also control Presentations  Spreadsheets.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Sun Jul  7 16:18:04 2013
  InstallationDate: Installed on 2013-06-14 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: activity-log-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/activity-log-manager/+bug/1198724/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1199605] Re: Only show apps that log to zg in Exclude Application chooser

** Changed in: activity-log-manager (Ubuntu)
   Status: New = Triaged

** Changed in: activity-log-manager (Ubuntu)
   Importance: Undecided = Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1199605

Title:
  Only show apps that log to zg in Exclude Application chooser

Status in Privacy Manager for Zeitgeist:
  New
Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  The Exclude Application chooser appears to include all .desktop's including 
many that don't make sense like:
  - Python v2.7
  - Network Connections
  - Compiz
  - GNOME Shell Classic
  - View File
  - Window Manager

  I think it would be better for users to only have relevant apps show
  up in this list.

  GNOME 3.8 has a new Notifications panel in Settings that allows users
  to customize GNOME Shell notifications. Apps show up there either
  because they've explicitly opted in (see
  https://wiki.gnome.org/GnomeGoals/NotificationSource ) or because
  they've shown at least one notification.

  Zeitgeist could do something similar. Show apps in this list once one
  event has been logged from the app. And also make a way for app
  developers to signal to zg that they log to zg even before they have
  logged one event.

To manage notifications about this bug go to:
https://bugs.launchpad.net/activity-log-manager/+bug/1199605/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1222325] Re: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** This bug is no longer a duplicate of bug 1221192
   gnome-control-center crashed with SIGSEGV in 
gtk_builder_set_translation_domain()
** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1222325

Title:
  gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  rajanikanth@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  rajanikanth@ubuntu:~$ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:3.6.3-0ubuntu33
Candidate: 1:3.6.3-0ubuntu33
Version table:
   *** 1:3.6.3-0ubuntu33 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  Tried to edit privacy settings when this issue occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 00:07:18 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-08 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130907)
  MarkForUpload: True
  ProcCmdline: gnome-control-center activity-log-manager
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f1ac72785b6 gtk_builder_get_object+22:mov
(%rbx),%rdx
   PC (0x7f1ac72785b6) ok
   source (%rbx) (0x0004) not located in a known VMA region (needed 
readable region)!
   destination %rdx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
  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/activity-log-manager/+bug/1222325/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1226812] Re: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1226812

Title:
  gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

Status in “activity-log-manager” package in Ubuntu:
  Confirmed

Bug description:
  Unbuntu 13.10. Was in system settings in the network settings. Clicked
  on Wired Network after program opened in Wireless showing local
  wireless networks and program locked up and initiated bug report.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep 17 15:15:10 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-08 (9 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130729)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f3302888496 gtk_builder_get_object+22:mov
(%rbx),%rdx
   PC (0x7f3302888496) ok
   source (%rbx) (0x0004) not located in a known VMA region (needed 
readable region)!
   destination %rdx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
  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/activity-log-manager/+bug/1226812/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1198554] Re: Allow enabling/disabling Unity scopes from Privacy Settings

** Changed in: activity-log-manager (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: activity-log-manager (Ubuntu)
   Importance: Undecided = Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1198554

Title:
  Allow enabling/disabling Unity scopes from Privacy Settings

Status in Privacy Manager for Zeitgeist:
  Confirmed
Status in Unity Applications Lens:
  New
Status in “activity-log-manager” package in Ubuntu:
  Triaged

Bug description:
  The include online search results toggle in Privacy Settings is only
  a partial solution to the customizability people want from Unity's
  online searches.

  Unity 7.1, as part of the 100 Scopes initiative, adds many more scopes and 
allows for scopes to be individually disabled without installing them. The 
UI/UX for this is pretty bad though.
  1. Open the Dash
  2. Switch to the Applications lens
  3. Click Filter Results
  4. Select Search plugins
  5. Select the scope you want to disable and click Disable

  A better way for discoverability and usability is to have the Privacy
  Settings' Search tab include the list of installed scopes with an
  on/off toggle switch next to them.

  The list of scopes can be found by recurisvely searching
  XDG_DATA_DIRS/unity/scopes/*.scope. If a scope is in a subdirectory,
  replace the / with a hyphen (for instance graphics/colourlovers.scope
  should be graphics-colourlovers.scope).

  A .scope is a modified .desktop so display the Name and Icon listed.
  If an icon isn't listed, you can fall back to displaying
  /usr/share/icons/unity-icon-theme/places/svg/service-generic.svg .

  To disable a scope, add its name to gsettings
  com.canonical.Unity.Lenses disabled-scopes.

  Optionally, you can extend the basic enabling/disabling interface to
  allow choosing which scopes should always be searched and which should
  show up by default in the Home lens.

  Also optionally, remove the Search plugins feature from unity-lens-
  applications.

  See also the final mockup on
  https://wiki.ubuntu.com/SecurityAndPrivacySettings for a proposed
  Ubuntu mobile version of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Sat Jul  6 18:04:49 2013
  InstallationDate: Installed on 2013-06-14 (22 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: activity-log-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/activity-log-manager/+bug/1198554/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1247360] Re: setxkbmap set incorrect layer for swedish and alt-intl keyboards

2014-02-03 Thread Gustavo Barreto

Hello to all!

I've found the possibile problem causa by accident, when applying this patch to 
ubuntu 13.10:
https://launchpad.net/~timekiller/+archive/unity-systrayfix

Ubuntu 13.10 are using two different keyboard layout configurations, the ibus 
and the gnome keyboard, and as it looks both of the are active.
But you cannot see the ibus icon on top, as it has been disabled...
---
If you appy the patch above, you will see another keyboard icon, that leads to 
ibus configuration, that (in my case) were different from the gnome keyboard, 
as the english keyboard was before us alt-int.
---
MY SOLUTION

-open a terminal
-open ibus configuration using the command: ibus-setup
- Configure your keyboard layout.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-xkb-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1247360

Title:
  setxkbmap set incorrect layer for swedish and alt-intl keyboards

Status in “x11-xkb-utils” package in Ubuntu:
  Confirmed

Bug description:
  For my work and for real life I write a lot in English, Italian and 
Portuguese so on all my system desktop (Lubuntu 13.04), netbook and notebook 
(Lubuntu 13.10), I set my keyboard to US alternative international.
  What I expect pressing the key  '  followed by  c  from the keyboard is  
the special char  ç  (ALT code 135) but on 13.10 it
  read it as a  ć , when on 13.04 is working as expected.
  I tried to configure it with the new keyboard layout Handler applet and with 
the old-but-good Lxkeymap but Lubuntu simply seems to ignore the existence of 
that character. The rest of the keyboard is working fine. This char is really 
important for Portuguese so it's a big issue. I tried with a standard Ubuntu 
13.04/13.10 live, same behavior.

  Another user on Lubuntu mailing list reported the same issue wih swedish 
keyboard:
  2013/11/2 Nio Wiklund @:
  I can confirm this behaviour also with Swedish keyboard

  Examples

  Acute accent + c  prints ç in 12.04.3 but ć in 13.10
  Acute accent + e  prints é in 12.04.3 and 13.10

  When I log in from a Lubuntu 13.10 client via ssh to a Xubuntu 12.04.3
  ssh server, I get the 13.10 behaviour, so it seems connected to the
  keyboard setting rather than interpreting the ascii code.

  --

  Note that entering a TTY the keyboard do not change at all. It's stuck
  on US keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: x11-xkb-utils 7.7~1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sat Nov  2 08:24:59 2013
  InstallationDate: Installed on 2013-10-30 (3 days ago)
  InstallationMedia:
   
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xkb-utils/+bug/1247360/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1221267] Re: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** This bug is no longer a duplicate of bug 1221192
   gnome-control-center crashed with SIGSEGV in 
gtk_builder_set_translation_domain()
** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1221267

Title:
  gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  I was relogging after installing KVM to include myself as user, then
  when logged back in USC, Chromium, crashed along with this error. I
  had other crash reports come up for the others and a third which I
  can't recall, tried logging into launchpad for each, lol, and found I
  can only log in a single time, sorry for that, so I am just reporting
  this crash. Hope it helps.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Thu Sep  5 08:13:30 2013
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1377794895
  InstallationDate: Installed on 2013-09-05 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130904)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcCwd: /home/james
  SegvAnalysis:
   Segfault happened at: 0x7fbceeddb5b6 gtk_builder_get_object+22:mov
(%rbx),%rdx
   PC (0x7fbceeddb5b6) ok
   source (%rbx) (0x0004) not located in a known VMA region (needed 
readable region)!
   destination %rdx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
  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/activity-log-manager/+bug/1221267/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1274728] Re: System Settings window reopens on close [XPS 13 Haswell]

** Changed in: activity-log-manager (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1274728

Title:
  System Settings window reopens on close [XPS 13 Haswell]

Status in “activity-log-manager” package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  When the 'security  privacy' icon is clicked, it highlights but no
  window opens. The system settings window will re-open when closed
  repeatedly and steals focus from other windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu50
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan 30 22:07:31 2014
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2014-01-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140130)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1274728/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1222485] Re: gnome-control-center crashed with SIGSEGV in gtk_builder_set_translation_domain()

*** This bug is a duplicate of bug 1275736 ***
https://bugs.launchpad.net/bugs/1275736

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1275736
   
/usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to activity-log-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1222485

Title:
  gnome-control-center crashed with SIGSEGV in
  gtk_builder_set_translation_domain()

Status in “activity-log-manager” package in Ubuntu:
  New

Bug description:
  I'm click Control Center and click update

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: activity-log-manager 0.9.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 21:34:10 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-08 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130908)
  MarkForUpload: True
  ProcCmdline: gnome-control-center region layouts
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANGUAGE=ru
   LANG=ru_RU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1986a685b6 gtk_builder_get_object+22:mov
(%rbx),%rdx
   PC (0x7f1986a685b6) ok
   source (%rbx) (0x0004) not located in a known VMA region (needed 
readable region)!
   destination %rdx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: activity-log-manager
  StacktraceTop:
   gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
  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/activity-log-manager/+bug/1222485/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1221192] Re: gnome-control-center crashed with SIGSEGV in gtk_builder_set_translation_domain()