[Dx-packages] [Bug 1364647] Re: [System Settings] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used
I don't know why this was assigned to me again. I'm not involved with the design of the Clock app, and I've already made a suggestion. ** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = (unassigned) ** Summary changed: - [System Settings] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used + Can't hear clock alarm when headphones are plugged in but not in your ears ** Description changed: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- - Calls and Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. + Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. + + (The equivalent for the ringtone is bug 1364647.) -- 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/1364647 Title: Can't hear clock alarm when headphones are plugged in but not in your ears Status in Ubuntu Clock App: Incomplete Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. (The equivalent for the ringtone is bug 1364647.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1364647/+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 1463332] Re: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus!
Feedback since the #4 commands: after a cold reboot, the fts.index have been rebuilt, and journalctl no more show the reported bug error. That's it -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1463332 Title: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus! Status in zeitgeist package in Ubuntu: Confirmed Bug description: get that error logged into journalctl: org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING **: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: zeitgeist-datahub 0.9.14-2.2ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Tue Jun 9 11:32:35 2015 SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1463332/+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 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears
bug #1483888 has been reported about the ringtone issue ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: ubuntu-clock-app Status: Incomplete = Invalid ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High ** Changed in: pulseaudio (Ubuntu) Importance: Undecided = High ** Changed in: ubuntu-ux Status: Triaged = Fix Committed -- 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/1364647 Title: Can't hear clock alarm when headphones are plugged in but not in your ears Status in Canonical System Image: New Status in Ubuntu Clock App: Invalid Status in Ubuntu UX: Fix Committed Status in indicator-datetime package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. (The equivalent for the ringtone is bug 1364647.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1364647/+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 1427566] Re: [Clock][UX] Add timers functionality
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- 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/1427566 Title: [Clock][UX] Add timers functionality Status in Indicator Date and Time: New Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! Before we will implement this we need to fix: https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1386111] Re: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04
I confirm that removing appmenu-qt5 package solves the issue. -- 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/1386111 Title: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04 Status in Unity: New Status in eclipse package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase package in Ubuntu: Confirmed Status in texmaker package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work. E.g. F1 for quick compile, Strg+F for searching ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: texmaker 4.3-1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 11:01:56 2014 InstallationDate: Installed on 2014-04-18 (191 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: texmaker UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386111/+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 1420630] Re: indicator-sound menu icon disappeared after volume down to zero
** Changed in: indicator-sound (Ubuntu) Status: Triaged = Fix Released -- 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/1420630 Title: indicator-sound menu icon disappeared after volume down to zero Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Incomplete Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound source package in Trusty: New Bug description: On the HP commercial notebooks, there're function keys to control volume. The menu volume icon will be disappeared if we volume down (with key combination: Fn+F6, you can also emulate the keys with xdotool key XF86AudioLowerVolume) to zero then logout and back in. But if we just zero down volume(with the single volume on/off button), then logout and back in, the volume icon is still there. This issue is fixed with installing indicator- sound_12.10.2+14.10.20141010-0ubuntu1(Utopic) Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Feb 11 14:18:50 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-trusty-amd64-20150114-3 InstallationDate: Installed on 2015-01-29 (13 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20150114-08:50 SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1420630/+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 1483014] Re: Unity Launcher and Terminal Windows
** Tags added: 16.04-hit-list -- 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/1483014 Title: Unity Launcher and Terminal Windows Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Using Unity Launcher to bring-up Terminal in order to switch between 6 terminal windows, clicking (or alt-tabbing) on the item will bring up the wrong window. When that happens, the next time you go through the selection process and click on the one you want, it will bring the window to the foreground, but it will be missing window decoration? or window titles, and borders.. etc Screenshot provided. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1483014/+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 1483014] Re: Unity Launcher and Terminal Windows
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (azzar1) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (azzar1) ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity Milestone: None = 7.3.3 -- 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/1483014 Title: Unity Launcher and Terminal Windows Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Using Unity Launcher to bring-up Terminal in order to switch between 6 terminal windows, clicking (or alt-tabbing) on the item will bring up the wrong window. When that happens, the next time you go through the selection process and click on the one you want, it will bring the window to the foreground, but it will be missing window decoration? or window titles, and borders.. etc Screenshot provided. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1483014/+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 1458897] Re: [mako] When starting/seeking music the volume notification appears
This bug isn't tracking volume changes, it is just tracking that fact that the notification bubble with the volume bar sometimes appears when you start/stop/seek a track, therefore it is not the same as the bug 1418210. Also this still occurs for me on the latest rc-proposed, not all the time but enough to be annoying. -- 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/1458897 Title: [mako] When starting/seeking music the volume notification appears Status in indicator-sound package in Ubuntu: Incomplete Bug description: What happened: 1) Open the music-app 2) Start playing a track or seek the playing track 3) Observe that the volume notification appears What was expected to happen: 1) At step 3 the volume notification should not be shown $ system-image-cli -i current build number: 194 device name: mako channel: ubuntu-touch/devel-proposed-customized-here alias: ubuntu-touch/vivid-proposed-customized-here last update: 2015-05-14 21:20:36 version version: 194 version ubuntu: 20150514 version device: 20150210 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1458897/+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 1478506] Re: Apps change audio output role all the time
** Branch linked: lp:~xavi-garcia-mena/indicator-sound/lp-1478506-use- role-volume -- 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/1478506 Title: Apps change audio output role all the time Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: To reproduce, install the app Maroon in trouble from the app store and play it a little with having sound enabled. Press the volume down hardware button on the phone. It will temporarily decrease the volume. However, whenever a new item comes into the scene, it will be on 100% volume again. Setting the system volume to 0 should keep everything at 0. Please note that this app does *not* have any code to set the volume! Also this app is one of the upstream Qt QML example demo apps, so this is really how QML apps are supposed to work (in other words, it is not a badly implemented app, but really an issue in the system) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506/+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 1396700] Re: Indicator needs to be updated to bluez5
** Branch linked: lp:ubuntu/wily-proposed/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/1396700 Title: Indicator needs to be updated to bluez5 Status in Canonical System Image: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Bug description: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for details To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1396700/+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 1483388] Re: System randomly won't complete boot
** Summary changed: - Boot gets stuck at purple Ubuntu screen forever if running from battery + System randomly won't complete boot -- 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/1483388 Title: System randomly won't complete boot Status in unity package in Ubuntu: New Bug description: I am not sure at all what package this bug is; I report it against Unity because I get to see the purple screen... Steps to reproduce: - turn on the laptop while not connected to AC power, but with more than enough battery charge (tested with battery completely charged) Expected result: should boot fine Observed result: When the purple Ubuntu loading screen appears and the four dots below the word Ubuntu are all filled in red, the system gets stuck at that screen for fucking ever. No matter how many times I retry, it will always remain stuck there. If I connect the charger and reboot, then it works fine. This REGRESSION has appeared after some recent automatic updates. This didn't use to happen before. I had booted with battery power thousands of time, though it's not something that I do very often so i can't tell exactly when the regression appeared. Before the purple screen appears, for a fraction of a second I've been able to see a black screen full of messages, probably error messages, while normally (when boot works fine) there would only be one usb-related error message. Please let me know from which log I can retrieve those error messages so that I can post them here. Don't tell me to update the bios, because this used to work on the very same machine, so the issue is obviously in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150603-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Aug 10 21:15:32 2015 InstallationDate: Installed on 2013-10-11 (668 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1483388/+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 1427566] Re: [Clock][UX] Add timers functionality
** Changed in: ubuntu-clock-app Milestone: 3.5 = 3.6 -- 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/1427566 Title: [Clock][UX] Add timers functionality Status in Indicator Date and Time: New Status in Ubuntu Clock App: Triaged Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I'm greatly missing timers from the clock app. In Android I use them all the time for fixed time periods (laundry/bread/cooking/tea is ready, etc.), and it's rather inconvenient to have to create a gazillion alarms at a fixed time for these. I'm not sure why they got removed, but could we have them back please? Thanks for considering! Before we will implement this we need to fix: https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1483388] Re: System randomly won't complete boot
** Attachment added: IMG_20150813_210905185.jpg https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1483388/+attachment/371/+files/IMG_20150813_210905185.jpg ** Description changed: - I am not sure at all what package this bug is; I report it against Unity - because I get to see the purple screen... + Since the incomplete/broken fix for #1431753 was released, and hence + NVidia drivers version 340 were installed AND enabled on my machine + (where previously I had 331 installed and disabled) this has started + happening: - Steps to reproduce: - - turn on the laptop while not connected to AC power, but with more than enough battery charge (tested with battery completely charged) + About 50-75% of the times (very rough estimation), when I boot, the boot + gets stuck at the purple screen with the Ubuntu word with four red + dots below. - Expected result: - should boot fine + Systematically, when this happens, that screen is preceded by a black screen with a lot of errors, of which I attach a picture (yes, I know, it's unreadable, but it's all I can do). + If anybody tells me in which log files those errors can be found, I will be happy to attach them. - Observed result: - When the purple Ubuntu loading screen appears and the four dots below the word Ubuntu are all filled in red, the system gets stuck at that screen for fucking ever. - No matter how many times I retry, it will always remain stuck there. - If I connect the charger and reboot, then it works fine. + Normally, that is, when the issue does not happen and the boot is + succesful, the black screen preceding the purple screen would only + contain one line with an unrelated error that has to do with USB. - This REGRESSION has appeared after some recent automatic updates. This - didn't use to happen before. I had booted with battery power thousands - of time, though it's not something that I do very often so i can't tell - exactly when the regression appeared. - - - Before the purple screen appears, for a fraction of a second I've been able to see a black screen full of messages, probably error messages, while normally (when boot works fine) there would only be one usb-related error message. - - Please let me know from which log I can retrieve those error messages so - that I can post them here. - - Don't tell me to update the bios, because this used to work on the very - same machine, so the issue is obviously in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150603-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Aug 10 21:15:32 2015 InstallationDate: Installed on 2013-10-11 (668 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago) -- 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/1483388 Title: System randomly won't complete boot Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Since the incomplete/broken fix for #1431753 was released, and hence NVidia drivers version 340 were installed AND enabled on my machine (where previously I had 331 installed and disabled) this has started happening: About 50-75% of the times (very rough estimation), when I boot, the boot gets stuck at the purple screen with the Ubuntu word with four red dots below. Systematically, when this happens, that screen is preceded by a black screen with a lot of errors, of which I attach a picture (yes, I know, it's unreadable, but it's all I can do). If anybody tells me in which log files those errors can be found, I will be happy to attach them. Normally, that is, when the issue does not happen and the boot is succesful, the black screen preceding the purple screen would only contain one line with an unrelated error that has to do with USB. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150603-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Aug 10 21:15:32 2015 InstallationDate: Installed on 2013-10-11 (668 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago)
[Dx-packages] [Bug 1483388] Re: System randomly won't complete boot
Inability to boot after the update of NVidia drivers to 340 has been confirmed by user Anna at https://bugs.launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340-updates/+bug/1431753/comments/104 ** Package changed: unity (Ubuntu) = nvidia-graphics-drivers-340 (Ubuntu) ** Changed in: nvidia-graphics-drivers-340 (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/1483388 Title: System randomly won't complete boot Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Since the incomplete/broken fix for #1431753 was released, and hence NVidia drivers version 340 were installed AND enabled on my machine (where previously I had 331 installed and disabled) this has started happening: About 50-75% of the times (very rough estimation), when I boot, the boot gets stuck at the purple screen with the Ubuntu word with four red dots below. Systematically, when this happens, that screen is preceded by a black screen with a lot of errors, of which I attach a picture (yes, I know, it's unreadable, but it's all I can do). If anybody tells me in which log files those errors can be found, I will be happy to attach them. Normally, that is, when the issue does not happen and the boot is succesful, the black screen preceding the purple screen would only contain one line with an unrelated error that has to do with USB. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150603-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Aug 10 21:15:32 2015 InstallationDate: Installed on 2013-10-11 (668 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1483388/+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 1484589] [NEW] Spurious volume notification when changing output role with headphones
Public bug reported: Ubuntu 15.04 r90 1. Install the Maroon in Trouble game. 2. With headphones connected, start a new game. 3. After a while, disconnect the headphones. What happens: 2. There's a volume notification each time a sound plays. 3. There are no more volume notifications. What should happen: 2. There are no volume notifications, because neither the sound output nor the volume is changing. https://wiki.ubuntu.com/Sound#notification: When the primary sound output changes for any reason except an app request, or when the sound volume changes for any reason, a confirmation bubble should appear ... There should be no special notification when the active output role changes. This could be a side-effect of bug 1418210, but probably not, since it is idempotent: the notifications keep happening even if you don't change the volume in the meantime. [Split off bug 1478506.] ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Changing audio output role shows a notification + Spurious volume notification when changing output role with headphones ** Description changed: Ubuntu 15.04 r90 1. Install the Maroon in Trouble game. 2. With headphones connected, start a new game. 3. After a while, disconnect the headphones. What happens: 2. There's a volume notification each time a sound plays. 3. There are no more volume notifications. What should happen: 2. There are no volume notifications, because neither the sound output nor the volume is changing. https://wiki.ubuntu.com/Sound#notification: When the primary sound output changes for any reason except an app request, or when the sound volume changes for any reason, a confirmation bubble should appear ... There should be no special notification when the active output role changes. + This might or might not be a side-effect of bug 1418210. + [Split off bug 1478506.] -- 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/1484589 Title: Spurious volume notification when changing output role with headphones Status in indicator-sound package in Ubuntu: New Bug description: Ubuntu 15.04 r90 1. Install the Maroon in Trouble game. 2. With headphones connected, start a new game. 3. After a while, disconnect the headphones. What happens: 2. There's a volume notification each time a sound plays. 3. There are no more volume notifications. What should happen: 2. There are no volume notifications, because neither the sound output nor the volume is changing. https://wiki.ubuntu.com/Sound#notification: When the primary sound output changes for any reason except an app request, or when the sound volume changes for any reason, a confirmation bubble should appear ... There should be no special notification when the active output role changes. This could be a side-effect of bug 1418210, but probably not, since it is idempotent: the notifications keep happening even if you don't change the volume in the meantime. [Split off bug 1478506.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1484589/+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 1478506] Re: Apps change system volume all the time
It seems as if there aren't two problems here after all ... There are three. First, if you are quick enough to change the volume while a sound effect is playing, you can see that it resets to the maximum the next time the sound effect plays. That's bug 1418210. Second, even if you don't do that, if headphones are connected, you still get volume notifications from the output role changing. That makes *this* bug much easier to notice (otherwise the only effect would be that the hardware keys seemed like they didn't work), but it's nonetheless separate, so I've reported it as bug 1484589. And third, this bug, that the output role changes too briefly for you to change its volume. Maroon in Trouble uses the Qt SoundEffect API. http://doc.qt.io/qt-5 /qtquick-demos-maroon-example.html Qt says that SoundEffect provides a way to play short sound effects, like in video games ... You should use Audio for music playback. http://doc.qt.io/qt-5/qml-multimedia.html#soundeffect Apparently SoundEffect is using the multimedia role, which is not the alert default, which causes a temporary role switch. So, the way to fix this bug following the current design would be to change SoundEffect in Qt to use the default alert role, while Audio continues using the multimedia role. Alternatively, we could change the volume controls to control not simply the active output role, but something like the active output role unless it was changed less than 5 seconds ago, in which case the previous output role. But I think just fixing SoundEffect would be simpler. ** Summary changed: - Apps change system volume all the time + Apps change audio output role all the time -- 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/1478506 Title: Apps change audio output role all the time Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: To reproduce, install the app Maroon in trouble from the app store and play it a little with having sound enabled. Press the volume down hardware button on the phone. It will temporarily decrease the volume. However, whenever a new item comes into the scene, it will be on 100% volume again. Setting the system volume to 0 should keep everything at 0. Please note that this app does *not* have any code to set the volume! Also this app is one of the upstream Qt QML example demo apps, so this is really how QML apps are supposed to work (in other words, it is not a badly implemented app, but really an issue in the system) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506/+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 1420630] Re: indicator-sound menu icon disappeared after volume down to zero
** Changed in: oem-priority Status: New = Incomplete -- 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/1420630 Title: indicator-sound menu icon disappeared after volume down to zero Status in OEM Priority Project: Incomplete Status in OEM Priority Project trusty series: Incomplete Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound source package in Trusty: New Bug description: On the HP commercial notebooks, there're function keys to control volume. The menu volume icon will be disappeared if we volume down (with key combination: Fn+F6, you can also emulate the keys with xdotool key XF86AudioLowerVolume) to zero then logout and back in. But if we just zero down volume(with the single volume on/off button), then logout and back in, the volume icon is still there. This issue is fixed with installing indicator- sound_12.10.2+14.10.20141010-0ubuntu1(Utopic) Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Feb 11 14:18:50 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-trusty-amd64-20150114-3 InstallationDate: Installed on 2015-01-29 (13 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20150114-08:50 SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1420630/+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
