[Dx-packages] [Bug 1542782] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()

2016-05-15 Thread Apport retracing service 
** Tags added: yakkety

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

Title:
  unity-scope-loader crashed with SIGSEGV in
  g_desktop_app_info_get_is_hidden()

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  I do not know, this error was made in a background.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  7 08:36:54 2016
  ExecutablePath: /usr/bin/unity-scope-loader
  InstallationDate: Installed on 2016-02-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope 
applications/scopes.scope commands.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=ru
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f7fbb1b3300 : 
movzbl 0xc0(%rdi),%eax
   PC (0x7f7fbb1b3300) ok
   source "0xc0(%rdi)" (0x00c0) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   g_desktop_app_info_get_is_hidden () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   gmenu_tree_load_sync () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so
  Title: unity-scope-loader crashed with SIGSEGV in 
g_desktop_app_info_get_is_hidden()
  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/libunity/+bug/1542782/+subscriptions

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

[Dx-packages] [Bug 1582059] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()

2016-05-15 Thread Apport retracing service 
*** This bug is a duplicate of bug 1542782 ***
https://bugs.launchpad.net/bugs/1542782

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1542782, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1582059/+attachment/4663591/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1582059/+attachment/4663593/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1582059/+attachment/4663595/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1582059/+attachment/4663596/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1582059/+attachment/4663597/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1582059/+attachment/4663598/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1582059/+attachment/4663599/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1542782
   unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-scope-loader crashed with SIGSEGV in
  g_desktop_app_info_get_is_hidden()

Status in libunity package in Ubuntu:
  New

Bug description:
  atualizaçao

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: libunity9 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 15 23:39:12 2016
  ExecutablePath: /usr/bin/unity-scope-loader
  InstallationDate: Installed on 2016-05-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope 
applications/scopes.scope commands.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fafef965340 : 
movzbl 0xc0(%rdi),%eax
   PC (0x7fafef965340) ok
   source "0xc0(%rdi)" (0x00c0) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   g_desktop_app_info_get_is_hidden () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   gmenu_tree_load_sync () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so
  Title: unity-scope-loader crashed with SIGSEGV in 
g_desktop_app_info_get_is_hidden()
  UpgradeStatus: Upgraded to yakkety on 2016-05-16 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1562822] Re: Bluetooth Browse Files... not working

2016-05-15 Thread Kent Lin 
** Changed in: oem-priority
   Status: Won't Fix => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1562822

Title:
  Bluetooth Browse Files... not working

Status in OEM Priority Project:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  * Impact
  The bluetooth settings include a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open settings->bluetooth, the only 
action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --

  Mobile phone: LG L40 Android 4.4.2

  1. Connecting to Phone is successful shown.
  2. Click on Button  "Browse Files... " nothing happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 13:31:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-02-04 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1582049] Re: Accountsservice fails to update user info

2016-05-15 Thread Gunnar Hjalmarsson 
*** This bug is a duplicate of bug 1581567 ***
https://bugs.launchpad.net/bugs/1581567

A corrected accountsservice version is available in xenial-proposed.

** This bug has been marked a duplicate of bug 1581567
   SRU regression, can't change own data

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

Title:
  Accountsservice fails to update user info

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Accountsservice version 0.6.40-2ubuntu11 fails to update user info of
  the file /var/lib/AccountsService/users/, for example
  changing your wallpaper doesn't update the image of Lightdm since it
  reads the path from this file. Workaround is downgrading both
  Accounsservice and Libaccountsservice0 to the previous version.

  sudo apt install accountsservice=0.6.40-2ubuntu10
  libaccountsservice0=0.6.40-2ubuntu10

  To prevent the packages from being updates to the broken version:

  sudo apt-mark hold accountsservice libaccountsservice0

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

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

[Dx-packages] [Bug 1582049] [NEW] Accountsservice fails to update user info

