[Dx-packages] [Bug 1451613] Re: [regression] Unity/compiz crashes when locking screen
** Changed in: unity (Ubuntu Trusty) Status: New = In Progress ** Changed in: unity (Ubuntu Trusty) Importance: Undecided = Critical ** Changed in: unity (Ubuntu Trusty) Assignee: (unassigned) = Christopher Townsend (townsend) -- 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/1451613 Title: [regression] Unity/compiz crashes when locking screen Status in Unity: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Invalid Status in unity source package in Trusty: In Progress Bug description: [ Impact ] A crash is occurring for many users of Trusty when the screen is locking. [ Test Case ] Lock the screen. [ Regression Potential ] None as this is removing a commit causing this regression. - Original Description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1451613] Re: [regression] Unity/compiz crashes when locking screen
The debdiff for the SRU. ** Patch added: unity.revert-3810.debdiff https://bugs.launchpad.net/unity/+bug/1451613/+attachment/4409311/+files/unity.revert-3810.debdiff ** Description changed: [ Impact ] A crash is occurring for many users of Trusty when the screen is locking. [ Test Case ] Lock the screen. [ Regression Potential ] None as this is removing a commit causing this regression. + + The debdiff is found at + https://bugs.launchpad.net/unity/+bug/1451613/+attachment/4409311/+files/unity.revert-3810.debdiff - Original Description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) -- 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/1451613 Title: [regression] Unity/compiz crashes when locking screen Status in Unity: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] A crash is occurring for many users of Trusty when the screen is locking. [ Test Case ] Lock the screen. [ Regression Potential ] None as this is removing a commit causing this regression. The debdiff is found at https://bugs.launchpad.net/unity/+bug/1451613/+attachment/4409311/+files/unity.revert-3810.debdiff - Original Description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1451613] Re: [regression] Unity/compiz crashes when locking screen
Hello Scaler, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150603-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1451613 Title: [regression] Unity/compiz crashes when locking screen Status in Unity: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] A crash is occurring for many users of Trusty when the screen is locking. [ Test Case ] Lock the screen. [ Regression Potential ] None as this is removing a commit causing this regression. The debdiff is found at https://bugs.launchpad.net/unity/+bug/1451613/+attachment/4409311/+files/unity.revert-3810.debdiff - Original Description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
** Changed in: ubuntu-themes (Ubuntu) Status: New = Fix Committed ** Changed in: indicator-messages (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) = Matthieu James (tiheum) -- 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/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Confirmed Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: New Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1461682] Re: [MX4] LED does not notify for incoming notifications
is this only on arale ? ** Also affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Also affects: powerd (Ubuntu) Importance: Undecided Status: New ** No longer affects: powerd (Ubuntu) ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New -- 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/1461682 Title: [MX4] LED does not notify for incoming notifications Status in indicator-messages package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Image r12 The notification LED on the device does not blink when a new SMS arrives. Its always static off. It however does lighten up when the button physical button is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1461682/+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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
** Branch linked: lp:~charlesk/ubuntu-themes/lp-1450894-green-messages- icon -- 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/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Confirmed Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: New Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1461682] Re: [MX4] LED does not notify for incoming notifications
Yes, works on krillin, doesn't work on arale. Unity8 uses the android-headers package to accomplish that for krillin. That gives us the following options to initialize lights: LIGHT_ID_BACKLIGHT LIGHT_ID_KEYBOARD LIGHT_ID_BUTTONS LIGHT_ID_BATTERY LIGHT_ID_NOTIFICATIONS LIGHT_ID_ATTENTION Krillin works fine with LIGHT_ID_NOTIFICATIONS, however, arale doesn't. I have tried with all the others and the only one that actually does something on arale is LIGHT_ID_BACKLIGHT, which is obviously not what we want. If we can talk to the lights at all, this probably needs to be fixed on the android side of things. -- 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/1461682 Title: [MX4] LED does not notify for incoming notifications Status in indicator-messages package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Image r12 The notification LED on the device does not blink when a new SMS arrives. Its always static off. It however does lighten up when the button physical button is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1461682/+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 1461482] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:url-dispatcher-bad-url
settings:///system/wifi is a valid URL. ** Package changed: indicator-network (Ubuntu) = url-dispatcher (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1461482 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:url-dispatcher-bad-url Status in url-dispatcher package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+15.10.20150519-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/d63c848f73a34299ec298a6d833b388cc276b3a2 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1461482/+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 1461482] [NEW] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:url-dispatcher-bad-url
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+15.10.20150519-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/d63c848f73a34299ec298a6d833b388cc276b3a2 contains more details. ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: vivid wily -- /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:url-dispatcher-bad-url https://bugs.launchpad.net/bugs/1461482 You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1461496] [NEW] initctl start url-dispatcher-update-user does not update the protocols database
Public bug reported: I want to register a protocol for an application putting it in ~/.config /url-dispatcher/urls. According to Ted, after running $ initctl start url-dispatcher-update-user the url dispatcher database should be updated with the new protocol. But that's not working. It only works if I run /usr/lib/*/url-dispatcher/update-directory with the path or my .url-dispatcher file. To check the database after the update: echo .quit | sqlite3 -batch -csv -cmd select urls.protocol, urls.domainsuffix, configfiles.name from urls, configfiles where urls.sourcefile = configfiles.rowid; ~/.cache/url-dispatcher/urls-1.db Here is the branch where I'm automating this test: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/register_url_dispatcher/+merge/260923 ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1461496 Title: initctl start url-dispatcher-update-user does not update the protocols database Status in url-dispatcher package in Ubuntu: New Bug description: I want to register a protocol for an application putting it in ~/.config/url-dispatcher/urls. According to Ted, after running $ initctl start url-dispatcher-update-user the url dispatcher database should be updated with the new protocol. But that's not working. It only works if I run /usr/lib/*/url-dispatcher/update-directory with the path or my .url-dispatcher file. To check the database after the update: echo .quit | sqlite3 -batch -csv -cmd select urls.protocol, urls.domainsuffix, configfiles.name from urls, configfiles where urls.sourcefile = configfiles.rowid; ~/.cache/url- dispatcher/urls-1.db Here is the branch where I'm automating this test: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/register_url_dispatcher/+merge/260923 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1461496/+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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
Agreed, let's change it to green ** Description changed: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in - indicators + indicators. + + Change the LED light to green as well. -- 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/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Confirmed Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1451613] Re: Unity/compiz crashes when locking screen
Hi, I encountered the same problem since 2-3 weeks now. My setup : - Ubuntu 14.04 LTS - Lenovo ThinkPad T420 + an additional Lenovo Screen ThinkVision (20) + Logitech Anywhere MX mouse I use the shortcut Windows + L (same as CTRL+ALT+L but less fingers are needed) to lock my laptop. I cannot reproduce the issue, but it happens every day. I have the same crash with Compiz (_usr_bin_compiz.1000.crash) I tried to update Unity package, but the crash hasn't been fixed. unity7.2.5 + 14.04.20150 amd64 compiz 1:0.9.11.3 + 14.04. all -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hello Grzegorz, or anyone else affected, Accepted nss-pam-ldapd into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nss-pam- ldapd/0.8.13-3ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nss-pam-ldapd (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- 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/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Invalid Status in nss-pam-ldapd package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in nss-pam-ldapd source package in Trusty: Fix Committed Status in unity source package in Trusty: Invalid Status in nss-pam-ldapd source package in Utopic: Fix Released Status in unity source package in Utopic: Invalid Status in nss-pam-ldapd package in Debian: Fix Released Bug description: SRU justification: [Impact] * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not able to unlock the Unity lockscreen. Utopic and later are not affected. Some workarounds are listed in comment #29. * nslcd in Trusty and earlier does not permit unprivileged users to read shadow entries. When invoked by the Unity lockscreen, running as the logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in pam_acct_mgmt when it tries to get password expiry information from shadow. This leads to an authorization failure, so Unity refuses to unlock the screen. pam_ldap is not consulted for pam_acct_mgmt after pam_unix fails because its rule is in the Additional section. * In Utopic and later, nslcd returns partial shadow entries to unprivileged users. This is enough for the expiry check in pam_unix to succeed, so the screen can be unlocked. See http://bugs.debian.org/706913 for a discussion of the upstream fix. * This proposed SRU backports the upstream solution to Trusty's nslcd. This is a change of behaviour for shadow queries from unprivileged users, compared to the current package. An alternative, more targeted fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from pam_acct_mgmt, like gnome-screensaver already does (see comment #29). The nslcd change is a more general fix for not just Unity, but any PAM-using program run by an unprivileged user. [Test Case] * Install and configure libnss-ldapd. Ensure ldap is enabled for at least the passwd and shadow services in /etc/nsswitch.conf. * Log into Unity as an LDAP user, lock the screen, and then try to unlock it again. [Regression Potential] * The patch is minimal, was written by the upstream author, and was backported (adjusting for whitespace changes) to Trusty. The change has already been released in Utopic and will be included in Debian Jessie as well. * Regression testing should include checking that shadow queries, both by name and for listing all users, are unchanged when issued as root. [Other Info] * Packages for testing are available in ppa:rtandy/lp1314095 Original description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1
[Dx-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
** Description changed: + [ Impact ] + + A crash is occurring for many users of Trusty when the screen is + locking. + + [ Test Case ] + + Lock the screen. + + [ Regression Potential ] + + None as this is removing a commit causing this regression. + + - + + Original Description: + Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… - I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) ** Summary changed: - Unity/compiz crashes when locking screen + [regression] Unity/compiz crashes when locking screen ** Tags added: regression-update 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/1451613 Title: [regression] Unity/compiz crashes when locking screen Status in Unity: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Invalid Bug description: [ Impact ] A crash is occurring for many users of Trusty when the screen is locking. [ Test Case ] Lock the screen. [ Regression Potential ] None as this is removing a commit causing this regression. - Original Description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
@pat-mcgowan, I've just came back from holidays today and I wasn't aware of previous conversations and the decision that was taken yesterday about the messaging indicator icon. You can ignore my previous comment. -- 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/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Confirmed Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1451613] Re: Unity/compiz crashes when locking screen
** Branch linked: lp:~townsend/unity/fix-lp1451613-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/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Invalid Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1451613] Re: Unity/compiz crashes when locking screen
So far, this has only been reported on Trusty. It's still unclear to us why this is occurring only on Trusty. Given that we still don't have a proper fix in place for this on Trusty, we are just going to revert the offending commit and get an SRU out with only this reversion as soon as possible. Thanks for everyone's patience and trying to help us debug this! ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity Status: Confirmed = Invalid ** Changed in: unity (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity/7.2 Status: New = In Progress ** Changed in: unity/7.2 Importance: Undecided = Critical ** Changed in: unity/7.2 Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity/7.2 Milestone: None = 7.2.6 -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Invalid Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
--- UX comment --- The use of blue to indicate 'unread' and 'missed' communications was not understood, 7/11 participants failed to interpret the meaning of blue. This is because of the following mental models: - Blue does not signify that attention is required - The presence of a communication indicator already suggests 'unread' and 'missed' User quotes: I don't know why it needs to be blue, I don't need it to be there if there aren't any unread messages. It normally will only show when there is an outstanding message. (Michael) The fact that it is present indicates there is something there for me to do. (Hansie) When there are no outstanding messages/missed calls, the participants did not expect the indicators to be shown. Therefore, the blue colour serves little meaning to them. Based on these findings, we've decided to only show the Notification indicator icon (white) if its current status is on/running or required the user's attention. (With the exception of informational indicators which are always present). Source: Notification indicator icon findings from Usability testing sessions - March and Sep 2014 (https://goo.gl/tncf2K) (https://goo.gl/EAE94I) --- Also, with the new design of the Notification System, we suggest using the lock screen to provide more functionality beyond unlocking the phone: such as notifications for emails and text messages, a date and time display, or even shortcuts to certain applications, for example, the camera or the media player control. This appearance of notifications on the lock screen addresses user's prioritisation of different communication content based on their context, for example, from earlier research, we found that participants gave different levels of attention according to the communication medium: a missed call is more likely to require an immediate action; text messages are checked on a frequent basis; personal emails are relatively less urgent, and tend to be checked at the user's convenience. Therefore, the 'envelope' icon in the status bar takes a 'secondary role' when notifying the user. Desired behaviour of 'Envelope' icon: User can swipe either way to unlock the screen, if she does, all notifications will disappear and be recorded in the Notification centre and the 'envelope' icon should be present on the Status bar. If user sees (opens) the Notification centre or acts on a notification when it arrives, then the 'envelope' icon should disappear from the status bar. (https://goo.gl/J6G9Yn) -- 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/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Confirmed Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1460271] Re: Update evolution-data-server to 3.16
They're about to do this in Debian so we can get patches for free-ish (or help out there) if we wait. -- 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/1460271 Title: Update evolution-data-server to 3.16 Status in evolution-data-server package in Ubuntu: Triaged Status in indicator-datetime package in Ubuntu: Triaged Bug description: Update to 3.16. Debian currently has this in experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+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 1072052] Re: [regression] HUD - No results from Indicator Menus
** Tags added: vivid -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1072052 Title: [regression] HUD - No results from Indicator Menus Status in The Application Menu: Triaged Status in Unity: Triaged Status in hud package in Ubuntu: Triaged Status in indicator-appmenu package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: HUD doesn't show results from the messaging menu. See screencast. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Oct 27 13:47:09 2012 InstallationDate: Installed on 2012-10-22 (5 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/indicator-appmenu/+bug/1072052/+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 1165420] Re: Unable to access indicators from HUD
*** This bug is a duplicate of bug 1072052 *** https://bugs.launchpad.net/bugs/1072052 ** This bug has been marked a duplicate of bug 1072052 [regression] HUD - No results from Indicator Menus -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1165420 Title: Unable to access indicators from HUD Status in Ayatana Design: Confirmed Status in Unity HUD: Confirmed Status in hud package in Ubuntu: Confirmed Bug description: In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's Update Status option there, making status updates to Twitter easy and fast. I could also use HUD to change my status in Empathy from Available to Busy and vice-versa. In Ubuntu 13.04 Beta HUD no longer finds the Update Status option when typing Update Status or Update Also writing Available Away or Busy no longer gives any results. Other indicators however are accessible and I can use HUD to Suspend my computer or to view Skype status or Ubuntu one indicator options. Repeating: 1. Press alt key to start HUD 2. Write Update status or Available What was expected: HUD should have shown options ether from Gwibber to Update Status or Empathy to change status to Available both available from the messaging indicator. What happened: HUD didn't find any results. Notes: I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm using proprietary fglrx drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1165420/+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 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message
** Branch linked: lp:~renatofilho/unity8/green-led -- 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/1450894 Title: [Indicators] Messaging indicator does not indicate that there is a new message Status in the base for Ubuntu mobile products: Confirmed Status in The Messaging Menu: New Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-messages package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: When you receive a message the indicator menu turns from opaque to full white to indicate that there is a new message. But this is not clear since all the other icons are white and you do not see any difference. This is very confuse to understand that the indicator is in a different state from the other indicators or if it needs attention. --DESIGN RESOLUTION--- Please use the current ubuntu theme green to indicate that there is a new message - #3FB24F, the same green as we use for the battery icon in indicators. Change the LED light to green as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450894/+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 1461618] [NEW] Dash control buttons (close, maximize) do not update on state change
Public bug reported: Dash control buttons should update according to the state when the mouse is hovering or pressing the button. i.e.: 1) hover the close button 2) the button pixmap should change to match the prelight state 3) press the close button 4) the button pixmap should change to match the pressed state ** Affects: unity Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: unity (Ubuntu) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity (Ubuntu) Importance: Undecided = Low ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Branch linked: lp:~3v1n0/unity/overlay-window-buttons-redraw -- 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/1461618 Title: Dash control buttons (close, maximize) do not update on state change Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Dash control buttons should update according to the state when the mouse is hovering or pressing the button. i.e.: 1) hover the close button 2) the button pixmap should change to match the prelight state 3) press the close button 4) the button pixmap should change to match the pressed state To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1461618/+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 1165420] Re: Unable to access indicators from HUD
*** This bug is a duplicate of bug 1072052 *** https://bugs.launchpad.net/bugs/1072052 These two are not duplicates, as per https://bugs.launchpad.net /indicator-appmenu/+bug/1072052/comments/14 -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1165420 Title: Unable to access indicators from HUD Status in Ayatana Design: Confirmed Status in Unity HUD: Confirmed Status in hud package in Ubuntu: Confirmed Bug description: In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's Update Status option there, making status updates to Twitter easy and fast. I could also use HUD to change my status in Empathy from Available to Busy and vice-versa. In Ubuntu 13.04 Beta HUD no longer finds the Update Status option when typing Update Status or Update Also writing Available Away or Busy no longer gives any results. Other indicators however are accessible and I can use HUD to Suspend my computer or to view Skype status or Ubuntu one indicator options. Repeating: 1. Press alt key to start HUD 2. Write Update status or Available What was expected: HUD should have shown options ether from Gwibber to Update Status or Empathy to change status to Available both available from the messaging indicator. What happened: HUD didn't find any results. Notes: I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm using proprietary fglrx drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1165420/+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 1388648] Re: Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native
** Summary changed: - Wine shows the Unity desktop dash when an application runs in full-screen with a resolution diferent from the native + Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity Status: Confirmed = Triaged -- 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/1388648 Title: Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. In the Configure Wine application, go to the graphics tab. 2. Under the window settings section, check the three first boxes and uncheck the latest. 3. Run a Windows application in full-screen mode using a screen resolution different from the default in the desktop. EXPECTED BEHAVIOUR - The application to be presented in full-screen. REAL BEHAVIOUR - As seen in the attached screen-shot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wine 1:1.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 3 00:47:54 2014 InstallationDate: Installed on 2013-05-21 (530 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: wine1.6 UpgradeStatus: Upgraded to utopic on 2014-09-24 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1388648/+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 1388648] Re: Wine shows the Unity desktop dash when an application runs in full-screen with a resolution diferent from the native
https://bugs.winehq.org/show_bug.cgi?id=37496 points to be a bug in Unity. ** Package changed: ubuntu-meta (Ubuntu) = unity (Ubuntu) ** Package changed: unity (Ubuntu) = ubuntu-meta (Ubuntu) ** Package changed: ubuntu-meta (Ubuntu) = unity (Ubuntu) ** Project changed: wine = unity ** No longer affects: unity ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Triaged -- 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/1388648 Title: Wine shows the Unity desktop dash when an application runs in full- screen with a resolution diferent from the native Status in Unity: Confirmed Status in unity package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. In the Configure Wine application, go to the graphics tab. 2. Under the window settings section, check the three first boxes and uncheck the latest. 3. Run a Windows application in full-screen mode using a screen resolution different from the default in the desktop. EXPECTED BEHAVIOUR - The application to be presented in full-screen. REAL BEHAVIOUR - As seen in the attached screen-shot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wine 1:1.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 3 00:47:54 2014 InstallationDate: Installed on 2013-05-21 (530 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: wine1.6 UpgradeStatus: Upgraded to utopic on 2014-09-24 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1388648/+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 1388648] [NEW] Wine shows the Unity desktop dash when an application runs in full-screen with a resolution diferent from the native
You have been subscribed to a public bug: HOW TO REPRODUCE 1. In the Configure Wine application, go to the graphics tab. 2. Under the window settings section, check the three first boxes and uncheck the latest. 3. Run a Windows application in full-screen mode using a screen resolution different from the default in the desktop. EXPECTED BEHAVIOUR - The application to be presented in full-screen. REAL BEHAVIOUR - As seen in the attached screen-shot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wine 1:1.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 3 00:47:54 2014 InstallationDate: Installed on 2013-05-21 (530 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: wine1.6 UpgradeStatus: Upgraded to utopic on 2014-09-24 (39 days ago) ** Affects: wine Importance: Unknown Status: Unknown ** Affects: unity (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug utopic -- Wine shows the Unity desktop dash when an application runs in full-screen with a resolution diferent from the native https://bugs.launchpad.net/bugs/1388648 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1388648] [NEW] Wine shows the Unity desktop dash when an application runs in full-screen with a resolution diferent from the native
You have been subscribed to a public bug: HOW TO REPRODUCE 1. In the Configure Wine application, go to the graphics tab. 2. Under the window settings section, check the three first boxes and uncheck the latest. 3. Run a Windows application in full-screen mode using a screen resolution different from the default in the desktop. EXPECTED BEHAVIOUR - The application to be presented in full-screen. REAL BEHAVIOUR - As seen in the attached screen-shot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wine 1:1.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 3 00:47:54 2014 InstallationDate: Installed on 2013-05-21 (530 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: wine1.6 UpgradeStatus: Upgraded to utopic on 2014-09-24 (39 days ago) ** Affects: wine Importance: Unknown Status: Unknown ** Affects: unity (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug utopic -- Wine shows the Unity desktop dash when an application runs in full-screen with a resolution diferent from the native https://bugs.launchpad.net/bugs/1388648 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1390625] Re: mouse cursor gets corrupted
Just to let subscribers know - there's a $60 bounty for this that can be claimed at any time , as the bug is officially closed. This means you'll receive a cheque for 90% of this bounty by cheque, through the post if you so wish to. https://www.bountysource.com/issues/7168750-mouse-cursor-gets-corrupted [$60 bounty] Thank-yous. -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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
