[Dx-packages] [Bug 1377847] [NEW] unity screen saver no longer blanks nor locks automatically
Public bug reported: After updating over the weekend the screen saver is no longer blanking or locking. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:44:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (472 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages utopic -- 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/1377847 Title: unity screen saver no longer blanks nor locks automatically Status in “unity” package in Ubuntu: Confirmed Bug description: After updating over the weekend the screen saver is no longer blanking or locking. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:44:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (472 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377847/+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 1377847] Re: unity screen saver no longer blanks nor locks automatically
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/1377847 Title: unity screen saver no longer blanks nor locks automatically Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: After updating over the weekend the screen saver is no longer blanking or locking. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:44:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (472 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377847/+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 1377847] Re: unity screen saver no longer blanks nor locks automatically
Confirmed. I did a fresh utopic daily install yesterday, and setting switch off screen to 1 min and lock screen to 30 s doesn't do anything at least for my account. This is with my ancient config, but I also confirmed this with a fresh user account. ** Changed in: unity (Ubuntu) Importance: Undecided = High ** Also affects: unity (Ubuntu Utopic) Importance: High Status: Confirmed ** Tags added: regression-release -- 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/1377847 Title: unity screen saver no longer blanks nor locks automatically Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: After updating over the weekend the screen saver is no longer blanking or locking. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:44:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (472 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377847/+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 1346355] Re: 14.04 power-cog does not turn red when restart is needed
You correctly allude to the fact that when a package update requires restart, you need to do two things: (A) install the update and (B) restart. As long as you haven't done both, you're just as badly off (for a security update, you're just as insecure) as if you've done neither. Until 2009 we used panel icons for both (A) and (B). Having noticed that that didn't work, we switched to using a dialog for (A), but still used an indicator icon for (B). Then having realized our inconsistency, we switched to a dialog for (B) too (the same dialog, if possible). The Unity design principle you refer to does not exist. And even if it did, usability testing trumps principles. Sorry. -- 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/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Bug = a popup-dialog asking the user to reboot the system after an update should not repeat (popup again) at a later time if the user chooses not to reboot. Instead, the power-cog should turn the color red and no further popup-dialogs should present at any time. In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+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 1369468] Re: no warning when volume increased to maximum and headphones plugged
*** This bug is a duplicate of bug 1373404 *** https://bugs.launchpad.net/bugs/1373404 I'm sorry, I reported bug 1373404 as a public version of a private bug, having totally forgotten that this bug report existed. ** This bug has been marked a duplicate of bug 1373404 No warning of high volume level -- 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/1369468 Title: no warning when volume increased to maximum and headphones plugged Status in “indicator-sound” package in Ubuntu: Triaged Bug description: Android gives the user a warning if they attempt to raise the volume to 100% when headphones are plugged. This is a sensible precaution both to save the user from tinnitus and to avoid any potential legal repercussions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1369468/+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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nux (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: In Progress Status in Nux trusty series: In Progress Status in “nux” package in Ubuntu: In Progress Status in “nux” source package in Trusty: Confirmed Bug description: [Impact] Unity crashes when unlocking the session [Test case] 1. Lock the session 2. Unlock the session 3. No crash should happen [Regression potential] None Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in
[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
A highly visible and very annoying bug! Would be great to have it fixed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: In Progress Status in Nux trusty series: In Progress Status in “nux” package in Ubuntu: In Progress Status in “nux” source package in Trusty: Confirmed Bug description: [Impact] Unity crashes when unlocking the session [Test case] 1. Lock the session 2. Unlock the session 3. No crash should happen [Regression potential] None Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from
[Dx-packages] [Bug 1241972] Re: Drag and drop from Dash to Desktop doesn't work
And me -- 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/1241972 Title: Drag and drop from Dash to Desktop doesn't work Status in Chromium Browser: New Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.1 series: Won't Fix Status in Unity 7.2 series: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When you try to drag and drop an app from Dash (both from app lens and home lens) to Desktop, system display an error and the shortcut isn't created. The error is: Error while copying - There was an error getting information about /. More details: The specified location is not supported Then there are four buttons: Cancel - Skip all - Skip - Retry. Way to reproduce: - Open the dash - Drag an app icon and drop on desktop What happend: - An error is raised What expected: - A shortcut is created With file, music and photo is all ok. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1241972/+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 1378022] [NEW] unity in utopic is failing to lock the apply the lock screen policy
*** This bug is a security vulnerability *** Public security bug reported: With the latest updates, unity is failing to apply the lock screen policy on my desktop. I have my desktop configured to lock the screen after 5 minutes of inactivity. I came back to my laptop in the morning after a full night's inactivity and found the screen still on and unlocked. This is a critical security regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:01:34 2014 InstallationDate: Installed on 2010-09-24 (1473 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-05-23 (136 days ago) ** Affects: unity (Ubuntu) Importance: Critical Status: New ** Affects: unity (Ubuntu Utopic) Importance: Critical Status: New ** Tags: amd64 apport-bug utopic ** Changed in: unity (Ubuntu) Importance: Undecided = Critical ** Information type changed from Public to Public Security ** Also affects: unity (Ubuntu Utopic) Importance: Critical Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378022 Title: unity in utopic is failing to lock the apply the lock screen policy Status in “unity” package in Ubuntu: New Status in “unity” source package in Utopic: New Bug description: With the latest updates, unity is failing to apply the lock screen policy on my desktop. I have my desktop configured to lock the screen after 5 minutes of inactivity. I came back to my laptop in the morning after a full night's inactivity and found the screen still on and unlocked. This is a critical security regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:01:34 2014 InstallationDate: Installed on 2010-09-24 (1473 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-05-23 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378022/+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 1378022] Re: unity in utopic is failing to lock the apply the lock screen policy
*** This bug is a duplicate of bug 1377847 *** https://bugs.launchpad.net/bugs/1377847 ** This bug has been marked a duplicate of bug 1377847 unity screen saver no longer blanks nor locks automatically -- 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/1378022 Title: unity in utopic is failing to lock the apply the lock screen policy Status in “unity” package in Ubuntu: New Status in “unity” source package in Utopic: New Bug description: With the latest updates, unity is failing to apply the lock screen policy on my desktop. I have my desktop configured to lock the screen after 5 minutes of inactivity. I came back to my laptop in the morning after a full night's inactivity and found the screen still on and unlocked. This is a critical security regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:01:34 2014 InstallationDate: Installed on 2010-09-24 (1473 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-05-23 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378022/+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 1342609] Re: altspace on windowless desktop opens window accessibility menu
This bug was fixed in the package bamf - 0.5.1+14.10.20140925-0ubuntu1 --- bamf (0.5.1+14.10.20140925-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Andrea Azzarone ] * BamfLegacyScreen: Do not show the actions menu for desktop type window. (LP: #1342609) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 25 Sep 2014 14:56:56 + ** Changed in: bamf (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1342609 Title: altspace on windowless desktop opens window accessibility menu Status in BAMF Application Matching Framework: In Progress Status in Unity: Invalid Status in “bamf” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: 1. Go to a desktop with now windows open. 2. Press altspace. 3. See that the window accessibility menu opens. Clicking on entries in this menu causes problems with Unity. For example if you click on Move Workspace Left, then many graphical issues arrise. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jul 16 11:11:27 2014 InstallationDate: Installed on 2013-10-03 (285 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-23 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1342609/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
I'm in agreement with Jochen. There will never be a situation where I want to see my mouse indicator. In my case I'm using a Targus mouse running on two AA batteries. Ubuntu seems to think my mouse is at 0% power and needs to be charged. It's not even a chargeable mouse. Even if it was rechargeable I wouldn't want this indicator to ever override my laptop battery status. My laptop is charging and I have to keep unplugging it to see the battery status because clicking the indicator only gives me a time to charged number when I'd rather see a percentage. While my power cord is plugged in and the laptop is charging all I see is a red mouse icon in the place of my battery indicator. I was only mildly annoyed at first because I assumed there had to be an option somewhere to just disable showing my mouse battery. I was wrong, so now I'm slightly more annoyed. -- 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/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in “indicator-power” package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1241972] Re: Drag and drop from Dash to Desktop doesn't work
If you don't have additional info, please just click on the This bug affects you and 93 other people exclamation mark (at the top of the bug report), so you add to the count. Adding comments like Me too just clutter reports and make it harder for developers. -- 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/1241972 Title: Drag and drop from Dash to Desktop doesn't work Status in Chromium Browser: New Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.1 series: Won't Fix Status in Unity 7.2 series: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When you try to drag and drop an app from Dash (both from app lens and home lens) to Desktop, system display an error and the shortcut isn't created. The error is: Error while copying - There was an error getting information about /. More details: The specified location is not supported Then there are four buttons: Cancel - Skip all - Skip - Retry. Way to reproduce: - Open the dash - Drag an app icon and drop on desktop What happend: - An error is raised What expected: - A shortcut is created With file, music and photo is all ok. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1241972/+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 1378046] [NEW] Can't switch between maximized windows of the same program sometimes
Public bug reported: Note: this is intermittent and I don't know of a way to systematically reproduce this, but I've observed it dozens of times. - I have two windows of the same program both maximized - I click on the program's icon on the Launcher (one icon with two tips indicating there are two windows open) = the downscaled previews of the two windows are shown one on top of the other as expected - I click on one of them Expected result: the one I clicked should get focus and be brought to front (maximized, as it was) Observed result: whichever I pick, only one of them, systematically always the same one, will get chosen. That is, if I click on window A, it's window A, if I click on window B, it's window A allthesame. Additionally, the title bar on the top of the screen is not displayed. I can click on the foreground window (which is not the expected one) and interact with it. If I click on the top of the screen, where the window title is not shown, then the correct window will be brought to front (not sure this _always_ work, but I have observed it sometimes). One thing that fixes the issue is to de-maximize both windows and then remaximize them. I've only observed this on maximized windows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 20:00:03 2014 InstallationDate: Installed on 2013-10-11 (360 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (135 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - Can't switch between maximized windows at random times + Can't switch between maximized windows of the same program sometimes -- 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/1378046 Title: Can't switch between maximized windows of the same program sometimes Status in “unity” package in Ubuntu: New Bug description: Note: this is intermittent and I don't know of a way to systematically reproduce this, but I've observed it dozens of times. - I have two windows of the same program both maximized - I click on the program's icon on the Launcher (one icon with two tips indicating there are two windows open) = the downscaled previews of the two windows are shown one on top of the other as expected - I click on one of them Expected result: the one I clicked should get focus and be brought to front (maximized, as it was) Observed result: whichever I pick, only one of them, systematically always the same one, will get chosen. That is, if I click on window A, it's window A, if I click on window B, it's window A allthesame. Additionally, the title bar on the top of the screen is not displayed. I can click on the foreground window (which is not the expected one) and interact with it. If I click on the top of the screen, where the window title is not shown, then the correct window will be brought to front (not sure this _always_ work, but I have observed it sometimes). One thing that fixes the issue is to de-maximize both windows and then remaximize them. I've only observed this on maximized windows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 20:00:03 2014 InstallationDate: Installed on 2013-10-11 (360 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (135 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378046/+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 1378044] [NEW] No Album art on Audio Controls
Public bug reported: Steps: 1. have music on your phone 2. Make sure that album art appears in the music scope 3. Play the album in the music player 4. Click the power button to blank the screen 5. turn on the power button button 6. pull down the sound indicator Observed: there is no album art in the indicator, the window is blank Expected: there is album art ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: avengers ** Description changed: Steps: 1. have music on your phone - 2. Make sure that album art appears in the mysic scope + 2. Make sure that album art appears in the music scope 3. Play the album in the music player 4. Click the power button to blank the screen 5. turn on the power button button 6. pull down the sound indicator Observed: there is no album art in the indicator, the window is blank Expected: there is album art -- 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/1378044 Title: No Album art on Audio Controls Status in “indicator-sound” package in Ubuntu: New Bug description: Steps: 1. have music on your phone 2. Make sure that album art appears in the music scope 3. Play the album in the music player 4. Click the power button to blank the screen 5. turn on the power button button 6. pull down the sound indicator Observed: there is no album art in the indicator, the window is blank Expected: there is album art To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378044/+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 1378048] [NEW] Forward button does not work
Public bug reported: Steps: 1. Play an album in the music player 2. Pull down sound indicator 3. Click forward button Observed: the music does not advance Expected: the music advances ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378048 Title: Forward button does not work Status in “indicator-sound” package in Ubuntu: New Bug description: Steps: 1. Play an album in the music player 2. Pull down sound indicator 3. Click forward button Observed: the music does not advance Expected: the music advances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048/+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 1367920] Re: dialer not brought to foreground when launched from messaging-menu
ok, I was doing some testing and this appears to be fixed already in the lastest RTM devel image i suspect the indactor polish branch corrected. if not, please reopen but with better instructions or a video as it means i didn't quite understand. ** Changed in: unity8 (Ubuntu) Status: Confirmed = Fix Released ** Changed in: indicator-messages (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367920 Title: dialer not brought to foreground when launched from messaging-menu Status in “indicator-messages” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: How to reproduce === 1 - Make sure that you have a missing call/voice mail message on messaging menu 2 - Open dialer app 3 - Open the messaging menu 4 - Click to expand the message 5 - Click on the phone app icon in the top right Expected The messaging menu disappear and the dialer app appears Current == The message is removed but the messaging menu still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367920/+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 1377294] Re: Indicator order change on the phone
** Branch linked: lp:ubuntu/utopic-proposed/indicator-transfer ** Branch linked: lp:ubuntu/utopic-proposed/indicator-location -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1377294 Title: Indicator order change on the phone Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Invalid Status in Display Indicator: Invalid Status in Indicator Location: In Progress Status in The Messaging Menu: In Progress Status in Network Menu: In Progress Status in The Power Indicator: In Progress Status in Sound Menu: Invalid Status in Transfer Indicator: In Progress Status in “indicator-bluetooth” package in Ubuntu: New Status in “indicator-location” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: New Status in “indicator-network” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: New Status in “indicator-transfer” package in Ubuntu: New Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: Design change: Panel items should be, from right to left: Time Alarm Power Volume Wifi Cellular Bluetooth Location Transfer Rotation Messages Which should translate into these ordering values: Datetime: 20 Power: 25 Sound: 30 Network: 35 Bluetooth: 36 Location: 60 Transfer: 71 Rotation: 90 Messages: 100 Documented: https://wiki.ubuntu.com/SystemComponents#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1377294/+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 1377294] Re: Indicator order change on the phone
This bug was fixed in the package indicator-location - 13.10.0+14.10.20141006-0ubuntu1 --- indicator-location (13.10.0+14.10.20141006-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Move the position of this indicator on the panel. (LP: #1377294) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 06 Oct 2014 17:33:36 + ** Changed in: indicator-location (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1377294 Title: Indicator order change on the phone Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Invalid Status in Display Indicator: Invalid Status in Indicator Location: In Progress Status in The Messaging Menu: In Progress Status in Network Menu: In Progress Status in The Power Indicator: In Progress Status in Sound Menu: Invalid Status in Transfer Indicator: In Progress Status in “indicator-bluetooth” package in Ubuntu: New Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: New Status in “indicator-network” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: New Status in “indicator-transfer” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: Design change: Panel items should be, from right to left: Time Alarm Power Volume Wifi Cellular Bluetooth Location Transfer Rotation Messages Which should translate into these ordering values: Datetime: 20 Power: 25 Sound: 30 Network: 35 Bluetooth: 36 Location: 60 Transfer: 71 Rotation: 90 Messages: 100 Documented: https://wiki.ubuntu.com/SystemComponents#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1377294/+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 1377294] Re: Indicator order change on the phone
This bug was fixed in the package indicator-transfer - 0.1+14.10.20141006-0ubuntu1 --- indicator-transfer (0.1+14.10.20141006-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Move the position of this indicator on the panel. (LP: #1377294) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 06 Oct 2014 17:36:14 + ** Changed in: indicator-transfer (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1377294 Title: Indicator order change on the phone Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Invalid Status in Display Indicator: Invalid Status in Indicator Location: In Progress Status in The Messaging Menu: In Progress Status in Network Menu: In Progress Status in The Power Indicator: In Progress Status in Sound Menu: Invalid Status in Transfer Indicator: In Progress Status in “indicator-bluetooth” package in Ubuntu: New Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: New Status in “indicator-network” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: New Status in “indicator-transfer” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: Design change: Panel items should be, from right to left: Time Alarm Power Volume Wifi Cellular Bluetooth Location Transfer Rotation Messages Which should translate into these ordering values: Datetime: 20 Power: 25 Sound: 30 Network: 35 Bluetooth: 36 Location: 60 Transfer: 71 Rotation: 90 Messages: 100 Documented: https://wiki.ubuntu.com/SystemComponents#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1377294/+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 1378103] [NEW] Indicator does not display message and there is no notification when screen is locked and message is in messaging app
Public bug reported: Steps: I used skype for this to make it easy to repro 0. Set your phone by opening the messaging app to a thread for a conversation that you are not about to test then use the power button to blank the screen 1. Open skype you on your desktop 2. Use skype to send a text to your phone 3. Wait a few seconds for the alert 4. Click on the notification to open it as a conversation in the messaging app 5. use the power button to blank your screen again 6. use skype to send another text Result: The alert sounds plays, and the screen turns on, but there is no notification and the message is not in the messaging menu. If you unlock the phone you see the message in the conversation. Expected: The notification shows and the message is in the indicator. This is krillin, r84 ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: avengers ** Summary changed: - Indicator does not display message when screen is locked and message is in messaging app + Indicator does not display message and there is no notification when screen is locked and message is in messaging app ** Description changed: Steps: I used skype for this to make it easy to repro 0. Set your phone by opening the messaging app to a thread for a conversation that you are not about to test then use the power button to blank the screen 1. Open skype you on your desktop 2. Use skype to send a text to your phone 3. Wait a few seconds for the alert 4. Click on the notification to open it as a conversation in the messaging app 5. use the power button to blank your screen again 6. use skype to send another text Result: The alert sounds plays, and the screen turns on, but there is no notification and the message is not in the messaging menu. If you unlock the phone you see the message in the conversation. Expected: The notification shows and the message is in the indicator. + + This is krillin, r84 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378103 Title: Indicator does not display message and there is no notification when screen is locked and message is in messaging app Status in “indicator-messages” package in Ubuntu: New Bug description: Steps: I used skype for this to make it easy to repro 0. Set your phone by opening the messaging app to a thread for a conversation that you are not about to test then use the power button to blank the screen 1. Open skype you on your desktop 2. Use skype to send a text to your phone 3. Wait a few seconds for the alert 4. Click on the notification to open it as a conversation in the messaging app 5. use the power button to blank your screen again 6. use skype to send another text Result: The alert sounds plays, and the screen turns on, but there is no notification and the message is not in the messaging menu. If you unlock the phone you see the message in the conversation. Expected: The notification shows and the message is in the indicator. This is krillin, r84 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378103/+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 1274181] Re: notification-daemon crashed with signal 5 in g_source_remove()
*** This bug is a duplicate of bug 1273014 *** https://bugs.launchpad.net/bugs/1273014 Maybe it's a little late to comment here, but bug #1273014 have nothing to do with Gnome Flashback Compiz the same as with the other users I have this problem since 12.04 and everytime (read my profile or Launchpad-blog)... It' s a hard time if your computer will change his start-up with the craziest ideas your never mentioned before. Sometimes I think it's in the hardware (Intel i7 Quad Core) and other times I think, who is here the dumm guy. I install all my installations with help from Linux-specialist near my living 12km from my home in the Netherlands (also disabled). I'm no Linux/Unix-specialist, but have 32-year experience wirh Windows-computers, so we two installers are not the dumm guys, only when a computer change his/her mind before or after grub and all white lines are listed on black background as fast it is going over my screen and is half way stopping with an error message Once I tried (in 12.04) the Ubuntu rescue cd, but it's better to install every time a new installation on your computer than to take other solutions, but a fix for this bug I think nobody will find a solution. Sorry for my English translation, I learned it 43-years ago, I use dictionaries when I'm not to tired), I do my best...pfff. After all crazy Windows years, Ubuntu is still my OS and happyness for the future. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274181 Title: notification-daemon crashed with signal 5 in g_source_remove() Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: Just rebooted and logged into Gnome Flashback with Compiz and immediately got this error notification. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jan 29 11:37:58 2014 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-08 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_source_remove() 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/notification-daemon/+bug/1274181/+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 1297150] Re: Unity quit button doesn't do anything when Wine application is frozen
I've seen this behavior. Unity should have a way of being more forceful about its kills after an application doesn't respond to quits for a while (or perhaps infer it when the user issues repeated quit commands). Other operating systems offer to do the equivalent of kill -9 (Force quit) in similar situations. Wine is smart enough to clean up wineserver if all the application processes are removed this way. ** Changed in: wine1.6 (Ubuntu) Importance: Undecided = Medium ** Changed in: wine1.6 (Ubuntu) Status: Confirmed = Triaged ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1297150 Title: Unity quit button doesn't do anything when Wine application is frozen Status in “unity” package in Ubuntu: New Status in “wine1.6” package in Ubuntu: Triaged Bug description: A Wine app that freezes up can be in a state where it is unkillable by using the interface. Killing the process in a terminal, or doing a wineserver -k command, can solve the situation, however there is no way to do this within Unity even after repeated quit demands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1297150/+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 1103833] Re: Wine's icon and description appears for all Windows applications
** Package changed: wine (Ubuntu) = wine1.6 (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/1103833 Title: Wine's icon and description appears for all Windows applications Status in One Hundred Papercuts: Triaged Status in Unity: Confirmed Status in Wine: Unknown Status in “unity” package in Ubuntu: Triaged Status in “wine1.6” package in Ubuntu: Triaged Bug description: If I start an application using Crossover (or Wine), the application will always be the Wine Logo instead of the application logo. This is the same independent of the application being run or using Wine instead of Crossover. That makes sense if the application has no logo, but it gets confusing running multiple Microsoft Office programs - and all of them have the same logo. The hint text for the icon is also Wine Windows Program Loader instead of Document 1 - Microsoft Word as it should be. Unity does not seem to allow Wine/Crossover to use application icons and title text. I have confirmed that this issue does NOT occur in Gnome Classic, and is only a Unity flaw. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Jan 23 23:37:43 2013 InstallationDate: Installed on 2012-10-21 (94 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1103833/+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 1334021] Re: Installing Skype package (from skype.com) via software center creates unclickable icon in Unity dash in Ubuntu 14.04 x64
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/1334021 Title: Installing Skype package (from skype.com) via software center creates unclickable icon in Unity dash in Ubuntu 14.04 x64 Status in Ubuntu Software Center: New Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Installing Skype package (from skype.com) via software center creates unclickable icon in Unity dash. Bug happens only with Unity and Software Center. Installing package via gdebi or dpkg works fine. Steps to reproduce: 1) Download skype-ubuntu-precise_4.3.0.37-1_i386.deb from skype.com 2) Open it with software center (software center should be started as normal user, not via sudo to reproduce this bug) 3) Press install button 4) Open dash (press super key), do not type anything (clear search field if there is something there). 5) Skype icon will be in recently accessed applications (strange, because it was never launched, seems software center adds it there). https://bugs.launchpad.net/unity/+bug/1334021/+attachment/4138553/+files/Screenshot%20from%202014-06-25%2002%3A07%3A21.png 6) Left click on it will not start skype. Nothing happens on left click. Right click will show document icon, instead of skype button. There will be no Launch button. https://bugs.launchpad.net/unity/+bug/1334021/+attachment/4138552/+files/Screenshot%20from%202014-06-25%2002%3A07%3A52.png 7) It is possible to start skype by doing following: Start typing skype in search bar. Now icon will become clickable. Right clicking also will work correctly (skype icon and launch button present). https://bugs.launchpad.net/unity/+bug/1334021/+attachment/4138555/+files/Screenshot%20from%202014-06-25%2002%3A09%3A26.png 8) Open dash again after starting skype. Clear search field. You will see two skype icons: one is correct and clickable, second one is not. https://bugs.launchpad.net/unity/+bug/1334021/+attachment/4138554/+files/Screenshot%20from%202014-06-25%2002%3A08%3A28.png 9) If you uninstall skype, this wrong icon (which doing nothing) will be left in the system, only correct icon will be removed. It is possible to remove wrong icon by going to Security Preferences and pressing Clear usage data there. test@Extensa-5630-2:~$ uname -a Linux Extensa-5630-2 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux test@Extensa-5630-2:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty test@Extensa-5630-2:~$ apt-cache policy unity unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages test@Extensa-5630-2:~$ apt-cache policy software-center software-center: Installed: 13.10-0ubuntu4.1 Candidate: 13.10-0ubuntu4.1 Version table: *** 13.10-0ubuntu4.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 13.10-0ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages test@Extensa-5630-2:~$ apt-cache policy zeitgeist zeitgeist: Installed: 0.9.14-0ubuntu4 Candidate: 0.9.14-0ubuntu4 Version table: *** 0.9.14-0ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1334021/+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 1367920] Re: dialer not brought to foreground when launched from messaging-menu
As possibly expected, I cannot reproduce this with the current image. By messaging menu, I assume you mean notifications? Current behavior results in the dialer app opening with the number of the missed call input. Given the slight ambiguity in the steps to reproduce, can you please confirm this when you have a chance @kevin? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367920 Title: dialer not brought to foreground when launched from messaging-menu Status in “indicator-messages” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: How to reproduce === 1 - Make sure that you have a missing call/voice mail message on messaging menu 2 - Open dialer app 3 - Open the messaging menu 4 - Click to expand the message 5 - Click on the phone app icon in the top right Expected The messaging menu disappear and the dialer app appears Current == The message is removed but the messaging menu still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367920/+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 1306499] Re: Sound indicator is jumpy while music playing (grooveshark)
fixed with latest polish branch ** Changed in: unity8 (Ubuntu) Status: Confirmed = 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/1306499 Title: Sound indicator is jumpy while music playing (grooveshark) Status in Sound Menu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: Open sound indicator Try and swipe the volume up and down Try and increase/decrease volume with the hardware vol+ vol- keys Note that the slider takes a long time to update, and sometimes leaps backwards and forwards despite you only holding one button down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Fri Apr 11 10:39:43 2014 InstallationDate: Installed on 2014-04-11 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140411) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1306499/+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 1378177] [NEW] Turn screen off when invactive timeout doesn't work
Public bug reported: I left my laptop open and running tonight when away. When I returned 1.5 hours later, my screen was still on, all black except for a white mouse pointer. I locked the screen with the windows+L combo and walked away when the lock screen displayed properly. The Brightness Lock section of the control panel shows Turn screen off when inactive for: 5 minutes. Lock is turned on, Lock screen after: 5 minutes, and Require my password when waking from suspend. I didn't suspend, and I manually locked before leaving. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Oct 6 21:42:24 2014 InstallationDate: Installed on 2012-10-18 (718 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-12 (178 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1378177 Title: Turn screen off when invactive timeout doesn't work Status in “unity” package in Ubuntu: New Bug description: I left my laptop open and running tonight when away. When I returned 1.5 hours later, my screen was still on, all black except for a white mouse pointer. I locked the screen with the windows+L combo and walked away when the lock screen displayed properly. The Brightness Lock section of the control panel shows Turn screen off when inactive for: 5 minutes. Lock is turned on, Lock screen after: 5 minutes, and Require my password when waking from suspend. I didn't suspend, and I manually locked before leaving. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Oct 6 21:42:24 2014 InstallationDate: Installed on 2012-10-18 (718 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-12 (178 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378177/+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 1378048] Re: Forward button does not work
Unlikely to be a bug in the sound menu, as that works with all other players. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: media-hub (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) 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/1378048 Title: Forward button does not work Status in “indicator-sound” package in Ubuntu: Incomplete Status in “media-hub” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Steps: 1. Play an album in the music player 2. Pull down sound indicator 3. Click forward button Observed: the music does not advance Expected: the music advances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048/+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 1378103] Re: Indicator does not display message and there is no notification when screen is locked and message is in messaging app
Unlikely to be a bug in the messaging indicator itself. The messaging app displays notifications and adds an entry into the messaging menu. If you can't see notifications either, it's probably a bug in the app. ** Package changed: indicator-messages (Ubuntu) = messaging-app (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378103 Title: Indicator does not display message and there is no notification when screen is locked and message is in messaging app Status in “messaging-app” package in Ubuntu: New Bug description: Steps: I used skype for this to make it easy to repro 0. Set your phone by opening the messaging app to a thread for a conversation that you are not about to test then use the power button to blank the screen 1. Open skype you on your desktop 2. Use skype to send a text to your phone 3. Wait a few seconds for the alert 4. Click on the notification to open it as a conversation in the messaging app 5. use the power button to blank your screen again 6. use skype to send another text Result: The alert sounds plays, and the screen turns on, but there is no notification and the message is not in the messaging menu. If you unlock the phone you see the message in the conversation. Expected: The notification shows and the message is in the indicator. This is krillin, r84 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1378103/+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
