[Dx-packages] [Bug 1258863] Re: Indicators should still provide dbus activation
** Changed in: indicator-session (Ubuntu) Status: New => Confirmed ** Changed in: indicator-session (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1258863 Title: Indicators should still provide dbus activation Status in The Session Menu: New Status in Sound Menu: Confirmed Status in “indicator-session” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: In bug #1185565, indicators are dropping xdg autostart files & dbus activation files. This breaks sessions which are not managed by upstart. One can have the best of the both worlds. Under upstart user-sessions, /usr/share/upstart/xdg/ is added to XDG_CONFIG_DIRS, thus one can place an override autostart/indicator-$foo.desktop file there which declares "Hidden=true" and thus under upstart managed session the xdg-autostart file will be ingored. Similarly dbus file is re-introduced, as to allow for dbus activation of the indicators. Patch to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1258863/+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 1258863] Re: Indicators should still provide dbus activation
** Also affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-session Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1258863 Title: Indicators should still provide dbus activation Status in The Session Menu: New Status in Sound Menu: Confirmed Status in “indicator-session” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: In bug #1185565, indicators are dropping xdg autostart files & dbus activation files. This breaks sessions which are not managed by upstart. One can have the best of the both worlds. Under upstart user-sessions, /usr/share/upstart/xdg/ is added to XDG_CONFIG_DIRS, thus one can place an override autostart/indicator-$foo.desktop file there which declares "Hidden=true" and thus under upstart managed session the xdg-autostart file will be ingored. Similarly dbus file is re-introduced, as to allow for dbus activation of the indicators. Patch to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1258863/+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 1258863] Re: Indicators should still provide xdg autostart & dbus
** Branch unlinked: lp:~xnox/indicator-sound/ubiquity ** Summary changed: - Indicators should still provide xdg autostart & dbus + Indicators should still provide dbus activation -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1258863 Title: Indicators should still provide dbus activation Status in Sound Menu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: In bug #1185565, indicators are dropping xdg autostart files & dbus activation files. This breaks sessions which are not managed by upstart. One can have the best of the both worlds. Under upstart user-sessions, /usr/share/upstart/xdg/ is added to XDG_CONFIG_DIRS, thus one can place an override autostart/indicator-$foo.desktop file there which declares "Hidden=true" and thus under upstart managed session the xdg-autostart file will be ingored. Similarly dbus file is re-introduced, as to allow for dbus activation of the indicators. Patch to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1258863/+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 1258863] Re: Indicators should still provide xdg autostart & dbus
at the moment indicator-sound is broken in ubiquity installer. ** Changed in: indicator-sound Status: New => Confirmed ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Status: New => Confirmed ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1258863 Title: Indicators should still provide xdg autostart & dbus Status in Sound Menu: Confirmed Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: In bug #1185565, indicators are dropping xdg autostart files & dbus activation files. This breaks sessions which are not managed by upstart. One can have the best of the both worlds. Under upstart user-sessions, /usr/share/upstart/xdg/ is added to XDG_CONFIG_DIRS, thus one can place an override autostart/indicator-$foo.desktop file there which declares "Hidden=true" and thus under upstart managed session the xdg-autostart file will be ingored. Similarly dbus file is re-introduced, as to allow for dbus activation of the indicators. Patch to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1258863/+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 1185565] Re: Indicators should have Upstart jobs
given how similar all the indicators are, i'm not sure why there is a unique job for each one: instance $INDICATOR export INDICATOR start on indicators-loaded or indicator-services-start stop on desktop-end or indicator-services-end respawn exec /usr/lib/x86_64-linux-gnu/indicator-$INDICATOR/indicator-$INDICATOR-service and then something else, e.g. can decide which indicators are wanted and simply do: start indicator INDICATOR=sound Such that to avoid boilerplate indicator-*.conf jobs. Each instance can individually be stopped, startered, restarted and gets it's own log file Similarly there is upstart-dbus-bridge, such that instead the indicators can do "start on dbus INTERFACE=com.ubuntu.foo", so I don't think removing dbus activation gains us anything, so far it only broke showing indicators in the ubiquity-dm and non-upstart mananged user-sessions where indicators can be used. At the moment, all user sessions on the desktop can be fully started without being managed by upstart and users can disable that. -- 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, dx-packages https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 1185565] Re: Indicators should have Upstart jobs
I agree with larsu on this one. Can we revert this? Or instead e.g. fix it properly - rebase upstart-dbus activation patches and still use dbus activation. -- 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, dx-packages https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 1239474] Re: do not build-depend on mono on AArch64, not yet available
** Changed in: libappindicator Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239474 Title: do not build-depend on mono on AArch64, not yet available Status in Libappindicator: Fix Released Status in “libappindicator” package in Ubuntu: Fix Released Status in “libappindicator” source package in Saucy: Fix Released Bug description: do not build-depend on mono on AArch64, not yet available To manage notifications about this bug go to: https://bugs.launchpad.net/libappindicator/+bug/1239474/+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 1239473] Re: do not build-depend on valgrind on AArch64, not yet available
** Changed in: libdbusmenu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239473 Title: do not build-depend on valgrind on AArch64, not yet available Status in DBus Menu: Fix Released Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “libdbusmenu” source package in Saucy: Fix Released Bug description: do not build-depend on valgrind on AArch64, not yet available for this architecture To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1239473/+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 1241539] Re: ubiquity-dm is missing keyboard, input, sound, system indicators
** Changed in: ubiquity (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1241539 Title: ubiquity-dm is missing keyboard, input, sound, system indicators Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-keyboard” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Fix Released Bug description: [Impact] Impacts any installs via ubiquity, but only the installation setup, not the desktop or live session. [Test case] Run an install with the new indicator packages available to the installer. This may require building a new ISO with the right packages pre-loaded. [Regression potential] Medium; adds a new ubiquity profile to be used in the installer. This would mean the indicators will be visible from the installer, but does not risk causing regressions on the desktop. ubiquity-dm is missing keyboard, input, sound, system indicators those need "ubiquity" profile defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1241539/+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 1239474] Re: do not build-depend on mono on AArch64, not yet available
** Changed in: libappindicator (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: libappindicator (Ubuntu Saucy) Status: Confirmed => Fix Committed ** Changed in: libappindicator (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: libappindicator (Ubuntu Saucy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239474 Title: do not build-depend on mono on AArch64, not yet available Status in Libappindicator: Fix Committed Status in “libappindicator” package in Ubuntu: Fix Released Status in “libappindicator” source package in Saucy: Fix Released Bug description: do not build-depend on mono on AArch64, not yet available To manage notifications about this bug go to: https://bugs.launchpad.net/libappindicator/+bug/1239474/+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 1239473] Re: do not build-depend on valgrind on AArch64, not yet available
** Changed in: libdbusmenu (Ubuntu Saucy) Status: Confirmed => Fix Released ** Changed in: libdbusmenu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239473 Title: do not build-depend on valgrind on AArch64, not yet available Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “libdbusmenu” source package in Saucy: Fix Released Bug description: do not build-depend on valgrind on AArch64, not yet available for this architecture To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1239473/+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 1241539] Re: ubiquity-dm is missing keyboard, input, sound, system indicators
** Also affects: indicator-keyboard (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-bluetooth (Ubuntu) Status: New => Triaged ** Changed in: indicator-keyboard (Ubuntu) Status: New => Triaged ** Changed in: indicator-keyboard (Ubuntu) Importance: Undecided => High ** Changed in: indicator-bluetooth (Ubuntu) Importance: Undecided => High ** Changed in: indicator-bluetooth (Ubuntu) Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) ** Changed in: indicator-keyboard (Ubuntu) Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1241539 Title: ubiquity-dm is missing keyboard, input, sound, system indicators Status in “indicator-bluetooth” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “indicator-session” package in Ubuntu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Status in “ubiquity” package in Ubuntu: Triaged Bug description: ubiquity-dm is missing keyboard, input, sound, system indicators those need "ubiquity" profile defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1241539/+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 1241539] Re: ubiquity-dm is missing keyboard, input, sound, system indicators
** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Status: New => Triaged ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Medium ** Changed in: ubiquity (Ubuntu) Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) ** Changed in: indicator-sound (Ubuntu) Status: New => Triaged ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => Critical ** Changed in: indicator-sound (Ubuntu) Importance: Critical => Medium ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) ** Changed in: indicator-sound (Ubuntu) Importance: Medium => High ** Also affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-session (Ubuntu) Status: New => Triaged ** Changed in: indicator-session (Ubuntu) Importance: Undecided => High ** Changed in: indicator-session (Ubuntu) Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1241539 Title: ubiquity-dm is missing keyboard, input, sound, system indicators Status in “indicator-session” package in Ubuntu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Status in “ubiquity” package in Ubuntu: Triaged Bug description: ubiquity-dm is missing keyboard, input, sound, system indicators those need "ubiquity" profile defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1241539/+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 1228538] Re: 3-finger touch to show grab handles does not work
works on lenovo yoga 13 ideapad. I get the 9 resize/move handles. ** Changed in: unity (Ubuntu) Milestone: ubuntu-13.10 => None ** Changed in: unity (Ubuntu) Status: New => Incomplete -- 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/1228538 Title: 3-finger touch to show grab handles does not work Status in “unity” package in Ubuntu: Incomplete Bug description: I am using the Lenovo Thinkpad Twist, a convertible with touch screen, Saucy with Unity desktop. All 3- and 4-finger gestures described on https://wiki.ubuntu.com/Multitouch#Supported_Gestures work on the touch screen, except showing the grab handles by a three-finger tap onto the window. Strange is that the problem only occures for my primary user account, not for the guest account. In the guest account the handles appear correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1228538/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: systemd (Ubuntu Saucy) Status: In Progress => 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/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
systemd task assigned to me: - make it possible for systemd-udevd to ignore kernel events from devices tagged "ignore", using a kernel netlink filter to completely avoid wakeups of systemd-udevd. ** Changed in: systemd (Ubuntu Saucy) Status: New => In Progress ** Changed in: systemd (Ubuntu Saucy) Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) ** Changed in: systemd (Ubuntu Saucy) Milestone: None => ubuntu-13.10 -- 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/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: In Progress Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1239473] Re: do not build-depend on valgrind on AArch64, not yet available
** Changed in: libdbusmenu (Ubuntu) Status: New => Confirmed ** Changed in: libdbusmenu (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239473 Title: do not build-depend on valgrind on AArch64, not yet available Status in DBus Menu: New Status in “libdbusmenu” package in Ubuntu: Confirmed Bug description: do not build-depend on valgrind on AArch64, not yet available for this architecture To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1239473/+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 1239474] Re: do not build-depend on mono on AArch64, not yet available
** Also affects: libappindicator Importance: Undecided Status: New ** Changed in: libappindicator Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) ** Changed in: libappindicator (Ubuntu) Status: New => Confirmed ** Changed in: libappindicator (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239474 Title: do not build-depend on mono on AArch64, not yet available Status in Libappindicator: New Status in “libappindicator” package in Ubuntu: Confirmed Bug description: do not build-depend on mono on AArch64, not yet available To manage notifications about this bug go to: https://bugs.launchpad.net/libappindicator/+bug/1239474/+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 1239473] Re: do not build-depend on valgrind on AArch64, not yet available
** Also affects: libdbusmenu Importance: Undecided Status: New ** Changed in: libdbusmenu Assignee: (unassigned) => Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239473 Title: do not build-depend on valgrind on AArch64, not yet available Status in DBus Menu: New Status in “libdbusmenu” package in Ubuntu: New Bug description: do not build-depend on valgrind on AArch64, not yet available for this architecture To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1239473/+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 1232040] [NEW] unity-panel-service assert failure: dbus_error.c:69: Unhandled error from nih_dbus_error_raise: Connection was disconnected before a reply was received
Public bug reported: 1) upgraded system upstart 2) logged out 3) logged back in 4) got this crash pop up ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AssertionMessage: dbus_error.c:69: Unhandled error from nih_dbus_error_raise: Connection was disconnected before a reply was received CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Sep 27 15:16:58 2013 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2013-09-27 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libnih.so.1 __run_exit_handlers (status=0, listp=0x7fe0d52556a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:77 __GI_exit (status=) at exit.c:99 __libc_start_main (main=0x404d60 , argc=1, ubp_av=0x7fff4fb30948, init=, fini=, rtld_fini=, stack_end=0x7fff4fb30938) at libc-start.c:294 _start () Title: unity-panel-service assert failure: dbus_error.c:69: Unhandled error from nih_dbus_error_raise: Connection was disconnected before a reply was received UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy third-party-packages -- 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/1232040 Title: unity-panel-service assert failure: dbus_error.c:69: Unhandled error from nih_dbus_error_raise: Connection was disconnected before a reply was received Status in “unity” package in Ubuntu: New Bug description: 1) upgraded system upstart 2) logged out 3) logged back in 4) got this crash pop up ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AssertionMessage: dbus_error.c:69: Unhandled error from nih_dbus_error_raise: Connection was disconnected before a reply was received CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Sep 27 15:16:58 2013 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2013-09-27 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libnih.so.1 __run_exit_handlers (status=0, listp=0x7fe0d52556a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:77 __GI_exit (status=) at exit.c:99 __libc_start_main (main=0x404d60 , argc=1, ubp_av=0x7fff4fb30948, init=, fini=, rtld_fini=, stack_end=0x7fff4fb30938) at libc-start.c:294 _start () Title: unity-panel-service assert failure: dbus_error.c:69: Unhandled error from nih_dbus_error_raise: Connection was disconnected before a reply was received 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/unity/+bug/1232040/+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 1189309] Re: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()
Re patch in #11, I'm not sure if this will not regress on gnome-panel and derivative GNOME-like sessions, which are not GNOME-Shell based. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1189309 Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() Status in Libappindicator: Confirmed Status in “libappindicator” package in Ubuntu: Confirmed Bug description: crashed on login. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: network-manager-gnome 0.9.8.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jun 10 12:34:25 2013 ExecutablePath: /usr/bin/nm-applet ExecutableTimestamp: 1362762982 InstallationDate: Installed on 2012-09-23 (260 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet ProcCwd: /home/darkness RfKill: SegvAnalysis: Segfault happened at: 0x7fe676a5f87c : cmp%rax,(%rdx) PC (0x7fe676a5f87c) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: network-manager-applet StacktraceTop: gtk_status_icon_set_visible (status_icon=0x265c300, visible=0) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkstatusicon.c:2057 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libappindicator3.so.1 g_object_unref (_object=0x25999b0) at /build/buildd/glib2.0-2.37.1/./gobject/gobject.c:3152 ?? () Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0.14vlan unmanaged /org/freedesktop/NetworkManager/Devices/2 test vlan unmanaged /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunmanaged /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/libappindicator/+bug/1189309/+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 1218622] [NEW] hud-service crashed with signal 5 in g_type_create_instance()
Public bug reported: tried to launch unity8 on my touch capable notebook. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130822.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 22:21:54 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-08-29 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: hud StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: hud-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy -- 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/1218622 Title: hud-service crashed with signal 5 in g_type_create_instance() Status in “hud” package in Ubuntu: New Bug description: tried to launch unity8 on my touch capable notebook. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130822.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 22:21:54 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-08-29 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: hud StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: hud-service crashed with signal 5 in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1218622/+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
