[Dx-packages] [Bug 2015962] Proposed package upload rejected
An upload of ayatana-indicator-messages to lunar-proposed has been rejected from the upload queue for the following reason: "Rejecting from the queue as this is still missing SRU information, and that should notify someone who cares :). The diff itself looks fine, although the it now also needs fixing in mantic and the lunar upload needs a non- conflicting version number. Please feel free to reupload with those fixed.". -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 1600136] Update Released
The verification of the Stable Release Update for libappindicator has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Released Status in libappindicator source package in Xenial: Fix Released Status in qtbase-opensource-src source package in Xenial: New Status in snapd source package in Xenial: New Status in sni-qt source package in Xenial: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1606246] Update Released
The verification of the Stable Release Update for appmenu-qt5 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1606246 Title: Hard-coded X11 calls cause Unity 8 to fail to run on desktop Status in appmenu-qt5: Fix Released Status in Mir: Triaged Status in appmenu-qt5 package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Released Status in unity8-desktop-session source package in Xenial: New Bug description: The appmenu-qt5 code has hardcoded Xlib calls that cause Unity 8 (or any other Qt-based applicaiton) to die on startup when run on Mir instead of X11. This library extension should either not hardcode X11 (preferred) or check for the presence of a $DISPLAY environment variable and avoid code paths that assume X11. The Unity 8 desktop currently has a hard-coded check for $QT_QPA_PLATFORMTHEME and unsets it as a workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1606246/+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 1393024] Re: Graphical corruption with hidpi scaling
** Changed in: unity Status: Incomplete = Confirmed ** Changed in: unity (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1393024 Title: Graphical corruption with hidpi scaling Status in Compiz: New Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: With a hidpi scaling greater or equal than 2 there is graphical corruption of the window borders in gtk3 apps. Steps to reproduce: 1. Set hidpi scaling to 2. 2. Enlarge a window for nautilus or eye of gnome. Probably it is necessary to do resize the window more than one time to spot the problem. 3. See corrupted window border on the right and/or the bottom. Expected behavior: Clean rendering Ubuntu 14.10 64 Bit Compiz 0.9.12+14.10.20140918-0ubuntu1 Unity 7.3.1+14.10.20141016-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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: Sat Nov 15 16:36:40 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:354e] InstallationDate: Installed on 2014-11-12 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=2a652086-a4da-44ed-ae7f-7b994401ef8b ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: GA-990FXA-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Nov 15 15:00:14 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1393024/+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 1208019] Re: Eclipse menus don't show up in Trusty
Hello Hans, or anyone else affected, Accepted unity-gtk-module into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity-gtk- module/0.0.0+14.04.20140403-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! ** Changed in: unity-gtk-module (Ubuntu Trusty) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus don't show up in Trusty Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Trusty: Fix Committed Status in “unity-gtk-module” source package in Trusty: Fix Committed Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === % === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No
[Dx-packages] [Bug 1290785] Update Released
The verification of the Stable Release Update for accountsservice has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290785 Title: Users with UID 6 are invisible in login and Settings-User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Fix Released Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID UID_MIN. In 13.10 this was changed to UID UID_MIN or UID UID_MAX. [Test Case] 1. Create a user with a UID UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: big-uid is shown in the greeter. Once logged in big-uid is shown in system settings. Observed result: big-uid is not shown in the greeter (14.04 LTS, 14.10) big-uid is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+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
** Also affects: unity (Ubuntu Trusty) 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/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: New 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 1221673] Re: compiz crashed with SIGSEGV in CompAction::initiate()
** Also affects: unity (Ubuntu Trusty) 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/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: New 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=set 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::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption 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 1313280] Re: Fullscreen window set to Always on Top in single-monitor will hide the lockscreen
** Also affects: unity (Ubuntu Trusty) 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/1313280 Title: Fullscreen window set to Always on Top in single-monitor will hide the lockscreen 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: New 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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
** Also affects: unity (Ubuntu Trusty) 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/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: New 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 1317276] Re: Unity 7 GCC ICE on ARM64
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-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/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 file:///usr/share/doc/gcc-4.8/README.Bugs 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 1313280] Re: Fullscreen window set to Always on Top in single-monitor will hide the lockscreen
Hello KillaW0lf04, 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-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1313280 Title: Fullscreen window set to Always on Top in single-monitor will hide the lockscreen 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] 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
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-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/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 1312749] Re: German translation: password wrong text is too long and destroys layout
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-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/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 1307748] Re: xpathselect attribute matching doesn't match anything other than object Ids
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-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
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-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/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 1221673] Re: compiz crashed with SIGSEGV in CompAction::initiate()
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-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/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=set 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::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption 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 1222339] Update Released
The verification of the Stable Release Update for gnome-panel has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1222339 Title: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear Status in Unity GTK+ module: Invalid Status in “gnome-panel” package in Ubuntu: Fix Released Status in “indicator-applet” package in Ubuntu: Invalid Status in “gnome-panel” source package in Trusty: Fix Released Status in “indicator-applet” source package in Trusty: Invalid Bug description: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear. Alt+right-click - delete on the upper left of the panel causes everything to be fixed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-applet-appmenu 12.10.2+13.10.20130822.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 00:10:38 2013 InstallationDate: Installed on 2013-06-11 (89 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True SourcePackage: indicator-applet UpgradeStatus: Upgraded to saucy on 2013-09-07 (0 days ago) [Test Case] 1. install gnome-session-flashback. 2. login in session. 3. add indicator-applet-appmenu to gnome-panel. at this point menu-bar will dissapear. 4. remove indicator-applet-appmenu from panel to get menu-bar back. [Regression Potential] I think there is no regression potential. Same fix is used for external applets built with libpanel-applet library. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/1222339/+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 1080076] Update Released
The verification of the Stable Release Update for ido has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1080076 Title: Music titles in SoundMenu too small Status in elementary OS: Invalid Status in Indicator Display Objects: In Progress Status in “ido” package in Ubuntu: In Progress Status in “ido” source package in Trusty: Fix Released Bug description: [Impact] The artist/title/album labels in the sound menu are often hard to read because they get ellipsized fairly quickly (i.e., for relatively short labels). Also, the menu is visually unbalanced in languages with longer strings (making the menu wider), because the playback controls are hardcoded with a ~100px left margin. The fix for this bug makes the font size a bit smaller, according to the design spec for the sound menu. It also makes sure that labels with a width of about 25 characters are always shown in full, independent of the font size. The playback controls are centered. [Test Case] Play a song in Rhythmbox that has an track name (or artist or album name) that is longer than about 20 characters. Open the sound menu and see that the long label is ellpsized. [Regression Potential] If the fix to this bug is faulty, it might lead to weird menu sizes (too small or too large). The playback controls used hard-coded coordinates for drawing and hit detection. Rendering or selection bugs might occur. [Original Description] When looking at the currently running track in SoundMenu (clementine music player), the space for the title of the track and album are too small, because the album art is directly next to it. Both titles are truncated and thus almost unreadable, when longer than about 10 characters. Is it possible to put the album artwork in a different column? Or make the SoundMenu wider? To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1080076/+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 1080076] Re: Music titles in SoundMenu too small
** Also affects: ido (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1080076 Title: Music titles in SoundMenu too small Status in elementary OS: Invalid Status in Indicator Display Objects: In Progress Status in “ido” package in Ubuntu: In Progress Status in “ido” source package in Trusty: New Bug description: [Impact] The artist/title/album labels in the sound menu are often hard to read because they get ellipsized fairly quickly (i.e., for relatively short labels). Also, the menu is visually unbalanced in languages with longer strings (making the menu wider), because the playback controls are hardcoded with a ~100px left margin. The fix for this bug makes the font size a bit smaller, according to the design spec for the sound menu. It also makes sure that labels with a width of about 25 characters are always shown in full, independent of the font size. The playback controls are centered. [Test Case] Play a song in Rhythmbox that has an track name (or artist or album name) that is longer than about 20 characters. Open the sound menu and see that the long label is ellpsized. [Regression Potential] If the fix to this bug is faulty, it might lead to weird menu sizes (too small or too large). The playback controls used hard-coded coordinates for drawing and hit detection. Rendering or selection bugs might occur. [Original Description] When looking at the currently running track in SoundMenu (clementine music player), the space for the title of the track and album are too small, because the album art is directly next to it. Both titles are truncated and thus almost unreadable, when longer than about 10 characters. Is it possible to put the album artwork in a different column? Or make the SoundMenu wider? To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1080076/+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 1080076] Re: Music titles in SoundMenu too small
This would be a UI change, which pre-release would need a UI freeze exception. It's not a string change, which would affect translations, but I'm not sure to what extent we care about making documentation screenshots inconsistent. I'll take this up with the rest of Ubuntu SRU. -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1080076 Title: Music titles in SoundMenu too small Status in elementary OS: Invalid Status in Indicator Display Objects: In Progress Status in “ido” package in Ubuntu: In Progress Status in “ido” source package in Trusty: New Bug description: [Impact] The artist/title/album labels in the sound menu are often hard to read because they get ellipsized fairly quickly (i.e., for relatively short labels). Also, the menu is visually unbalanced in languages with longer strings (making the menu wider), because the playback controls are hardcoded with a ~100px left margin. The fix for this bug makes the font size a bit smaller, according to the design spec for the sound menu. It also makes sure that labels with a width of about 25 characters are always shown in full, independent of the font size. The playback controls are centered. [Test Case] Play a song in Rhythmbox that has an track name (or artist or album name) that is longer than about 20 characters. Open the sound menu and see that the long label is ellpsized. [Regression Potential] If the fix to this bug is faulty, it might lead to weird menu sizes (too small or too large). The playback controls used hard-coded coordinates for drawing and hit detection. Rendering or selection bugs might occur. [Original Description] When looking at the currently running track in SoundMenu (clementine music player), the space for the title of the track and album are too small, because the album art is directly next to it. Both titles are truncated and thus almost unreadable, when longer than about 10 characters. Is it possible to put the album artwork in a different column? Or make the SoundMenu wider? To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1080076/+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 1080076] Re: Music titles in SoundMenu too small
That does make sense, and I lean towards acceptance. I'll wait for the rest of the SRU team to be able to express their preference, though, as this is the first time I can recall dealing with this :). -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1080076 Title: Music titles in SoundMenu too small Status in elementary OS: Invalid Status in Indicator Display Objects: In Progress Status in “ido” package in Ubuntu: In Progress Status in “ido” source package in Trusty: New Bug description: [Impact] The artist/title/album labels in the sound menu are often hard to read because they get ellipsized fairly quickly (i.e., for relatively short labels). Also, the menu is visually unbalanced in languages with longer strings (making the menu wider), because the playback controls are hardcoded with a ~100px left margin. The fix for this bug makes the font size a bit smaller, according to the design spec for the sound menu. It also makes sure that labels with a width of about 25 characters are always shown in full, independent of the font size. The playback controls are centered. [Test Case] Play a song in Rhythmbox that has an track name (or artist or album name) that is longer than about 20 characters. Open the sound menu and see that the long label is ellpsized. [Regression Potential] If the fix to this bug is faulty, it might lead to weird menu sizes (too small or too large). The playback controls used hard-coded coordinates for drawing and hit detection. Rendering or selection bugs might occur. [Original Description] When looking at the currently running track in SoundMenu (clementine music player), the space for the title of the track and album are too small, because the album art is directly next to it. Both titles are truncated and thus almost unreadable, when longer than about 10 characters. Is it possible to put the album artwork in a different column? Or make the SoundMenu wider? To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1080076/+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 1253591] Re: Display switch and Radio enable/disable hotkey icons
Hello Tim, or anyone else affected, Accepted notify-osd-icons into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/notify-osd- icons/0.8~precise in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: notify-osd-icons (Ubuntu Precise) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd-icons in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons Status in OEM Priority Project: In Progress Status in “notify-osd-icons” package in Ubuntu: Fix Released Status in “notify-osd-icons” source package in Precise: Fix Committed Bug description: 12.04 Precise SRU info: [Impact] The package provide new notify-osd-icons for Radio enable/disable and Display switch. This is related to https://bugs.launchpad.net/ubuntu/+source/notify- osd/+bug/404658 to be used in OEM projects. [Test Case] The package should be install/upgrade correctly. [Regression Potential] No known risk right now. [Other Info] 1) Radio enable/disable, for example Fn-F2 on a Dell XPS13. 2) Display switch, for example Fn-F1 on a Dell XPS13 attached are icons from John Lea To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+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 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted x11proto-input into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/x11proto- input/2.3-1~precise1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: x11proto-input (Ubuntu Precise) 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/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: Fix Committed Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+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 1252121] Update Released
The verification of the Stable Release Update for systemd-shim has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+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 1211514] Update Released
The verification of the Stable Release Update for systemd-shim has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1211514 Title: Shutdowns fail to finish if laptop lid is closed before completely shutdown Status in “systemd-shim” package in Ubuntu: Fix Released Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd-shim” source package in Trusty: Fix Released Bug description: Only seen in a ubuntu (unity) session, others report gnome sessions SRU INFORMATION TEST CASE on laptop: - Shutdown machine from session indicator, close laptop lid right after selecting shutdown or reboot from pop up window. - What should happen: lid close gets ignored and machine should complete shutdown process - What does happen: machine gets suspended until the laptop lid is re-opened, then it either completes the shutdown (if the lid close happened early enough), or hangs eternally FIX: https://github.com/desrt/systemd-shim/commit/6c65a113 and https://github.com/desrt/systemd-shim/commit/b8f324dae5 (both are needed) REGRESSION POTENTIAL: A broken systemd-shim can potentially completely prevent shutdown, reboot, suspend, hibernate. This code has been tested with all scenarios, with both doing suspend/lid close during normal operation, and during shutdown (at which point lid close is now ignored). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130812.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 Uname: Linux 3.11.0-1-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Aug 12 17:01:09 2013 InstallationDate: Installed on 2013-08-07 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1211514/+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 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted qt4-x11 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.1-0ubuntu4.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: qt4-x11 (Ubuntu Precise) 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/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: Fix Committed Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: Fix Committed Status in “x11proto-input” source package in Precise: Fix Committed Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+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 1242633] Re: unity pointer barriers sru bug
** Also affects: libxfixes (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: libxi (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: qt4-x11 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: x11proto-input (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: unity-2d (Ubuntu Precise) 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/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: New Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: New Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+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 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted libxi into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libxi/2:1.7.1.901-1ubuntu1~precise1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libxi (Ubuntu Precise) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: New Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: New Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+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 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted libxfixes into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libxfixes/1:5.0-4ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libxfixes (Ubuntu Precise) 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/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: New Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: New Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+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 1203888] Re: appindicator ignores menu entries after having sent the menu to the indicator
Hello Jeremy, or anyone else affected, Accepted into saucy-proposed. The package will build now and be available in a few hours in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libdbusmenu (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1203888 Title: appindicator ignores menu entries after having sent the menu to the indicator Status in Glipper: Invalid Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Fix Committed Status in “libdbusmenu” source package in Saucy: Fix Committed Bug description: Impact: some indicator menus are incomplete Test Case: see comment #8 Regression potential: Check that your menus still work correctly, the change is only impacting gtk2 and renaming from a signal that was dropped to an existant one, it shouldn't create any issue --- On Saucy, the glipper appindicator shows but none of its menu items show up when left or right-clicking on it. $ glipper SHARED_DATA_DIR: /usr/share/glipper Binding shortcut CtrlAltc to popup glipper Changed process name to: glipper /usr/lib/python2.7/dist-packages/glipper/AppIndicator.py:43: Warning: /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:2475: signal 'child-added' is invalid for instance '0x20c90f0' of type 'GtkMenu' self._app_indicator.set_menu(self.menu) (glipper:20249): LIBDBUSMENU-GLIB-WARNING **: About to Show called on an item wihtout submenus. We're ignoring it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: glipper 2.4-3 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Mon Jul 22 18:17:16 2013 InstallationDate: Installed on 2013-06-14 (38 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True PackageArchitecture: all SourcePackage: glipper UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glipper/+bug/1203888/+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 1067414] Re: gdm crashes if a user account is deleted or added (nslcd, ldap)
*** This bug is a duplicate of bug 1004515 *** https://bugs.launchpad.net/bugs/1004515 Hello H.-Dirk, or anyone else affected, Accepted accountsservice into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/accountsservice/0.6.15-2ubuntu9.7 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! ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1067414 Title: gdm crashes if a user account is deleted or added (nslcd,ldap) Status in “accountsservice” package in Ubuntu: New Status in “gdm” package in Ubuntu: New Bug description: Scenario: * LDAP User Account (NFS Home Directory) * nslcd and gdm are used * user account information is manipulated, e.g. apt-get remove --purge tomcat7* Result: gdm session crashed Syslog: Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l This can be reproduced on 2 different machines and user accounts ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Oct 16 18:00:05 2012 SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+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 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
Hello Wookey, or anyone else affected, Accepted accountsservice into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/accountsservice/0.6.15-2ubuntu9.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: accountsservice (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Committed Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+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
