[Dx-packages] [Bug 1343962] Re: Sound slider moves itself randomly when scrolling or moving sound pointer
My laptop has nothing to do with NVIDIA, so I think it's a wrong guess.
It must have been Ubuntu SDK or something related to its installation.
--
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/1343962
Title:
Sound slider moves itself randomly when scrolling or moving sound
pointer
Status in “indicator-sound” package in Ubuntu:
Incomplete
Bug description:
I've described this bug in details at askubuntu.com ::
http://askubuntu.com/questions/499268/strange-bug-with-sound-slider
In brief:
1) Problem caused by installation of Ubuntu-SDK
2) Removing Ubuntu-SDK didn't fix the problem
3) This problem occurs only with desktop sound slider (notification slider).
In Ubuntu sound settings, everything is fine.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute':
(true, '', []), 'phone-settings': (true, '', []), 'mic-volume': (true,
'', [<0.1183929443359375>]), 'scroll': (true, 'i', []),
'play-playlist.spotify.desktop': (true, 's', []), 'vlc.desktop': (true, '',
[<{'running': , 'state': <'Paused'>}>]), 'desktop-settings': (true, '',
[]), 'previous.vlc.desktop': (true, '', []), 'play-playlist.vlc.desktop':
(true, 's', []), 'spotify.desktop': (true, '', [<{'running': , 'state':
<'Paused'>}>]), 'volume': (true, 'i', [<0.51992553710937495>]),
'play.spotify.desktop': (true, '', [<'Paused'>]), 'previous.spotify.desktop':
(true, '', []), 'root': (true, '', [<{'title': <'Dźwięk'>, 'accessible-desc':
<'Głośność (51%)'>, 'icon': <('themed', <['audio-volume-medium-panel',
'audio-volume-medium', 'audio-volume', 'audio']>)>, 'visible': }>]),
'next.spotify.desktop': (true, '', []), 'play.vlc.desktop': (true, '',
[<'Paused'>])},)
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul 18 12:28:16 2014
ExecutablePath:
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
InstallationDate: Installed on 2014-04-17 (91 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=pl
XDG_RUNTIME_DIR=
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1343962/+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 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled
Just tried this on a recent image ( #183 ) on mako, and I can reproduce it. It looks like the bluetooth indicator doesn't talk to urfkill directly. When I disable BT via the indicator, the rfkill state is indeed toggled, as if I run 'rfkill list', it shows as soft-blocked. -- 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/1296114 Title: Bluetooth is always enabled after reboot even if it was disabled Status in Bluetooth Menu: Invalid Status in “indicator-bluetooth” package in Ubuntu: Invalid Status in “rfkill” package in Ubuntu: Triaged Status in “urfkill” package in Ubuntu: Triaged Bug description: If bluetooth was disabled using the switcher in the bluetooth indicator, after reboot it becomes enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 22 22:34:52 2014 InstallationDate: Installed on 2014-01-27 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: Connecting to session manager To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
I'm seeing this too on Utopic quite regularly. For me, it happens when I use the icon in the task switcher to get an overview of the four workspaces. When things freeze, I see the four workspaces filling the screen, with the shrunk windows in each workspace, and no more response at that point. Sometimes, hitting Super-S gets things back, other times it doesn't. -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in “compiz-plugins-main” package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1330037] Re: upower 0.99 transition
This bug was fixed in the package cairo-dock-plug-ins - 3.3.99.rc1.1~20140818~bzr3115-0ubuntu1 --- cairo-dock-plug-ins (3.3.99.rc1.1~20140818~bzr3115-0ubuntu1) utopic; urgency=medium * New upstream snapshot. * Short Upstream ChangeLog: - All: updated due to recent API changes and changes in the global style - All: removed GTK2 support - DnD2Share: refresh support of some backend - GMenu: - Do not create empty menus - Show dialogue to open a new app after the end of the installation - Added an option to not show this dialogue - Gnome: support Cinnamon logout - Logout: display a message to reboot after the end of the update - Shortcuts: improve the support of bookmarks - Status-Notifier: support scroll events - System-Monitor: fixed RAM info - Terminal: open terminal on middle click, support Maj+Ctrl+[CV] - UPower: support 0.99 version (LP: #1330037 - was already patched) - Stop using GTK Stock icons - po: updated translations (added Korean) - Some bugs have been fixed, other tweaks (LP: #1303263) * debian/control: - Bumped Cairo-Dock (core) versions - Added libwayland (initial support, not enabled by default) * debian/patches: - Removed all patches: all of them were created from this version -- Matthieu Baerts (matttbe)Tue, 19 Aug 2014 22:10:43 +0200 ** Changed in: cairo-dock-plug-ins (Ubuntu) Status: Fix Committed => Fix Released -- 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/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Released Status in “gnome-applets” package in Ubuntu: Invalid Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: Triaged Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: In Progress Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal.
[Dx-packages] [Bug 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** Tags removed: rtm ** Tags added: rtm14 -- 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/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: "After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again." Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1330037] Re: upower 0.99 transition
** Branch linked: lp:ubuntu/utopic-proposed/cairo-dock-plug-ins -- 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/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Invalid Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: Triaged Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: In Progress Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1357311] Re: Datetime indicator's menu no longer shows events or Settings button: "Empty!"
AFAIU this has the same background as bug #1328646 -- 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/1357311 Title: Datetime indicator's menu no longer shows events or Settings button: "Empty!" Status in The Unity 8 shell: New Status in “indicator-datetime” package in Ubuntu: Invalid Bug description: Since #189 the datetime indicator shows no events at all inside the pull-down from i-d. See screenshot Split into two bugs, related: bug 1357307 To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1357311/+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 1358922] [NEW] Web App won't install
Public bug reported: I run a steampunk writing/social network site CitizensOfAntiford.com and the unity integration works in 13.10, but not in 14.04 Steps: Go to site See integration popup Click 'Yes' In 13.10: The app to show up in the taskbar/launcher and in the dash under applications In 14.04: Nothing. I never get the message again and there are no icons for the web app anywhere. If you're curious, the code is here: https://citizensofantiford.com/js/unity.js ** Affects: libunity-webapps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1358922 Title: Web App won't install Status in “libunity-webapps” package in Ubuntu: New Bug description: I run a steampunk writing/social network site CitizensOfAntiford.com and the unity integration works in 13.10, but not in 14.04 Steps: Go to site See integration popup Click 'Yes' In 13.10: The app to show up in the taskbar/launcher and in the dash under applications In 14.04: Nothing. I never get the message again and there are no icons for the web app anywhere. If you're curious, the code is here: https://citizensofantiford.com/js/unity.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1358922/+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 1330037] Re: upower 0.99 transition
** Branch linked: lp:ubuntu/cairo-dock-plug-ins -- 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/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Invalid Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: Triaged Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: In Progress Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1358745] Re: Screen lock has no place to type in a password
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- 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/1358745 Title: Screen lock has no place to type in a password Status in “unity” package in Ubuntu: New Bug description: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1358745/+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 1358745] [NEW] Screen lock has no place to type in a password
You have been subscribed to a public bug: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- Screen lock has no place to type in a password https://bugs.launchpad.net/bugs/1358745 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1328646] Re: Clock out of sync on resume from suspend
Marking this as Invalid for indicator-datetime as -- similar to bug#1357311 -- the service is correctly pushing out menuitems and the header label to the bus. ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Invalid ** Changed in: indicator-datetime Status: New => Invalid -- 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/1328646 Title: Clock out of sync on resume from suspend Status in The Date and Time Indicator: Invalid Status in The Unity 8 shell: In Progress Status in “indicator-datetime” package in Ubuntu: Invalid Status in “qmenumodel” package in Ubuntu: Confirmed Bug description: When the device is resumed by pressing the power button and the device is not connected over USB the clock is out of sync You need another system to compare the time to verify this bug report, and make sure both clocks are in sync. TEST CASE 1. Unplug the device from its USB cable 2. Press the power button to switch to suspend mode or wait until it goes to suspend 3. Wait 2 or more minutes 4. Press the power button again to resume the device 5. Compare the time on the greeter and indicator with the time on the other system EXPECTED RESULT Clocks are in sync ACTUAL RESULT Time on the device is behind by several minutes. The use case are people who use their device as a watch. You usually resume it, check the time, suspend it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.88+14.10.20140606-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Tue Jun 10 19:11:42 2014 InstallationDate: Installed on 2014-06-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140610) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms
Hm, actually I'm not sure it made sense for me to reopen this for datetime: the questions of how to make this user friendly (e.g., do we fold alarms into a single notification) need to be addressed but are not traincon0 blockers and shouldn't hold up the resolution of this ticket if MacSlow's patch does the job. So I've opened a separate ticket (bug #1358890) for the secondary question of how two alarms at once should be displayed, and am re- closing this ticket as invalid wrt datetime. ** Changed in: indicator-datetime (Ubuntu) Status: Triaged => Invalid -- 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/1354406 Title: PIN-locked phone becomes unresponsive after simultaneous alarms Status in “indicator-datetime” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings -> accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. I have further discovered that if your phone gets into this state you can tap where you think the dismiss icon is for the notification (top left of the screen) and you _can_ dismiss it, despite it not actually being visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+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 1357311] Re: Datetime indicator's menu no longer shows events or Settings button: "Empty!"
Marking this as Invalid for indicator-datetime, as the service is correctly pushing out menuitems and the header label to the bus, as described in comment:3 However, obviously this has a large impact on indicator-datetime -- it's basically unusable on the phone right now. If there's any information I can provide about indicator-datetime-service to help track down this bug in unity8 just ask. ** Changed in: indicator-datetime (Ubuntu) Status: New => Invalid ** Changed in: unity8 Assignee: (unassigned) => Nick Dedekind (nick-dedekind) -- 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/1357311 Title: Datetime indicator's menu no longer shows events or Settings button: "Empty!" Status in The Unity 8 shell: New Status in “indicator-datetime” package in Ubuntu: Invalid Bug description: Since #189 the datetime indicator shows no events at all inside the pull-down from i-d. See screenshot Split into two bugs, related: bug 1357307 To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1357311/+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 1311316] Re: After locking screen there is no input field to type password for unlock
This is happening much more often since the latest Unity releases. There were several changes done to the lockscreen and it seems that these changes made this problem more frequent. It seems to be particularly frequent when the machine is under heavy load (i.e. compiling stuff), which seems to point to some kind of race condition that is made worse when things are going slow. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms
Reopening for indicator-datetime: Even if unity-notification's guard were working properly, indicator- datetime should probably do something to fold multiple alarms into a single notification / single sound. ** Changed in: indicator-datetime (Ubuntu) Status: Invalid => Triaged ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) -- 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/1354406 Title: PIN-locked phone becomes unresponsive after simultaneous alarms Status in “indicator-datetime” package in Ubuntu: Triaged Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings -> accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. I have further discovered that if your phone gets into this state you can tap where you think the dismiss icon is for the notification (top left of the screen) and you _can_ dismiss it, despite it not actually being visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+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 1192789] Re: search disrupting unity lens research
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: unity Status: New => Invalid ** Changed in: unity (Ubuntu) Status: New => 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/1192789 Title: search disrupting unity lens research Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: unity 8 search disrupting unity lens research, several surveys do not work properly, levels of errors are still visible, latches to FIND things simple conflict of languages. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1192789/+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 1243506] Re: unity no lens, search no dash
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: unity Status: New => Invalid ** Changed in: unity (Ubuntu) Status: New => 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/1243506 Title: unity no lens, search no dash Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: No search in Dash, No lens in the Dash! Вообще в Даше всё пусто, ни чего ни найти в нём! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243506/+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 1334618] Re: Fullscreen apps are displayed on the lock screen for some time after suspend
** Information type changed from Private Security to Public Security -- 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/1334618 Title: Fullscreen apps are displayed on the lock screen for some time after suspend Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: The bug appears on low perfomance hardware (netbooks) Steps to reproduce: 1)Open in Evinve some file on netbook. 2)Go to fullscreen mode (F11) 3)Close the lid of your netbook (or if you are trsting on the desktop press Alt+F10 and navigate by arrow to Suspend button 4)Press suspend and wake up the device 5) So the bug: for 2 or three seconds after waking up The pdf will be displayed on your netbook instead of Unity-greeter. Than unity greeter will ask you your password It is unsecure, because somebody my see your content, while you are just opened the lid To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1334618/+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 1358830] [NEW] indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings
Public bug reported: Summary: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings steps: 1. Open system settings 2. Go to bluetooth page 3. Disable and enable bluetooth 4. Pull down bluetooth indicator Expected results: Bluetooth indicator has widgets on it Actual results: Indicator is blank ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: 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/1358830 Title: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings Status in “indicator-bluetooth” package in Ubuntu: New Bug description: Summary: indicator-bluetooth is blank after disabling bluetooth from the indicator and enabling bluetooth in system settings steps: 1. Open system settings 2. Go to bluetooth page 3. Disable and enable bluetooth 4. Pull down bluetooth indicator Expected results: Bluetooth indicator has widgets on it Actual results: Indicator is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1358830/+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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
** Also affects: compiz-winrules-plugin Importance: Undecided Status: New ** No longer affects: compiz-winrules-plugin -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in “compiz-plugins-main” package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1357311] Re: Datetime indicator's menu no longer shows events or Settings button: "Empty!"
** Branch linked: lp:~nick-dedekind/unity8/lp1328646 -- 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/1357311 Title: Datetime indicator's menu no longer shows events or Settings button: "Empty!" Status in The Unity 8 shell: New Status in “indicator-datetime” package in Ubuntu: New Bug description: Since #189 the datetime indicator shows no events at all inside the pull-down from i-d. See screenshot Split into two bugs, related: bug 1357307 To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1357311/+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 1358293] Re: Turning off Bluetooth in the Indicator Crashes the Phone
In case it's a clue: this morning I turned off the bluetooth headset
before I turned off bluetooth in the indicator. The bluetooth indicator
disappeared, but the phone did not crash.
--
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/1358293
Title:
Turning off Bluetooth in the Indicator Crashes the Phone
Status in “indicator-bluetooth” package in Ubuntu:
In Progress
Bug description:
Steps:
1. Enable a bluetooth headset or earbuds
2. Start the music player and play an album
3. Confirm that the music is playing
4. Turn off the screen and listen to the music for a few tracks
5. Turn on the screen and pause the music player
6. Pull down the indicator and try to disable bluetooth
The indicator freezes for a time, then the whole phone reboots
root@ubuntu-phablet:/# cat /proc/last_kmsg
ram console header, hw_status: 2, fiq step 40.
bin log 0.
x104) from [] (dump_stack+0x20/0x24)
[ 1164.156265] (1)[2070:unity8][] (dump_stack+0x20/0x24) from
[] (handle_IPI+0x21c/0x250)
[ 1164.157473] (1)[2070:unity8][] (handle_IPI+0x21c/0x250) from
[] (do_IPI+0x18/0x1c)
[ 1164.158638] (1)[2070:unity8][] (do_IPI+0x18/0x1c) from
[] (__irq_usr+0x34/0xc0)
[ 1164.160851] (0)[2053:indicator-bluet]init emmc for ipanic dump
[ 1164.175534] (0)[2053:indicator-bluet][pll]0xF020924C = 0x8001
[ 1164.176285] (0)[2053:indicator-bluet][pll]0xF0209240 = 0x121
[ 1164.176992] (0)[2053:indicator-bluet][mux] 0xF060 = 0x1818100
[ 1164.177749] (0)[2053:indicator-bluet][mux] 0xF070 = 0x81808101
[ 1164.178519] (0)[2053:indicator-bluet][clk] 0xF0003010 = 0x0
[ 1164.179213] (0)[2053:indicator-bluet][clk] 0xF0003018 = 0x2fecffd
[ 1164.180068] (0)[2053:indicator-bluet]send cmd0
[ 1164.184692] (0)[2053:indicator-bluet]cmd1: resp(0xff8080), i=500
[ 1164.185430] (0)[2053:indicator-bluet]send cmd0
[ 1164.213984] (0)[2053:indicator-bluet]cmd1: resp(0xc0ff8080), i=498
[ 1164.216746] (0)[2053:indicator-bluet]resp: 0x11010030 0x30384739
0x32009acc 0xa9373149
[ 1164.240817] (0)[2053:indicator-bluet]read fifo done, wait xfer_compl
interrupt
[ 1164.241712] (0)[2053:indicator-bluet]emmc offset (0x5c00)
[ 1164.244389] (0)[2053:indicator-bluet]init eMMC success
[ 1167.466826] (0)[2053:indicator-bluet]card_dump_func_write failed (18),
size: 0x58000
[ 1167.467803] (0)[2053:indicator-bluet]CPU: 0Tainted: GW
(3.4.67 #1)
[ 1167.468745] (0)[2053:indicator-bluet]PC is at l2cap_chan_destroy+0x3c/0x88
[ 1167.469599] (0)[2053:indicator-bluet]LR is at __raw_write_lock+0x34/0xa8
[ 1167.470437] (0)[2053:indicator-bluet]pc : []lr :
[]psr: 600f0013
[ 1167.470444] (0)[2053:indicator-bluet]sp : d8897d68 ip : 00100100 fp :
d8897d7c
[ 1167.472412] (0)[2053:indicator-bluet]r10: cc583a20 r9 : cf9db800 r8 :
c74e1300
[ 1167.473335] (0)[2053:indicator-bluet]r7 : 0067 r6 : c74e13bc r5 :
cc58380c r4 : cc583800
[ 1167.474419] (0)[2053:indicator-bluet]r3 : 00200200 r2 : 00100100 r1 :
00200200 r0 : c1128f40
[ 1167.475505] (0)[2053:indicator-bluet]Flags: nZCv IRQs on FIQs on Mode
SVC_32 ISA ARM Segment user
[ 1167.476664] (0)[2053:indicator-bluet]Control: 10c5387d Table: 8ddd806a
DAC: 0015
[ 1167.480769] (0)[2053:indicator-bluet]Process indicator-bluet (pid: 2053,
stack limit = 0xd8896300)
[ 1167.481881] (0)[2053:indicator-bluet]Stack: (0xd8897d68 to 0xd8898000)
[ 1167.482697] (0)[2053:indicator-bluet]7d60: 0009
cf548400 d8897d94 d8897d80 c07ac5b8 c07a6aac
[ 1167.483989] (0)[2053:indicator-bluet]7d80: 0002 cc583800 d8897da4
d8897d98 c07ac690 c07ac580 d8897ddc d8897da8
[ 1167.485279] (0)[2053:indicator-bluet]7da0: c07a2fc8 c07ac684 c74e13c4
d00bf400 d8897ddc d00bf400 d6dd6d00 d6dd6d00
[ 1167.486570] (0)[2053:indicator-bluet]7dc0: 0009 d6dd6808 d8897f78
d6dd6828 d8897df4 d8897de0 c07aa9dc c07a2f0c
[ 1167.487861] (0)[2053:indicator-bluet]7de0: d6dd6cec d00bf400 d8897e14
d8897df8 c0793444 c07aa9bc d6dd6800 d6dd6ecc
[ 1167.489151] (0)[2053:indicator-bluet]7e00: 0008 d6dd6ca0 d8897e4c
d8897e18 c078ee50 c07933a8 d8897e34 c07f9818
[ 1167.490442] (0)[2053:indicator-bluet]7e20: d8897e4c dbdb7600 0001
0008 d883e0c0 0008 d8897f78 be9d7e48
[ 1167.491733] (0)[2053:indicator-bluet]7e40: d8897e5c d8897e50 c078f094
c078ed90 d8897e74 d8897e60 c07e270c c078f080
[ 1167.493023] (0)[2053:indicator-bluet]7e60: dbdb7600 c0c59bb0 d8897e9c
d8897e78 c07e288c c07e2688 00010302
[ 1167.494314] (0)[2053:indicator-bluet]7e80: d883e0c0 0008 c07e2774
d8896000 d8897f6c d8897ea0 c0147b30 c07e2780
[ 1167.495605] (0)[2053:indicator-bluet]7ea0: d8896000 d9f1ed04 d8897ec4
d8897eb8 c07f98b0 c07f932c d8897ed4 d8897ec8
[ 1167.496895] (0)[2053:indicator-bluet]7ec0: c09abcb8 c09abcc4 c09abcd0
[ 1167.4981
[Dx-packages] [Bug 1348039] Re: shim does not implement 'Subscribe' method called by logind
https://github.com/desrt/systemd-shim/commit/1def7e9 ** Changed in: systemd-shim (Ubuntu) Status: Triaged => Fix Committed -- 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/1348039 Title: shim does not implement 'Subscribe' method called by logind Status in “systemd-shim” package in Ubuntu: Fix Committed Bug description: Get that error logged at the end of the dmesg file. That error seems to have no sad effect on the system: [ 30.793181] systemd-logind[1006]: Failed to enable subscription: No such method 'Subscribe' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-6ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 24 07:25:46 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+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 1348039] Re: shim does not implement 'Subscribe' method called by logind
Your dmesg talks about plymouth-upstart-bridge, which only exists under upstart. So I'm still convinced you were running upstart here, with systemd-shim. -- 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/1348039 Title: shim does not implement 'Subscribe' method called by logind Status in “systemd-shim” package in Ubuntu: Fix Committed Bug description: Get that error logged at the end of the dmesg file. That error seems to have no sad effect on the system: [ 30.793181] systemd-logind[1006]: Failed to enable subscription: No such method 'Subscribe' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-6ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 24 07:25:46 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+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 1348039] Re: shim does not implement 'Subscribe' method called by logind
I don't see this message; what do you do to trigger it? Anyway, I'll just test this with d-feet. -- 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/1348039 Title: shim does not implement 'Subscribe' method called by logind Status in “systemd-shim” package in Ubuntu: Fix Committed Bug description: Get that error logged at the end of the dmesg file. That error seems to have no sad effect on the system: [ 30.793181] systemd-logind[1006]: Failed to enable subscription: No such method 'Subscribe' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-6ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 24 07:25:46 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+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 1351815] Re: StartTransientUnit signature has changed in systemd 214
Meh, that doesn't actually work, logind complains about a signature mismatch. So indeed this will have to wait until we update systemd. ** Changed in: systemd-shim (Ubuntu) Status: Fix Committed => Triaged -- 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/1351815 Title: StartTransientUnit signature has changed in systemd 214 Status in “systemd-shim” package in Ubuntu: Triaged Bug description: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+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 1351815] Re: StartTransientUnit signature has changed in systemd 214
I committed https://github.com/desrt/systemd-shim/commit/b4f1dc0ca to advertise both APIs. ** Changed in: systemd-shim (Ubuntu) Status: Triaged => Fix Committed -- 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/1351815 Title: StartTransientUnit signature has changed in systemd 214 Status in “systemd-shim” package in Ubuntu: Fix Committed Bug description: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+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 1355966] Re: Implement AbandonScope (etc)
** Changed in: systemd-shim (Debian) Status: Unknown => 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/1355966 Title: Implement AbandonScope (etc) Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: New Bug description: Currently, logout produces the following error in upstart systems: systemd-logind[15351]: Failed to abandon scope session-c7.scope systemd-logind[15351]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc7_2escope Whlie the cgroup is being autoremoved when empty, the more important bug is that StopSession won't forcibly kill the cgroup. These methods should be added at some point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1355966/+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 1304434] Re: indicator-printers not working on Ubuntu 14.04
Stopped working Ubuntu 32bit latest kernel 3.13.0.33.39 latest indicator-printers 0.1.7+14.04.20140527-0ubuntu1 -- 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/1304434 Title: indicator-printers not working on Ubuntu 14.04 Status in Print Indicator: In Progress Status in “indicator-printers” package in Ubuntu: Fix Released Status in “indicator-printers” source package in Trusty: Fix Released Bug description: [Impact] The panel should have a print indicator as long as there are any print jobs queued or processed. Currently, this indicator never appears, even though printing works fine. This is because the service that listens to CUPS fails to register its D-Bus name (as of revision 68), which results in the panel component not finding the service. The attached branch fixes this by making the service register the name the panel expects. [Test Case] Print a document from any application and check whether the print indicator appears while it is printing. [Regression Potential] Almost none. The print indicator is not working at all right now, and the fix only touches that indicator. [Original Description] even after lates updates still no printer notifications in the panel . I checked and the package "indicator-printers" is correctly installed and the printer prints without problems. But, there is no notification icons on unity panel. I had no problems at all with 13.10 instead To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-printers/+bug/1304434/+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 1341562] Re: indicator-printers not working on Ubuntu 14.04
Stopped working Ubuntu 32bit latest kernel 3.13.0.33.39 latest indicator-printers 0.1.7+14.04.20140527-0ubuntu1 -- 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/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+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 1328646] Re: Clock out of sync on resume from suspend
** Branch linked: lp:~nick-dedekind/unity8/lp1328646 -- 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/1328646 Title: Clock out of sync on resume from suspend Status in The Date and Time Indicator: New Status in The Unity 8 shell: In Progress Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “qmenumodel” package in Ubuntu: Confirmed Bug description: When the device is resumed by pressing the power button and the device is not connected over USB the clock is out of sync You need another system to compare the time to verify this bug report, and make sure both clocks are in sync. TEST CASE 1. Unplug the device from its USB cable 2. Press the power button to switch to suspend mode or wait until it goes to suspend 3. Wait 2 or more minutes 4. Press the power button again to resume the device 5. Compare the time on the greeter and indicator with the time on the other system EXPECTED RESULT Clocks are in sync ACTUAL RESULT Time on the device is behind by several minutes. The use case are people who use their device as a watch. You usually resume it, check the time, suspend it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.88+14.10.20140606-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Tue Jun 10 19:11:42 2014 InstallationDate: Installed on 2014-06-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140610) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1234482] Re: systemd-shim crashed with SIGSEGV in power_unit_start()
I'm afraid this stack trace does not make any sense. It crashes in if (pu->action == POWER_SUSPEND) but the "pu" pointer is clearly initialized (as seen in the Stacktrace), and the very same pu->action is being used before already (and not modified in between). So I'm afraid with the current data this can't be investigated and fixed. Do you have a way to reproduce this crash? Did it happen several times, or just once? Did you see it with later Ubuntu versions? Thanks! ** Changed in: systemd-shim (Ubuntu) Status: Confirmed => Incomplete -- 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/1234482 Title: systemd-shim crashed with SIGSEGV in power_unit_start() Status in “systemd-shim” package in Ubuntu: Incomplete Bug description: Crashes on startup. Unknown why and dont see what problems it may, or may not be causing. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: systemd-shim 3+real-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sun Sep 29 19:38:40 2013 ExecutablePath: /usr/lib/i386-linux-gnu/systemd-shim InstallationDate: Installed on 2013-09-26 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130903) MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/systemd-shim ProcEnviron: Signal: 11 SourcePackage: systemd-shim StacktraceTop: ?? () ?? () ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: systemd-shim crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1234482/+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 1234482] Re: systemd-shim crashed with SIGSEGV in power_unit_start()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd-shim (Ubuntu) Status: New => Confirmed -- 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/1234482 Title: systemd-shim crashed with SIGSEGV in power_unit_start() Status in “systemd-shim” package in Ubuntu: Confirmed Bug description: Crashes on startup. Unknown why and dont see what problems it may, or may not be causing. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: systemd-shim 3+real-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sun Sep 29 19:38:40 2013 ExecutablePath: /usr/lib/i386-linux-gnu/systemd-shim InstallationDate: Installed on 2013-09-26 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130903) MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/systemd-shim ProcEnviron: Signal: 11 SourcePackage: systemd-shim StacktraceTop: ?? () ?? () ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: systemd-shim crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1234482/+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 1234482] Re: systemd-shim crashed with SIGSEGV in power_unit_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 systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1234482 Title: systemd-shim crashed with SIGSEGV in power_unit_start() Status in “systemd-shim” package in Ubuntu: Confirmed Bug description: Crashes on startup. Unknown why and dont see what problems it may, or may not be causing. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: systemd-shim 3+real-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sun Sep 29 19:38:40 2013 ExecutablePath: /usr/lib/i386-linux-gnu/systemd-shim InstallationDate: Installed on 2013-09-26 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130903) MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/systemd-shim ProcEnviron: Signal: 11 SourcePackage: systemd-shim StacktraceTop: ?? () ?? () ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: systemd-shim crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1234482/+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 1290604] Re: Crash at boot with 3.5.0-47-generic
Please attach a screenshot with the crash, it should show a traceback or other error. Thanks! ** Package changed: systemd-shim (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1290604 Title: Crash at boot with 3.5.0-47-generic Status in “linux” package in Ubuntu: Incomplete Bug description: Crash at Boot with this kernel. I am unsure whats causing it as I can't find anything in the log I reverted to linux- headers-3.5.0-46-generic and it solves my problem... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290604/+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 1299925] Re: systemd-shim crashed with SIGSEGV in g_slice_alloc()
*** This bug is a duplicate of bug 1234482 *** https://bugs.launchpad.net/bugs/1234482 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1234482 systemd-shim crashed with SIGSEGV in power_unit_start() -- 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/1299925 Title: systemd-shim crashed with SIGSEGV in g_slice_alloc() Status in “systemd-shim” package in Ubuntu: New Bug description: Ubuntu Trusty Tahr 14.04 trying to install winusb and GTK crash ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: systemd-shim 6-2bzr1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Sun Mar 30 18:19:02 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/systemd-shim InstallationDate: Installed on 2014-03-07 (23 days ago) InstallationMedia: It ProcCmdline: /usr/lib/x86_64-linux-gnu/systemd-shim ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f4ea475528a :mov 0x8(%rdx),%rbx PC (0x7f4ea475528a) ok source "0x8(%rdx)" (0x7f4e90004708) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: systemd-shim StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_new_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 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 Title: systemd-shim crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1299925/+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 1328884] Re: Can't Sustain Full Screen Flash Video while using Multiple Monitors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- 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/1328884 Title: Can't Sustain Full Screen Flash Video while using Multiple Monitors Status in Adobe Flash Plugin Tools: New Status in Chromium: New Status in The Mozilla Firefox Browser: New Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: I've been using Ubuntu desktop since April of 2007 (starting with version 7.04). This is the oldest unfixed bug I know of. When you have two monitors, if you maximize a youtube flash video on one monitor, any action you perform on the other monitor minimizes the video. It has always been impossible to watch a flash video full-screen on one monitor while preforming tasks on a second monitor. I reported this back in 2007, but couldn't find that bug report. Anyway, it is 7 years later, and the bug still persists. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jun 11 06:51:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:7001] InstallationDate: Installed on 2014-04-28 (43 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=41b9be5e-d0cf-4389-8320-5576d93a437c ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 7001 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv8 Notebook PC dmi.product.version: 04992224121000104 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jun 11 05:51:11 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1328884/+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 1353989] Re: Errors on cleaning up cgroups
*** This bug is a duplicate of bug 1355966 *** https://bugs.launchpad.net/bugs/1355966 ** This bug has been marked a duplicate of bug 1355966 Implement AbandonScope (etc) -- 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/1353989 Title: Errors on cleaning up cgroups Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: New Bug description: Problem Description -- Lot of systemd failure messages pops up on console as well as seen in dmesg ---uname output--- Linux u10vm14 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Power 8 ---Debugger--- A debugger is not configured Steps to Reproduce -- 1) Install Ubuntu 14.10 August 6th build 2) After the installation while logging in seen multiple systemd failed messages on console and on dmesg Failed messages: [ 58.564179] systemd-logind[1420]: Failed to enable subscription: No such method 'Subscribe' [ 58.576888] systemd-logind[1420]: New seat seat0. [ 58.580312] systemd-logind[1420]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 58.581059] systemd-logind[1420]: Failed to start user service: Unknown unit: user@1000.service [ 58.584561] systemd-logind[1420]: New session c1 of user ubuntu. [11293.015056] init: hvc0 main process ended, respawning [11293.045923] systemd-logind[1420]: Failed to abandon scope session-c1.scope [11293.046499] systemd-logind[1420]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [17818.110774] systemd-logind[1420]: Failed to start unit user@0.service: Unknown unit: user@0.service [17818.111944] systemd-logind[1420]: Failed to start user service: Unknown unit: user@0.service [17818.115571] systemd-logind[1420]: New session c2 of user root. [18812.879680] systemd-logind[1420]: New session 22 of user root. [18814.620794] systemd-logind[1420]: Failed to abandon scope session-22.scope [18814.622186] systemd-logind[1420]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2d22_2escope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1353989/+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 1263138] Re: systemd-shim does not terminate at computer shutdown
This was fixed a while ago already: Changes in version 5 = - write a sendsigs.omit.d file to prevent upstart from killing us during shutdown. This should fix the suspend-when-shutting-down issue once and for all. ** Changed in: systemd-shim (Ubuntu) Status: New => Fix Released -- 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/1263138 Title: systemd-shim does not terminate at computer shutdown Status in “systemd-shim” package in Ubuntu: Fix Released Bug description: 1) Ubuntu 13.10 Received this message on start up ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-shim 4-0ubuntu0.13.10 Uname: Linux 3.12.0-031200-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 19 13:45:25 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/systemd-shim InstallationDate: Installed on 2013-10-19 (61 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True OmitPids: 1130 941 755 11955 732 713 699 12012 819 719 12041 755 11955 732 713 699 12012 819 719 ProcCmdline: /usr/lib/x86_64-linux-gnu/systemd-shim ProcEnviron: SourcePackage: systemd-shim Title: systemd-shim does not terminate at computer shutdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1263138/+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 1355966] Re: Implement AbandonScope (etc)
** Bug watch added: Debian Bug tracker #756076 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076 ** Also affects: systemd-shim (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076 Importance: Unknown Status: Unknown ** Changed in: systemd-shim (Ubuntu) Status: Confirmed => Triaged -- 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/1355966 Title: Implement AbandonScope (etc) Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: Unknown Bug description: Currently, logout produces the following error in upstart systems: systemd-logind[15351]: Failed to abandon scope session-c7.scope systemd-logind[15351]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc7_2escope Whlie the cgroup is being autoremoved when empty, the more important bug is that StopSession won't forcibly kill the cgroup. These methods should be added at some point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1355966/+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 1193944] Re: systemd-shim doesn't respect /etc/default/halt setting
Fixed in https://github.com/desrt/systemd-shim/commit/21210f7fd Thanks for the report! ** Changed in: systemd-shim (Ubuntu) Status: New => Triaged ** Changed in: systemd-shim (Ubuntu) Importance: Undecided => Low ** Changed in: systemd-shim (Ubuntu) Status: Triaged => Fix Committed -- 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/1193944 Title: systemd-shim doesn't respect /etc/default/halt setting Status in “systemd-shim” package in Ubuntu: Fix Committed Bug description: Package: systemd-shim Version: 3+real-0ubuntu1 Very minor niggle: /sbin/poweroff is called on system halt regardless of the setting of "HALT" in /etc/default/halt. For consistency with calling shutdown directly, this variable probably ought to be inspected - or simply call /sbin.shutdown instead of poweroff. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1193944/+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 1254851] Re: qpdfview renders black pages after poppler update
** Package changed: systemd-shim (Ubuntu) => poppler (Ubuntu) -- 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/1254851 Title: qpdfview renders black pages after poppler update Status in “poppler” package in Ubuntu: Incomplete Bug description: qpdfview was working fine in 13.10, then I did an apt-get dist-upgrade qpdfview only renders black pages now. Suspect poppler library upgrade is the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1254851/+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 1286230] Re: 14e4:1713 [HP Compaq 6715s Notebook PC] Ethernet connection does not reactivate following Resume from Sleep
*** This bug is a duplicate of bug 1252121 *** https://bugs.launchpad.net/bugs/1252121 ** This bug has been marked a duplicate of bug 1252121 missing PrepareForSleep signal after resuming, causing networking to stay disabled -- 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/1286230 Title: 14e4:1713 [HP Compaq 6715s Notebook PC] Ethernet connection does not reactivate following Resume from Sleep Status in “systemd-shim” package in Ubuntu: New Bug description: Waking from Sleep, Wireless Connections resume without delay, but the Ethernet connection does not reactivate unless forced by command or by rebooting the system. the interface (very) occasionally resumes properly, but the reported condition occurs >80% of the time with current Ubuntu Release amd64 kernel. Re-plugging the network cable has no apparent effect. WORKAROUND: Restore all network connections until next Sleep: sudo service network-manager restart nmccurdy@gc-hpcompaqLaptop:~$ apt-cache policy network-manager network-manager: Installed: 0.9.8.0-0ubuntu22 Candidate: 0.9.8.0-0ubuntu22 Version table: *** 0.9.8.0-0ubuntu22 0 500 http://de.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Solution attempted to force wake of network-manager (Failed): Creating file: /etc/pm/sleep.d/network-manager-restart With contents: ### Start #!/bin/sh # This script gets NetworkManager out of suspend. case $1 in suspend|suspend_hybrid|hibernate) # No need to do anything here. ;; resume|thaw) nmcli nm sleep false ;; esac ### End Mainline Kernels also tested: 3.11.10-03111004 : Condition Exists 3.13.5-031305 : Condition Exists 3.14.0-031400rc4 : Inconclusive. System Too Unstable to Verify. Indicator Applet appears to show correct Icon, but System Crashes during final stages of waking process. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-17-generic 3.11.0-17.31 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nmccurdy 2362 F pulseaudio Date: Fri Feb 28 17:03:01 2014 HibernationDevice: RESUME=UUID=bfdf28bd-0398-4c14-b34f-938ed08d040b InstallationDate: Installed on 2014-01-14 (44 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Compaq 6715s (KE061ET#ABD) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic root=UUID=816b1999-49d9-4918-8e6b-35e9a4dfe229 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YTT Ver. F.0B dmi.board.name: 30C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.2D dmi.chassis.asset.tag: CNU8291MPN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YTTVer.F.0B:bd03/04/2008:svnHewlett-Packard:pnHPCompaq6715s(KE061ET#ABD):pvrF.0B:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.2D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6715s (KE061ET#ABD) dmi.product.version: F.0B dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1286230/+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 1296372] Re: network disabled 14.04 trusty
** Package changed: systemd-shim (Ubuntu) => network-manager (Ubuntu) -- 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/1296372 Title: network disabled 14.04 trusty Status in “network-manager” package in Ubuntu: New Bug description: I first downloaded the 3/20 build, then the 3/21 build both with the same problem I have no network connection at all. Both installs installed completely with no errors, they even connected to the network and downloaded the files it's programmed to download, which is why I really can't believe the network isn't working. I do use mobile broadband to connect, but it is connecting to the computer as regular wifi, not mobile broadband. I tried two Samsung, and one LG phone, all on wifi and usb connections with the same result, on an Acer Aspire laptop. When running iwconfig,ifconfig, and lshw -c network, they all show that the connection is coming in to the computer, however the network connection is disabled. Network Manager is not installed so that is no help, I'll have to make a manual connection then updating, and adding programs to correct the problem. Running "sudo ifup wlan0 up", returns the error "Ignore unknown init wlan0=wlan0, and ignore unknown up=up". Iwlist scan, shows "scannning is not capable, wlan0 is down", apport collect 126883 is not installed, "/sbin/ifconfig -a" shows all information is correct except connection is disabled. Hwinfo is not installed, neither is /sys/class/net. The computer is showing an ip address of 127.0.0.1 netmask 255.0.0.0, the phones are showing something like 10.74.26.171, 255.255.255.0, however my 13.10 Ubuntu on same computer has an address of 192.168.43.1, so network manager is compatible with the difference, but I don't think that the minimal services of this install can translate them. I have 13.10 and windows 7 both on the computer in addition to the 14.04, both other OS's, can connect both wirelessly and by usb0, so I know the hardware itself is good, I don't know if the right drivers are there. I think I have elimanated every possible problem except a software or driver problem. Unfortunately I can't update the network without the network. I've tried connection through wpa-supplicant, with no luck. I have spent three days trying to troubleshoot the issue with no luck. I tried using my 13.10 to download a .deb of network manager and installing with dpkg, however no matter what I did dpkg returned with an error of, "file does not exist". For some reason the network is disabled on this version, at least with mobile broadband wifi, and usb connections, there needs to be a way to update the system so you can connect and update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1296372/+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 1358436] Re: Indicator sound missing from unity panel
I'm not sure what the bug is here. The setting controls whether the sound menu is shown or not. If it is set to false, it is not visible. It can be controlled from the sound panel in System Settings. ** Changed in: indicator-sound (Ubuntu) Status: New => Invalid -- 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/1358436 Title: Indicator sound missing from unity panel Status in “indicator-sound” package in Ubuntu: Invalid Bug description: Indicator sound is missing from the panel. Restarting the panel service doesn't bring it up. Neither does a reboot. The menu reappeared only after toggling the dconf setting: gsettings set com.canonical.indicator.sound visible false gsettings set com.canonical.indicator.sound visible true ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 14:31:05 2014 InstallationDate: Installed on 2013-12-19 (242 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131218) SourcePackage: indicator-sound SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to utopic on 2014-05-09 (101 days ago) upstart.indicator-sound.log: (process:7458): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (process:12518): CRITICAL **: volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1358436/+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 1328646] Re: Clock out of sync on resume from suspend
** Changed in: unity8 Status: Triaged => In Progress -- 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/1328646 Title: Clock out of sync on resume from suspend Status in The Date and Time Indicator: New Status in The Unity 8 shell: In Progress Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “qmenumodel” package in Ubuntu: Confirmed Bug description: When the device is resumed by pressing the power button and the device is not connected over USB the clock is out of sync You need another system to compare the time to verify this bug report, and make sure both clocks are in sync. TEST CASE 1. Unplug the device from its USB cable 2. Press the power button to switch to suspend mode or wait until it goes to suspend 3. Wait 2 or more minutes 4. Press the power button again to resume the device 5. Compare the time on the greeter and indicator with the time on the other system EXPECTED RESULT Clocks are in sync ACTUAL RESULT Time on the device is behind by several minutes. The use case are people who use their device as a watch. You usually resume it, check the time, suspend it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.88+14.10.20140606-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Tue Jun 10 19:11:42 2014 InstallationDate: Installed on 2014-06-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140610) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1291110] Re: launcher not auto-hiding
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- 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/1291110 Title: launcher not auto-hiding Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: 14.04 gnome launcher doesnt autohide even after turning the autohide option on and off To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291110/+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 1358293] Re: Turning off Bluetooth in the Indicator Crashes the Phone
** Changed in: indicator-bluetooth (Ubuntu)
Status: Confirmed => In Progress
--
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/1358293
Title:
Turning off Bluetooth in the Indicator Crashes the Phone
Status in “indicator-bluetooth” package in Ubuntu:
In Progress
Bug description:
Steps:
1. Enable a bluetooth headset or earbuds
2. Start the music player and play an album
3. Confirm that the music is playing
4. Turn off the screen and listen to the music for a few tracks
5. Turn on the screen and pause the music player
6. Pull down the indicator and try to disable bluetooth
The indicator freezes for a time, then the whole phone reboots
root@ubuntu-phablet:/# cat /proc/last_kmsg
ram console header, hw_status: 2, fiq step 40.
bin log 0.
x104) from [] (dump_stack+0x20/0x24)
[ 1164.156265] (1)[2070:unity8][] (dump_stack+0x20/0x24) from
[] (handle_IPI+0x21c/0x250)
[ 1164.157473] (1)[2070:unity8][] (handle_IPI+0x21c/0x250) from
[] (do_IPI+0x18/0x1c)
[ 1164.158638] (1)[2070:unity8][] (do_IPI+0x18/0x1c) from
[] (__irq_usr+0x34/0xc0)
[ 1164.160851] (0)[2053:indicator-bluet]init emmc for ipanic dump
[ 1164.175534] (0)[2053:indicator-bluet][pll]0xF020924C = 0x8001
[ 1164.176285] (0)[2053:indicator-bluet][pll]0xF0209240 = 0x121
[ 1164.176992] (0)[2053:indicator-bluet][mux] 0xF060 = 0x1818100
[ 1164.177749] (0)[2053:indicator-bluet][mux] 0xF070 = 0x81808101
[ 1164.178519] (0)[2053:indicator-bluet][clk] 0xF0003010 = 0x0
[ 1164.179213] (0)[2053:indicator-bluet][clk] 0xF0003018 = 0x2fecffd
[ 1164.180068] (0)[2053:indicator-bluet]send cmd0
[ 1164.184692] (0)[2053:indicator-bluet]cmd1: resp(0xff8080), i=500
[ 1164.185430] (0)[2053:indicator-bluet]send cmd0
[ 1164.213984] (0)[2053:indicator-bluet]cmd1: resp(0xc0ff8080), i=498
[ 1164.216746] (0)[2053:indicator-bluet]resp: 0x11010030 0x30384739
0x32009acc 0xa9373149
[ 1164.240817] (0)[2053:indicator-bluet]read fifo done, wait xfer_compl
interrupt
[ 1164.241712] (0)[2053:indicator-bluet]emmc offset (0x5c00)
[ 1164.244389] (0)[2053:indicator-bluet]init eMMC success
[ 1167.466826] (0)[2053:indicator-bluet]card_dump_func_write failed (18),
size: 0x58000
[ 1167.467803] (0)[2053:indicator-bluet]CPU: 0Tainted: GW
(3.4.67 #1)
[ 1167.468745] (0)[2053:indicator-bluet]PC is at l2cap_chan_destroy+0x3c/0x88
[ 1167.469599] (0)[2053:indicator-bluet]LR is at __raw_write_lock+0x34/0xa8
[ 1167.470437] (0)[2053:indicator-bluet]pc : []lr :
[]psr: 600f0013
[ 1167.470444] (0)[2053:indicator-bluet]sp : d8897d68 ip : 00100100 fp :
d8897d7c
[ 1167.472412] (0)[2053:indicator-bluet]r10: cc583a20 r9 : cf9db800 r8 :
c74e1300
[ 1167.473335] (0)[2053:indicator-bluet]r7 : 0067 r6 : c74e13bc r5 :
cc58380c r4 : cc583800
[ 1167.474419] (0)[2053:indicator-bluet]r3 : 00200200 r2 : 00100100 r1 :
00200200 r0 : c1128f40
[ 1167.475505] (0)[2053:indicator-bluet]Flags: nZCv IRQs on FIQs on Mode
SVC_32 ISA ARM Segment user
[ 1167.476664] (0)[2053:indicator-bluet]Control: 10c5387d Table: 8ddd806a
DAC: 0015
[ 1167.480769] (0)[2053:indicator-bluet]Process indicator-bluet (pid: 2053,
stack limit = 0xd8896300)
[ 1167.481881] (0)[2053:indicator-bluet]Stack: (0xd8897d68 to 0xd8898000)
[ 1167.482697] (0)[2053:indicator-bluet]7d60: 0009
cf548400 d8897d94 d8897d80 c07ac5b8 c07a6aac
[ 1167.483989] (0)[2053:indicator-bluet]7d80: 0002 cc583800 d8897da4
d8897d98 c07ac690 c07ac580 d8897ddc d8897da8
[ 1167.485279] (0)[2053:indicator-bluet]7da0: c07a2fc8 c07ac684 c74e13c4
d00bf400 d8897ddc d00bf400 d6dd6d00 d6dd6d00
[ 1167.486570] (0)[2053:indicator-bluet]7dc0: 0009 d6dd6808 d8897f78
d6dd6828 d8897df4 d8897de0 c07aa9dc c07a2f0c
[ 1167.487861] (0)[2053:indicator-bluet]7de0: d6dd6cec d00bf400 d8897e14
d8897df8 c0793444 c07aa9bc d6dd6800 d6dd6ecc
[ 1167.489151] (0)[2053:indicator-bluet]7e00: 0008 d6dd6ca0 d8897e4c
d8897e18 c078ee50 c07933a8 d8897e34 c07f9818
[ 1167.490442] (0)[2053:indicator-bluet]7e20: d8897e4c dbdb7600 0001
0008 d883e0c0 0008 d8897f78 be9d7e48
[ 1167.491733] (0)[2053:indicator-bluet]7e40: d8897e5c d8897e50 c078f094
c078ed90 d8897e74 d8897e60 c07e270c c078f080
[ 1167.493023] (0)[2053:indicator-bluet]7e60: dbdb7600 c0c59bb0 d8897e9c
d8897e78 c07e288c c07e2688 00010302
[ 1167.494314] (0)[2053:indicator-bluet]7e80: d883e0c0 0008 c07e2774
d8896000 d8897f6c d8897ea0 c0147b30 c07e2780
[ 1167.495605] (0)[2053:indicator-bluet]7ea0: d8896000 d9f1ed04 d8897ec4
d8897eb8 c07f98b0 c07f932c d8897ed4 d8897ec8
[ 1167.496895] (0)[2053:indicator-bluet]7ec0: c09abcb8 c09abcc4 c09abcd0
[ 1167.498186] (0)[2053:indicator-bluet]7ee0:
be9d7f2c d8897fac d8897f00 c00083d4
[Dx-packages] [Bug 1358293] Re: Turning off Bluetooth in the Indicator Crashes the Phone
** Also affects: indicator-bluetooth
Importance: Undecided
Status: New
** No longer affects: indicator-bluetooth
--
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/1358293
Title:
Turning off Bluetooth in the Indicator Crashes the Phone
Status in “indicator-bluetooth” package in Ubuntu:
Confirmed
Bug description:
Steps:
1. Enable a bluetooth headset or earbuds
2. Start the music player and play an album
3. Confirm that the music is playing
4. Turn off the screen and listen to the music for a few tracks
5. Turn on the screen and pause the music player
6. Pull down the indicator and try to disable bluetooth
The indicator freezes for a time, then the whole phone reboots
root@ubuntu-phablet:/# cat /proc/last_kmsg
ram console header, hw_status: 2, fiq step 40.
bin log 0.
x104) from [] (dump_stack+0x20/0x24)
[ 1164.156265] (1)[2070:unity8][] (dump_stack+0x20/0x24) from
[] (handle_IPI+0x21c/0x250)
[ 1164.157473] (1)[2070:unity8][] (handle_IPI+0x21c/0x250) from
[] (do_IPI+0x18/0x1c)
[ 1164.158638] (1)[2070:unity8][] (do_IPI+0x18/0x1c) from
[] (__irq_usr+0x34/0xc0)
[ 1164.160851] (0)[2053:indicator-bluet]init emmc for ipanic dump
[ 1164.175534] (0)[2053:indicator-bluet][pll]0xF020924C = 0x8001
[ 1164.176285] (0)[2053:indicator-bluet][pll]0xF0209240 = 0x121
[ 1164.176992] (0)[2053:indicator-bluet][mux] 0xF060 = 0x1818100
[ 1164.177749] (0)[2053:indicator-bluet][mux] 0xF070 = 0x81808101
[ 1164.178519] (0)[2053:indicator-bluet][clk] 0xF0003010 = 0x0
[ 1164.179213] (0)[2053:indicator-bluet][clk] 0xF0003018 = 0x2fecffd
[ 1164.180068] (0)[2053:indicator-bluet]send cmd0
[ 1164.184692] (0)[2053:indicator-bluet]cmd1: resp(0xff8080), i=500
[ 1164.185430] (0)[2053:indicator-bluet]send cmd0
[ 1164.213984] (0)[2053:indicator-bluet]cmd1: resp(0xc0ff8080), i=498
[ 1164.216746] (0)[2053:indicator-bluet]resp: 0x11010030 0x30384739
0x32009acc 0xa9373149
[ 1164.240817] (0)[2053:indicator-bluet]read fifo done, wait xfer_compl
interrupt
[ 1164.241712] (0)[2053:indicator-bluet]emmc offset (0x5c00)
[ 1164.244389] (0)[2053:indicator-bluet]init eMMC success
[ 1167.466826] (0)[2053:indicator-bluet]card_dump_func_write failed (18),
size: 0x58000
[ 1167.467803] (0)[2053:indicator-bluet]CPU: 0Tainted: GW
(3.4.67 #1)
[ 1167.468745] (0)[2053:indicator-bluet]PC is at l2cap_chan_destroy+0x3c/0x88
[ 1167.469599] (0)[2053:indicator-bluet]LR is at __raw_write_lock+0x34/0xa8
[ 1167.470437] (0)[2053:indicator-bluet]pc : []lr :
[]psr: 600f0013
[ 1167.470444] (0)[2053:indicator-bluet]sp : d8897d68 ip : 00100100 fp :
d8897d7c
[ 1167.472412] (0)[2053:indicator-bluet]r10: cc583a20 r9 : cf9db800 r8 :
c74e1300
[ 1167.473335] (0)[2053:indicator-bluet]r7 : 0067 r6 : c74e13bc r5 :
cc58380c r4 : cc583800
[ 1167.474419] (0)[2053:indicator-bluet]r3 : 00200200 r2 : 00100100 r1 :
00200200 r0 : c1128f40
[ 1167.475505] (0)[2053:indicator-bluet]Flags: nZCv IRQs on FIQs on Mode
SVC_32 ISA ARM Segment user
[ 1167.476664] (0)[2053:indicator-bluet]Control: 10c5387d Table: 8ddd806a
DAC: 0015
[ 1167.480769] (0)[2053:indicator-bluet]Process indicator-bluet (pid: 2053,
stack limit = 0xd8896300)
[ 1167.481881] (0)[2053:indicator-bluet]Stack: (0xd8897d68 to 0xd8898000)
[ 1167.482697] (0)[2053:indicator-bluet]7d60: 0009
cf548400 d8897d94 d8897d80 c07ac5b8 c07a6aac
[ 1167.483989] (0)[2053:indicator-bluet]7d80: 0002 cc583800 d8897da4
d8897d98 c07ac690 c07ac580 d8897ddc d8897da8
[ 1167.485279] (0)[2053:indicator-bluet]7da0: c07a2fc8 c07ac684 c74e13c4
d00bf400 d8897ddc d00bf400 d6dd6d00 d6dd6d00
[ 1167.486570] (0)[2053:indicator-bluet]7dc0: 0009 d6dd6808 d8897f78
d6dd6828 d8897df4 d8897de0 c07aa9dc c07a2f0c
[ 1167.487861] (0)[2053:indicator-bluet]7de0: d6dd6cec d00bf400 d8897e14
d8897df8 c0793444 c07aa9bc d6dd6800 d6dd6ecc
[ 1167.489151] (0)[2053:indicator-bluet]7e00: 0008 d6dd6ca0 d8897e4c
d8897e18 c078ee50 c07933a8 d8897e34 c07f9818
[ 1167.490442] (0)[2053:indicator-bluet]7e20: d8897e4c dbdb7600 0001
0008 d883e0c0 0008 d8897f78 be9d7e48
[ 1167.491733] (0)[2053:indicator-bluet]7e40: d8897e5c d8897e50 c078f094
c078ed90 d8897e74 d8897e60 c07e270c c078f080
[ 1167.493023] (0)[2053:indicator-bluet]7e60: dbdb7600 c0c59bb0 d8897e9c
d8897e78 c07e288c c07e2688 00010302
[ 1167.494314] (0)[2053:indicator-bluet]7e80: d883e0c0 0008 c07e2774
d8896000 d8897f6c d8897ea0 c0147b30 c07e2780
[ 1167.495605] (0)[2053:indicator-bluet]7ea0: d8896000 d9f1ed04 d8897ec4
d8897eb8 c07f98b0 c07f932c d8897ed4 d8897ec8
[ 1167.496895] (0)[2053:indicator-bluet]7ec0: c09abcb8 c09abcc4 c09abcd0
[ 1167.498186] (0)[2053:indicator-bluet]7ee0:
