[Dx-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality
Fix committed into lp:ubuntu-clock-app at revision 89, scheduled for release in ubuntu-clock-app, milestone rtm ** Changed in: ubuntu-clock-app Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+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 1329089] Re: g++-4.9 binary incompatibilties with libraries built with g++-4.8
Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown ** Changed in: mir Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilties with libraries built with g++-4.8 Status in Mir: Fix Committed Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: New Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+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 1283236] Re: Alarms are triggered in UTC tz despite saving in local tz
Fix committed into lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/staging at revision 1010, scheduled for release in ubuntu-ui-toolkit, milestone Unknown ** Changed in: ubuntu-ui-toolkit Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283236 Title: Alarms are triggered in UTC tz despite saving in local tz Status in The Date and Time Indicator: In Progress Status in Clock application for Ubuntu devices: Invalid Status in Ubuntu UI Toolkit: Fix Committed Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “qtorganizer5-eds” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Setting an alarm in the local timezone is not respected by the system since the alarms is triggered in the equivalent UTC timezone. Mako build 200, 205 Steps to reproduce: 1. Ensure that phone timezone is something other than UTC. For instance eastern tz (UTC-5) 2. Set an alarm for 3:00 PM in the ubuntu clock app. 3. Indicator shows a pending alarm for 3:00 PM 4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM What happens: The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM What should happen: The alarm is triggered at 3:00 PM To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283236/+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 1279499] Re: Input interactions in the Switcher has random behavior
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1279499 Title: Input interactions in the Switcher has random behavior Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: When using the Switcher with either the mouse or arrow keys, sometimes they would work and other times they would not. This is causing quite a few AP tests to fail which is blocking landing Unity in distro. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1279499/+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 1113008] Re: F10 or Alt+accelerator opens the window menus within the window
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1113008 Title: F10 or Alt+accelerator opens the window menus within the window Status in Unity: Fix Committed Status in Unity GTK+ module: Triaged Status in “unity-gtk-module” package in Ubuntu: Triaged Bug description: Attempting to activate the menu bar using F10 or Alt+F causes the menu to pop open within the menu instead of from the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1113008/+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 1269409] Re: Reenable closing apps from HUD
Fix committed into lp:ubuntu-ui-toolkit at revision 935, scheduled for release in ubuntu-ui-toolkit, milestone february-2014 ** Changed in: ubuntu-ui-toolkit Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1269409 Title: Reenable closing apps from HUD Status in Camera App: In Progress Status in Unity HUD: Fix Committed Status in Ubuntu UI Toolkit: Fix Committed Status in unity-action-api: Fix Committed Status in The Unity 8 shell: New Status in “hud” package in Ubuntu: Fix Released Bug description: Readd the closing functionality to HUD. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1269409/+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 1277265] Re: Clicking a menu entry doesn't always show the drop down menu the first time
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1277265 Title: Clicking a menu entry doesn't always show the drop down menu the first time Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: When clicking an applications menu entry in the Panel, the drop down menu associated with that entry isn't always shown the first time the entry is clicked. This is particularly apparent when dragging a window to a different monitor and then trying to click. This issue was actually caught during Autopilot testing on multi- monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1277265/+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 1274985] Re: Hud icon states are incorrect when displaying Hud on a monitor with no Launcher
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1274985 Title: Hud icon states are incorrect when displaying Hud on a monitor with no Launcher Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: When using multi-monitors and having the Launcher only on the primary monitor, displaying the Hud on the monitor with no monitor sets the Hud icon with incorrect active and visible states. This causes an Autopilot test failure. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1274985/+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 1269409] Re: Reenable closing apps from HUD
Fix committed into lp:unity-action-api at revision 32, scheduled for release in unity-action-api, milestone Unknown ** Changed in: unity-action-api Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1269409 Title: Reenable closing apps from HUD Status in Unity HUD: Fix Committed Status in Ubuntu UI Toolkit: In Progress Status in unity-action-api: Fix Committed Status in The Unity 8 shell: New Status in “hud” package in Ubuntu: New Bug description: Readd the closing functionality to HUD. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1269409/+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 793450] Re: Calendar doesn't show today's date until opened a second time today
Fix committed into lp:indicator-datetime at revision 296, scheduled for release in indicator-datetime, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/793450 Title: Calendar doesn't show today's date until opened a second time today Status in The Date and Time Indicator: Fix Committed Status in Libindicator: Fix Committed Status in Unity Foundations: Fix Committed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Ubuntu 11.04 indicator-datetime 0.3.1-0ubuntu1, Ubuntu 11.10 indicator-datetime 0.3.94-0ubuntu2, Ubuntu 12.04 Ubuntu 12.10 indicator-datetime 12.10.3daily13.03.26-0ubuntu1, Ubuntu 13.04 Ubuntu 13.10 1) Log in 2) Run a session for a day or two 3) Open the calendar applet by clicking the clock. Although the date in the text field is correct, the graphic calendar still shows the date at which you either originally logged in, or clicked the calendar before. 4) Hide it, and show it once more. The calendar now shows the correct date. The conflicting visual data can be very confusing if you only summon the calendar to find out what day it is. (I don't get much sunlight.) This is the sequel to bug 649800, which was supposedly fixed in Ubuntu 11.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/793450/+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 691817] Re: Framing around window decorations on windows and panel should be identical.
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/691817 Title: Framing around window decorations on windows and panel should be identical. Status in Unity: Fix Committed Status in Unity 2D: Won't Fix Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: Triaged Bug description: AS per the screen shot. The AppMenu in Unity does not display the indent around the window controls the same as a standard window. Sorry to report something so petty. But I read on Mark Shuttleworth's blog that he wants us to report anything and everything to make Natty the most beautiful version of Ubuntu ever. Avoiding any flies in the icecream. Edit: Title to reflect mark's comments bellow. It might be worth updating the bug summary to say they should be identical, rather than that the panel should get the framing, as I don't think the design is final for Natty. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/691817/+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 1267210] Re: Dash/Hud stealing focus from fullscreen windows
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1267210 Title: Dash/Hud stealing focus from fullscreen windows Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Right now with a fullscreen window if you open the dash or hud the focus is taken off the fullscreen window then given to the dash/hud. The problem with this is the dash/hud get rendered under the fullscreen window so you cant actually see the dash/hud. Relating to this bug: https://bugs.launchpad.net/unity/+bug/860970 Once that bug is fixed, then this fix wont be needed any longer. The problem is fixing bug 860970 has a high risk for regressions all over the place in unity, which is not something we would like to introduce into an LTS. So right now we would much rather fix the problem of the dash/hud stealing focus. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1267210/+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 1267888] Re: Using mouse scrollwheel on unfocused/inactive Launcher icons should not focus that app
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1267888 Title: Using mouse scrollwheel on unfocused/inactive Launcher icons should not focus that app Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: In bug #1081843, the following design was given: If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. Subsequent clicks of the mouse wheel the operate exactly as described above. However, a community member recently brought up the issue that this is not expected behavior and posted as such in that bug. Mark Shuttleworth then responded that that design is a mistake and that nothing should happen when using the mouse scroll wheel over a Launcher icon of an unfocused app, no matter how many windows are associated with it. This bug is to fix that design. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1267888/+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 961890] Re: Keyboard shortcuts - dash home does not minimize with ctrl-super-D
Fix committed into lp:unity at revision 3618, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/961890 Title: Keyboard shortcuts - dash home does not minimize with ctrl-super-D Status in Ayatana Design: Incomplete Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: I'm not sure if this is a bug or a feature request. I'm going for a bug because this feature blocks an efficient work proces using ctrl- super-d to go to your desktop. * steps to reproduce - open firefox - open dash home - minimize your windows by pressing ctrl-super-d * expected behavior firefox and dash home are minimized * current behavior Neither firefox or the dash home is minimized, there seems to be a flicker in the screen when pressing ctrl-super-d. all screens and windows should be minimized when pressing ctrl-super-d to ensure an expected behavior when using this keyboard shortcut. Its also neccessary for an efficient work process (kind of important on a desktop computer). * Extra information At this moment there seems no shortcuts working when there is an active unity menu item opened. e.g. no shortcut is working if dash home is opened, or any of the dropdowns in the upper right corner (switch user account, time and date settings, etc). An solution that solves these generic problems is prefered. -- Desired resolution: - Pressing Ctrl+Super+D should minimise both the Dash (if it is open) and all windows. ( See http://tinyurl.com/chxs485 for the full list of Unity keyboard shortcuts ) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/961890/+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 1239381] Re: Unity crashes when entering a term including emu in the home lens
Fix committed into lp:unity/7.1 at revision None, scheduled for release in unity, milestone 7.1.2 ** Changed in: unity Status: Fix Released = 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/1239381 Title: Unity crashes when entering a term including emu in the home lens Status in Pango - Layout and Text Rendering LIbrary: New Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Saucy: In Progress Bug description: Unity version 7.1.2. on Ubuntu 13.10 daily build 2013-10-13 To reproduce: -Make sure an Internet connection is working -Start the Unity Dash, in the home lens -Enter a term including emu -Unity crashes ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.60 Wed Sep 25 14:28:26 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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 Date: Sun Oct 13 17:50:58 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:11c0] InstallationDate: Installed on 2013-10-13 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013) JockeyStatus: kmod:nvidia_319_updates - nvidia_319_updates (Proprietär, Aktiviert, Nicht benutzt) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c1338261-d55c-4a44-87e4-cb7a961b0a27 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z87 Pro3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2.1-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Oct 13 17:29:03 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Gaming Mouse MOUSE, id 8 inputChicony Saitek Eclipse II Keyboard KEYBOARD, id 9 inputChicony Saitek Eclipse II Keyboard KEYBOARD, id 10 xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol:
[Dx-packages] [Bug 830709] Re: Keyboard shortcut - Unity should also use Super-L to lock screen by default
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/830709 Title: Keyboard shortcut - Unity should also use Super-L to lock screen by default Status in Ayatana Design: Fix Committed Status in Gnome Settings Daemon: New Status in Unity: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: In Progress Bug description: Many of Unity's bindings use Super, including 'Show Desktop' which used to use Ctrl-Alt-D. Lock screen however, has remained with Ctrl- Alt-L. Super-L should be added to (not replace) the existing keybinding by default. This would also be familiar for users switching from a well-known OS. --- Desired solution: - Add Super-L keyboard shortcut to lock screen - Leave the existing Ctrl-Alt-L keyboard shortcut in place as an alternative To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/830709/+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 1265565] Re: Add Preedit support for XIM
Fix committed into lp:nux at revision None, scheduled for release in nux, milestone 4.0.4 ** Changed in: nux Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1265565 Title: Add Preedit support for XIM Status in Nux: Fix Committed Status in “nux” package in Ubuntu: In Progress Bug description: Right now in Nux XIM support is very limited. It basically just commit text, with the default style. It really needs to support preedit highlighting, as well as at lease position the preedit window along the X window boundary. So currently if you are using XIM (such as using fcitx in nux) preedit does not show up in the TextEntry. It only appears once you have committed the text. The preedit text needs to be rendered in the TextEntry while the user types in XIM. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1265565/+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 834777] Re: static blur does not show what was on the desktop before the dash opened
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/834777 Title: static blur does not show what was on the desktop before the dash opened Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: When the area behind the dash changes the blur is not updated when using static blur. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/834777/+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 1244704] Re: Some test_hud tests fail on trusty desktop
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 -- 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/1244704 Title: Some test_hud tests fail on trusty desktop Status in Unity HUD: Invalid Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Last daily release run revealed several autopilot failures in the HUD stack, high above our threshold. Those are blocking the release of the HUD stack. The failures are as follows: unity.tests.test_hud.HudBehaviorTests.test_closes_then_focuses_window_on_mouse_down unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Monitor 1,Launcher autohide) unity.tests.test_hud.HudVisualTests.test_hud_icon_shows_the_focused_application_emblem(Monitor 0,Launcher autohide,Launcher on primary monitor) unity.tests.test_hud.HudVisualTests.test_hud_icon_is_shown(Monitor 1,Launcher autohide,Launcher on all monitors) unity.tests.test_hud.HudBehaviorTests.test_mouse_changes_selected_hud_button unity.tests.test_hud.HudBehaviorTests.test_keyboard_steals_focus_from_mouse unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Single Monitor,Launcher never hide) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) Not all happened on both machines at once. Some tests might be flacky on trusty right now. It is unrelated to autopilot 1.4 as we are still using autopilot 1.3 for this run. No public jenkins instance available yet: http://10.97.0.1:8080/job/autopilot-trusty-daily_release/104/ To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1244704/+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 1244704] Re: Some test_hud tests fail on trusty desktop
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 -- 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/1244704 Title: Some test_hud tests fail on trusty desktop Status in Unity HUD: Invalid Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Last daily release run revealed several autopilot failures in the HUD stack, high above our threshold. Those are blocking the release of the HUD stack. The failures are as follows: unity.tests.test_hud.HudBehaviorTests.test_closes_then_focuses_window_on_mouse_down unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Monitor 1,Launcher autohide) unity.tests.test_hud.HudVisualTests.test_hud_icon_shows_the_focused_application_emblem(Monitor 0,Launcher autohide,Launcher on primary monitor) unity.tests.test_hud.HudVisualTests.test_hud_icon_is_shown(Monitor 1,Launcher autohide,Launcher on all monitors) unity.tests.test_hud.HudBehaviorTests.test_mouse_changes_selected_hud_button unity.tests.test_hud.HudBehaviorTests.test_keyboard_steals_focus_from_mouse unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudLauncherInteractionsTests.test_multiple_hud_reveal_does_not_break_launcher(Single Monitor,Launcher never hide) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(transposition) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(duplication) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(insertion) unity.tests.test_search.HudFuzzySearchTests.test_hud_fuzzy_search(deletion) unity.tests.test_search.HudSearchTests.test_hud_search(basic) unity.tests.test_search.HudSearchTests.test_hud_search(lowercase) unity.tests.test_search.HudSearchTests.test_hud_search(uppercase) unity.tests.test_search.HudSearchTests.test_hud_search(partial) Not all happened on both machines at once. Some tests might be flacky on trusty right now. It is unrelated to autopilot 1.4 as we are still using autopilot 1.3 for this run. No public jenkins instance available yet: http://10.97.0.1:8080/job/autopilot-trusty-daily_release/104/ To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1244704/+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 907635] Re: lidbusmenu-GTK crash with Geany IDE using Python
Fix committed into lp:libdbusmenu at revision 464, scheduled for release in libdbusmenu, milestone Unknown ** Changed in: libdbusmenu Status: Expired = Fix Committed -- 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/907635 Title: lidbusmenu-GTK crash with Geany IDE using Python Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Expired Bug description: When I list debug msgs from the Geany Menu, i get: 22:59:03: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:00:42: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:09:48: Geany INFO : *DOC* : Python (UTF-8) 23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:55: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed I have seen the same or similar postings all on Ubuntu or a derivative. Some have implied that it was a known bug with Ubuntu 11.10. Any help would be greatly appreciated. Geany 0.20, libdbusmenu-gtk4, libdbusmenu-gtk3-4, libdbusmenu-gtk-dev, libdbusmenu-gtk3-dev, Ubuntu 11.10 Someone else on the web was having the same problems using Lotus Notes, same error msg. To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/907635/+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 1253740] Re: Active blur for Quicklists/Tooltips no longer working after committing performance updates to Unity
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253740 Title: Active blur for Quicklists/Tooltips no longer working after committing performance updates to Unity Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: After revno. 3591, active blur under Quicklists and Tooltips no longer work. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1253740/+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 1251777] Re: [regression] Semi-maximizing and then restoring the window does not return it to it's original place using Ctrl-Super-Left/Right
Fix committed into lp:compiz at revision None, scheduled for release in compiz, milestone 0.9.11.0 ** Changed in: compiz Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1251777 Title: [regression] Semi-maximizing and then restoring the window does not return it to it's original place using Ctrl-Super-Left/Right Status in Compiz: Fix Committed Status in Unity: In Progress Status in “compiz” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Semi-maximizing a window and then restoring it does not return the window back to it's original place before semi-maximizing it. Steps to reproduce: 1. Place window somewhere near the left side of the screen. 2. Press Ctrl-Super-Right to semi-maximize the window to the right side of the screen. 3. Click the restore button. Observe the window is restored to near right side of the screen instead of back where it was originally near the left. Note: Dragging the window to the left/right edge to semi-maximize *will* restore the window back to its original position. It's only the shortcut that causes this. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1251777/+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 1251777] Re: [regression] Semi-maximizing and then restoring the window does not return it to it's original place using Ctrl-Super-Left/Right
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1251777 Title: [regression] Semi-maximizing and then restoring the window does not return it to it's original place using Ctrl-Super-Left/Right Status in Compiz: Fix Committed Status in Unity: Fix Committed Status in “compiz” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Semi-maximizing a window and then restoring it does not return the window back to it's original place before semi-maximizing it. Steps to reproduce: 1. Place window somewhere near the left side of the screen. 2. Press Ctrl-Super-Right to semi-maximize the window to the right side of the screen. 3. Click the restore button. Observe the window is restored to near right side of the screen instead of back where it was originally near the left. Note: Dragging the window to the left/right edge to semi-maximize *will* restore the window back to its original position. It's only the shortcut that causes this. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1251777/+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 404658] Re: notification summary doesn't change for synchronous messages
Fix committed into lp:notify-osd at revision 475, scheduled for release in notify-osd, milestone Unknown ** Changed in: notify-osd Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages Status in Notify OSD: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “notify-osd” package in Ubuntu: Confirmed Status in “notify-osd” source package in Precise: New Bug description: Precise SRU info: [Impact] * The patch provide a fix to provide the x-canonical-private- synchronous to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the x-canonical-private- synchronous interface only provide this layout to support brightness and volume control. [Test Case] * This patch make following command behave correctly. #notify-send -h string:x-canonical-private-synchronous:1 wireless disable -i notification-network-wireless-none ; sleep 1 ; notify- send -h string:x-canonical-private-synchronous:1 bluetooth enable -i bluetooth In current implementation, both Summary and Body text didn't get updated. [Regression Potential] * The risk should be minimal, the patch should only affect x -canonical-private-synchronous interface. This interface is only used in brightness and volume hotkey, and layout is different. * The patch is already tested in OEM projects. [Other Info] *** Original bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send first title first subtitle -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send second title second subtitle -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION=Ubuntu 9.04 Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Andre Filipe de Assuncao e Brito de...@noisemakers.org Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (= 2.3.4), libglib2.0-0 (= 2.12.0), libnotify1 (= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/notify-osd/+bug/404658/+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 1255241] Re: [regression] Clicking the Hud icon does not close the Hud
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255241 Title: [regression] Clicking the Hud icon does not close the Hud Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: When clicking the Hud icon, the Hud no longer closes. This is a regression in Saucy (and Trusty). This was detected in a Hud AP test failure. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1255241/+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 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0
Fix committed into lp:upstart-app-launch at revision 85, scheduled for release in upstart-app-launch, milestone Unknown ** Changed in: upstart-app-launch Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1197569 Title: Move from zeitgeist-1.0 to zeitgeist-2.0 Status in Bijiben: Fix Released Status in Cairo-Dock: Plug-ins: Fix Released Status in Diodon - GTK+ Clipboard Manager: Triaged Status in Scratch: Fix Committed Status in Totem Movie Player: Fix Released Status in Unity: Fix Released Status in Unity Applications Lens: In Progress Status in Unity Files Lens: Fix Committed Status in Unity Videos Lens: In Progress Status in Upstart Application Launcher: Fix Committed Status in “activity-log-manager” package in Ubuntu: Fix Released Status in “bijiben” package in Ubuntu: New Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Released Status in “diodon” package in Ubuntu: Fix Released Status in “folks” package in Ubuntu: New Status in “nautilus” package in Ubuntu: Confirmed Status in “synapse” package in Ubuntu: New Status in “totem” package in Ubuntu: New Status in “unity” package in Ubuntu: Fix Released Status in “unity-lens-applications” package in Ubuntu: In Progress Status in “unity-lens-files” package in Ubuntu: Fix Released Status in “unity-lens-video” package in Ubuntu: In Progress Status in “upstart-app-launch” package in Ubuntu: New Bug description: The older libzeitgeist (http://launchpad.net/libzeitgeist) served its days and will be deprecated soon. All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0) To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1197569/+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 1179210] Re: unity_low_gfx_mode + auto hide launcher causes visual artifacts
Fix committed into lp:unity/7.1 at revision None, scheduled for release in unity, milestone 7.1.2 -- 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/1179210 Title: unity_low_gfx_mode + auto hide launcher causes visual artifacts Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: If you enable low gfx mode and auto hide launcher an ugly rectangle is drawn on top of the desktop along the left screen border, where the hidden launcher would have been. Take a look at the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-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 Date: Sun May 12 15:16:18 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c08c] Subsystem: Samsung Electronics Co Ltd Device [144d:c08c] InstallationDate: Installed on 2013-05-11 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: SAMSUNG ELECTRONICS CO., LTD. NF110/NF210/NF310 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=a402d2be-1682-4d17-9229-f152a96a19e0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04MY.M033.20110308.JIP dmi.board.asset.tag: SAMSUNG dmi.board.name: NF110/NF210/NF310 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04MY.M033.20110308.JIP:bd03/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnNF110/NF210/NF310:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNF110/NF210/NF310:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: NF110/NF210/NF310 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun May 12 15:11:20 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1179210/+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 1240595] Re: [regression] Unity Launcher Panel is gone after leaving full screen unredirected windows
Fix committed into lp:unity/7.1 at revision None, scheduled for release in unity, milestone 7.1.2 -- 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/1240595 Title: [regression] Unity Launcher Panel is gone after leaving full screen unredirected windows Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Saucy: New Bug description: Unity launcher is gone after fullscreen windows are minimized! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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 Date: Wed Oct 16 19:11:56 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5011] MachineType: LENOVO 37612ZG MarkForUpload: True ProcEnviron: LANGUAGE=lv PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=lv_LV.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=65f7e510-9ce8-4bf6-9fb0-9e6d8c6b4714 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET63WW (0.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 37612ZG dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET63WW(0.63):bd09/05/2012:svnLENOVO:pn37612ZG:pvrLenovoB590:rvnLENOVO:rn37612ZG:rvrWin8STDMMDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37612ZG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 16 18:19:24 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8684 vendor AUO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240595/+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 1232726] Re: Dash bg color doesn't match its surroundings
Fix committed into lp:unity/7.1 at revision None, scheduled for release in unity, milestone 7.1.2 -- 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/1232726 Title: Dash bg color doesn't match its surroundings Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “mesa” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Saucy: In Progress Bug description: Lately, after login the Dash keeps a black background even if the Launcher and panel follow the current wallpaper color. I've added a screenshot. If I change the wallpaper, Dash recovers its chameleonic effect (until next reboot). Also, this started happening at the same time that a new error message (at log time) appeared, I've attached this error message, too. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 unity: Installed: 7.1.1+13.10.20130927.1-0ubuntu1 Candidate: 7.1.1+13.10.20130927.1-0ubuntu1 Version table: *** 7.1.1+13.10.20130927.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20130927.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Sep 29 08:00:07 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30a2] Subsystem: Hewlett-Packard Company Device [103c:30a2] InstallationDate: Installed on 2013-08-31 (28 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YGU Ver. F.0A dmi.board.name: 30A2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.17 dmi.chassis.asset.tag: CNU7111JLR dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx7400 (GF451LA#ABM) dmi.product.version: F.0A dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Sep 29 07:53:46 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputTV-0 VGA-0 xserver.version: 2:1.14.2.901-2ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1232726/+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 1237359] Re: [regression] Icons rearranged on Launcher not saved after reboot
Fix committed into lp:unity/7.1 at revision None, scheduled for release in unity, milestone 7.1.2 -- 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/1237359 Title: [regression] Icons rearranged on Launcher not saved after reboot Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in Unity trunk series: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: First of all, Ubuntu-bug doesn't work properly any more. In the first screen, if I select the option for other it bounces me out of the program. So I selected the least inappropriate working option. Taskbar -- I have the taskbar showing 7 programs. I have deleted some and added the following: Emacs, Wine-NaturallySpeaking, and Wine-notepad. The icons add fine. But I want to move wine-notepad up. I can do this, but when I re-boot the icon is always back where it started. This is a regression. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 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 Date: Wed Oct 9 07:16:01 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2013-08-12 (58 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811) MachineType: LENOVO 3434CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bc02d17d-d76c-41e2-9c8b-038deee84dfb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GCET21WW (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 3434CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET21WW(1.10):bd07/25/2012:svnLENOVO:pn3434CTO:pvrThinkPadX230Tablet:rvnLENOVO:rn3434CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3434CTO dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 9 07:10:01 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.14.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1237359/+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 1247896] Re: /usr/lib/x86_64-linux-gnu/hud/hud-service:11:hud_source_search:hud_query_refresh:hud_query_dispatch_refresh:g_main_dispatch:g_main_context_dispatch
Fix committed into lp:hud at revision 346, scheduled for release in hud, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1247896 Title: /usr/lib/x86_64-linux-gnu/hud/hud- service:11:hud_source_search:hud_query_refresh:hud_query_dispatch_refresh:g_main_dispatch:g_main_context_dispatch Status in Unity HUD: Fix Committed Status in Unity HUD 13.10 series: In Progress Status in Unity HUD 14.04 series: Fix Committed Status in “hud” package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131024-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6afab4b34c7532163fd7a103bb4f321fbb6a7cab contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1247896/+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 1247898] Re: /usr/lib/i386-linux-gnu/hud/hud-service:11:hud_menu_model_collector_add_window:hud_application_source_context_add_window:hud_application_source_add_window:view_opened:f
Fix committed into lp:hud at revision None, scheduled for release in hud, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1247898 Title: /usr/lib/i386-linux-gnu/hud/hud- service:11:hud_menu_model_collector_add_window:hud_application_source_context_add_window:hud_application_source_add_window:view_opened:ffi_call_SYSV Status in Unity HUD: Fix Committed Status in Unity HUD 13.10 series: In Progress Status in Unity HUD 14.04 series: Fix Committed Status in “hud” package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131024-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5af5f02229aef3cf6e93ddb9f7aaaf35a1124842 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1247898/+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 1234624] Re: Spread - In the spread view, clicking on an empty space should perform the same action as pressing the ESC key
Fix committed into lp:compiz at revision None, scheduled for release in compiz, milestone 0.9.11.0 ** Changed in: compiz Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1234624 Title: Spread - In the spread view, clicking on an empty space should perform the same action as pressing the ESC key Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Unity: Invalid Status in “compiz” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Bug description: In the spread view, clicking on an empty space (e.g. anywhere that is not a window or the launcher) should perform the same action as pressing the ESC key and should exit the spread. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1234624/+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 1179210] Re: unity_low_gfx_mode + auto hide launcher causes visual artifacts
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1179210 Title: unity_low_gfx_mode + auto hide launcher causes visual artifacts Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: If you enable low gfx mode and auto hide launcher an ugly rectangle is drawn on top of the desktop along the left screen border, where the hidden launcher would have been. Take a look at the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-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 Date: Sun May 12 15:16:18 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c08c] Subsystem: Samsung Electronics Co Ltd Device [144d:c08c] InstallationDate: Installed on 2013-05-11 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: SAMSUNG ELECTRONICS CO., LTD. NF110/NF210/NF310 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=a402d2be-1682-4d17-9229-f152a96a19e0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04MY.M033.20110308.JIP dmi.board.asset.tag: SAMSUNG dmi.board.name: NF110/NF210/NF310 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04MY.M033.20110308.JIP:bd03/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnNF110/NF210/NF310:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNF110/NF210/NF310:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: NF110/NF210/NF310 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun May 12 15:11:20 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1179210/+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 1185565] Re: Indicators should have Upstart jobs
Fix committed into lp:unity-greeter at revision 1014, scheduled for release in unity-greeter, milestone 14.04.01 ** Changed in: unity-greeter Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in Unity Greeter: Fix Committed Status in “indicator-application” package in Ubuntu: New Status in “indicator-datetime” package in Ubuntu: New Status in “indicator-location” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: New Status in “indicator-session” package in Ubuntu: New Status in “indicator-sound” package in Ubuntu: New Status in “indicator-sync” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: In Progress Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 1080947] Re: damageScreen() in UnityScreen::nuxDamageCompiz() severely hurts Unity performance
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1080947 Title: damageScreen() in UnityScreen::nuxDamageCompiz() severely hurts Unity performance Status in Unity: Fix Committed Status in Unity 6.0 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: There's a call to damageScreen in UnityScreen::nuxDamageCompiz that I had to put there to work around rendering bugs when we did the GLES port. It has a significant impact on performance however and should be removed ASAP, replaced with something like the old version of UnityScreen::nuxDamageCompiz. I think this is causing bug 1039942, and probably others too. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1080947/+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 1248446] Re: unity-panel-service crashed with SIGSEGV in g_object_unref()
Fix committed into lp:ido at revision 158, scheduled for release in ido, milestone Unknown ** Changed in: ido Status: In Progress = Fix Committed -- 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/1248446 Title: unity-panel-service crashed with SIGSEGV in g_object_unref() Status in Indicator Display Objects: Fix Committed Status in “ido” package in Ubuntu: Confirmed Bug description: This started happening after today's dist-upgrade. The panel crashes every few minutes, causing some annoying screen flicker. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7 Uname: Linux 3.12.0-1-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashCounter: 1 Date: Wed Nov 6 09:29:01 2013 EcryptfsInUse: Yes ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2013-10-14 (23 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, user) LANGUAGE=de_DE XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f794f6ea9b4 g_object_unref+20:cmpq $0x50,(%rax) PC (0x7f794f6ea9b4) ok source $0x50 ok destination (%rax) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: g_object_unref (_object=0x1840040) at /build/buildd/glib2.0-2.38.1/./gobject/gobject.c:3089 g_file_icon_finalize (object=0x18d6aa0) at /build/buildd/glib2.0-2.38.1/./gio/gfileicon.c:123 g_object_unref (_object=0x18d6aa0) at /build/buildd/glib2.0-2.38.1/./gobject/gobject.c:3197 ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 g_object_run_dispose (object=0x1b7bc60) at /build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1067 Title: unity-panel-service crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ido/+bug/1248446/+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 1240756] Re: Weirdly-located label for battery Brightness
Fix committed into lp:unity8 at revision 497, scheduled for release in unity8, milestone phone-v1-freeze ** Changed in: unity8 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1240756 Title: Weirdly-located label for battery Brightness Status in The Power Indicator: Fix Committed Status in The Unity 8 shell: Fix Committed Status in “indicator-power” package in Ubuntu: New Bug description: Possibly this is related to lp:1227250 , which I see is freshly fixed; I'm on build 99 (20131015.2), and I've seen this in earlier builds although I haven't been able to reproduce it (and am not confident of these conditions now :( ). With these caveats, I'll attach a screenshot. The label for the brightness indicator appears (unreliably) inside the slider--is this intentional? Will verify in released image tomw. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20131008-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Thu Oct 17 01:07:24 2013 InstallationDate: Installed on 2013-10-15 (1 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131015.2) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1240756/+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 1247898] Re: /usr/lib/i386-linux-gnu/hud/hud-service:11:hud_menu_model_collector_add_window:hud_application_source_context_add_window:hud_application_source_add_window:view_opened:f
Fix committed into lp:hud/13.10 at revision 347, scheduled for release in hud, milestone Unknown ** Changed in: hud Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1247898 Title: /usr/lib/i386-linux-gnu/hud/hud- service:11:hud_menu_model_collector_add_window:hud_application_source_context_add_window:hud_application_source_add_window:view_opened:ffi_call_SYSV Status in Unity HUD: Fix Committed Status in Unity HUD 13.10 series: In Progress Status in Unity HUD 14.04 series: Fix Committed Status in “hud” package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131024-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5af5f02229aef3cf6e93ddb9f7aaaf35a1124842 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1247898/+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 1091589] Re: Nux draws every single BaseWindow to the backbuffer regardless of what the host WM draw region is
Fix committed into lp:nux at revision None, scheduled for release in nux, milestone 4.0.4 ** Changed in: nux Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1091589 Title: Nux draws every single BaseWindow to the backbuffer regardless of what the host WM draw region is Status in Nux: Fix Committed Status in “nux” package in Ubuntu: In Progress Bug description: At the moment, this bug is essentially the reason why bug 1091583 exists in unity. When we switched to using backbuffer persistence in compiz, it means that it was no longer permissible for plugins to draw outside damage boundaries, as that would result in bleeding from the regions beneath not being redrawn. At the moment, calling nux::WindowThread::RenderInterfaceFromForeignCmd causes the entire interface to be drawn on-screen, regardless of the damage region inside of compiz. This means bleeding everywhere. Nux should support the concept of being able to selectively present its render targets to the screen, so that there's no overdraw when we only need to re-present, eg, the launcher or the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1091589/+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 1221871] Re: indicator-power-service is a lightly busy all the time
Fix committed into lp:indicator-power at revision 214, scheduled for release in indicator-power, milestone Unknown ** Changed in: indicator-power Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1221871 Title: indicator-power-service is a lightly busy all the time Status in The Power Indicator: Fix Committed Status in “indicator-power” package in Ubuntu: Triaged Bug description: In a vain attempt to reduce power on these phone devices I noticed that indicator-power-service is using just under 1% of one CPU all the time. CPU usage: PID ProcessUSR% SYS% TOTAL% 1358 indicator-power-serv 0.05 0.04 0.08 (very light load) It seems to be waiting on poll() on a couple of threads which cumulatively add up to about 1.68 wakeups a second over a 1 hour analysis: Top polling system calls: PID 1369 indicator-power-serv poll1.3462 polls/sec 1358 indicator-power-serv poll0.3376 polls/sec Total 1.6838 polls/sec This contributes to a bunch of context switching by these threads: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 1369 indicator-power-serv10.75 0.1510.90 (moderate) 1358 indicator-power-serv 3.53 0.07 3.60 (low) 1372 indicator-power-serv 0.00 0.00 0.00 (idle) Total 14.29 0.2214.50 [ See the attached log, launchpad formatting sucks ] I also observed a couple of brk() calls, and a small amount of heap growth which may indicate it has a small memory leak, but I am speculating on this. Attached is a full report from a 1 hour of monitoring indicator-power- service for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1221871/+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
Fix committed into lp:libdbusmenu at revision 462, scheduled for release in libdbusmenu, milestone Unknown ** Changed in: libdbusmenu Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator 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: New Status in DBus Menu: Fix Committed Status in “blueman” package in Ubuntu: Confirmed Status in “glipper” package in Ubuntu: Triaged Status in “libappindicator” package in Ubuntu: Triaged Bug description: 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 1246812] Re: Can open Evolution in greeter mode
Fix committed into lp:indicator-datetime/13.10 at revision None, scheduled for release in indicator-datetime, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: Fix Committed Status in “indicator-datetime” package in Ubuntu: New Status in “indicator-datetime” source package in Saucy: New Status in “indicator-datetime” source package in Trusty: New Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+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
Fix committed into lp:libdbusmenu/13.10 at revision 462, scheduled for release in libdbusmenu, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages, 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: In Progress 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 1246812] Re: Can open Evolution in greeter mode
Fix committed into lp:indicator-datetime at revision 286, scheduled for release in indicator-datetime, milestone Unknown ** Changed in: indicator-datetime Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: Fix Committed Status in “indicator-datetime” package in Ubuntu: New Status in “indicator-datetime” source package in Saucy: New Status in “indicator-datetime” source package in Trusty: New Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+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 1240141] Re: List of client scopes is not up-to-date
Fix committed into lp:libunity at revision None, scheduled for release in libunity, milestone 7.0.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240141 Title: List of client scopes is not up-to-date Status in LibUnity: Fix Committed Status in “libunity” package in Ubuntu: Fix Released Bug description: The list of scopes in /usr/share/unity/client-scopes.json is not up- to-date with that's provided by the packages, there's just three differences, but we should still fix it, so the server gets correct information. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1240141/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
Fix committed into lp:indicator-appmenu/13.10 at revision None, scheduled for release in indicator-appmenu, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 664647] Re: All menu item text is invisible in Adobe Reader
Fix committed into lp:unity-gtk-module at revision None, scheduled for release in unity-gtk-module, milestone Unknown ** Changed in: unity-gtk-module Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-gtk in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/664647 Title: All menu item text is invisible in Adobe Reader Status in Application menu module for GTK+: Confirmed Status in Unity Foundations: Confirmed Status in Unity GTK+ module: Fix Committed Status in “acroread” package in Ubuntu: Confirmed Status in “appmenu-gtk” package in Ubuntu: Invalid Bug description: indicator-appmenu 0.0.13-0ubuntu1, Ubuntu 10.10 beta appmenu-gtk 0.2.0-0ubuntu1, Ubuntu 11.04 1. Launch Adobe Reader. 2. Open any menu. What you see: All items present, and all separators visible, but the item text is invisible. https://launchpadlibrarian.net/59735690/acroread.png What you should see: The menu items are visible. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/664647/+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 710824] Re: Sound applications without main window should behave different
Fix committed into lp:indicator-sound at revision 401, scheduled for release in indicator-sound, milestone Unknown ** Changed in: indicator-sound Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/710824 Title: Sound applications without main window should behave different Status in Sound Menu: Fix Committed Status in “indicator-sound” package in Ubuntu: Triaged Bug description: Binary package hint: indicator-sound Applications with canRaise()==true and with canRaise()==false are identical in the sound menu. They are all have clickable menuitem with application name, however, applications with canRaise()==false of course do nothing if the menuitem is clicked. I suppose they should be presented in some other way than usual ones. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: indicator-sound 0.5.8-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 Architecture: i386 Date: Mon Jan 31 21:15:39 2011 ProcEnviron: LANGUAGE=pl_PL:pl:ru:ru_RU:en_GB:en PATH=(custom, user) LANG=pl_PL.utf8 LC_MESSAGES=pl_PL.utf8 SHELL=/bin/bash SourcePackage: indicator-sound To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/710824/+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 1237509] Re: test coverage is far too low
Fix committed into lp:indicator-datetime at revision None, scheduled for release in indicator-datetime, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1237509 Title: test coverage is far too low Status in The Date and Time Indicator: Fix Committed Status in “indicator-datetime” package in Ubuntu: New Bug description: Improving test coverage is an ongoing goal across lots of our codebases, but the ratio of features to tests in datetime is just insane. I'm adding the alarm features right now on a tight schedule and it would take me days to add tests for this code because there's absolutely no framework in tests/ for unit testing features in datetime, much less features whose states change over time. So, adding this ticket as a line in the sand to remind myself to improve this in the 14.04 cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1237509/+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 465689] Re: Ubuntu Clock Won't Show Year
Fix committed into lp:indicator-datetime at revision 282, scheduled for release in indicator-datetime, milestone Unknown ** Changed in: indicator-datetime Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/465689 Title: Ubuntu Clock Won't Show Year Status in Desktop panel for GNOME: In Progress Status in The Date and Time Indicator: Fix Committed Status in “gnome-panel” package in Ubuntu: Triaged Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: indicator-datetime, Ubuntu 12.10 The Ubuntu menu bar clock offers no setting to show year. Yes, I know what year it is, but I have very good reason for wanting it shown. For years, I've been collecting screen-shots, when I'm doing something I think is pretty cool. When I use to use windows, these screen shots (over the years) have always showed the current year. However, since April of 2007 (The date I started using Ubuntu exclusively), my screen shots have not included the year, because the Gnome clock doesn't provide this capability. https://wiki.ubuntu.com/TimeAndDate#settings: 'Year' should be both insensitive and unchecked whenever 'Date and month' is unchecked... To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/465689/+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 1091142] Re: Volume scrolling inconsistent
Fix committed into lp:indicator-sound/13.10 at revision 393, scheduled for release in indicator-sound, milestone 0.5.6 ** Changed in: indicator-sound Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1091142 Title: Volume scrolling inconsistent Status in Sound Menu: Fix Committed Status in Unity: Invalid Status in “indicator-sound” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Bug description: When adjusting the volume with the scroll wheel there are two scenario's which are inconsistent with eachother: Scenario 1: 1. Click on the speaker icon in the top right corner 2. Keep hovering over the speaker icon 3. Scroll to adjust the volume. The volume is adjusted in small steps. Sceanrio 2: 1. Click on the speaker icon in the top right corner 2. Move the cursor down and hover over the volume slider. 3. Scroll to adjust the volume. The volume is adjusted in large steps. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Dec 17 10:41:09 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1091142/+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 1240595] Re: [regression] Unity Launcher Panel is gone after leaving full screen unredirected windows
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240595 Title: [regression] Unity Launcher Panel is gone after leaving full screen unredirected windows Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Unity launcher is gone after fullscreen windows are minimized! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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 Date: Wed Oct 16 19:11:56 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5011] MachineType: LENOVO 37612ZG MarkForUpload: True ProcEnviron: LANGUAGE=lv PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=lv_LV.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=65f7e510-9ce8-4bf6-9fb0-9e6d8c6b4714 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET63WW (0.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 37612ZG dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET63WW(0.63):bd09/05/2012:svnLENOVO:pn37612ZG:pvrLenovoB590:rvnLENOVO:rn37612ZG:rvrWin8STDMMDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37612ZG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 16 18:19:24 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8684 vendor AUO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240595/+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 1244010] Re: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service:11:_IO_vfprintf_internal:buffered_vfprintf:_IO_vfprintf_internal:___fprintf_chk:pa_log_levelv_meta
Fix committed into lp:indicator-sound/13.10 at revision None, scheduled for release in indicator-sound, milestone 0.5.6 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244010 Title: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound- service:11:_IO_vfprintf_internal:buffered_vfprintf:_IO_vfprintf_internal:___fprintf_chk:pa_log_levelv_meta Status in Sound Menu: Fix Committed Status in “indicator-sound” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-sound. This problem was most recently seen with version 12.10.2+13.10.20131011-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/d73e81071c5c71876c0087cb4715f18d3c038725 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1244010/+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 767752] Re: Unity Windows return to the wrong place in multi-moniter
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/767752 Title: Unity Windows return to the wrong place in multi-moniter Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Binary package hint: unity When a window is minimized or an icon is placed on the unity panel, the window or icon's animation flys towards the left side of the left hand moniter (even though it has no unity panel). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.10-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz DRM.card0.HDMI.A.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.VGA.1: status: connected enabled: enabled dpms: On modes: 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400 edid-base64: AP///wAebdpK9qkAAAUQAQNoJh546qKlo1dMnSURUFSlaoAxT0VPYU+BgAEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5GCwAKICAgICAg/ABNMTkxN0EKICAgICAg/AAKACAgICAgICAgICAgALg= Date: Wed Apr 20 22:26:44 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu GraphicsCard: ATI Technologies Inc RV710 [Radeon HD 4350] [1002:954f] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2008] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413) InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413) InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=4f56d13d-1499-460e-b05e-6c1d928e3c0c ro quiet splash vt.handoff=7 ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2 ProcVersionSignature__: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Renderer: Unknown SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0407 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78-VM IN/SI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0407:bd07/15/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78-VMIN/SI:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.ia32-libs: ia32-libs 20090808ubuntu12 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/767752/+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 1243529] Re: unity FTBFS on trusty
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1243529 Title: unity FTBFS on trusty Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: See https://launchpadlibrarian.net/154760401/buildlog_ubuntu-trusty- amd64.unity_7.1.2%2B14.04.20131023-0ubuntu1_FAILEDTOBUILD.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243529/+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 1244010] Re: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service:11:_IO_vfprintf_internal:buffered_vfprintf:_IO_vfprintf_internal:___fprintf_chk:pa_log_levelv_meta
Fix committed into lp:indicator-sound at revision None, scheduled for release in indicator-sound, milestone Unknown ** Changed in: indicator-sound Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244010 Title: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound- service:11:_IO_vfprintf_internal:buffered_vfprintf:_IO_vfprintf_internal:___fprintf_chk:pa_log_levelv_meta Status in Sound Menu: Fix Committed Status in “indicator-sound” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-sound. This problem was most recently seen with version 12.10.2+13.10.20131011-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/d73e81071c5c71876c0087cb4715f18d3c038725 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1244010/+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 1220204] Re: speaker icon no longer displays mute status correctly
Fix committed into lp:libindicator/13.10 at revision None, scheduled for release in libindicator, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1220204 Title: speaker icon no longer displays mute status correctly Status in Sound Menu: Invalid Status in Libindicator: Fix Committed Status in “indicator-sound” package in Ubuntu: Invalid Status in “libindicator” package in Ubuntu: Fix Committed Status in “indicator-sound” source package in Saucy: Invalid Status in “libindicator” source package in Saucy: Fix Committed Bug description: Impact: indicator icons stop updating sometime Testcase: - use a non US locale/keyboard - start a guest session - change they keyboard layout from the indicator - the icon in the panel should update to reflect the current layout Regression potential: check that indicators icons are correctly listed and updated --- Selecting Mute from the sound indicator no longer updates the icon properly. For example, my sound currently isn't muted, but the icon shows a muted speaker with an X beside it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20130829-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 Date: Tue Sep 3 07:40:26 2013 InstallationDate: Installed on 2012-11-13 (293 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: Upgraded to saucy on 2013-08-19 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1220204/+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 1239710] Re: indicator-datetime and -session missing ~10% of the time
Fix committed into lp:indicator-datetime/13.10 at revision None, scheduled for release in indicator-datetime, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1239710 Title: indicator-datetime and -session missing ~10% of the time Status in The Date and Time Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: Confirmed Bug description: Indicator-datetime is not showing in the indicator bar today on image 96. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf Date: Mon Oct 14 16:00:26 2013 InstallationDate: Installed on 2013-10-14 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131014) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1239710/+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 1220204] Re: speaker icon no longer displays mute status correctly
Fix committed into lp:libindicator at revision 514, scheduled for release in libindicator, milestone Unknown ** Changed in: libindicator Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1220204 Title: speaker icon no longer displays mute status correctly Status in Sound Menu: Invalid Status in Libindicator: Fix Committed Status in “indicator-sound” package in Ubuntu: Invalid Status in “libindicator” package in Ubuntu: Confirmed Bug description: Selecting Mute from the sound indicator no longer updates the icon properly. For example, my sound currently isn't muted, but the icon shows a muted speaker with an X beside it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20130829-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 Date: Tue Sep 3 07:40:26 2013 InstallationDate: Installed on 2012-11-13 (293 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: Upgraded to saucy on 2013-08-19 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1220204/+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 1239381] Re: Unity crashes when entering a term including emu in the home lens
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239381 Title: Unity crashes when entering a term including emu in the home lens Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Unity version 7.1.2. on Ubuntu 13.10 daily build 2013-10-13 To reproduce: -Make sure an Internet connection is working -Start the Unity Dash, in the home lens -Enter a term including emu -Unity crashes ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.60 Wed Sep 25 14:28:26 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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 Date: Sun Oct 13 17:50:58 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:11c0] InstallationDate: Installed on 2013-10-13 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013) JockeyStatus: kmod:nvidia_319_updates - nvidia_319_updates (Proprietär, Aktiviert, Nicht benutzt) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c1338261-d55c-4a44-87e4-cb7a961b0a27 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z87 Pro3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2.1-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Oct 13 17:29:03 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Gaming Mouse MOUSE, id 8 inputChicony Saitek Eclipse II Keyboard KEYBOARD, id 9 inputChicony Saitek Eclipse II Keyboard KEYBOARD, id 10 xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context Failed to load module glamoregl (loader failed, 7) open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs:
[Dx-packages] [Bug 1236720] Re: unity-panel-service crashed with SIGABRT
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: Triaged = 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/1236720 Title: unity-panel-service crashed with SIGABRT Status in The Application Menu: New Status in Unity: Fix Committed Status in Unity 7.1 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Crash at login. Ubuntu 13.10 daily build fresh install ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 8 09:17:33 2013 Disassembly: = 0xb7782424: Cannot access memory at address 0xb7782424 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] [1002:7145] (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions Device [1734:10b0] InstallationDate: Installed on 2013-10-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta i386 (20131007) MachineType: FUJITSU SIEMENS AMILO Pi 1536 MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=it XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=b2533600-b3b2-4a53-9e01-1734bcba7662 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: unity Stacktrace: #0 0xb7782424 in ?? () No symbol table info available. Cannot access memory at address 0xbfffb044 StacktraceTop: ?? () ThreadStacktrace: . Thread 4 (LWP 9353): #0 0xb7782424 in ?? () No symbol table info available. Cannot access memory at address 0xac94108c Title: unity-panel-service crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 03/16/2007 dmi.bios.vendor: FUJITSU SIEMENS dmi.bios.version: 1.23 dmi.board.name: AMILO Pi 1536 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Not Applicable dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: Not Applicable dmi.modalias: dmi:bvnFUJITSUSIEMENS:bvr1.23:bd03/16/2007:svnFUJITSUSIEMENS:pnAMILOPi1536:pvrNotApplicable:rvnFUJITSUSIEMENS:rnAMILOPi1536:rvrNotApplicable:cvnFUJITSUSIEMENS:ct10:cvrNotApplicable: dmi.product.name: AMILO Pi 1536 dmi.product.version: Not Applicable dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Oct 8 09:17:38 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1236720/+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 1227106] Re: indicator-datetime menu buttons do nothing
Fix committed into lp:indicator-datetime at revision 271, scheduled for release in indicator-datetime, milestone Unknown ** Changed in: indicator-datetime Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1227106 Title: indicator-datetime menu buttons do nothing Status in The Date and Time Indicator: Fix Committed Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “indicator-datetime” source package in Saucy: Confirmed Bug description: None of the links inside the datetime indicator work. Press the clock or calendar app don't open, neither do the indicator settings. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.1-0ubuntu4 Architecture: armhf Date: Wed Sep 18 12:44:27 2013 InstallationDate: Installed on 2013-09-17 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130917.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1227106/+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 1233994] Re: hud apport hook fails with: File /usr/share/apport/package-hooks/source_hud.py, line 4, in add_info NameError: global name 'apport' is not defined
Fix committed into lp:hud at revision 337, scheduled for release in hud, milestone Unknown ** Changed in: hud Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1233994 Title: hud apport hook fails with: File /usr/share/apport/package- hooks/source_hud.py, line 4, in add_info NameError: global name 'apport' is not defined Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: In Progress Bug description: From the command line run: $ ubunt-bug hud The following error is displayed on the terminal ERROR: hook /usr/share/apport/package-hooks/source_hud.py crashed: Traceback (most recent call last): File /usr/lib/python3/dist-packages/apport/report.py, line 197, in _run_hook symb['add_info'](report, ui) TypeError: add_info() takes 1 positional argument but 2 were given During handling of the above exception, another exception occurred: Traceback (most recent call last): File /usr/lib/python3/dist-packages/apport/report.py, line 202, in _run_hook symb['add_info'](report) File /usr/share/apport/package-hooks/source_hud.py, line 4, in add_info if not apport.packaging.is_distro_package(report['Package'].split()[0]): NameError: global name 'apport' is not defined ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130918-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu1 Architecture: armhf Date: Wed Oct 2 06:05:00 2013 InstallationDate: Installed on 2013-10-01 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131001.3) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1233994/+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 1239474] Re: do not build-depend on mono on AArch64, not yet available
Fix committed into lp:libappindicator at revision 268, scheduled for release in libappindicator, milestone Unknown ** Changed in: libappindicator Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239474 Title: do not build-depend on mono on AArch64, not yet available Status in Libappindicator: Fix Committed Status in “libappindicator” package in Ubuntu: Confirmed Status in “libappindicator” source package in Saucy: Confirmed Bug description: do not build-depend on mono on AArch64, not yet available To manage notifications about this bug go to: https://bugs.launchpad.net/libappindicator/+bug/1239474/+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 1175669] Re: fcitx often fails to work in dash with Unity
Fix committed into lp:nux at revision None, scheduled for release in nux, milestone 4.0.4 ** Changed in: nux Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1175669 Title: fcitx often fails to work in dash with Unity Status in Nux: Fix Committed Status in Unity: Invalid Status in “nux” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Bug description: The input method fcitx' is supposed to work with Unity dash in raring,but it is not working well. This happens *only* when I set the launcher to hide as default. When I press Super to open the dash and begin to type characters into dash or HUD display (by pressing left alt),sometimes I can activate the input method.In more cases,there aren't any response when pressing ctrl+space.Sometimes I can't type anything into dash. I've asked a developer of fcitx (csslayer) but he said he knew nothing about it.He said it could be a bug of unity and suggested me to report the bug here. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu May 2 23:51:07 2013 InstallationDate: Installed on 2012-05-01 (365 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-04-03 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1175669/+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 1237359] Re: [regression] Icons rearranged on Launcher not saved after reboot
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1237359 Title: [regression] Icons rearranged on Launcher not saved after reboot Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in Unity trunk series: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: First of all, Ubuntu-bug doesn't work properly any more. In the first screen, if I select the option for other it bounces me out of the program. So I selected the least inappropriate working option. Taskbar -- I have the taskbar showing 7 programs. I have deleted some and added the following: Emacs, Wine-NaturallySpeaking, and Wine-notepad. The icons add fine. But I want to move wine-notepad up. I can do this, but when I re-boot the icon is always back where it started. This is a regression. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 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 Date: Wed Oct 9 07:16:01 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2013-08-12 (58 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811) MachineType: LENOVO 3434CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bc02d17d-d76c-41e2-9c8b-038deee84dfb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GCET21WW (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 3434CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET21WW(1.10):bd07/25/2012:svnLENOVO:pn3434CTO:pvrThinkPadX230Tablet:rvnLENOVO:rn3434CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3434CTO dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 9 07:10:01 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.14.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1237359/+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 1233992] Re: HUD does not support unity8's ApplicationManger
Fix committed into lp:unity-mir at revision 110, scheduled for release in unity-mir, milestone phone-v1-freeze ** Changed in: unity-mir Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1233992 Title: HUD does not support unity8's ApplicationManger Status in Unity HUD: New Status in Unity Mir: Fix Committed Status in “hud” package in Ubuntu: In Progress Bug description: I got this crash right after booting the device with mir enabled. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130918-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu1 Architecture: armhf Date: Wed Oct 2 05:57:57 2013 Disassembly: = 0x4007b494: Cannot access memory at address 0x4007b494 ExecutablePath: /usr/lib/arm-linux-gnueabihf/hud/hud-service InstallationDate: Installed on 2013-10-01 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131001.3) LocalLibraries: /android/system/lib/libGLESv2.so /android/system/lib/libnetutils.so /android/system/lib/libsync.so /android/system/lib/libskia.so /android/system/lib/libstlport.so /android/system/lib/libstdc++.so /android/system/lib/libdsyscalls.so /android/system/lib/libm.so /android/system/lib/libc.so /android/system/lib/libGLES_trace.so /android/system/lib/libexpat.so /android/system/lib/liblog.so /android/system/lib/libcorkscrew.so /android/system/lib/libubuntu_application_api.so /android/system/lib/libgccdemangle.so /android/system/lib/libutils.so /android/system/lib/libjpeg.so /android/system/lib/libemoji.so /android/system/lib/libhardware_legacy.so /android/system/lib/libandroidfw.so /android/system/lib/libbinder.so /android/system/lib/libhardware.so /android/system/lib/libz.so /android/system/lib/libgui.so /android/system/lib/libcutils.so /android/system/lib/libEGL.so /android/system/lib/libwpa_client.so /android/system/lib/libui.so MarkForUpload: True ProcCmdline: /usr/lib/arm-linux-gnueabihf/hud/hud-service Signal: 11 SourcePackage: hud StacktraceTop: ?? () ?? () ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1233992/+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 1210357] Re: FTBFS
Fix committed into lp:unity-lens-music at revision 147, scheduled for release in unity-lens-music, milestone 0.2.8 ** Changed in: unity-lens-music Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1210357 Title: FTBFS Status in unity-lens-music: Fix Committed Status in “unity-lens-music” package in Ubuntu: Confirmed Bug description: The lens itself is quite troubled, maybe you all are getting rid of? (no dev since june error - GEN unity_music_daemon.vala.stamp simple-scope.vala:134.33-134.59: error: The name `FLOW' does not exist in the context of `Unity.CategoryRenderer' Unity.CategoryRenderer.FLOW); ^^^ daemon.vala:37.11-37.33: warning: unhandled error `GLib.Error' banshee.scope.export (); ^^^ daemon.vala:48.11-48.28: warning: unhandled error `GLib.Error' rb.scope.export (); ^^ Compilation failed: 1 error(s), 2 warning(s) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-lens-music 6.9.0daily13.06.21-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Thu Aug 8 22:20:05 2013 InstallationDate: Installed on 2013-08-07 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803) MarkForUpload: True SourcePackage: unity-lens-music UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-music/+bug/1210357/+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 1233992] Re: HUD does not support unity8's window stack API
Fix committed into lp:hud at revision 329, scheduled for release in hud, milestone Unknown ** Changed in: hud Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1233992 Title: HUD does not support unity8's window stack API Status in Unity HUD: Fix Committed Status in Unity Mir: Fix Committed Status in “hud” package in Ubuntu: In Progress Status in “unity-mir” package in Ubuntu: New Bug description: The crux of the problem here is that HUD was talking to the SurfaceFlinger based Unity Platform API. We HUD to talk to unity8's new window stack API. On the desktop we will construct a bridge daemon that adapts from the BAMF API to the unity8 API. --- I got this crash right after booting the device with mir enabled. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130918-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu1 Architecture: armhf Date: Wed Oct 2 05:57:57 2013 Disassembly: = 0x4007b494: Cannot access memory at address 0x4007b494 ExecutablePath: /usr/lib/arm-linux-gnueabihf/hud/hud-service InstallationDate: Installed on 2013-10-01 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131001.3) LocalLibraries: /android/system/lib/libGLESv2.so /android/system/lib/libnetutils.so /android/system/lib/libsync.so /android/system/lib/libskia.so /android/system/lib/libstlport.so /android/system/lib/libstdc++.so /android/system/lib/libdsyscalls.so /android/system/lib/libm.so /android/system/lib/libc.so /android/system/lib/libGLES_trace.so /android/system/lib/libexpat.so /android/system/lib/liblog.so /android/system/lib/libcorkscrew.so /android/system/lib/libubuntu_application_api.so /android/system/lib/libgccdemangle.so /android/system/lib/libutils.so /android/system/lib/libjpeg.so /android/system/lib/libemoji.so /android/system/lib/libhardware_legacy.so /android/system/lib/libandroidfw.so /android/system/lib/libbinder.so /android/system/lib/libhardware.so /android/system/lib/libz.so /android/system/lib/libgui.so /android/system/lib/libcutils.so /android/system/lib/libEGL.so /android/system/lib/libwpa_client.so /android/system/lib/libui.so MarkForUpload: True ProcCmdline: /usr/lib/arm-linux-gnueabihf/hud/hud-service Signal: 11 SourcePackage: hud StacktraceTop: ?? () ?? () ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1233992/+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 1237161] Re: Unity may crash on ApplicationLauncherIcon::Stick after installing an app from Software Center
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1237161 Title: Unity may crash on ApplicationLauncherIcon::Stick after installing an app from Software Center Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.1.1+13.10.20131004-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/eae0211c6130d2de17e2ee3682fa4c8411d7ad01 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1237161/+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 1227519] Re: no time indicator on boot
Fix committed into lp:indicator-datetime at revision None, scheduled for release in indicator-datetime, milestone Unknown ** Changed in: indicator-datetime Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1227519 Title: no time indicator on boot Status in The Date and Time Indicator: Fix Committed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: mako 20130918 TEST CASE: 1. Flash a device with 20130918 2. After installation, reboot with: adb reboot - Check the status of the indicators ACTUAL RESULT Time indicator is missing (screenshot attached) EXPECTED RESULT: It is present. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.2-0ubuntu1 Architecture: armhf Date: Thu Sep 19 08:37:04 2013 InstallationDate: Installed on 2013-09-18 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130918) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1227519/+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 1231444] Re: Use /// to remove hostname element
Fix committed into lp:indicator-power at revision 206, scheduled for release in indicator-power, milestone Unknown ** Changed in: indicator-power Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1231444 Title: Use /// to remove hostname element Status in Bluetooth Menu: Fix Released Status in The Date and Time Indicator: Fix Released Status in Indicator Location: Fix Released Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in Sound Menu: Fix Released Status in The Unity 8 shell: In Progress Status in URL Dispatcher: Fix Released Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: New Status in “indicator-sound” package in Ubuntu: Fix Released Status in “url-dispatcher” package in Ubuntu: Fix Released Bug description: The standard URL format (summarized) is $(protocol)://$(hostname)/$(stuff). Since most of the custom URLs we're using have no hostname, and QtUrl treats it specially, we need to ensure that it's not an issue. URL dispatcher was not enforcing this on some URLs, and needs to be adjusted to enforce. Others weren't specified that way, and they need to be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1231444/+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 1197071] Re: on_indicator_menu_show() called with a NULL entry
Fix committed into lp:unity at revision 3551, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1197071 Title: on_indicator_menu_show() called with a NULL entry Status in The Application Menu: Won't Fix Status in Unity: Fix Committed Status in “indicator-appmenu” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: In Progress Bug description: In saucy those warnings are displayed by the unity-panel-service on every alt-tab: Breakpoint 1, g_log (log_domain=0x0, log_level=G_LOG_LEVEL_WARNING, format=0x80538fc on_indicator_menu_show() called with a NULL entry) at /build/buildd/glib2.0-2.37.3/./glib/gmessages.c:1021 1021 in /build/buildd/glib2.0-2.37.3/./glib/gmessages.c #0 g_log (log_domain=0x0, log_level=G_LOG_LEVEL_WARNING, format=0x80538fc on_indicator_menu_show() called with a NULL entry) at /build/buildd/glib2.0-2.37.3/./glib/gmessages.c:1021 #1 0xb7f7a0e5 in _indicator_object_marshal_VOID__POINTER_UINT ( closure=0x817cb50, return_value=0x0, n_param_values=3, param_values=0xbfffe050, invocation_hint=0xbfffdffc, marshal_data=0x0) at indicator-object-marshal.c:162 #2 0xb76789ce in g_closure_invoke (closure=0x817cb50, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0xbfffe050, invocation_hint=invocation_hint@entry=0xbfffdffc) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777 #3 0xb768c029 in signal_emit_unlocked_R (node=node@entry=0x81486d0, detail=0, instance=0x8184048, emission_return=emission_return@entry=0x0, instance_and_params=0xbfffe050) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3582 #4 0xb7693dc9 in g_signal_emit_valist (instance=instance@entry=0x8184048, signal_id=signal_id@entry=224, detail=detail@entry=0, var_args=0xbfffe240 , var_args@entry=0xbfffe238 ) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3326 #5 0xb76944d1 in g_signal_emit_by_name (instance=0x8184048, detailed_signal=detailed_signal@entry=0xb579012d menu-show) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3422 #6 0xb5788e05 in window_show_menu (mw=0x0, entry=entry@entry=0x0, timestamp=0, user_data=user_data@entry=0x8184048) at indicator-appmenu.c:1359 #7 0xb5788f25 in switch_active_window (iapp=iapp@entry=0x8184048, active_window=active_window@entry=0x806f2e8) at indicator-appmenu.c:894 #8 0xb57891a5 in switch_default_app (iapp=0x8184048, newdef=0x8194db8, active_window=0x806f2e8) at indicator-appmenu.c:978 #9 0xb6fee48e in ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 #10 0xb6fee1ef in ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 #11 0xb76795b1 in g_cclosure_marshal_generic_va (closure=0x8186dd8, return_value=0x0, instance=0x8133110, args_list=0xbfffe5ec , marshal_data=0x0, n_params=2, param_types=0x81a38d8) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1550 #12 0xb7678c0e in _g_closure_invoke_va (closure=closure@entry=0x8186dd8, return_value=return_value@entry=0x0, instance=instance@entry=0x8133110, args=args@entry=0xbfffe5ec , n_params=2, param_types=0x81a38d8) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:840 #13 0xb769388d in g_signal_emit_valist (instance=instance@entry=0x8133110, signal_id=signal_id@entry=248, detail=detail@entry=0, var_args=var_args@entry=0xbfffe5ec ) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3234 #14 0xb7694013 in g_signal_emit (instance=instance@entry=0x8133110, signal_id=248, detail=detail@entry=0) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3382 #15 0xac7be2d0 in bamf_matcher_on_active_window_changed (proxy=0x80b6998, old_path=0x814ab70 , new_path=0x8150a78 /org/ayatana/bamf/window73400367, matcher=0x8133110) at bamf-matcher.c:199 #16 0xb6fee48e in ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 #17 0xb6fee1ef in ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 #18 0xb7679249 in g_cclosure_marshal_generic (closure=0x8187038, return_gvalue=0x0, n_param_values=3, param_values=0x8149e80, invocation_hint=0xbfffe85c, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454 #19 0xb76789ce in g_closure_invoke (closure=0x8187038, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0x8149e80, invocation_hint=invocation_hint@entry=0xbfffe85c) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777 #20 0xb768c029 in signal_emit_unlocked_R (node=node@entry=0x8178c70, detail=detail@entry=0,
[Dx-packages] [Bug 1231444] Re: Use /// to remove hostname element
Fix committed into lp:indicator-location at revision 49, scheduled for release in indicator-location, milestone Unknown ** Changed in: indicator-location Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231444 Title: Use /// to remove hostname element Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: In Progress Status in Indicator Location: Fix Committed Status in Network Menu: Fix Committed Status in Sound Menu: Fix Released Status in The Unity 8 shell: In Progress Status in URL Dispatcher: Fix Committed Status in “indicator-network” package in Ubuntu: New Status in “indicator-sound” package in Ubuntu: Fix Released Status in “url-dispatcher” package in Ubuntu: Fix Released Bug description: The standard URL format (summarized) is $(protocol)://$(hostname)/$(stuff). Since most of the custom URLs we're using have no hostname, and QtUrl treats it specially, we need to ensure that it's not an issue. URL dispatcher was not enforcing this on some URLs, and needs to be adjusted to enforce. Others weren't specified that way, and they need to be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1231444/+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 1231444] Re: Use /// to remove hostname element
Fix committed into lp:indicator-datetime at revision 264, scheduled for release in indicator-datetime, milestone Unknown ** Changed in: indicator-datetime Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231444 Title: Use /// to remove hostname element Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Committed Status in Sound Menu: Fix Released Status in The Unity 8 shell: In Progress Status in URL Dispatcher: Fix Committed Status in “indicator-network” package in Ubuntu: New Status in “indicator-sound” package in Ubuntu: Fix Released Status in “url-dispatcher” package in Ubuntu: Fix Released Bug description: The standard URL format (summarized) is $(protocol)://$(hostname)/$(stuff). Since most of the custom URLs we're using have no hostname, and QtUrl treats it specially, we need to ensure that it's not an issue. URL dispatcher was not enforcing this on some URLs, and needs to be adjusted to enforce. Others weren't specified that way, and they need to be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1231444/+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 1231444] Re: Use /// to remove hostname element
Fix committed into lp:indicator-bluetooth at revision 66, scheduled for release in indicator-bluetooth, milestone Unknown ** Changed in: indicator-bluetooth Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231444 Title: Use /// to remove hostname element Status in Bluetooth Menu: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Committed Status in Sound Menu: Fix Released Status in The Unity 8 shell: In Progress Status in URL Dispatcher: Fix Committed Status in “indicator-network” package in Ubuntu: New Status in “indicator-sound” package in Ubuntu: Fix Released Status in “url-dispatcher” package in Ubuntu: Fix Released Bug description: The standard URL format (summarized) is $(protocol)://$(hostname)/$(stuff). Since most of the custom URLs we're using have no hostname, and QtUrl treats it specially, we need to ensure that it's not an issue. URL dispatcher was not enforcing this on some URLs, and needs to be adjusted to enforce. Others weren't specified that way, and they need to be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1231444/+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 1214504] Re: unity-panel-service not running in non-upstart-sessions on Saucy (including guest session)
Fix committed into lp:lightdm at revision None, scheduled for release in lightdm, milestone Unknown ** Changed in: lightdm Status: Triaged = 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/1214504 Title: unity-panel-service not running in non-upstart-sessions on Saucy (including guest session) Status in Light Display Manager: Fix Committed Status in Unity: Triaged Status in “lightdm” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When changing to guest session on Saucy, you do not get the session gear indicator so to go back to a users session or logout or shutdown, all the indicators are missing in the top bar. See attached screenshot. The only way to get out of guest session once you are in, is CTRL+ALT+F1 and reboot on command line. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Tue Aug 20 19:41:01 2013 InstallationDate: Installed on 2013-03-28 (144 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130328) LightdmConfig: [SeatDefaults] user-session=ubuntu type=unity greeter-session=unity-greeter MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to saucy on 2013-05-19 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1214504/+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 1234778] Re: [regression] Launcher icon tooltips do not always hide using Unity trunk
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1234778 Title: [regression] Launcher icon tooltips do not always hide using Unity trunk Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Committed Bug description: A regression was introduced in http://bazaar.launchpad.net/~unity- team/unity/trunk/revision/3548 in which Launcher icon tooltips do not always disappear after moving the mouse away from the icon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1234778/+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 1073103] Re: Unity launcher not showing proper notifications count (on secondary monitors)
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1073103 Title: Unity launcher not showing proper notifications count (on secondary monitors) Status in Unity: Fix Committed Status in “empathy” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: In Progress Bug description: Since I installed 12.10, the unity panel is not showing notifications count properly, e.g. unread conversations for empathy, new emails for thunderbird. It works somehow - numbers are shown if the application sets it on startup. In very rare occasions even later. However, it doesn't work in the same way as it was in 12.04 - every time I get a new mail or a new IM message, a number over icon is shown. Message indicator works as before. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 30 10:00:29 2012 InstallationDate: Installed on 2012-10-19 (10 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1073103/+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 1233679] Re: Incorrect translation's template handling since the switch to cmake
Fix committed into lp:indicator-location at revision None, scheduled for release in indicator-location, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1233679 Title: Incorrect translation's template handling since the switch to cmake Status in Indicator Location: Fix Committed Status in Network Menu: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in “indicator-sound” package in Ubuntu: New Status in “pkgbinarymangler” package in Ubuntu: New Bug description: The switch to cmake seems to have made the translation setup a bit harder to deal with * Doing that in the source $ mkdir build $ cd build $ cmake .. $ make leads to a build dir without po subdir/template * The Ubuntu magic seems to be not working anymore: https://launchpadlibrarian.net/151894146/buildlog_ubuntu-saucy-i386.indicator-sound_12.10.2%2B13.10.20130930-0ubuntu1_UPLOADING.txt.gz Building ${CMAKE_PROJECT_NAME}.pot... ... None of the files in POTFILES.in contain strings marked for translation. dh_langpack: processing files to add translation domain '${CMAKE_PROJECT_NAME}'.. dh_translations does that while (CMAKELISTSFILE) { if ( -e 'po/POTFILES.in' ) { $use_intltool = 1; } $domain = $1 if /^set\s*\(GETTEXT_PACKAGE\s*?([^\s]*)?\s*\)/; That doesn't work great with the cmakefilelist having set(GETTEXT_PACKAGE ${CMAKE_PROJECT_NAME}) (e.g it doesn't know to escape it) * There doesn't seem to be a standard makefile target to update the pot? Well at least those don't work $ make pot $ make translations $ make update-pot $ make indicator-sound.pot The result is that currently the list of string handed to translations is not updated as it should :/ To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1233679/+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 1233679] Re: Incorrect translation's template handling since the switch to cmake
Fix committed into lp:indicator-network at revision None, scheduled for release in indicator-network, milestone Unknown ** Changed in: indicator-network Status: In Progress = Fix Committed ** Changed in: indicator-location Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1233679 Title: Incorrect translation's template handling since the switch to cmake Status in Indicator Location: Fix Committed Status in Network Menu: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in “indicator-sound” package in Ubuntu: New Status in “pkgbinarymangler” package in Ubuntu: New Bug description: The switch to cmake seems to have made the translation setup a bit harder to deal with * Doing that in the source $ mkdir build $ cd build $ cmake .. $ make leads to a build dir without po subdir/template * The Ubuntu magic seems to be not working anymore: https://launchpadlibrarian.net/151894146/buildlog_ubuntu-saucy-i386.indicator-sound_12.10.2%2B13.10.20130930-0ubuntu1_UPLOADING.txt.gz Building ${CMAKE_PROJECT_NAME}.pot... ... None of the files in POTFILES.in contain strings marked for translation. dh_langpack: processing files to add translation domain '${CMAKE_PROJECT_NAME}'.. dh_translations does that while (CMAKELISTSFILE) { if ( -e 'po/POTFILES.in' ) { $use_intltool = 1; } $domain = $1 if /^set\s*\(GETTEXT_PACKAGE\s*?([^\s]*)?\s*\)/; That doesn't work great with the cmakefilelist having set(GETTEXT_PACKAGE ${CMAKE_PROJECT_NAME}) (e.g it doesn't know to escape it) * There doesn't seem to be a standard makefile target to update the pot? Well at least those don't work $ make pot $ make translations $ make update-pot $ make indicator-sound.pot The result is that currently the list of string handed to translations is not updated as it should :/ To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1233679/+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 1233679] Re: Incorrect translation's template handling since the switch to cmake
Fix committed into lp:indicator-session at revision None, scheduled for release in indicator-session, milestone Unknown ** Changed in: indicator-session Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1233679 Title: Incorrect translation's template handling since the switch to cmake Status in Indicator Location: Fix Committed Status in Network Menu: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in “indicator-sound” package in Ubuntu: New Status in “pkgbinarymangler” package in Ubuntu: New Bug description: The switch to cmake seems to have made the translation setup a bit harder to deal with * Doing that in the source $ mkdir build $ cd build $ cmake .. $ make leads to a build dir without po subdir/template * The Ubuntu magic seems to be not working anymore: https://launchpadlibrarian.net/151894146/buildlog_ubuntu-saucy-i386.indicator-sound_12.10.2%2B13.10.20130930-0ubuntu1_UPLOADING.txt.gz Building ${CMAKE_PROJECT_NAME}.pot... ... None of the files in POTFILES.in contain strings marked for translation. dh_langpack: processing files to add translation domain '${CMAKE_PROJECT_NAME}'.. dh_translations does that while (CMAKELISTSFILE) { if ( -e 'po/POTFILES.in' ) { $use_intltool = 1; } $domain = $1 if /^set\s*\(GETTEXT_PACKAGE\s*?([^\s]*)?\s*\)/; That doesn't work great with the cmakefilelist having set(GETTEXT_PACKAGE ${CMAKE_PROJECT_NAME}) (e.g it doesn't know to escape it) * There doesn't seem to be a standard makefile target to update the pot? Well at least those don't work $ make pot $ make translations $ make update-pot $ make indicator-sound.pot The result is that currently the list of string handed to translations is not updated as it should :/ To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1233679/+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 1172769] Re: Launcher icon tooltip doesn't disappear with the icon
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1172769 Title: Launcher icon tooltip doesn't disappear with the icon Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: If an application is closed or removable drive unplugged and the tooltip of the icon is visible, the tooltip doesn't disappear with the icon. Steps to reproduce: 1. Open an application that's not pinned to launcher and focus it. 2. Hover mouse over the icon of the application and wait for the tooltip to appear. 3. Press ALT-F4 to close the application. What happens: Icon vanishes but the tooltip stays on screen until mouse is moved. What should happen: Icon and tooltip vanish from the launcher. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Apr 25 18:31:44 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-25 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1172769/+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 1223635] Re: Move Title to Backend
Fix committed into lp:unity8 at revision 378, scheduled for release in unity8, milestone ubuntu-13.09 ** Changed in: unity8 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1223635 Title: Move Title to Backend Status in Bluetooth Menu: Fix Released Status in The Date and Time Indicator: Fix Released Status in Indicator Location: Fix Released Status in The Messaging Menu: Fix Released Status in Network Menu: Fix Released Status in The Power Indicator: Fix Released Status in Sound Menu: Fix Released Status in The Sevilerow project: New Status in The Unity 8 shell: Fix Committed Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Bug description: We should have the titles in the root action state for the indicators. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1223635/+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 1215520] Re: The icon does not change based on the actual charge level
Fix committed into lp:indicator-power at revision 203, scheduled for release in indicator-power, milestone Unknown ** Changed in: indicator-power Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1215520 Title: The icon does not change based on the actual charge level Status in The Power Indicator: Fix Committed Status in “indicator-power” package in Ubuntu: Triaged Bug description: indicator-power 12.10.6daily13.03.07-0ubuntu1, Ubuntu 13.04 indicator-power 12.10.6+13.10.20130821-0ubuntu1, Ubuntu S The icon is always the same indicating something like 10% charge even when 90% charged. https://launchpadlibrarian.net/148600965/bug-1215520-charge.png https://wiki.ubuntu.com/Power#Icons: And if it is charging, the icon interior should feature a lightning bolt emblem. Depending on clarity and space available, the icon interior may also be filled from left to right approximately as much as the amount charged. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1215520/+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 1231444] Re: Use /// to remove hostname element
Fix committed into lp:indicator-network at revision 287, scheduled for release in indicator-network, milestone Unknown ** Changed in: indicator-network Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231444 Title: Use /// to remove hostname element Status in Bluetooth Menu: New Status in The Date and Time Indicator: New Status in Indicator Location: New Status in Network Menu: Fix Committed Status in Sound Menu: Fix Released Status in The Unity 8 shell: In Progress Status in URL Dispatcher: Fix Committed Status in “indicator-sound” package in Ubuntu: Fix Released Status in “url-dispatcher” package in Ubuntu: New Bug description: The standard URL format (summarized) is $(protocol)://$(hostname)/$(stuff). Since most of the custom URLs we're using have no hostname, and QtUrl treats it specially, we need to ensure that it's not an issue. URL dispatcher was not enforcing this on some URLs, and needs to be adjusted to enforce. Others weren't specified that way, and they need to be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1231444/+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 1172769] Re: Launcher icon tooltip doesn't disappear with the icon
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1172769 Title: Launcher icon tooltip doesn't disappear with the icon Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: If an application is closed or removable drive unplugged and the tooltip of the icon is visible, the tooltip doesn't disappear with the icon. Steps to reproduce: 1. Open an application that's not pinned to launcher and focus it. 2. Hover mouse over the icon of the application and wait for the tooltip to appear. 3. Press ALT-F4 to close the application. What happens: Icon vanishes but the tooltip stays on screen until mouse is moved. What should happen: Icon and tooltip vanish from the launcher. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Apr 25 18:31:44 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-25 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1172769/+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 969039] Re: HUD appears when tapping Alt+Left very quickly
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/969039 Title: HUD appears when tapping Alt+Left very quickly Status in Compiz: Invalid Status in Compiz Core: Invalid Status in Unity: Fix Committed Status in Unity Distro Priority: Confirmed Status in “compiz” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: In Progress Bug description: When I press Alt plus any cursor key in quick succession, the HUD erroneously appears. This steals focus and disrupts the workflow quite severely. This was much worse in earlier Unity versions, 5.8 already made this a lot better. But this case still remains for me. When I leave some time (0.5 s or so) between pressing Alt and the cursor key, this does not happen. But when pressing them almost at the same time, the bug happens. I can reproduce this 100%, so feel free to ask for any additional debugging info. The problem is not that I hit the Cursor key before alt. This proves it: $ xev | grep -A2 ^KeyPress KeyPress event, serial 36, synthetic NO, window 0x381, root 0xbe, subw 0x0, time 17590219, (112,69), root:(113,867), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, -- KeyPress event, serial 36, synthetic NO, window 0x381, root 0xbe, subw 0x0, time 17590299, (112,69), root:(113,867), state 0x8, keycode 113 (keysym 0xff51, Left), same_screen YES, and I get the HUD. It does not matter which application/window is focussed. It happens in gnome-terminal, Firefox, or the blank desktop all alike. It does not happen with other Alt key combinations, just with the cursor keys. I also saw this happen quite a lot with Ctrl+Alt (controlling screen grab in KVM) or Ctrl+Alt+Cursor (changing workspaces), but I cannot reliably reproduce those. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Mar 30 12:00:47 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110831) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/969039/+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 1233195] Re: [Regression] Bad redraw of the dash overlay connector
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1233195 Title: [Regression] Bad redraw of the dash overlay connector Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Rev 3535 introduce a regression on the redrawing of the dash overlay connector. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1233195/+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 1231435] Re: indicator does not change color on new messages in saucy
Fix committed into lp:indicator-messages at revision 381, scheduled for release in indicator-messages, milestone 13.10.0 ** Changed in: indicator-messages Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231435 Title: indicator does not change color on new messages in saucy Status in The Messaging Menu: Fix Committed Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: It seems xchat-indicator is not fully functional on saucy. When someone mentions my name, I do get the little 'xchat' icon to pop out and wiggle on the side (from the launcher), but my little 'mail' icon in the status bar does not change color and clicking it does not show any items under 'X-Chat'. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xchat-indicator 0.3.11-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Thu Sep 26 08:54:20 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (707 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: xchat-indicator UpgradeStatus: Upgraded to saucy on 2013-05-20 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1231435/+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 1231218] Re: indicator-appmenu holds a circular reference on itself, causes leaks
Fix committed into lp:indicator-appmenu at revision 245, scheduled for release in indicator-appmenu, milestone Unknown ** Changed in: indicator-appmenu Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231218 Title: indicator-appmenu holds a circular reference on itself, causes leaks Status in The Application Menu: Fix Committed Status in “indicator-appmenu” package in Ubuntu: In Progress Bug description: An IndicatorAppmenu object adds an extra g_object_ref to itself in its initializer and it only removes it in its finalizer, which means such objects will never get disposed (their refcount will never drop below 1). This causes a largish memory leak when unity-panel-service is shut down. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1231218/+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 1231679] Re: Launcher not auto hiding after clicking on an icon
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1231679 Title: Launcher not auto hiding after clicking on an icon Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: To reproduce, make sure your launcher is set to autohide. 1) Open an application such as gedit 2) Move to a different workspace then gedit 3) Click on the gedit icon 4) While the viewport is changing move the mouse outside of the launcher. Expected: The launcher after a normal amount of time, hides. Result: The launcher stays open until we move the mouse back in then out. The problem is while the viewport is moving compiz has a grab on the mouse. So the launcher never gets the MouseLeave event. So the launcher still thinks the mouse is inside the launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1231679/+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 1228965] Re: compiz crashed with SIGSEGV in unity::ui::EdgeBarrierController::Impl::SetupBarriers()
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228965 Title: compiz crashed with SIGSEGV in unity::ui::EdgeBarrierController::Impl::SetupBarriers() Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Committed Bug description: This crash happened when I disconnected my external monitor. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Sep 22 15:28:54 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2010-09-24 (1094 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MarkForUpload: True ProcCmdline: compiz --sm-client-id 10f36c25ff9ff470351371241230896410003843 SegvAnalysis: Segfault happened at: 0x478fc80: addb $0x0,(%rax) PC (0x0478fc80) in non-executable VMA region: 0x023b6000-0x049c7000 rw-p [heap] source $0x0 ok destination (%rax) (0x03c93160) ok SegvReason: executing writable VMA [heap] Signal: 11 SourcePackage: unity StacktraceTop: ?? () unity::ui::EdgeBarrierController::Impl::SetupBarriers(std::vectornux::Rect, std::allocatornux::Rect const) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so unity::glib::Source::SourceCallback(void*) () from /usr/lib/libunity-core-6.0.so.7 g_main_dispatch (context=0x23c9170) at /build/buildd/glib2.0-2.37.93/./glib/gmain.c:3065 Title: compiz crashed with SIGSEGV in unity::ui::EdgeBarrierController::Impl::SetupBarriers() UpgradeStatus: Upgraded to saucy on 2013-05-06 (139 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1228965/+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 1225391] Re: Installed Applications is blank after doing a search
Fix committed into lp:unity8 at revision 346, scheduled for release in unity8, milestone ubuntu-13.09 ** Changed in: unity8 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1225391 Title: Installed Applications is blank after doing a search Status in Unity Applications Lens: Invalid Status in The Unity 8 shell: Fix Committed Status in “unity-lens-applications” package in Ubuntu: Invalid Bug description: Steps: 1. Search for applications in the home scope 2. Dismiss the search Result: sometimes the Installed Applications section is then blank (see attached screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/1225391/+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 1228308] Re: Active blur for Quicklists and Tooltips is not working again
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228308 Title: Active blur for Quicklists and Tooltips is not working again Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Active blur for Quicklists and Tooltips were recently fixed, but a recent changed regressed that again. The offending commit is http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3515 in the unityshell.cpp file. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1228308/+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 1223630] Re: [Alt+Tab] Hover mouse bump accordion icons steals icon focus
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223630 Title: [Alt+Tab] Hover mouse bump accordion icons steals icon focus Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Same problem as bug 1215630, but only when icons are in accordion mode. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1223630/+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 1224340] Re: Visual corruption of Dash
Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1 ** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1224340 Title: Visual corruption of Dash Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Bug description: Dash has a visual corruption on the bottom. I attached video to see it clearly. In Ubuntu 13.04 there were no such problems. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Sep 12 11:20:32 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1203] InstallationDate: Installed on 2013-07-31 (42 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730) JockeyStatus: kmod:nvidia_319_updates - nvidia_319_updates (Проприетарные, Активирован, Не используется) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Проприетарные, Выключен, Не используется) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Проприетарные, Выключен, Не используется) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Проприетарные, Выключен, Не используется) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=69cd82a7-9a60-46b8-b39a-0985ac8652aa ro noresume ipv6.disable=1 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Sep 11 22:58:10 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRuling Technologies Sdn. Bhd. SteelSeries Gaming Device MOUSE, id 8 inputRuling Technologies Sdn. Bhd. SteelSeries Gaming Device KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1224340/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net
[Dx-packages] [Bug 1225387] Re: Multiple entries for each application
Fix committed into lp:unity-lens-applications at revision 368, scheduled for release in unity-lens-applications, milestone 7.0.0 ** Changed in: unity-lens-applications Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1225387 Title: Multiple entries for each application Status in Unity Applications Lens: Fix Committed Status in “unity-lens-applications” package in Ubuntu: Confirmed Bug description: In each part of the application scope, applications are listed multiple times. When doing a search, etc... See screenshot for an example in the Installed lens. This also happens when doing a search. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/1225387/+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