2016-05-15 Thread Sebastian Perez 
Public bug reported:

Accountsservice version 0.6.40-2ubuntu11 fails to update user info of
the file /var/lib/AccountsService/users/, for example changing
your wallpaper doesn't update the image of Lightdm since it reads the
path from this file. Workaround is downgrading both Accounsservice and
Libaccountsservice0 to the previous version.

sudo apt install accountsservice=0.6.40-2ubuntu10
libaccountsservice0=0.6.40-2ubuntu10

To prevent the packages from being updates to the broken version:

sudo apt-mark hold accountsservice libaccountsservice0

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

** Description changed:

- Accountsservice version 0.6.40-2ubuntu10 fails to update user info of
+ Accountsservice version 0.6.40-2ubuntu11 fails to update user info of
  the file /var/lib/AccountsService/users/, for example changing
  your wallpaper doesn't update the image of Lightdm since it reads the
  path from this file. Workaround is downgrading both Accounsservice and
  Libaccountsservice0 to the previous version.
  
  sudo apt install accountsservice=0.6.40-2ubuntu10
  libaccountsservice0=0.6.40-2ubuntu10
  
  To prevent the packages from being updates to the broken version:
  
  sudo apt-mark hold accountsservice libaccountsservice0

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

Title:
  Accountsservice fails to update user info

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Accountsservice version 0.6.40-2ubuntu11 fails to update user info of
  the file /var/lib/AccountsService/users/, for example
  changing your wallpaper doesn't update the image of Lightdm since it
  reads the path from this file. Workaround is downgrading both
  Accounsservice and Libaccountsservice0 to the previous version.

  sudo apt install accountsservice=0.6.40-2ubuntu10
  libaccountsservice0=0.6.40-2ubuntu10

  To prevent the packages from being updates to the broken version:

  sudo apt-mark hold accountsservice libaccountsservice0

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

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

[Dx-packages] [Bug 1582048] [NEW] cannot timeout suspend GDM from logind

2016-05-15 Thread KeithG 
Public bug reported:

Previously (12.04 - 15.04), if I edited the /etc/systemd/logind.conf
file to auto suspend the GDM login screen it worked. Now, if I edit the
2 lines to cause a suspend if the login screen (GDM) is up and no one
logs in for 15 minutes, I get unintended random suspend from an active,
logged in user.

The edit I make is to uncomment 2 lines:
...
IdleAction=suspend
IdleActionSec=15min
...

This happens with 15.10 and 16.04 and is repeatable on my 3 machines. 1
is nvidia current, another nvidia legacy and another is i915. All were
clean installs (not upgraded)

Release:  
Description:Ubuntu 16.04 LTS
Release:16.04

Version:
systemd:
  Installed: 229-4ubuntu5
  Candidate: 229-4ubuntu5
  Version table:
 *** 229-4ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

What I expect:
If no user is logged in, the GDM screen should suspend. If a user is logged in, 
it should not suspend

What happens:
after a user logs in, the computer will suspend after 15 min. There is nothing 
odd in the dmesg log. It just appears as any suspend event. If a user is logged 
in, it should not suspend unless the user has a timeout and suspend set fort 
their login.

