[Dx-packages] [Bug 1728449] Re: Indicator icons do not appear after upgrade to Ubuntu 17.10

2017-11-17 Thread Treviño 
Question is, why indicator-application-service is running in your GNOME
session?

Are you using some special systemd configuration?
As this should not be running in GNOME but only in the Unity session.


As for the other issues mentioned here, I think that it's not really an ubuntu 
bug, but it looks like a misconfiguration on the client part.

Having two extensions trying to handle indicators isn't feasible (as
they both want the same dbus name), so we can't do much. At least in
future it won't be possible to install KSTatusNotificationIcon extension
and the ubuntu indicators one together, so the issue will be less
visible.

** Changed in: indicator-application (Ubuntu)
   Status: Confirmed => Incomplete

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Indicator icons do not appear after upgrade to Ubuntu 17.10

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in indicator-application package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 17.04 to 17.10 all the indicator icons (Steam,
  InSync, Google Chrome, Hangouts, Slack, etc) are missing.

  A temporary workaround is to kill indicator-application-service, but
  this only works until the next reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: indicator-application 12.10.1+17.04.20161201-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 20:45:06 2017
  InstallationDate: Installed on 2015-03-28 (946 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-application
  UpgradeStatus: Upgraded to artful on 2017-10-07 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728449/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage

2017-11-17 Thread Anders Hall 
Last work-around didn't stick. Don't think this bug or #1731939 is about
indicator-datetime-service. It seems to be evolution calendar that is
the problem. See comment below:

https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1731939/comments/4

Will test 17.10 now.

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM

2017-11-17 Thread Anders Hall 
Last work-around didn't stick. Did some test and can reproduce the error
now easily in 17.04. Ubuntu reports it is the Indicator-datetime-service
that crashes when its the evolution calendar that is the problem. During
the system overload the problem can be fixed by killing all evolution
processes and sub-processes indirectly.

Evolution is overloading the Indicator-datetime-service somehow with
lots of (factory?) sub-processes.

Attached screenshot of the processes active during the error. Resolved
by killing the evolution processes in the screenshot.

Also, this problem started after enabling Empathy on boot. However,
after disabling Empathy completely at startup the problem persisted.

Will update to 17.10 (KVM bug fixed) and see if the error is unresolved.


** Attachment added: "htop screenshot sorted by mem usage"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5010707/+files/Screenshot%20from%202017-11-17%2022-45-57.png

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

Title:
   Indicator-datetime-service renders 25% CPU usage and 100% RAM

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Same as Bug #774071 but with 100% RAM instead. Collected info while
  the Indicator-datetime-service was acting up. I.e., writing this with
  a few hundred megabytes RAM available..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Nov 13 15:41:39 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2015-07-18 (848 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 1703046] Re: indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()

2017-11-17 Thread Launchpad Bug Tracker 
This bug was fixed in the package indicator-printers -
0.1.7+17.10.20171101-0ubuntu1

---
indicator-printers (0.1.7+17.10.20171101-0ubuntu1) bionic; urgency=medium

  [ Andrea Azzarone ]
  * According to the documentation cupsGetOptions can return NULL.
Do not crash if it happens. (lp: #1703046)

 -- Sebastien Bacher   Fri, 17 Nov 2017 16:11:19
+0100

** Changed in: indicator-printers (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  indicator-printers-service crashed with SIGSEGV in
  __GI_strtol_l_internal()

Status in indicator-printers package in Ubuntu:
  Fix Released
Status in indicator-printers source package in Artful:
  Fix Committed

Bug description:
  [ Impact ]

  indicators-printers crashes, notifying the error to the user.

  [ Test case ]

  This was one of the most hit crash in errors.ubuntu.com. Make sure this will 
no longer happen once the fix is released.
  The link is 
https://errors.ubuntu.com/problem/43e6488fd8640c6a0cb8ca237286153b5b547f80

  [ Regression potential ]

  Nothing really possible, other not crashing.

  Just got this from the recent update

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Jul  7 16:55:07 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
  InstallationDate: Installed on 2015-12-17 (567 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>:
movsbq (%r14),%rax
   PC (0x7fa9166826b5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-printers
  StacktraceTop:
   __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-printers-service crashed with SIGSEGV in 
__GI_strtol_l_internal()
  UpgradeStatus: Upgraded to artful on 2017-02-14 (143 days ago)
  UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo 
ubridge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1703046/+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 1703046] Re: indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()

2017-11-17 Thread Sebastien Bacher 
** Changed in: indicator-printers (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  indicator-printers-service crashed with SIGSEGV in
  __GI_strtol_l_internal()

Status in indicator-printers package in Ubuntu:
  Fix Committed
Status in indicator-printers source package in Artful:
  Fix Committed

Bug description:
  [ Impact ]

  indicators-printers crashes, notifying the error to the user.

  [ Test case ]

  This was one of the most hit crash in errors.ubuntu.com. Make sure this will 
no longer happen once the fix is released.
  The link is 
https://errors.ubuntu.com/problem/43e6488fd8640c6a0cb8ca237286153b5b547f80

  [ Regression potential ]

  Nothing really possible, other not crashing.

  Just got this from the recent update

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Jul  7 16:55:07 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
  InstallationDate: Installed on 2015-12-17 (567 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>:
movsbq (%r14),%rax
   PC (0x7fa9166826b5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-printers
  StacktraceTop:
   __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-printers-service crashed with SIGSEGV in 
__GI_strtol_l_internal()
  UpgradeStatus: Upgraded to artful on 2017-02-14 (143 days ago)
  UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo 
ubridge

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