[Dx-packages] [Bug 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled
And, that's also on a Nexus 4, using the stable releases. Failed again this morning on OTA-13. -- 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/1554504 Title: Calendar reminder does not wake phone when airplane mode is enabled Status in Canonical System Image: Incomplete Status in indicator-datetime package in Ubuntu: Incomplete Bug description: If airplane mode is enabled, the phone seems to go into a deep sleep where it doesn't wake up for a calendar reminder. The reminder does not sound until the power button is pressed to wake the phone, in some cases this has been more than an hour after the reminder was scheduled for. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled
Since filing this bug, the issue has only got worse. It has been 100% reproducible for me for the past couple of months. I have a calendar reminder to go off at 8am. Every morning, it only goes off when I actually wake up the phone myself, in some cases this has been over an hour past the time it was supposed to remind me. The only time it successfully works, is if I have woken the phone a few minutes early (presumably the phone doesn't go back to a deep sleep for a few minutes or something). -- 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/1554504 Title: Calendar reminder does not wake phone when airplane mode is enabled Status in Canonical System Image: Incomplete Status in indicator-datetime package in Ubuntu: Incomplete Bug description: If airplane mode is enabled, the phone seems to go into a deep sleep where it doesn't wake up for a calendar reminder. The reminder does not sound until the power button is pressed to wake the phone, in some cases this has been more than an hour after the reminder was scheduled for. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
Fixed with OTA-13. Thank you. -- 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/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in powerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1573115] Re: No Speakers Sound in Ubuntu 16.04
Bug affects me: Using Alsamixer, the Headphone setting controls speaker volume, while the Speaker setting controls digital volume -- 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/1573115 Title: No Speakers Sound in Ubuntu 16.04 Status in compiz-plugins-main package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 16.04 and I'm having a problem with my audio device. *The internal mic is working properly *The external output (headphones) is working properly too. *But the internal speakers doesn't work. I tried on the live version of 16.04 and I had the same issue. Information of my laptop: lspci -v: 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Dell 6 Series/C200 Series Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 39 Memory at f7f0 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel aplay -l: Lista de PLAYBACK dispositivos hardware tarjeta 0: PCH [HDA Intel PCH], dispositivo 0: Generic Analog [Generic Analog] Subdispositivos: 1/1 Subdispositivo #0: subdevice #0 tarjeta 0: PCH [HDA Intel PCH], dispositivo 3: Generic Digital [Generic Digital] Subdispositivos: 1/1 Subdispositivo #0: subdevice #0 Attached you can see the alsamixer configuration which shows the speaker volume. In capture view the audio is also in 100% I have no idea how to solve it. I used the same laptop with 14.04LTS without this problem. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1573115/+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 1623768] Re: Adapt to new Totem icon name
This bug was fixed in the package moka-icon-theme - 5.3.2-2 Sponsored for fossfreedom (fossfreedom) --- moka-icon-theme (5.3.2-2) unstable; urgency=medium * cherry-pick upstream patches - fix GTK+3.22 and GTK+3.20 based apps not displaying correctly due to upstream changing their .desktop exec=icon names - fix ubuntu-software, ImageMagik and Guake icon display * Packaging Changes: - update maintainer email address -- David Mohammed Sun, 25 Sep 2016 10:48:43 +0100 ** Also affects: moka-icon-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: moka-icon-theme (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1623768 Title: Adapt to new Totem icon name Status in humanity-icon-theme package in Ubuntu: New Status in lubuntu-artwork package in Ubuntu: Fix Committed Status in moka-icon-theme package in Ubuntu: Fix Released Status in ubuntukylin-theme package in Ubuntu: New Status in xubuntu-artwork package in Ubuntu: Fix Committed Bug description: Totem has changed its icon name for easier integration with flatpak -Icon=totem +Icon=org.gnome.Totem If your icon theme will be used in Ubuntu 16.04 LTS also, then I recommend making a symlink from the totem icon to the new org.gnome.Totem icon. Alternatively, you could drop the icon and let users use the high resolution icons shipped by Totem itself. See also bug 1618138 which lists some other app icon name changes but those icons aren't shipped in all themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+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 1597473] Re: [MIR] Indicator Transfer
Override component to main indicator-transfer 0.2+16.10.20160808.1-0ubuntu1 in yakkety: universe/misc -> main indicator-transfer 0.2+16.10.20160808.1-0ubuntu1 in yakkety amd64: universe/misc/optional/100% -> main indicator-transfer 0.2+16.10.20160808.1-0ubuntu1 in yakkety arm64: universe/misc/optional/100% -> main indicator-transfer 0.2+16.10.20160808.1-0ubuntu1 in yakkety armhf: universe/misc/optional/100% -> main indicator-transfer 0.2+16.10.20160808.1-0ubuntu1 in yakkety i386: universe/misc/optional/100% -> main indicator-transfer 0.2+16.10.20160808.1-0ubuntu1 in yakkety powerpc: universe/misc/optional/100% -> main indicator-transfer 0.2+16.10.20160808.1-0ubuntu1 in yakkety ppc64el: universe/misc/optional/100% -> main indicator-transfer-download-manager 0.2+16.10.20160808.1-0ubuntu1 in yakkety amd64: universe/misc/optional/100% -> main indicator-transfer-download-manager 0.2+16.10.20160808.1-0ubuntu1 in yakkety arm64: universe/misc/optional/100% -> main indicator-transfer-download-manager 0.2+16.10.20160808.1-0ubuntu1 in yakkety armhf: universe/misc/optional/100% -> main indicator-transfer-download-manager 0.2+16.10.20160808.1-0ubuntu1 in yakkety i386: universe/misc/optional/100% -> main indicator-transfer-download-manager 0.2+16.10.20160808.1-0ubuntu1 in yakkety powerpc: universe/misc/optional/100% -> main indicator-transfer-download-manager 0.2+16.10.20160808.1-0ubuntu1 in yakkety ppc64el: universe/misc/optional/100% -> main libindicator-transfer-dev 0.2+16.10.20160808.1-0ubuntu1 in yakkety amd64: universe/libdevel/optional/100% -> main libindicator-transfer-dev 0.2+16.10.20160808.1-0ubuntu1 in yakkety arm64: universe/libdevel/optional/100% -> main libindicator-transfer-dev 0.2+16.10.20160808.1-0ubuntu1 in yakkety armhf: universe/libdevel/optional/100% -> main libindicator-transfer-dev 0.2+16.10.20160808.1-0ubuntu1 in yakkety i386: universe/libdevel/optional/100% -> main libindicator-transfer-dev 0.2+16.10.20160808.1-0ubuntu1 in yakkety powerpc: universe/libdevel/optional/100% -> main libindicator-transfer-dev 0.2+16.10.20160808.1-0ubuntu1 in yakkety ppc64el: universe/libdevel/optional/100% -> main libindicator-transfer0 0.2+16.10.20160808.1-0ubuntu1 in yakkety amd64: universe/libs/optional/100% -> main libindicator-transfer0 0.2+16.10.20160808.1-0ubuntu1 in yakkety arm64: universe/libs/optional/100% -> main libindicator-transfer0 0.2+16.10.20160808.1-0ubuntu1 in yakkety armhf: universe/libs/optional/100% -> main libindicator-transfer0 0.2+16.10.20160808.1-0ubuntu1 in yakkety i386: universe/libs/optional/100% -> main libindicator-transfer0 0.2+16.10.20160808.1-0ubuntu1 in yakkety powerpc: universe/libs/optional/100% -> main libindicator-transfer0 0.2+16.10.20160808.1-0ubuntu1 in yakkety ppc64el: universe/libs/optional/100% -> main 25 publications overridden. ** Changed in: indicator-transfer (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-transfer in Ubuntu. https://bugs.launchpad.net/bugs/1597473 Title: [MIR] Indicator Transfer Status in indicator-transfer package in Ubuntu: Fix Released Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has both unit tests and integration tests. [Dependencies] Most dependencies are already in main with the exception of the following: * cppcheck (build dep only) * google-mock (build dep only) [Standards compliance] * This package uses cmake and is properly translated. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-transfer/+bug/1597473/+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 1623768] Re: Adapt to new Totem icon name
** Branch linked: lp:~jbicha/+junk/humanity-adapt-to-new-totem-icon-name -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1623768 Title: Adapt to new Totem icon name Status in humanity-icon-theme package in Ubuntu: Fix Committed Status in lubuntu-artwork package in Ubuntu: Fix Committed Status in moka-icon-theme package in Ubuntu: Fix Released Status in ubuntukylin-theme package in Ubuntu: New Status in xubuntu-artwork package in Ubuntu: Fix Committed Bug description: Totem has changed its icon name for easier integration with flatpak -Icon=totem +Icon=org.gnome.Totem If your icon theme will be used in Ubuntu 16.04 LTS also, then I recommend making a symlink from the totem icon to the new org.gnome.Totem icon. Alternatively, you could drop the icon and let users use the high resolution icons shipped by Totem itself. See also bug 1618138 which lists some other app icon name changes but those icons aren't shipped in all themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+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 1623768] Re: Adapt to new Totem icon name
** Changed in: humanity-icon-theme (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1623768 Title: Adapt to new Totem icon name Status in humanity-icon-theme package in Ubuntu: Fix Committed Status in lubuntu-artwork package in Ubuntu: Fix Committed Status in moka-icon-theme package in Ubuntu: Fix Released Status in ubuntukylin-theme package in Ubuntu: New Status in xubuntu-artwork package in Ubuntu: Fix Committed Bug description: Totem has changed its icon name for easier integration with flatpak -Icon=totem +Icon=org.gnome.Totem If your icon theme will be used in Ubuntu 16.04 LTS also, then I recommend making a symlink from the totem icon to the new org.gnome.Totem icon. Alternatively, you could drop the icon and let users use the high resolution icons shipped by Totem itself. See also bug 1618138 which lists some other app icon name changes but those icons aren't shipped in all themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+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 1627935] Re: unity-scope-loader crashed with SIGSEGV in malloc_consolidate()
*** This bug is a duplicate of bug 1624683 *** https://bugs.launchpad.net/bugs/1624683 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1624683, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1627935/+attachment/4749154/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1627935/+attachment/4749156/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1627935/+attachment/4749158/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1627935/+attachment/4749159/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1627935/+attachment/4749160/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1627935/+attachment/4749161/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1627935/+attachment/4749162/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1624683 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1627935 Title: unity-scope-loader crashed with SIGSEGV in malloc_consolidate() Status in libunity package in Ubuntu: New Bug description: Not sure what happened. I had just installed Chrome browser. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: libunity9 7.1.4+16.10.20160516-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 01:49:31 2016 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2016-09-27 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f553d8c3ef9 : cmp 0x18(%r10),%rbx PC (0x7f553d8c3ef9) ok source "0x18(%r10)" (0xd7034018) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: malloc_consolidate (av=av@entry=0x7f553dc04b00 ) at malloc.c:4210 _int_malloc (av=av@entry=0x7f553dc04b00 , bytes=bytes@entry=4096) at malloc.c:3485 __GI___libc_malloc (bytes=4096) at malloc.c:2925 g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 Title: unity-scope-loader crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1627935/+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