** Affects: systemd-shim (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1582048

Title:
  cannot timeout suspend GDM from logind

Status in systemd-shim package in Ubuntu:
  New

Bug description:
  Previously (12.04 - 15.04), if I edited the /etc/systemd/logind.conf
  file to auto suspend the GDM login screen it worked. Now, if I edit
  the 2 lines to cause a suspend if the login screen (GDM) is up and no
  one logs in for 15 minutes, I get unintended random suspend from an
  active, logged in user.

  The edit I make is to uncomment 2 lines:
  ...
  IdleAction=suspend
  IdleActionSec=15min
  ...

  This happens with 15.10 and 16.04 and is repeatable on my 3 machines.
  1 is nvidia current, another nvidia legacy and another is i915. All
  were clean installs (not upgraded)

  Release:  
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Version:
  systemd:
Installed: 229-4ubuntu5
Candidate: 229-4ubuntu5
Version table:
   *** 229-4ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  What I expect:
  If no user is logged in, the GDM screen should suspend. If a user is logged 
in, it should not suspend

  What happens:
  after a user logs in, the computer will suspend after 15 min. There is 
nothing odd in the dmesg log. It just appears as any suspend event. If a user 
is logged in, it should not suspend unless the user has a timeout and suspend 
set fort their login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1582048/+subscriptions

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

[Dx-packages] [Bug 1259562] Re: Old guest users pollute accountsservice

2016-05-15 Thread Gunnar Hjalmarsson 
** No longer affects: lightdm

** No longer affects: lightdm (Ubuntu)

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

Title:
  Old guest users pollute accountsservice

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  When you log out from a guest session, the temporary guest account is
  removed - but only almost. The folder /var/lib/AccountsService/users
  gets 'polluted' with files for previous guest users.

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

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

[Dx-packages] [Bug 1581470] Re: gnome-language-selector crashes when trying to drag English to the top

2016-05-15 Thread Gunnar Hjalmarsson 
*** This bug is a duplicate of bug 1581567 ***
https://bugs.launchpad.net/bugs/1581567

On 2016-05-15 16:19, ray wrote:
> Would like to know an approximate timescale for this -

So would I. ;)

> will try 14.04 in the meantime.

Another, probably more convenient, option is to install accountsservice
from xenial-proposed.

https://wiki.ubuntu.com/Testing/EnableProposed

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

Title:
  gnome-language-selector crashes when trying to drag English to the top

Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  CID: 201409-15485

  I have this 16.04 system configured in Traditional Chinese (Taiwan),
  but when I was trying to drag "English (United States)" back to the
  top, the language selector will crash.

  Steps:
  1. Boot and make sure the system using Traditional Chinese (Taiwan)
  2. Open Language Settings
  3. Try to change the order by dragging English (United States) to the top.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: language-selector-gnome 0.165.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 13 06:55:03 2016
  InstallationDate: Installed on 2016-05-04 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1581470] Re: gnome-language-selector crashes when trying to drag English to the top

2016-05-15 Thread ray 
*** This bug is a duplicate of bug 1581567 ***
https://bugs.launchpad.net/bugs/1581567

I'm getting no error when changing the language order (except lack of
persistence beyond a reboot), but when I try to change the regional
settings, I get a crash due to permission denial.

Would like to know an approximate timescale for this - will try 14.04 in
the meantime.

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

Title:
  gnome-language-selector crashes when trying to drag English to the top

Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  CID: 201409-15485

  I have this 16.04 system configured in Traditional Chinese (Taiwan),
  but when I was trying to drag "English (United States)" back to the
  top, the language selector will crash.

  Steps:
  1. Boot and make sure the system using Traditional Chinese (Taiwan)
  2. Open Language Settings
  3. Try to change the order by dragging English (United States) to the top.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: language-selector-gnome 0.165.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 13 06:55:03 2016
  InstallationDate: Installed on 2016-05-04 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1553696] Re: indicator-datetime-service crashed with SIGSEGV in g_type_check_instance()

2016-05-15 Thread Apport retracing service 
** Tags added: yakkety

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_type_check_instance()

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  occurs on login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar  6 06:35:22 2016
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2016-02-23 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7eff737ead8d : mov
(%rdi),%rax
   PC (0x7eff737ead8d) ok
   source "(%rdi)" (0x72747365645f6c6c) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_handler_disconnect () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1553696/+subscriptions

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

[Dx-packages] [Bug 1581939] Re: indicator-datetime-service crashed with SIGSEGV in g_type_check_instance()

