[Dx-packages] [Bug 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
I have tested exactly what this bug is intended to fix and it does indeed work correctly now. -- 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. [Test Case] 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. [Regression Potential] 1. There may potentially be missing keyboard shorts. 2. Key grabs may persist after the lockscreen has been released. 3. new code contains dynamic memory allocation, which always introduces potential leaks, crashes, or exhaustion To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1289470] Re: The phone has three brightness sliders
mpt, do you want to leave both brightness sliders in u-s-s as well? -- 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/1289470 Title: The phone has three brightness sliders Status in “indicator-power” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: The current phone design has three brightness sliders that do exactly the same thing: * System Settings > "Brightness" * System Settings > "Battery" * the Battery menu. This is kind of ridiculous. We should get rid of one or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1289470/+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 1324068] Re: Brightness slider becomes ineffective with auto brightness turned on
The power indicator's brightness slider is being removed for bug #1289470, and that will of course fix this bug too... -- 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/1324068 Title: Brightness slider becomes ineffective with auto brightness turned on Status in The Power Indicator: New Status in “indicator-power” package in Ubuntu: New Bug description: 1. Go to system settings 2. open brightness panel 3. make sure auto brightness is ticked. 4. drag down the battery indicator from the top 5. try to change the brightness What happens: The slider moves but the brightness remains the same What should happen: probably the slider should be greyed out and not movable with the mention that auto brightness is on and needs to be turned off. Personally I think we are really showing too many indicators in the OS ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.86+14.10.20140522-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5 Uname: Linux 3.15.0-1-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 28 15:44:14 2014 InstallationDate: Installed on 2014-04-21 (36 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity8 UpgradeStatus: Upgraded to utopic on 2014-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1324068/+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 1324298] Re: Incorrect (perhaps outdated) number of windows displayed next to launcher icons
*** This bug is a duplicate of bug 1283775 *** https://bugs.launchpad.net/bugs/1283775 ** This bug has been marked a duplicate of bug 1283775 Launcher: icon pips are not always updated properly -- 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/1324298 Title: Incorrect (perhaps outdated) number of windows displayed next to launcher icons Status in “unity” package in Ubuntu: New Bug description: The number of white arrows on the left of Launcher icons, which is supposed to indicate the number of open windows of a given application, often is incorrect; I think it is because it doesn't always get updated when the number of windows changes (e.g. a window of the same application is open or closed). Switching to another application and then back to the affected one fixes the issue. For example, i have observed only one arrow next to the Terminal icon on Launcher, when I did have two terminal windows open. AND viceversa, on another occasion, there were two arrows next to Google Chrome's Launcher icon when I there was only one open Google Chrome window (I had closed the second window several minutes earlier). I'm almost sure this is a regression in Ubuntu 14.04, because I had never observed it before the upgrade, and now, after upgrading, I have already observed it twice in just a couple of days. Unless that's just an unlikely coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-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: Thu May 29 01:01:20 2014 InstallationDate: Installed on 2013-10-11 (229 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1324298/+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 1312749] Please test proposed package
Hello Jonas, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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! -- 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/1312749 Title: German translation: password wrong text is too long and destroys layout Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: When I try to log in with a wrong password, the string which informs me about the wrong password is too long (I will attach a "screenshot") it makes the password box enlarge, which makes the right end of it (with the circle, that is spinning while logging in) disappear. [Test Case] (1) Log in to Unity (2) Set the local to German (Use the Language Support panel in System Settings) (3) Bring up the lockscren (eg. using control-alt-L) (4) Attempt to unlock but enter an incorrect password [Regression Potential] Rendering error message text in the password dialog has been modified. It is possible the text may break incorrectly or the box may be incorrectly sized. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312749/+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 1317276] Please test proposed package
Hello Stephen, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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! -- 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/1317276 Title: Unity 7 GCC ICE on ARM64 Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “gcc-4.8” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Fix Released Bug description: Unity 7 failed to build from source on ARM64 on Utopic due to an internal compiler error in GCC. Build log excerpt as follows. [ 15%] Building CXX object UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o cd /build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu/UnityCore && /usr/bin/aarch64-linux-gnu-g++ -DUSE_X11 -Dunity_core_6_0_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -O2 -D_FORTIFY_SOURCE=2 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++0x -fno-permissive -Werror -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self -Warray-bounds -Wno-error=unused-local-typedefs -fPIC -I/usr/include/gmock/include -I/usr/src/gmock/gtest/include -I/usr/include/Nux-4.0 -I/usr/include/sigc++-2.0 -I/usr/lib/aarch64-linux-gnu/sigc++-2.0/include -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu -I/build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu/UnityCore -include unitycore_pch.hh -fpch-preprocess -Winvalid-pch -o CMakeFiles/unity-core-6.0.dir/Category.cpp.o -c /build/buildd/unity-7.2.0+14.10.20140507/UnityCore/Category.cpp aarch64-linux-gnu-g++: internal compiler error: Segmentation fault (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See for instructions. UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:126: recipe for target 'UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o' failed make[3]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o] Error 4 More information at https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/+build/5987360 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317276/+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 1283775] Re: Launcher: icon pips are not always updated properly
Since there is some question on how this fix will get out, this is what will happen. First, we need to get this into trunk, which is the 7.3 branch. This will occur on what I believe will be the next landing into Utopic. After that occurs, we will then get the SRU process under way for Trusty. As Mateusz points out, this process can take a bit of time to finally get into trusty-updates, but we will keep pushing to get it done. Thanks! ** Changed in: unity Milestone: 7.2.1 => 7.3.0 ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Milestone: None => 7.2.1 ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => High ** Changed in: unity/7.2 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/1283775 Title: Launcher: icon pips are not always updated properly Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Only occurs when there is just 1 app's windows (unmaxed), assumes multiple workspaces is enabled Test case: Open nautilus (1 pip shows up R. click nautilus icon > open another nautilus window (a 2nd pip does not show, likely due to Bug 1281816 Drag the 2nd naut window fully into current ws, 2nd pip still not shown Click on Desktop, 2nd pip shows up Close one of the naut windows, icon still shows 2 pips. Click again on Desktop, 2nd pip is then removed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 12:28:18 2014 InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+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 1307748] Please test proposed package
Hello Christopher, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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! -- 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/1307748 Title: xpathselect attribute matching doesn't match anything other than object Ids Status in Unity: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: I came across this issue while testing an autopilot branch of mine. The xpathselect server-side matching (as opposed to matching in the autopilot python code) is not working as expected. To reproduce: - Save this code as test_selection_attributes.py - http://paste.ubuntu.com/7252495/ - (with the unity-autopilot package installed) run: `autopilot run test_selection_attributes` This script contains 2 tests, one passes to prove that it can get a Launcher that has the monitor attribute of 0, the 2nd test attempts to select the Launcher object with attribute monitor=0 and fails. We see in the unity logs: - "Unable to match 'monitor' against property of unknown integer type." A bit of digging suggests that GetPropertyValue is returning an array of values (Probably: Object type id, Value?) which means that, in MatchIntegerProperty for instance, the values GVariantClass will never be one of the Integer types. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307748/+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 1221673] Please test proposed package
Hello Tiago, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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! -- 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/1221673 Title: compiz crashed with SIGSEGV in CompAction::initiate() Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] at boot ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 6 10:38:05 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-09-04 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe02b8d169d <_ZN10CompAction8initiateEv+13>: mov0x8(%rdi),%rdx PC (0x7fe02b8d169d) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: unity StacktraceTop: CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130415 unity::MultiActionList::Initiate(std::string const&, std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vector > const&, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so unity::launcher::LauncherIcon::Activate(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo [Test Case] Unclear: this is an intermittent crash problem. [Regression Potential] The worst case is that session would continue to crash on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1221673/+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 1251193] Please test proposed package
Hello 박정규(Jung-Kyu, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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! -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1291461] Please test proposed package
Hello Ruslan, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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! -- 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. [Test Case] 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. [Regression Potential] 1. There may potentially be missing keyboard shorts. 2. Key grabs may persist after the lockscreen has been released. 3. new code contains dynamic memory allocation, which always introduces potential leaks, crashes, or exhaustion To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Changed in: oem-priority/trusty Status: Triaged => Fix Committed ** Changed in: oem-priority Status: New => Fix Committed -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: Fix Committed Status in OEM Priority Project trusty series: Fix Committed Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Status in “qtbase-opensource-src” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Invalid Status in “xorg-server” source package in Trusty: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+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-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,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 Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1323278] Re: Ubuntu Lock Screen always asks to change password when using LDAP Auth
Do you require a password to access to ldap database? -- 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/1323278 Title: Ubuntu Lock Screen always asks to change password when using LDAP Auth Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: After setting up LDAP authentication for user login. Users can log in fine but as soon as the lock screen is activated, the user has to change their password before they can unlock the screen. First prompt is: Enter your password Then: Enter your LDAP Password Then: Enter new password Finally: Confirm (Wording is paraphrased) You can reboot and login without changing the password it is just the lock screen. Obviously what should happen is that you enter your password and carry on with life. Guide for LDAP auth was cobbled together from the community page which references Ubuntu 7.04 and 10.04 and some other googling. It effectively boils down to: sudo apt-get install libnss-ldap libpam-ldap nscd Then editing /etc/nsswitch.conf and /etc/pam.d/common-session to get the user home directories created from skel. I then amend the lightdm config to allow manual logins and disable the guest account. Its entirely possible I've configured something incorrectly however I'm at a loss why login works fine but the lock screen always complains. Any ideas? lsb_release -rd : Description: Ubuntu 14.04 LTS / Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1323278/+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 1251193] Re: Language issue from the unity lense screen
Thank you Chris , Brian I have tested it now , but unfortunately, it failed to upgrade due to dependency problem please see the screenshot I checked it up through sudo aptitude -t trusty-proposed and found one unsatisfied dependency package : libunity-core-6.0-9 ( =7.2.1+14.04.20140513-0ubuntu1) please check it up and let me know what I should do best regards for helping to solve this issue Thank you friends ** Attachment added: "스크린샷, 2014-05-29 16:54:16.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1251193/+attachment/4121979/+files/%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B7%2C%202014-05-29%2016%3A54%3A16.png -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1313280] Re: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen
Removing the verification-failed/needed since the fix for this bug mistakingly missed getting in the SRU. The next SRU will contain this fix. Sorry about the confusion. ** Tags removed: verification-failed ** Branch unlinked: lp:~bregma/unity/7.2.1 ** Changed in: unity (Ubuntu Trusty) Status: Fix Committed => In Progress ** Changed in: unity Status: In Progress => Fix Committed -- 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/1313280 Title: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards, (2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+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 1251193] Re: Language issue from the unity lense screen
I tried this, “unity” 7.2.1+14.04.20140513-0ubuntu1 on Proposed repository, and it works good. The ??? problem has gone. There was no dependency issue for me, as Jung-Kyu Park wrote. Ubuntu 14.04, 32bit. No ppa has been added other than google chrome's. Thanks! -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1324437] [NEW] Nautilus window is not closed upon removable medium ejection
Public bug reported: Usecase / description: Insert USB disk-on-key. It is automounted, opening a new file browser window for each mountable partition. On the left side pane, select any partition with a mouse, right click, select "eject" from the menu. The device is unmounted / ejected all right, but the file browser window stays open. The way it used to be in 12.04: The device used to be unmounted / ejected just the same, the file browser windows (one for each partition) were closed. Why it is so annoying: I constantly use an SD-card with 8 partitions. It was really much nicer when all the windows went away the moment I had ejected the device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Thu May 29 11:33:40 2014 InstallationDate: Installed on 2011-10-23 (948 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (4 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1324437 Title: Nautilus window is not closed upon removable medium ejection Status in “unity” package in Ubuntu: New Bug description: Usecase / description: Insert USB disk-on-key. It is automounted, opening a new file browser window for each mountable partition. On the left side pane, select any partition with a mouse, right click, select "eject" from the menu. The device is unmounted / ejected all right, but the file browser window stays open. The way it used to be in 12.04: The device used to be unmounted / ejected just the same, the file browser windows (one for each partition) were closed. Why it is so annoying: I constantly use an SD-card with 8 partitions. It was really much nicer when all the windows went away the moment I had ejected the device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Thu May 29 11:33:40 2014 InstallationDate: Installed on 2011-10-23 (948 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1324437/+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 1320286] Re: On LTSP thick client gnome-settings-daemon gets loaded before unity-settings-daemon
** Also affects: unity-settings-daemon Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid ** Also affects: gnome-settings-daemon Importance: Undecided Status: New ** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (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/1320286 Title: On LTSP thick client gnome-settings-daemon gets loaded before unity- settings-daemon Status in Gnome Settings Daemon: New Status in Unity Settings Daemon: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Status in “unity-settings-daemon” package in Ubuntu: New Bug description: On amd64 ltsp fat client, gnome-settings-daemon gets loaded before unity-settings-daemon, and thus unity-panel-service doesn't start at all. manually running /usr/lib/unity/unity-panel-service after logging into the unity desktop is a work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1320286/+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 1322808] Re: Window content disappears when double clicking the title bar.
The setting gsettings get org.gnome.desktop.wm.preferences action-double-click- titlebar Is set to shade the window, right? As it seems we've some troubles when a window is shaded... -- 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/1322808 Title: Window content disappears when double clicking the title bar. Status in “unity” package in Ubuntu: New Bug description: Double clicking the window bar makes window content "crash" / disappear and it's almost impossible to restore the window aftewards. This is always reproducable on 14.04, tested on two different computers with both Ati and Nvidia cards with open drivers. 1) Open any app, terminal for example: http://i.imgur.com/NQ8ubk0.png 2) Double click the window decoration 3) Boom, the app is dead: http://i.imgur.com/ohCmk0S.png More example shots: http://i.imgur.com/MJld1DV.png -> http://i.imgur.com/fYQ9DEg.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 24 09:21:20 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2305] InstallationDate: Installed on 2014-04-18 (36 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ae516432-a41a-47d1-a3fe-0d6224e64909 ro quiet splash radeon.dpm=1 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1005 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A87TD/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd08/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TD/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat May 24 09:00:35 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Keyboard KEYBOARD, id 8 inputUSB Keyboard KEYBOARD, id 9 inputKingsis Peripherals ZOWIE Gaming mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1322808/+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 1316005] Re: Panel shadow appears over full screen applications w/ locally integrated menus enabled
** Changed in: unity Milestone: 7.2.1 => 7.3.0 ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Assignee: (unassigned) => Christopher Townsend (townsend) ** Changed in: unity/7.2 Milestone: None => 7.2.1 -- 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/1316005 Title: Panel shadow appears over full screen applications w/ locally integrated menus enabled Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: The shadow of the top Unity panel draws over full screen applications that have controls visible when the mouse is moved. Steps to reproduce: 1) Open an image in Image Viewer 2) Double click the image to full-screen it 3) Move the mouse to the top of the screen to access the controls Expected behavior: Only the image and the Image Viewer controls should be visible Acutal behavior: The Unity panel shadow is drawn on top of the controls at the top of the screen Notes: This also appears in the Videos application, but does not in VLC or gimp. I believe it is GTK applications with UI elements that only appear on mouse movement (gimp's UI is static, and I believe VLC is Qt based). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun May 4 22:37:44 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:2117] InstallationDate: Installed on 2014-04-19 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. G55VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=927ff2bd-c81d-4a5d-9acb-3bd3dd820e35 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G55VW.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G55VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G55VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg
[Dx-packages] [Bug 1309739] Re: Unity launcher icon edge illumination is offset
** Changed in: unity Milestone: 7.2.1 => 7.3.0 ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Assignee: (unassigned) => Christopher Townsend (townsend) ** Changed in: unity/7.2 Milestone: None => 7.2.1 -- 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/1309739 Title: Unity launcher icon edge illumination is offset Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: [Impact] Many users tend to change the size of the Launcher icons to better fit the screen resolution of their monitor or for personal tastes and workflow reasons. This issue causes the "edge glow" of icons to be offset at sizes less than 40 and greater than 56. This looks really ugly and unprofessional. [Test case] * Open CCSM->Ubuntu Unity Plugin->Launcher * Change "Launcher Icon Backlight Mode" to "Edge Illumination Toggles" * Change "Launcher Icon Size" to some value in the range described above such as 38. * Make sure an application is open on the Launcher to see the edge glow around the icon. [Regression Potential] None identified. Original Description: In Unity, when using the edge illumination effect on launcher icons is offset. It shows to the top and left of the icons, but barely at all to the right and bottom. This was not a problem before Trusty; in Saucy and previous releases the edges were aligned properly. See attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1309739/+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 1233199] Re: lock to launcher / unlock from launcher not working...
#11 worked for me as well (14.04, upgraded from 12.04) -- 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/1233199 Title: lock to launcher / unlock from launcher not working... Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When I either click on "Lock to Launcher" or "Unlock from Launcher" nothing happens. Ubuntu Version: 13.10 Unity Version: 7 Steps Taken: - reinstall unity / ubuntu-desktop - reset unity icons Other Info: The only way I'm able to change the icons currently is manually through "gconf" which often requires me to logout and login to take effect. -Peter ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 48.845411] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Mon Sep 30 07:16:12 2013 DistUpgraded: 2013-09-02 00:45:43,852 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-20 (40 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: Gigabyte Technology Co., Ltd. H61N-USB3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=227939ab-2f00-4536-87e2-e2c048aac315 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-09-02 (28 days ago) dmi.bios.date: 05/15/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: H61N-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd05/15/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61N-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61N-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H61N-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 30 00:36:18 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Optical MouseMOUSE, id 8 inputDell Dell USB Keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 723 vendor ACR xserver.version: 2:1.14.2.901-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1233199/+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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
I honestly can't understand how it is supposed to be an intended behavior and I'm sure going to open a new bug. All that said this bug is fixed with trusty-proposed package. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. [Test Case] 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. [Regression Potential] 1. There may potentially be missing keyboard shorts. 2. Key grabs may persist after the lockscreen has been released. 3. new code contains dynamic memory allocation, which always introduces potential leaks, crashes, or exhaustion To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
I reported that confusing behavior as Bug #1324489 if anyone else feels that keyboard layout should carry over from lockscreen to session please mark that bug as affecting you. -- 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. [Test Case] 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. [Regression Potential] 1. There may potentially be missing keyboard shorts. 2. Key grabs may persist after the lockscreen has been released. 3. new code contains dynamic memory allocation, which always introduces potential leaks, crashes, or exhaustion To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 974480] Re: Notification area whitelist is obsolete
Dear Mark, Since you are 'on' this thread...Please see this post from the perspective of some one who has been an unabashed fan of Ubuntu, Canonical and your personal investment into an open source OS with the aim of making it self sustaining ...all of which are noble goals and I fully appreciate the need to have it this way since it should survive beyond you and your personal finances...Having said that...(wait its not bashing time yet) I think you're not respecting the power of lethargy and status quo and learning the lesson from Windows XP as well as can be done...inspite of the best efforts of MS to move people away from XP (discounts on upgrades)...currently there are people paying top dollar for keeping their dependencies going and these people have dedicated IT departments...instead of upgrading closed source commercial applications which they own You are asking nay demanding that open source developers follow a cathedral line where Open source has always been about the Bazaarkeep the options open and let people find their own path...what comes out popular may not be the best technically but it will help your cause win...what is more important to be right or be right now? Sincerely, A ubuntu lover tormented seeing the slow demise of a great movement ironically due to the SA nature of the BDFL...here is hoping that the SABDFL is open to some open thought -- 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/974480 Title: Notification area whitelist is obsolete Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Mark has asked us to consider retiring the notification area whitelist for 12.10. The application indicator system has been in place for two years now, which should be long enough for applications to adopt it. If the whitelist was retired, Java and Wine would be hard-coded as the only software still able to use the menu bar as if it was a notification area, because their developers don't necessarily know that Ubuntu even exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+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 1323992] Re: Logout doesn't call com.canonical.Unity.Session.RequestLogout
Moving to Critical since https://bugs.launchpad.net/unity8/+bug/1302213 that depends on this one is set as Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1323992 Title: Logout doesn't call com.canonical.Unity.Session.RequestLogout Status in “indicator-session” package in Ubuntu: New Bug description: Hi, I've tried with by branch lp:~paulliu/unity8/logout with Unity-Mir session. When manually using qdbus, I can successfully kill unity8 process. But when click logout in indicator-session, I found it didn't call com.canonical.Unity.Session.RequestLogout Here's the dbus-monitor --session log http://paste.ubuntu.com/7534797/ Please check it. Many Thanks, Paul -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Distributor ID: Ubuntu Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 Codename: utopic 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center indicator-session: Installed: 12.10.5+14.04.20140410-0ubuntu1 Candidate: 12.10.5+14.04.20140410-0ubuntu1 Version table: *** 12.10.5+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 500 http://tw.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen unity8 process killed 4) What happened instead nothing happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1323992/+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 1323992] Re: Logout doesn't call com.canonical.Unity.Session.RequestLogout
Ah, i can't :D Well, just wanted to say it should be Critical then ^_^ -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1323992 Title: Logout doesn't call com.canonical.Unity.Session.RequestLogout Status in “indicator-session” package in Ubuntu: New Bug description: Hi, I've tried with by branch lp:~paulliu/unity8/logout with Unity-Mir session. When manually using qdbus, I can successfully kill unity8 process. But when click logout in indicator-session, I found it didn't call com.canonical.Unity.Session.RequestLogout Here's the dbus-monitor --session log http://paste.ubuntu.com/7534797/ Please check it. Many Thanks, Paul -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Distributor ID: Ubuntu Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 Codename: utopic 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center indicator-session: Installed: 12.10.5+14.04.20140410-0ubuntu1 Candidate: 12.10.5+14.04.20140410-0ubuntu1 Version table: *** 12.10.5+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 500 http://tw.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen unity8 process killed 4) What happened instead nothing happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1323992/+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 1323992] Re: Logout doesn't call com.canonical.Unity.Session.RequestLogout
** Changed in: indicator-session (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1323992 Title: Logout doesn't call com.canonical.Unity.Session.RequestLogout Status in “indicator-session” package in Ubuntu: New Bug description: Hi, I've tried with by branch lp:~paulliu/unity8/logout with Unity-Mir session. When manually using qdbus, I can successfully kill unity8 process. But when click logout in indicator-session, I found it didn't call com.canonical.Unity.Session.RequestLogout Here's the dbus-monitor --session log http://paste.ubuntu.com/7534797/ Please check it. Many Thanks, Paul -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Distributor ID: Ubuntu Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 Codename: utopic 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center indicator-session: Installed: 12.10.5+14.04.20140410-0ubuntu1 Candidate: 12.10.5+14.04.20140410-0ubuntu1 Version table: *** 12.10.5+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 500 http://tw.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen unity8 process killed 4) What happened instead nothing happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1323992/+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 1323278] Re: Ubuntu Lock Screen always asks to change password when using LDAP Auth
Hi, I honestly thought I had anonymous read access but it turns out SASL is involved. As a test: ldapsearch -b 'dc=test,dc=local' -H ldap://ldap001 cn=waynemerricks I get: SASL/DIGEST-MD5 authentication started Please enter your password: ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: SASL(-13): user not found: no secret in database But if I do: ldapsearch -x -b 'dc=test,dc=local' -H ldap://ldap001 cn=waynemerricks It works fine. Just trying to figure out how to force simple auth. The login screen must do simple auth somehow but the lock screen certainly doesn't. -- 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/1323278 Title: Ubuntu Lock Screen always asks to change password when using LDAP Auth Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: After setting up LDAP authentication for user login. Users can log in fine but as soon as the lock screen is activated, the user has to change their password before they can unlock the screen. First prompt is: Enter your password Then: Enter your LDAP Password Then: Enter new password Finally: Confirm (Wording is paraphrased) You can reboot and login without changing the password it is just the lock screen. Obviously what should happen is that you enter your password and carry on with life. Guide for LDAP auth was cobbled together from the community page which references Ubuntu 7.04 and 10.04 and some other googling. It effectively boils down to: sudo apt-get install libnss-ldap libpam-ldap nscd Then editing /etc/nsswitch.conf and /etc/pam.d/common-session to get the user home directories created from skel. I then amend the lightdm config to allow manual logins and disable the guest account. Its entirely possible I've configured something incorrectly however I'm at a loss why login works fine but the lock screen always complains. Any ideas? lsb_release -rd : Description: Ubuntu 14.04 LTS / Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1323278/+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
Re: [Dx-packages] [Aims] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
We did not have this problem on 12.04. Only now on 14.04 Regards, Jan On 28 May 2014 17:53, Andrea Azzarone <1314...@bugs.launchpad.net> wrote: > I managed to setup a working system using this guide: > > https://www.digitalocean.com/community/articles/how-to-authenticate-client-computers-using-ldap-on-an-ubuntu-12-04-vps > > So not sure it's a unity issue. If you are using something special > please help to to replicate your configuration. > > ** Changed in: unity >Status: Confirmed => Incomplete > > ** Changed in: unity (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are a member of AIMS, > which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1314095 > > Title: > Unity Lockscreen in 14.04 can't unlock when using LDAP account > > Status in Unity: > Incomplete > Status in "unity" package in Ubuntu: > Incomplete > > Bug 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 > Version table: >*** 7.2.0+14.04.20140416-0ubuntu1 0 > 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages > 100 /var/lib/dpkg/status > lightdm: > Installed: 1.10.0-0ubuntu3 > Candidate: 1.10.0-0ubuntu3 > Version table: >*** 1.10.0-0ubuntu3 0 > 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages > 100 /var/lib/dpkg/status > libpam-modules: > Installed: 1.1.8-1ubuntu2 > Candidate: 1.1.8-1ubuntu2 > Version table: >*** 1.1.8-1ubuntu2 0 > 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages > 100 /var/lib/dpkg/status > > Contents of /var/log/auth.log: > > Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "user" > Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): > authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= > user=user > Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user > authenticated as user@NETWORK > Apr 29 06:49:32 localhost lightdm[15604]: > pam_unix(lightdm-greeter:session): session closed for user lightdm > Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown > Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for > user (user) > Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication > failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user > Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user > authenticated as user@NETWORK > Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info > (user) > Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info > (user) > Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "user" > > cat /etc/pam.d/common-auth > account requiredpam_unix.so > authrequiredpam_group.so > auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure > auth [success=1 default=ignore] pam_krb5.so try_first_pass > minimum_uid=200 > authrequisite pam_deny.so > authrequiredpam_permit.so > > authoptionalpam_afs_session.so minimum_uid=200 > authoptionalpam_ecryptfs.so unwrap > authoptionalpam_cap.so > > cat /etc/pam.d/common-account > account requiredpam_unix.so > > cat /etc/pam.d/lightdm > authrequisite pam_nologin.so > authsufficient pam_succeed_if.so user ingroup nopasswdlogin > @include common-auth > authoptionalpam_gnome_keyring.so > @include common-account > session [success=ok ignore=ignore module_unknown=ignore default=bad] > pam_selinux.so close > authoptionalpam_group.so > session requiredpam_limits.so > @include common-session > session [success=ok ignore=ignore module_unknown=ignore default=
[Dx-packages] [Bug 1324104] Re: Ctrl + Super + D hides windows but still resizable when cursor over border
** Summary changed: - Ctrl + Super + D hides windows but still resizable when mouse over border + Ctrl + Super + D hides windows but still resizable when cursor over border -- 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/1324104 Title: Ctrl + Super + D hides windows but still resizable when cursor over border Status in “unity” package in Ubuntu: New Bug description: If You Press Ctrl + Super + D Shortcut To minimize all windows it works but when you move the cursor you will see it change to an arrow for resizing the hidden windows when the cursor is in the location of the border of the hidden windows Description: Ubuntu 14.04 LTS Release: 14.04 unity: Installed: 7.2.0+14.04.20140423-0ubuntu1.2 Candidate: 7.2.0+14.04.20140423-0ubuntu1.2 Version table: *** 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://lb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 500 http://lb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1324104/+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 1323992] Re: Logout doesn't call com.canonical.Unity.Session.RequestLogout
*** This bug is a duplicate of bug 1296814 *** https://bugs.launchpad.net/bugs/1296814 So, this is not the bug that I thought it was -- I already have a branch for this that I thought had landed in trunk but hasn't, so when investigating I expected to see a bug in the new code rather than the old, unpatched code :-) This is all covered in bug #1296814 so I'm marking this ticket as a duplicate and will promote its importance to Critical to match this one. ** This bug has been marked a duplicate of bug 1296814 When Unity.Session is available, use its API for logging out -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1323992 Title: Logout doesn't call com.canonical.Unity.Session.RequestLogout Status in “indicator-session” package in Ubuntu: New Bug description: Hi, I've tried with by branch lp:~paulliu/unity8/logout with Unity-Mir session. When manually using qdbus, I can successfully kill unity8 process. But when click logout in indicator-session, I found it didn't call com.canonical.Unity.Session.RequestLogout Here's the dbus-monitor --session log http://paste.ubuntu.com/7534797/ Please check it. Many Thanks, Paul -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Distributor ID: Ubuntu Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 Codename: utopic 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center indicator-session: Installed: 12.10.5+14.04.20140410-0ubuntu1 Candidate: 12.10.5+14.04.20140410-0ubuntu1 Version table: *** 12.10.5+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 500 http://tw.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen unity8 process killed 4) What happened instead nothing happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1323992/+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
Perhaps this should then be changed to be a bug against another package rather than unconfirming it. It affects more than one user. We don't want to change our (simple) configurations to an out of date document, we find that our LDAP setup works for logins but not lock screen, and that there seems to be a precedent from the redhat bug. -- 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: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug 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 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "user" Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "user" cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_gnome_keyring.so auto_start session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-password To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314095/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Pos
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Perhaps this should then be changed to be a bug against another package rather than unconfirming it. It affects more than one user. We don't want to change our (simple) configurations to an out of date document, we find that our LDAP setup works for logins but not lock screen, and that there seems to be a precedent from the redhat bug. Since this bug seems to not occur with sssd (comment #4) or libpam-ldap (comment #8) then maybe the bug is with libpam-ldapd. Can Grzegorz Gutowski , Callum Dickinson, Alex Bachmeier, and Nick Piggott confirm that the original problem for them was with libpam- ldapd? -- 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: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug 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 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "user" Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "user" cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_gnome_keyring.so auto_start session requiredpam_env.so readenv=1 session
[Dx-packages] [Bug 1323837] Re: Sim toolkit is not available on UT
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity (Ubuntu) ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided => Wishlist -- 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/1323837 Title: Sim toolkit is not available on UT Status in “ofono” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Triaged Bug description: E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ /SIM-Toolkit While a lot of those addons are completely crap and useless, the SIm toolkit is sometimes used by some phone provider to set your sim card to roaming mode when you are abroad which makes it a must have. For the moment i need to borrow a second phone put my sim card in it, go to the Sim-toolkit, enable my sim card for roaming and put the sim card back in my UT to get my phone working while i am abroad. I need to do the same when i go back home. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1323837/+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 1283775] Re: Launcher: icon pips are not always updated properly
Great, thanks for working on this and keeping us informed, Christopher! -- 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/1283775 Title: Launcher: icon pips are not always updated properly Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Only occurs when there is just 1 app's windows (unmaxed), assumes multiple workspaces is enabled Test case: Open nautilus (1 pip shows up R. click nautilus icon > open another nautilus window (a 2nd pip does not show, likely due to Bug 1281816 Drag the 2nd naut window fully into current ws, 2nd pip still not shown Click on Desktop, 2nd pip shows up Close one of the naut windows, icon still shows 2 pips. Click again on Desktop, 2nd pip is then removed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 12:28:18 2014 InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+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 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
Confirmed on trusty as well. -- 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/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine, press the Super key Expected Result: the super key acts inside the VM Actual Result: the super key acts in the host and the Unity Dash is displayed [regression Potential] This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+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 1251193] Re: Language issue from the unity lense screen
Thank you for test JH Park Here is the way to test I have been through I followed the guide line of https://wiki.ubuntu.com/Testing/EnableProposed * enabling the "trusty-proposed" at the software & update * sudo gedit /etc/apt/preferences Package: * Pin: release a=trusty-proposed Pin-Priority: 400 * sudo apt-get update;sudo apt-get upgrade -s * sudo aptitude -t trusty-proposed of course , I have failed to upgrade by both of them due to dependency sudo apt-get update; sudo apt-get upgrade and sudo apt-get update;sudo apt-get dist-upgrade please leave me a comment, If I did wrong process -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
Any update on this? Lockscreen still falls back to gnome-screensaver after enabling accessibility. -- 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/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard on-screen keyboard: Invalid Status in Unity: Invalid Status in “onboard” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] 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: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413) Package: unity PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1305127] Re: Skype systray icon disappear
** Changed in: unity Status: Triaged => In Progress ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Status: Confirmed => In Progress ** Changed in: unity Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) -- 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/1305127 Title: Skype systray icon disappear Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: I did a Ubuntu 14.04 beta 2 fresh install on one of my notebooks. After that I install Skype from partner repository. The Skype icon in systray shows at start, but disappear after login into my Skype account. Any questions about this just ask. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305127/+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 1307748] Re: xpathselect attribute matching doesn't match anything other than object Ids
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity Milestone: 7.2.1 => 7.3.0 ** Changed in: unity Status: In Progress => Fix Committed ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => High ** Changed in: unity/7.2 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity/7.2 Milestone: None => 7.2.1 -- 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/1307748 Title: xpathselect attribute matching doesn't match anything other than object Ids Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: I came across this issue while testing an autopilot branch of mine. The xpathselect server-side matching (as opposed to matching in the autopilot python code) is not working as expected. To reproduce: - Save this code as test_selection_attributes.py - http://paste.ubuntu.com/7252495/ - (with the unity-autopilot package installed) run: `autopilot run test_selection_attributes` This script contains 2 tests, one passes to prove that it can get a Launcher that has the monitor attribute of 0, the 2nd test attempts to select the Launcher object with attribute monitor=0 and fails. We see in the unity logs: - "Unable to match 'monitor' against property of unknown integer type." A bit of digging suggests that GetPropertyValue is returning an array of values (Probably: Object type id, Value?) which means that, in MatchIntegerProperty for instance, the values GVariantClass will never be one of the Integer types. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307748/+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 1312749] Re: German translation: password wrong text is too long and destroys layout
** Changed in: unity Status: In Progress => Fix Committed -- 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/1312749 Title: German translation: password wrong text is too long and destroys layout Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: When I try to log in with a wrong password, the string which informs me about the wrong password is too long (I will attach a "screenshot") it makes the password box enlarge, which makes the right end of it (with the circle, that is spinning while logging in) disappear. [Test Case] (1) Log in to Unity (2) Set the local to German (Use the Language Support panel in System Settings) (3) Bring up the lockscren (eg. using control-alt-L) (4) Attempt to unlock but enter an incorrect password [Regression Potential] Rendering error message text in the password dialog has been modified. It is possible the text may break incorrectly or the box may be incorrectly sized. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312749/+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 1251193] Re: Language issue from the unity lense screen
** Changed in: unity Status: In Progress => Fix Committed -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1305127] Re: Skype systray icon disappear
*** This bug is a duplicate of bug 1310200 *** https://bugs.launchpad.net/bugs/1310200 ** This bug has been marked a duplicate of bug 1310200 Indicators disappear at the panel (clementine, dropbox, skype etc) -- 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/1305127 Title: Skype systray icon disappear Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: I did a Ubuntu 14.04 beta 2 fresh install on one of my notebooks. After that I install Skype from partner repository. The Skype icon in systray shows at start, but disappear after login into my Skype account. Any questions about this just ask. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305127/+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 1310200] Re: Indicators disappear at the panel (clementine, dropbox, skype etc)
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: unity Status: Confirmed => Won't Fix ** Changed in: unity Status: Won't Fix => In Progress ** Changed in: unity Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: unity/7.2 Importance: Undecided => High -- 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/1310200 Title: Indicators disappear at the panel (clementine, dropbox, skype etc) Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Unconstant indicators (which are changig their graphical state during work of the app, for example skype, clemetine) disappears on the panel. They appear again if you click the mouse on th closest rightest indicator and pull it into left side or they appear after some time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 20 12:26:14 2014 InstallationDate: Installed on 2014-01-14 (95 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310200/+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 1269436] Re: Unity systray disappears
*** This bug is a duplicate of bug 1310200 *** https://bugs.launchpad.net/bugs/1310200 ** This bug is no longer a duplicate of bug 1305127 Skype systray icon disappear ** This bug has been marked a duplicate of bug 1310200 Indicators disappear at the panel (clementine, dropbox, skype etc) -- 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/1269436 Title: Unity systray disappears Status in “unity” package in Ubuntu: Confirmed Bug description: From time to time, systray disappears with all of its icons, which were showing OK up to that point. Needless to say, this defeats the main purpose of apps like Skype or Pidgin. Strange thing is, if I switch to another desktop workspace (Ctrl+Alt+Arrows), the systray appears for a split second during the workspace scrolling, then disappears again. I checked several other bugs and neither seemed to be my case. Also, note that Skype, Pidgin and a few others are whitelisted: $ gsettings get com.canonical.Unity.Panel systray-whitelist ['JavaEmbeddedFrame', 'Wine', 'Update-notifier', 'Skype', 'Pidgin', 'Evolution', 'Vuze', 'Azureus', 'Azureus2'] Is there at least a workaround to get the systray back when this happens? Thanks Using Ubuntu Desktop 12.04.4 LTS 64 bit, ATI Radeon with open source driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1269436/+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 721431] Re: Skype tray icon appeared. It's against new unity philosophy.
Skype now supports libappindicator. Marking as invalid. ** Changed in: unity Status: Confirmed => Invalid ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/721431 Title: Skype tray icon appeared. It's against new unity philosophy. Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Binary package hint: unity Possibly a feature, not a bug, though it's bad to return Skype tray icon, it's against new philosophy of ubuntu desktop. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4 Uname: Linux 2.6.38-3-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,gnomecompat,vpswitch,place,resize,move,shift,regex,mousepoll,thumbnail,session,animation,wall,workarounds,wobbly,fade,scale,expo,unityshell] CompositorRunning: compiz DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: AP///wAGr+wQAAESAQOAIhN4Cua1o1dPlCYeUFQBAQEBAQEBAQEBAQEBAQEBIBxWeFAAJjAwIDQAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2WFcwMSBWMCAKACo= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Fri Feb 18 19:27:32 2011 DistUpgraded: Yes, recently upgraded Log time: 2011-02-17 23:19:57.658042 DistroCodename: natty DistroVariant: ubuntu GraphicsCard: Subsystem: Acer Incorporated [ALI] Device [1025:028d] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110202) InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110202) MachineType: eMachines eMachines E627 ProcEnviron: LANGUAGE=en_US:en LANG=en_GB.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-3-generic root=UUID=9cc66a8c-199d-45cf-b7a2-37cd9127c654 ro quiet splash vt.handoff=7 ProcVersionSignature_: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4 Renderer: Unknown SourcePackage: unity dmi.bios.date: 10/20/2009 dmi.bios.vendor: eMachines dmi.bios.version: V1.08 dmi.board.name: eMachines E627 dmi.board.vendor: eMachines dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: eMachines dmi.chassis.version: V1.08 dmi.modalias: dmi:bvneMachines:bvrV1.08:bd10/20/2009:svneMachines:pneMachinesE627:pvrV1.08:rvneMachines:rneMachinesE627:rvrV1.08:cvneMachines:ct10:cvrV1.08: dmi.product.name: eMachines E627 dmi.product.version: V1.08 dmi.sys.vendor: eMachines version.compiz: compiz 1:0.9.2.1+glibmainloop4-0ubuntu11 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu5 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2+git20110124.fadee040-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu9 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/721431/+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 1317276] Re: Unity 7 GCC ICE on ARM64
Seeing as this built in the ci-train silo, I'd considered this fixed. Otherwise, it wouldn't build and we would be blocked:) ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1317276 Title: Unity 7 GCC ICE on ARM64 Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “gcc-4.8” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Fix Released Bug description: Unity 7 failed to build from source on ARM64 on Utopic due to an internal compiler error in GCC. Build log excerpt as follows. [ 15%] Building CXX object UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o cd /build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu/UnityCore && /usr/bin/aarch64-linux-gnu-g++ -DUSE_X11 -Dunity_core_6_0_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -O2 -D_FORTIFY_SOURCE=2 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++0x -fno-permissive -Werror -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self -Warray-bounds -Wno-error=unused-local-typedefs -fPIC -I/usr/include/gmock/include -I/usr/src/gmock/gtest/include -I/usr/include/Nux-4.0 -I/usr/include/sigc++-2.0 -I/usr/lib/aarch64-linux-gnu/sigc++-2.0/include -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu -I/build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu/UnityCore -include unitycore_pch.hh -fpch-preprocess -Winvalid-pch -o CMakeFiles/unity-core-6.0.dir/Category.cpp.o -c /build/buildd/unity-7.2.0+14.10.20140507/UnityCore/Category.cpp aarch64-linux-gnu-g++: internal compiler error: Segmentation fault (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See for instructions. UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:126: recipe for target 'UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o' failed make[3]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o] Error 4 More information at https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/+build/5987360 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317276/+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 1251193] Re: Language issue from the unity lense screen
@bagjunggyu Enable trusty-proposed as you did. Do 'sudo apt-get update' Then just do 'sudo apt-get install unity'. That should pull in the libunity-core package that is needed. Thanks for trying to test this! -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1272448] Re: December 2013 updates to 12.04 LTS cause multiple problems
Update today to 12.04 restores URL bar copy/paste. However, when the restart button on the update page is clicked, the computer does not complete the restart procedure, but hangs with a dark green screen. It can only be restarted by removing power and the battery. Manual retry works with no further problems (yet). Upon completing the update, a pane displays with the message "failed to download extra data files" flashplugin-installer. This happened with the previous one or two updates also. Very limited testing seems to indicate better keyboard response. -- 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/1272448 Title: December 2013 updates to 12.04 LTS cause multiple problems Status in “unity” package in Ubuntu: New Bug description: December 2013 and January 2014 updates have caused numerous usability problems. Some disappear, then reappear. All the following are current. 1. Firefox and Thunderbird no longer find internet connection when connected wirelessly. System reports wireless connection is established and working, but neither FF nor TB cab find it. Wired connection works OK. This problem first appeared in early December and has continued to date (January 24, 2014). 2. Booting HP Pavilion dv6 laptop fails when external power is connected. Boots OK on battery alone. Bug reported. Problem appeared after January 1, 2014. 3. Firefox loses tab history -- it's still there, but inaccessable unless I reboot. Long-standing issue. 4. Right-click no longer works in Firefox. Can't copy or cut-and- paste. 5. After running for more than a few hours, Firefox window frames become transparent and Firefox no longer works. 6. When using LibreOffice, screen updates cause brief, but very annoying, display flashing or blanking. Blanking is sometimes extended up to ten seconds. (AMD A-8 quad-core processor with 6 GB main memory!). Very alarming. 7. Lost ability to scroll, etc. using "gestures" shortly after January 1, 2014. 8. Unity magically appearing/disappearing scroll tabs replaced Gnome's hard scrollbars. That's not nice. I don't like them. 9. Firefox never, ever restores automagically (though it always did in 10.04 LTS and does on Linux Mint). This issue has been outstanding for two years, or more. No biggie, but it's annoying and very unprofessional. Two bugs reported on this vs. Oneric! C'mon, people. Surely you can do better than that. This system is single-boot Ubuntu 12.04 LTS Gnome 3/Unity on an ext4 filesystem, installed about August 6, 2012 and kept up to date. What happened to the concept that 12.04 was to be a "stable" release? This is the most unstable *n*x OS release I have ever used since 1999 (SuSE 5 through 8, Ubuntu 8.04, 10.04, Mint 13 and 14). This nonsense makes Microsoft Windows almost seem desirable. I also use Linux Mint 14 on other "boxes", an HP Pavilion dv7 and a Dell Optiplex GX620. None of these issues affect Mint 14, although it is based on Ubuntu 12.04 LTS (Mint 14 has its own issues, but none affect usability like these do). Unity sucks stumpwater. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1272448/+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 1272448] Re: December 2013 updates to 12.04 LTS cause multiple problems
The "failed to download extra data files" message doesn't seem to accomplish anything. It just keeps repeating, even though I click the "run this action" button and authenticate. This was the case with previous updates too. THUNDERBIRD problem About two or three weeks ago (perhaps a bit longer), Thunderbird started issuing notices that it could not save to the drafts file. About the same time it started creating a new subdirectory, "Drafts>>[Gmail]>Trash" (or Trash>>[Gmail]>Drafts, I forget which and have lost my notes). Although I can delete the (empty) directory, it reappears and the message persists. Keyboard response is definitely better. Autoclick timeout seems more reasonable, but only with limited testing. -- 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/1272448 Title: December 2013 updates to 12.04 LTS cause multiple problems Status in “unity” package in Ubuntu: New Bug description: December 2013 and January 2014 updates have caused numerous usability problems. Some disappear, then reappear. All the following are current. 1. Firefox and Thunderbird no longer find internet connection when connected wirelessly. System reports wireless connection is established and working, but neither FF nor TB cab find it. Wired connection works OK. This problem first appeared in early December and has continued to date (January 24, 2014). 2. Booting HP Pavilion dv6 laptop fails when external power is connected. Boots OK on battery alone. Bug reported. Problem appeared after January 1, 2014. 3. Firefox loses tab history -- it's still there, but inaccessable unless I reboot. Long-standing issue. 4. Right-click no longer works in Firefox. Can't copy or cut-and- paste. 5. After running for more than a few hours, Firefox window frames become transparent and Firefox no longer works. 6. When using LibreOffice, screen updates cause brief, but very annoying, display flashing or blanking. Blanking is sometimes extended up to ten seconds. (AMD A-8 quad-core processor with 6 GB main memory!). Very alarming. 7. Lost ability to scroll, etc. using "gestures" shortly after January 1, 2014. 8. Unity magically appearing/disappearing scroll tabs replaced Gnome's hard scrollbars. That's not nice. I don't like them. 9. Firefox never, ever restores automagically (though it always did in 10.04 LTS and does on Linux Mint). This issue has been outstanding for two years, or more. No biggie, but it's annoying and very unprofessional. Two bugs reported on this vs. Oneric! C'mon, people. Surely you can do better than that. This system is single-boot Ubuntu 12.04 LTS Gnome 3/Unity on an ext4 filesystem, installed about August 6, 2012 and kept up to date. What happened to the concept that 12.04 was to be a "stable" release? This is the most unstable *n*x OS release I have ever used since 1999 (SuSE 5 through 8, Ubuntu 8.04, 10.04, Mint 13 and 14). This nonsense makes Microsoft Windows almost seem desirable. I also use Linux Mint 14 on other "boxes", an HP Pavilion dv7 and a Dell Optiplex GX620. None of these issues affect Mint 14, although it is based on Ubuntu 12.04 LTS (Mint 14 has its own issues, but none affect usability like these do). Unity sucks stumpwater. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1272448/+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 1251193] Re: Language issue from the unity lense screen
Thank you for comment Christopher I have treid that already too, but , also failed to install it I have tested for doing it by these after adding trusty-proposed repository first , I tried * sudo apt-get update; sudo apt-get upgrade -s for checkinng upgrade , but there was no upgradable message from the terminal so that I tried directly to upgrade to the system * sudo apt-get update * sudo apt-get install unity * sudo apt-get install unity-services * sudo apt-get upgrade * sudo apt-get dist-upgrade but, it said "unity is alreadya newiest package version" , "unity-services is already a newiest package version" Thus, After that I tried to firgure out clearly by * sudo aptitude -t trusty-proposed and, I found one unsatisfied dependency package : libunity-core-6.0-9 ( =7.2.1+14.04.20140513-0ubuntu1) from the terminal I will re-install the ubuntu 14.04 for testing at the fresh install and, I will check it again Thank you for helping to make it clear Thank you 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/1251193 Title: Language issue from the unity lense screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1251193] Re: Language issue from the unity lense screen
I forgot the screenshot for #19 Here it is ** Attachment added: "스크린샷, 2014-05-30 13:15:50.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1251193/+attachment/4122527/+files/%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B7%2C%202014-05-30%2013%3A15%3A50.png -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 798445] Re: can't discern between two files or folder with identical names
This is also to me the main dash problem. I have backup directories and
want to easily know which is the original file/directory and which is
the backup one. Having no indication about it is very user-unfriendly.
--
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/798445
Title:
can't discern between two files or folder with identical names
Status in Ayatana Design:
New
Status in Unity:
Incomplete
Status in Unity Files Lens:
Incomplete
Status in “unity” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: dash
1. create two folders/files with the same name (in two different locations).
2. press the BFB ("Big Freakin Button" aka Home Button) and search for that
folder/file name
see that there is no way to tell which folder/file is which.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: dash 0.5.5.1-7.2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Jun 16 17:50:38 2011
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dash
UpgradeStatus: Upgraded to natty on 2011-04-21 (55 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/798445/+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 1173623] Re: Launcher - Mouse wheel and touchpad two finger/edge scrolling doesn't permit navigating through icons anymore
This is a perfect example of everything that's wrong with Ubuntu. Throwing away a perfectly sane feature just to add an unwanted and unnecessary extra way of doing something is just demented. It just gets more and more unusable. In 14.04 holding ALT activates something else and does NOT allow scrolling the launcher. If I knew the shortcut to bring up the screen of shortcuts I could probably tell you (discoverable much?). Is it Search? -- 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/1173623 Title: Launcher - Mouse wheel and touchpad two finger/edge scrolling doesn't permit navigating through icons anymore Status in Ayatana Design: Won't Fix Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: In Ubuntu 12.10 and earlier, two finger scrolling with the cursor over the Launcher allowed to move the column of icons and reach those below the bottom edge of the screen. It was especially useful on smaller screens (like my 13.3" laptop) with multiple apps in the Launcher (running or pinned). Now, two finger scrolling with the cursor over the Launcher does nothing. Except when precisely over the icon which is associated with more than one window (two or more windows of the same application) in the same virtual desktop when it allows to switch between those windows. Is there a switch/setting to change this behaviour? Desired solution: - The 'window switching using the mouse wheel when the cursor is over a Launcher icon' should only be triggered by the mouse wheel, and should not be triggered by a two-finger trackpad gesture. - Performing a two finger scroll gesture on a trackpad when the cursor is over the Launcher should move the Launcher vertically. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1173623/+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 1307748] Re: xpathselect attribute matching doesn't match anything other than object Ids
ubuntu 14.04-32bit on virtualbox [test case] $ autopilot run test_selection_attributes Loading tests from: /home/testuser/work Tests running... * "Autopilot does not end. * "break was done by "CTRL + C". [ recheck by proposed package] * enable trusty-proposed & installed package. 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 400 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-proposed/main i386 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-updates/main i386 Packages 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-security/main i386 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty/main i386 Packages libunity-core-6.0-9: 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 400 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-proposed/main i386 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-updates/main i386 Packages 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-security/main i386 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty/main i386 Packages unity-services: 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 400 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-proposed/main i386 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-updates/main i386 Packages 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-security/main i386 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty/main i386 Packages unity-autopilot: 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 400 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-proposed/universe i386 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-updates/universe i386 Packages 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty-security/universe i386 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://ubuntu-ashisuto.ubuntulinux.jp/ubuntu/ trusty/universe i386 Packages $ autopilot run test_selection_attributes Loading tests from: /home/testuser/work Tests running... Ran 1 test in 1.361s OK * Is this result correct? -- 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/1307748 Title: xpathselect attribute matching doesn't match anything other than object Ids Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: I came across this issue while testing an autopilot branch of mine. The xpathselect server-side matching (as opposed to matching in the autopilot python code) is not working as expected. To reproduce: - Save this code as test_selection_attributes.py - http://paste.ubuntu.com/7252495/ - (with the unity-autopilot package installed) run: `autopilot run test_selection_attributes` This script contains 2 tests, one passes to prove that it can get a Launcher that has the monitor attribute of 0, the 2nd test attempts to select the Launcher object with attribute monitor=0 and fails. We see in the unity logs: - "Unable to match 'monitor' against property of unknown integer type." A bit of digging suggests that GetPropertyValue is returning an array of values (Probably: Object type id, Value?) which means that, in MatchIntegerProperty for instance, the values GVariantClass will never be one of the Integer types. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307748/+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 1251193] Re: Language issue from the unity lense screen
It sounds like libunity-core-6.0-9 did not get updated for some reason. Could you give the output of the following: apt-cache policy unity apt-cache policy libunity-core-6.0-9 With trusty-proposed enabled, what happens if you type: sudo apt-get install libunity-core-6.0-9 -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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 1307748] Re: xpathselect attribute matching doesn't match anything other than object Ids
Hi, Yes, that is the correct result, so marking this verification-done. Thanks for testing! ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1307748 Title: xpathselect attribute matching doesn't match anything other than object Ids Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: I came across this issue while testing an autopilot branch of mine. The xpathselect server-side matching (as opposed to matching in the autopilot python code) is not working as expected. To reproduce: - Save this code as test_selection_attributes.py - http://paste.ubuntu.com/7252495/ - (with the unity-autopilot package installed) run: `autopilot run test_selection_attributes` This script contains 2 tests, one passes to prove that it can get a Launcher that has the monitor attribute of 0, the 2nd test attempts to select the Launcher object with attribute monitor=0 and fails. We see in the unity logs: - "Unable to match 'monitor' against property of unknown integer type." A bit of digging suggests that GetPropertyValue is returning an array of values (Probably: Object type id, Value?) which means that, in MatchIntegerProperty for instance, the values GVariantClass will never be one of the Integer types. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307748/+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 1251193] Re: Language issue from the unity lense screen
Oh~I already re-install the Ubuntu 14.04 I am sorry for can't help you for checking up libunity-core-6.0-9, Christopher. By the way, For this "" issue of related to Unity The packages delivered from trusty-proposed repository worked perfect! please see the screenshot * software & update -> update -> trusty-proposed * sudo apt-get update; sudo apt-get upgrade -s * sudo apt-get upgrade Thank you for all of you helping to solve this issue Thank you ** Attachment added: "스크린샷, 2014-05-30 15:31:06.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1251193/+attachment/4122650/+files/%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B7%2C%202014-05-30%2015%3A31%3A06.png ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1251193 Title: Language issue from the unity lense screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Every characters over U+AA60 will shown as '?' in dash. It's critical to Korean user because every hangul character(Korean alphabet) is over U+AA60. [Test Case] 1. Install Ubuntu with Korean language. 2. Open dash. 3. See if dash show application's name as set of '?'. [Regression Potential] This fix modifies code added to prevent crashes in the Pango renderer when composing certain Unicode characters in the Burmese code plane. It is likely that the original problem is limited to that code plane, however it is possible that a similar desktop crash could occur with other Unicode code planes in which composite characters are rendered, including Hangul. Form the Unity lens , There are several characters of "" There should be displayed name of certain package , files, etc ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] Date: Thu Nov 14 19:38:05 2013 InstallationDate: Installed on 2013-11-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131113) MarkForUpload: TrueSourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251193/+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
