[Dx-packages] [Bug 1559731] Re: Battery indicator turns red at 30% on desktop
** Branch linked: lp:~unity-api-team/indicator-power/16.04-lp1559731 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1559731 Title: Battery indicator turns red at 30% on desktop Status in Canonical System Image: Fix Committed Status in indicator-power package in Ubuntu: Fix Released Status in indicator-power source package in Xenial: Triaged Bug description: The indicator turns red as soon as battery goes 30% Please refer to the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 20 20:43:32 2016 InstallationDate: Installed on 2016-03-18 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1559731/+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 1304500] Re: Indicator Test Plan QA Review
** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- 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/1304500 Title: Indicator Test Plan QA Review Status in Bluetooth Menu: New Status in The Date and Time Indicator: New Status in Indicator keyboard: New Status in Indicator Location: New Status in The Messaging Menu: New Status in The Power Indicator: New Status in The Session Menu: New Status in Sound Menu: New Status in The Sync Menu: New Status in indicator-bluetooth package in Ubuntu: New Status in indicator-network package in Ubuntu: Fix Released Bug description: indicator-bluetooth Additional tests required to ensure indicator status reflects Bluetooth states (enable/disable, scanning, device listing, pairing status etc.) indicator-datetime Additional tests required to ensure indicator menu includes upcoming events indicator-keyboard N/A for unity 8 Expand test cases and ensure menu options and keyboard language can be set and indicator is updated with correct language indicator-location Additional tests to ensure Location and GPS menu items can be enabled/disabled correctly Does indicator status change when a location fix is available? indicator-messages Additional tests to include new messaging items are displayed correctly in indicator status menu indicator-network Additional tests to include Wi-Fi scanning and connection Ensure indicator icon reflects signal strength for Wi-Fi and telephone network indicator-power Additional tests required to ensure indicator status reflects power states (battery level, charging, charged) Display brightness slider is functional indicator-session Is the Session indicator used on Unity8? Ensure test plan is valid. indicator-sound Additional tests to ensure volume slider is functional Indicator changes according to volume level set on slider indicator-sync Is the Sync indicator used on Unity8? Ensure test plan is valid. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1304500/+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 1301699] Re: Indicators do not show in Pantheon
** Changed in: indicator-network (Ubuntu) Status: Confirmed = Triaged ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Wishlist -- 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, dx-packages https://bugs.launchpad.net/bugs/1301699 Title: Indicators do not show in Pantheon Status in elementary OS: Fix Released Status in Application Indicators: New Status in The Date and Time Indicator: New Status in The Session Menu: New Status in Sound Menu: New Status in indicator-datetime package in Ubuntu: Fix Released Status in indicator-network package in Ubuntu: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Released Bug description: [Impact] It looks like OnlyShowIn=Unity;GNOME; has been added to indicator- datetime, indicator-session, and indicator-sound We should provide a patch to add Pantheon to that list. [Test Case] (1) install the Pantheon desktop sesssion (eg. Elementary OS) and log in (2) verify the appropriate indicator (for this case, session indicator) appears (3) install the Unity 7 desktop session and log in (4) verify the indicator still appears [Regression Potential] A typo in the modified .desktop file could cause the indicator to not appear in a Ubuntu session such as Unity 7 or Gnome Flashback. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1301699/+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 1461482] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:url-dispatcher-bad-url
settings:///system/wifi is a valid URL. ** Package changed: indicator-network (Ubuntu) = url-dispatcher (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1461482 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:url-dispatcher-bad-url Status in url-dispatcher package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+15.10.20150519-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/d63c848f73a34299ec298a6d833b388cc276b3a2 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1461482/+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 1301699] Re: Indicators do not show in Pantheon
i-network requires the indicator-panel-service to implement custom items such as AccessPointItem and ModemInfoItem. Before unity7 or any other DE implements these, i-network is not usable on them. ** Changed in: indicator-network Status: New = Triaged ** Changed in: indicator-network Importance: Undecided = Wishlist -- 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, dx-packages https://bugs.launchpad.net/bugs/1301699 Title: Indicators do not show in Pantheon Status in elementary OS: Fix Released Status in Application Indicators: New Status in The Date and Time Indicator: New Status in Network Menu: Triaged Status in The Session Menu: New Status in Sound Menu: New Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: [Impact] It looks like OnlyShowIn=Unity;GNOME; has been added to indicator- datetime, indicator-session, and indicator-sound We should provide a patch to add Pantheon to that list. [Test Case] (1) install the Pantheon desktop sesssion (eg. Elementary OS) and log in (2) verify the appropriate indicator (for this case, session indicator) appears (3) install the Unity 7 desktop session and log in (4) verify the indicator still appears [Regression Potential] A typo in the modified .desktop file could cause the indicator to not appear in a Ubuntu session such as Unity 7 or Gnome Flashback. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1301699/+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 1391490] [NEW] indicator-power reports incorrect charge level
Public bug reported: I had my krillin sitting on a table for multiple days and now that I picked it up I immediately noticed something is wrong. indicator-power reports that there is 89% of battery left even with days of standby and this is clearly impossible based on empirical data. ** Affects: indicator-power (Ubuntu) Importance: Undecided Assignee: Charles Kerr (charlesk) Status: New ** Changed in: indicator-power (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1391490 Title: indicator-power reports incorrect charge level Status in “indicator-power” package in Ubuntu: New Bug description: I had my krillin sitting on a table for multiple days and now that I picked it up I immediately noticed something is wrong. indicator-power reports that there is 89% of battery left even with days of standby and this is clearly impossible based on empirical data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1391490/+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 1358340] Re: [Indicators] Complete greeter profiles
** Tags removed: touch-2014-09-25 ** Tags added: touch-2014-10-02 ** Tags removed: touch-2014-10-02 ** Tags added: touch-2014-10-09 -- 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, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1358340 Title: [Indicators] Complete greeter profiles Status in The Date and Time Indicator: Confirmed Status in The Messaging Menu: In Progress Status in Sound Menu: Confirmed Status in Transfer Indicator: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Fix Released Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: A recent change in the interest of security removed access to the indicators when the phone is locked and the greeter is showing. This was an accentual change based on a misunderstanding There had been a plan to support media playback control via the sound indicator. Without this the user must unlock the phone in order to simply pause the music or change songs, etc. Desired resolution: - Revert the change that caused this issue - Add a switch to System Settings to enable security conscious user to switch off Launcher and Greeter access while the phone is locked. This setting should *always* be off by default. https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1369453] Re: able to view and change indicators without unlocking phone
** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki) -- 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/1369453 Title: able to view and change indicators without unlocking phone Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “indicator-location” package in Ubuntu: Confirmed Status in “indicator-network” package in Ubuntu: Confirmed Bug description: This is a pretty significant security issue that affects: - networking - able to switch networks without entering pin to unlock phone - GPS - can toggle. - bluetooth - can toggle. - upcoming events - can view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1369453/+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 1364453] Re: Brightness setting does not persist across reboots
mterry: we have a plan cooking for post-rtm to address these issues of system-wide settings vs. user-settings and split greeter. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1364453 Title: Brightness setting does not persist across reboots Status in “indicator-power” package in Ubuntu: Confirmed Status in “unity-system-compositor” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: When altering the brightness setting, it is always reset to the default value after a reboot. It is expected that changing the setting should persist across reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1364453/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: indicator-network (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-network” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
added telephony-service to affected projects as we still need the incoming call snap decision and some of the messaging snap decisions to use this hint. ** Also affects: telephony-service Importance: Undecided Status: New ** Changed in: telephony-service Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** Changed in: indicator-network Status: New = Fix Released ** Changed in: unity-notifications Status: In Progress = Fix Released ** Changed in: unity Status: Triaged = Invalid ** Changed in: unity (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
marked the Unity as Invalid as no changes needed on that side. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Branch unlinked: lp:~unity-api-team/indicator-network/devel -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “indicator-network” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Also affects: indicator-network Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Branch linked: lp:~unity-api-team/indicator-network/devel -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1235059] Re: hud-service crashed with signal 5 in _start()
** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1235059 Title: hud-service crashed with signal 5 in _start() Status in “hud” package in Ubuntu: Confirmed Bug description: In a cairo launcher session hud-service crashed on me. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131002.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Thu Oct 3 22:50:54 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-10-04 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131003) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: hud StacktraceTop: _start () Title: hud-service crashed with signal 5 in _start() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.hud.log: (process:2046): hud-service-WARNING **: SIGTERM recieved (process:2046): hud-service-ERROR **: Unable to get name 'com.canonical.hud' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1235059/+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 1281227] Re: hud-service crashed with SIGSEGV with an invalid pointer reference when a bad QSharedPointer goes out of scope in hud::service::QueryImpl::updateToken()
** Changed in: hud (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1281227 Title: hud-service crashed with SIGSEGV with an invalid pointer reference when a bad QSharedPointer goes out of scope in hud::service::QueryImpl::updateToken() Status in “hud” package in Ubuntu: Fix Released Bug description: no more icons in the tray area ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140212-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 17 19:22:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service SegvAnalysis: Segfault happened at: 0x43317d _ZN3hud7service9QueryImpl11updateTokenE14QSharedPointerINS0_6WindowEE+77: lock subl $0x1,0x4(%rbx) PC (0x0043317d) ok source $0x1 ok destination 0x4(%rbx) (0x00b4) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () hud::service::QueryImpl::refresh() () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () Title: hud-service crashed with SIGSEGV in hud::service::QueryImpl::updateToken() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.7' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1281227/+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 967879] Re: hud-service has a memory leak (I think)
this is not a duplicate of #1253593 as the code base in 12.04 is different. ** This bug is no longer a duplicate of bug 1253593 hud memory usage grows over time -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/967879 Title: hud-service has a memory leak (I think) Status in “indicator-appmenu” package in Ubuntu: Confirmed Bug description: After about 8 hours of use, I closed all the following programs: Pidgin Eclipse Rational Team Concert ATT's AGNclient VPN software Banshee Chrome Synaptic Gnome-Calculator Gnome-Terminal Nautilus Lotus Notes ...and noticed that hud-service is taking up 162M of RAM. It started out taking up something like 24M. Isn't that memory usage a little high? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/967879/+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 1253676] Re: hud-service crashed with SIGSEGV in hud_source_search()
** Also affects: hud Importance: Undecided Status: New ** Changed in: hud Status: New = Fix Committed ** Changed in: hud Importance: Undecided = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1253676 Title: hud-service crashed with SIGSEGV in hud_source_search() Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: Confirmed Bug description: Not sure of the steps, I found this when running unity8 autopilot tests. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20131029.1-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Thu Nov 21 13:19:27 2013 ExecutablePath: /usr/lib/arm-linux-gnueabihf/hud/hud-service ExecutableTimestamp: 1383046411 InstallationDate: Installed on 2013-11-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131120.2) MarkForUpload: True ProcCmdline: /usr/lib/arm-linux-gnueabihf/hud/hud-service ProcCwd: /home/phablet RetraceOutdatedPackages: outdated debug symbol package for libdbusmenu-glib4: package version 12.10.3+13.10.20130913-0ubuntu2 dbgsym version 12.10.3+13.10.20131104-0ubuntu1 Signal: 11 SourcePackage: hud Title: hud-service crashed with SIGSEGV in hud_source_search() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1253676/+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 1253676] Re: hud-service crashed with SIGSEGV in hud_source_search()
** Changed in: hud Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki) -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1253676 Title: hud-service crashed with SIGSEGV in hud_source_search() Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: Confirmed Bug description: Not sure of the steps, I found this when running unity8 autopilot tests. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20131029.1-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Thu Nov 21 13:19:27 2013 ExecutablePath: /usr/lib/arm-linux-gnueabihf/hud/hud-service ExecutableTimestamp: 1383046411 InstallationDate: Installed on 2013-11-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131120.2) MarkForUpload: True ProcCmdline: /usr/lib/arm-linux-gnueabihf/hud/hud-service ProcCwd: /home/phablet RetraceOutdatedPackages: outdated debug symbol package for libdbusmenu-glib4: package version 12.10.3+13.10.20130913-0ubuntu2 dbgsym version 12.10.3+13.10.20131104-0ubuntu1 Signal: 11 SourcePackage: hud Title: hud-service crashed with SIGSEGV in hud_source_search() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1253676/+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 967879] Re: hud-service has a memory leak (I think)
@ryan could you take a look at this. We have fresh reports from 12.04 users saying that hud1 is eating up their RAM. Thanks! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/967879 Title: hud-service has a memory leak (I think) Status in “indicator-appmenu” package in Ubuntu: Confirmed Bug description: After about 8 hours of use, I closed all the following programs: Pidgin Eclipse Rational Team Concert ATT's AGNclient VPN software Banshee Chrome Synaptic Gnome-Calculator Gnome-Terminal Nautilus Lotus Notes ...and noticed that hud-service is taking up 162M of RAM. It started out taking up something like 24M. Isn't that memory usage a little high? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/967879/+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 967879] Re: hud-service has a memory leak (I think)
@eddyg-j: could you describe the workflow on these machines: are there a lot of applications being opened and closed constantly or are some apps running more than others? @rutsky-vladimir: could you please file a separate bug against hud package? https://bugs.launchpad.net/ubuntu/+source/hud/+filebug 13.10 has a new hud package and the memory leak you are seeing most likely unrelated to 12.04 memory leak. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/967879 Title: hud-service has a memory leak (I think) Status in “indicator-appmenu” package in Ubuntu: Fix Released Bug description: After about 8 hours of use, I closed all the following programs: Pidgin Eclipse Rational Team Concert ATT's AGNclient VPN software Banshee Chrome Synaptic Gnome-Calculator Gnome-Terminal Nautilus Lotus Notes ...and noticed that hud-service is taking up 162M of RAM. It started out taking up something like 24M. Isn't that memory usage a little high? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/967879/+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