2016-05-15 Thread Apport retracing service 
*** This bug is a duplicate of bug 1553696 ***
https://bugs.launchpad.net/bugs/1553696

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1553696, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1581939/+attachment/4663189/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1581939/+attachment/4663191/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1581939/+attachment/4663193/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1581939/+attachment/4663194/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1581939/+attachment/4663195/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1581939/+attachment/4663197/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1581939/+attachment/4663198/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1553696
   indicator-datetime-service crashed with SIGSEGV in g_type_check_instance()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_type_check_instance()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Wobbly install of 16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Sun May 15 11:37:11 2016
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2014-08-13 (640 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_handler_disconnect () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1581939/+subscriptions

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

[Dx-packages] [Bug 1553696] Re: indicator-datetime-service crashed with SIGSEGV in g_type_check_instance()

2016-05-15 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_type_check_instance()

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  occurs on login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar  6 06:35:22 2016
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2016-02-23 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7eff737ead8d : mov
(%rdi),%rax
   PC (0x7eff737ead8d) ok
   source "(%rdi)" (0x72747365645f6c6c) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_handler_disconnect () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1553696/+subscriptions

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

[Dx-packages] [Bug 1577414] Re: Adding time zones to locations of indicator-datetime

2016-05-15 Thread Matthew Paul Thomas 
Alas, I’m just a designer. For advice on that you’d need an engineer.
:-)

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

Title:
  Adding time zones to locations of indicator-datetime

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Dear all,

  May I suggest the feature to add time zones, e.g. CEST, EDT, directly
  to the very useful locations menu?

  Currently only city names are supported.

  I am attaching two screenshots:

  1. showing the locations menu
  2. a mockup of how I envision the time zone to be represented in the indicator

  Thankfully,

  ~Robert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1577414/+subscriptions

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

[Dx-packages] [Bug 1581920] Re: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed

2016-05-15 Thread Doug Gale 
I tried `apport-collect 1581920` in a terminal (without backticks) and
it says "No additional information collected"

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

Title:
  Endless syslog assert spam: Gtk-CRITICAL **:
  gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed

Status in indicator-applet package in Ubuntu:
  New

Bug description:
  Every time I look at my syslog it is a sea of assertions interspersed
  with actual relevant logs.

  I have been letting this go for a long time. I think it is time I
  tried to stop the log spam.

  I love the applet, it is great!

  My syslog consists of endless spam like this:

  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1581920/+subscriptions

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

[Dx-packages] [Bug 1581920] Re: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed

2016-05-15 Thread Doug Gale 
You may notice that the assertion failures are happening so fast that a
whole screen full of syslog messages are all in the same second.

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

Title:
  Endless syslog assert spam: Gtk-CRITICAL **:
  gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed

Status in indicator-applet package in Ubuntu:
  New

Bug description:
  Every time I look at my syslog it is a sea of assertions interspersed
  with actual relevant logs.

  I have been letting this go for a long time. I think it is time I
  tried to stop the log spam.

  I love the applet, it is great!

  My syslog consists of endless spam like this:

  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1581920/+subscriptions

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

[Dx-packages] [Bug 1581920] [NEW] Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed

2016-05-15 Thread Doug Gale 
Public bug reported:

Every time I look at my syslog it is a sea of assertions interspersed
with actual relevant logs.

I have been letting this go for a long time. I think it is time I tried
to stop the log spam.

I love the applet, it is great!

My syslog consists of endless spam like this:

May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed

** Affects: indicator-applet (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Endless syslog assert spam: Gtk-CRITICAL **:
  gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed

Status in indicator-applet package in Ubuntu:
  New

Bug description:
  Every time I look at my syslog it is a sea of assertions interspersed
  with actual relevant logs.

  I have been letting this go for a long time. I think it is time I
  tried to stop the log spam.

  I love the applet, it is great!

  My syslog consists of endless spam like this:

  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:01:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
  May 14 16:03:52 doug-lt 
org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: 
(indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  May 14 16:03:52 doug-lt