[Dx-packages] [Bug 1310356] Re: Grey trace beside the scrollbar

[Mathew Hodson]

** Tags removed: cosmetic ubuntu-desktop-trusty
** Tags added: trusty

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1310356

Title:
  Grey trace beside the scrollbar

Status in Overlay Scrollbar:
  New
Status in overlay-scrollbar package in Ubuntu:
  Triaged

Bug description:
  Some times appears grey traces beside orange. It is reproduced in many
  ways, for example after minimizing app. This cosmetic bug appears
  since Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1310356/+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 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open

[Mathew Hodson]

** Tags removed: ubuntu-desktop-trusty

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1281058

Title:
  [UIFe] The system shutdowns when multiple accounts are open

Status in Ayatana Design:
  Fix Committed
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in indicator-session package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Fix Released
Status in indicator-session source package in Trusty:
  Confirmed
Status in systemd source package in Trusty:
  Invalid
Status in unity source package in Trusty:
  Fix Released
Status in unity-greeter source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Other users logged into a system may loose work if another user shuts
  down/reboots a system.  Data loss is not a Good Thing.

  [Test Case]

  Steps to reproduce:

  1) Create a second account in the system
  2) While the first account is open, open a session with the second one
  3) Try to shutdown the system

  Expected results:
  The system logs out instead of shutting down (ideally with a warning on why 
it did that)

  Actual results:
  The system shutdowns and unsaved data on session1 is lost

  [ Regression Potential]

  None.

  --
  Desired resolution:

  - Add a warning message informing the user that other users are logged in and 
then shutting down will also close their sessions as proposed in the mockup 
attached to comment #12
  - The warning message should be "Other users are currently logged in to this 
computer, shutting down now will also close these other sessions"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1281058/+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 1302958] Re: Synaptic doesn't close properly after exiting from "enter password" window

[Mathew Hodson]

** Tags removed: iso-testing synaptic ubuntu-desktop-trusty ui

-- 
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/1302958

Title:
  Synaptic doesn't close properly after exiting from "enter password"
  window

Status in The synaptic package manager:
  New
Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 14.04 64 bit with Unity, fully updated

  Reproducible: always

  How to reproduce the bug:

  1) Pin the "Synaptic package manager" to the Unity launcher
  2) Click on the Synaptic icon
  3) There will appear a window, which asks for your password
  4) Close that window
  5) The Synaptic icon on the Unity launcher will have pulsing light for 5-10 
sec (this is the animation that Unity launcher uses when the app is launching) 
and you can't launch Synaptic by clicking on that icon during the pulsing light 
animation.

  Expected behaviour:

  5) The synaptic icon on the Unity launcher gets back to default state
  immediately and the icon acts as if the Synaptic was closed. So you
  can just click on the icon and launch Synaptic again.

  
  Important: such issue with Synaptic doesn't happen with other DEs like LXDE 
or XFCE

  I can provide more info if needed. This happens on every Ubuntu 14.04
  setup I tested, so it seems it's unrelated to hardware and drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/synaptic/+bug/1302958/+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 1074758] Re: Timely Logouts, Restarts, and Shutdowns with Unity Desktop

[Mathew Hodson]

** Tags removed: raring saucy ubuntu ubuntu-desktop-trusty
** Tags added: trusty

** Tags removed: trusty

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1074758

Title:
  Timely Logouts, Restarts, and Shutdowns with Unity Desktop

Status in The GNOME 2 Session Manager:
  New
Status in Insserv:
  New
Status in Molly Guard:
  New
Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Why does it take so long to logout (or restart or shutdown) from the
  Unity desktop?

  I have the xfce and lxde desktops installed along with unity:
  sudo apt-get install xfce4 lxde

  When I logout (restart or shutdown) with those desktops, it happens
  very quickly. When I shutdown with LXDE, it is almost as if someone
  yanked the battery out of my laptop it is so fast.

  So, what is the Unity desktop doing, during logout (restart and
  shutdown), that is so time-consuming?

  What can we do to make it more immediate (by default) in future
  updates and releases?

  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
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Nov  3 16:51:07 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, x86_64: installed
   virtualbox, 4.1.18: added
  DpkgLog:

  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:02a0]
     Subsystem: Dell Device [1028:02a0]
  InstallationDate: Installed on 2012-10-19 (15 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Dell Inc. Studio 1737
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=c61a0f60-f1c2-4c39-b22b-70af976dd426 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/26/2008:svnDellInc.:pnStudio1737:pvrA04:rvnDellInc.:rn0P792H:rvrA04:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: Studio 1737
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.4-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1074758/+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 785852] Re: Menu reordering does not work

[Mathew Hodson]

** Tags removed: ubuntu-desktop-trusty
** Tags added: trusty

-- 
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/785852

Title:
  Menu reordering does not work

Status in GTK+ GUI Toolkit:
  New
Status in DBus Menu:
  In Progress
Status in libdbusmenu package in Ubuntu:
  Confirmed

Bug description:
  gtk_menu_reorder_child does nothing on menus managed by application
  indicator. This is further demonstrated by the two attached C++
  programs. Both create a window and a application indicator menu with
  two items in it and reorder the items. The other attaches the menu to
  the application indicator icon and the other to a widget on screen. In
  the first case, the menu gets wrongly rendered in the original
  ordering. In the second case, the menu gets properly rendered with the
  two items reordered.

  The programs compile on ubuntu 12.04 with some necessary development
  packages installed:

  g++ bugtest.cpp `pkg-config gtkmm-3.0 appindicator3-0.1 --cflags --libs` -o 
bugtest
  g++ bugtest2.cpp `pkg-config gtkmm-3.0 appindicator3-0.1 --cflags --libs` -o 
bugtest2

  Duplicate bug 1026791 also has a Python script to demonstrate the
  problem.
  


To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/785852/+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 723167] Re: Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance theme.

[Mathew Hodson]

** Tags removed: oneiric quantal raring ubuntu-desktop-trusty
** Tags added: trusty unity

-- 
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/723167

Title:
  Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance
  theme.

Status in Ayatana Design:
  Invalid
Status in Cairo Graphics Library:
  New
Status in Unity:
  Fix Released
Status in cairo package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Since the switch to a theme-aware panel, the Unity panel uses very
  fuzzy fonts. The actual submenus in the global menu bar, as well as
  the indicators look fine, but the top-level menu entries, time, name
  in me-menu, and the window title look fuzzy. Presumably this is
  because it doesn't use the configured Pango font anti-aliasing as the
  rest of GTK, as these are rendered by nux?

  This is Unity 3.4.4 on current Natty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/723167/+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 1170647] Re: After minimizing an external media, clicking on the "Files" icon on the Launcher doesn't restore the minimized window, but opens a new one

[Mathew Hodson]

** Tags removed: amd64 saucy ubuntu-desktop-trusty

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1170647

Title:
  After minimizing an external media, clicking on the "Files" icon on
  the Launcher doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the "Files" icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the "Files" icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - One way to navigate between windows at this moment is to use the
  "control + tabulation" key combination, or to click again on the
  "Files" icon so windows are exposed.

  Otherwise the minimized window Can be restored by clicking on the
  Volume's launcher icon or scrolling on the Files icon

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the "Files" icon and select the
  "unlock from Launcher" option.

  FIX

  - The launcher icon for "Files" to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the "Files" icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1270486] Re: indicator-application doesn't use the menu item's label if it has a stock icon

[Mathew Hodson]

** Tags removed: regression trusty ubuntu-desktop-trusty
** Tags added: regression-release

-- 
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/1270486

Title:
  indicator-application doesn't use the menu item's label if it has a
  stock icon

Status in libdbusmenu package in Ubuntu:
  Triaged

Bug description:
  To reproduce, run the attached testcase1.py. You will see a new
  indicator, inside it will be one menu item with label "Pause" and a
  pause button icon. The menu item should have the label "Hello".

  Also note that this bug has been fixed once before:
  https://bugs.launchpad.net/indicator-application/+bug/520048

  For trusty, see comment 3. Glade is used by deluge to set the
  indicator menu, this is where the problem was first observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-application 12.10.1+13.10.20131107-0ubuntu1
  Uname: Linux 3.11.0-031100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Jan 18 20:40:29 2014
  InstallationDate: Installed on 2013-08-27 (143 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  MarkForUpload: True
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1270486/+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 732653] Re: Menus are hidden by default

[Adolfo Jayme]

** No longer affects: unity-2d (Ubuntu)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-2d in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/732653

Title:
  Menus are hidden by default

Status in Ayatana Design:
  Confirmed
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 11.04, Ubuntu 11.10, Ubuntu 12.04

  1. Log in to Unity, and try to connect to a server: "File" > "Connect to 
Server".
  2. Launch Firefox, and try to select an item from the "Bookmarks" menu.

  What happens:

  1. The "File" menu, and the rest of Nautilus's menus, are hidden by default.
  - Unless you mouse over it, the menu bar is blank.
  - When you mouse over it, the menus appear.

  2. The "Bookmarks" menu, and the rest of Firefox's menus, are hidden by 
default.
  - Unless you mouse over it, the menu bar contains only the text "Firefox Web 
Browser", which isn't useful at all (especially, but not only, since the real 
name of the application -- "Mozilla Firefox" -- is already present in the 
window title bar).
  - When you mouse over it, the menus appear, partly but not completely 
replacing the previous text: "Firefox W File Edit View…".

  What should happen: Menus should be visible by default, so that you
  can know that they exist without scrubbing the screen, and so that you
  can see where a menu is each time you aim for it.

  The current behavior has led some people (including, this week, one of
  my design colleagues) to conclude that Ubuntu applications don't have
  menus when they do. For example
  : "One of the most handy menu entries in
  GNOME (for me at least) is the Connect to Server entry in the Places
  menu. This allows the user to connect to nearly any type of server
  quickly and easily. The user can even connect to a Windows Share from
  here. In Unity - you won’t find that. In fact, you will be hard
  pressed to find any means to connect to a server in Ubuntu Unity."

  In bug 720424, Jono Bacon reported that "when we did some developer
  tools usability testing last week and on some other occasions when I
  have had someone use Unity, I have noticed that some folks don't
  realize there is a menu there as it is not visible."

  This was confirmed by usability testing of Ubuntu 11.04, where 2 out
  of the 10 people who needed to use a menu item could not find the
  menus at all -- and of the 8 who did find them, 7 did so only when the
  window was maximized. https://lists.ubuntu.com/archives/ubuntu-
  desktop/2011-April/002970.html (Usability testing results of Ubuntu
  11.10 or 12.04 have never been published, but this part of the design
  did not change.)

  Do not confuse this bug with bug 682788, which is about adding an
  option for visibility. Adding any options would not fix this bug,
  which is about menus being hidden *by default*.

  -
  Desired change:

  Implement the 'Enhanced Menu' project for 12.10. This project will
  address the issues described in this bug and also issues described in
  the duplicates of this bus. Note the 'official' bug that tracks the
  implementation of this project is bug #682788

  The following options will be added to 'System Settings/Appearance':

  ---
  Menus
  Location: Global/Local
  Visibility: Hidden/Always displayed
  ---

  More details to follow during the 12.10 cycle... ;-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/732653/+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 1348538] Re: [power] Display should come on when started charging

[Launchpad Bug Tracker]

** Branch linked: lp:~rsalveti/powerd/display_on_charging_discharging

-- 
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/1348538

Title:
  [power] Display should come on when started charging

Status in Ubuntu UX bugs:
  Triaged
Status in Unity System Compositor:
  New
Status in indicator-power package in Ubuntu:
  New
Status in powerd package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The display should be triggered to turn on for a $timeout when
  connected to a charger, so that users can see charging commenced.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 25 09:45:42 2014
  SourcePackage: unity-system-compositor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1348538/+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 827818] Re: Runaway memory usage in gtk-window-decorator

[positivek]

My gtk-window-decorator regularly climbs to 500 MB and I end up swapping
a lot with other programs running. Alt-Tab between windows increases the
use. Basically, I get around 1 MB added to the total memory used by gtk-
window-decorator for each time I Alt-Tab between windows (as observed by
System Monitor's). No end in sight in terms of chomping more (leaking
more?) memory.

-- 
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/827818

Title:
  Runaway memory usage in gtk-window-decorator

Status in Unity:
  Fix Released
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I've just been in a situation where gtk-window-decorator has consumed almost 
all of my memory via i915 gem objects:
  └─(16:33:%)── sudo cat /sys/kernel/debug/dri/0/i915_gem_objects   

   ──(Wed,Aug17)─┘
  5420 objects, 7376883712 bytes
  211 [197] objects, 216399872 [152293376] bytes in gtt
3 [2] active objects, 10493952 [8192] bytes
8 [8] pinned objects, 20107264 [20107264] bytes
200 [187] inactive objects, 185798656 [132177920] bytes
0 [0] freed objects, 0 [0] bytes
  8 pinned mappable objects, 20107264 bytes
  43 fault mappable objects, 15736832 bytes
  2147479552 [268435456] gtt total

  Killing compiz dropped that object total by ~1GB; killing gtk-window-
  decorator dropped it back down to ~300MB.

  Perhaps gtk-window-decorator or compiz is leaking textures?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
  Uname: Linux 3.0.0-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,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Wed Aug 17 16:46:26 2011
  DistUpgraded: Log time: 2011-08-09 07:42:59.079778
  DistroCodename: oneiric
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0493]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110730)
  MachineType: Dell Inc. Latitude E6420
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic 
root=UUID=944f10ac-f387-4ced-be3c-66f2cea7c4d9 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to oneiric on 2011-08-16 (0 days ago)
  dmi.bios.date: 01/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X48
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrX48:bd01/20/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.5.0-0ubuntu5
  version.ia32-libs: ia32-libs 20090808ubuntu13
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
7.11-0ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/827818/+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 1061792] Re: Memory Leak in Unity (Compiz)

[positivek]

Yes, still a problem in Ubuntu 14.04.1 LTS trusty.
gtk-window-decorator racks up memory use over time.

-- 
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/1061792

Title:
  Memory Leak in Unity (Compiz)

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  There seems to be a memory leak in Unity that comes with use (not
  age).

  Hardware: ThinkPad W510 (nVidia Quadro FX 880M, driver 304.51), Core2
  -Duo-based desktop with nVidia 560Ti (same driver)

  Software: Quantal Beta, up-to-the-moment updates, both 64- and 32-bit
  (one of each).

  *Note: I can *not* test with nouveau.  Not only is it completely
  unsuitable for laptops due to terrible power management, but neither
  computer will boot with it - I get the PFIFO stuff, even though the
  -16 kernel was supposed to fix that.

  Steps to reproduce:

  1) Log into Unity and launch System Monitor (gnome-system-monitor).
  Set to view "all processes" and organize by the "memory" column.  Take
  note of the amount of RAM taken by the Compiz and Xorg processes.

  2) Open a bunch of programs.  I use: Nautilus, Gnome-Terminal, Chrome,
  Banshee, EasyTag, EasyMP3Gain, Empathy, Eclipse, and Rhythmbox.

  3) Close all of the programs except gnome-system-monitor.  Note the
  increase in RAM the Compiz and Xorg processes take.

  4) Repeat steps 3-4.  Memory on each process steadily rises.

  It isn't by a lot, but it creates an environment wherein the longer
  one uses one's Unity session, the less free RAM one has to work with
  (as neither process ever seems to give up any of its RAM, ever, not
  even after 10 hours of use).

  I don't seem to have any stability or performance issues stemming from
  this.

  ALSO: Opening the dash at all raises the RAM usage by a LOT, and
  subsequent openings of the dash (poking around, clicking on new
  buttons that reveal icons I haven't seen before, etc) also grows the
  process's RAM.  By a LOT on the first run, but by a noticeable amount
  on later runs.

  *I* think this is a pretty high-priority issue, but as the RAM use and
  growth isn't all THAT large (~0.5/1 MiB every time steps 2-3 are
  repeated), I could understand if it weren't marked critical... but I
  think any leak is critical, so there's my bias.

  STEALTH EDIT: I want to point out that just leaving the system logged
  in does not cause Unity *or* Xorg to use more RAM over time.  Not even
  with the indicator-multiload running.

  STEALTH EDIT #2: All lenses and scopes except the Application lens have been 
uninstalled, and do not factor into this.  So I'm pretty sure we don't have a 
runaway call in any indexer or anything like it.
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistroRelease: Ubuntu 12.10
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  NonfreeKernelModules: nvidia
  Package: unity 6.8.0-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
  Tags: quantal third-party-packages
  Uname: Linux 3.5.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1061792/+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 1312137] Re: Local menus broken for Qt apps after opening dialog

[Michele Giacomoli]

@Stephen
Sorry for my previous answer, it was a bit rude.

It's great to see this bug fixed for vivid, but since the target for
this bug was set from 7.2.x to 7.3.x, I wondered if one day the bug
would be fixed for 14.04 too. I'll be patient ;-)

-- 
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/1312137

Title:
  Local menus broken for Qt apps after opening dialog

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt
  app that produces a dialog, the menu is no longer accessible. e.g.

  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' -> 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
  5. Move mouse over window titlebar -> menu is no longer shown.

  The only way to get the menu back, is to switch to another window, and
  then back to the affected app.

  Note: This does not seem to affect the 'File' dialog from QtCreator -
  I'm assuming this is because it loads the Gtk file dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1312137/+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 1312137] Re: Local menus broken for Qt apps after opening dialog

[Stephen M. Webb]

Just be patient: the fix only just appeared in the current development
version of Ubuntu.  It has to mellow there for a bit to shake out bugs
before it will get backported to an LTS release.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1312137

Title:
  Local menus broken for Qt apps after opening dialog

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt
  app that produces a dialog, the menu is no longer accessible. e.g.

  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' -> 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
  5. Move mouse over window titlebar -> menu is no longer shown.

  The only way to get the menu back, is to switch to another window, and
  then back to the affected app.

  Note: This does not seem to affect the 'File' dialog from QtCreator -
  I'm assuming this is because it loads the Gtk file dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1312137/+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 1194231] Re: Typo in Error Message

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libdbusmenu (Ubuntu)
   Status: New => Confirmed

-- 
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/1194231

Title:
  Typo in Error Message

Status in DBus Menu:
  New
Status in libdbusmenu package in Ubuntu:
  Confirmed

Bug description:
  There is an error message which for me is showing up a lot when I run
  Audacity. I'm not concerned in this bug report with resolving the
  error message, but fixing the typo in the message. The message says,

  (Audacity:4190): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child
  that doesn't believe we're it's parent.

  please change "it's" to "its".

To manage notifications about this bug go to:
https://bugs.launchpad.net/libdbusmenu/+bug/1194231/+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 1403956] Re: menu highlights are wrong color

[Adolfo Jayme]

Can you provide a screenshot? I can’t reproduce the issue.

** Changed in: unity (Ubuntu)
   Status: New => Incomplete

** Changed in: unity (Ubuntu)
   Importance: High => Undecided

-- 
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/1403956

Title:
  menu highlights are wrong color

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  With the latest Unity update in Vivid when I click on a menu there is
  no highlight making it difficult to tell if an item is selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec 18 10:37:41 2014
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21ce]
  InstallationDate: Installed on 2014-12-17 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141216)
  MachineType: LENOVO 4177CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4177CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4177CTO
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.0+15.04.20141210.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141119-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Dec 18 10:28:26 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 738 
   vendor LGD
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403956/+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 1276177] Re: Applications using client-side decorations are not resizable in Unity

[Treviño]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1276177

Title:
  Applications using client-side decorations are not resizable in Unity

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  [ Impact ]

  GNOME applications that use client-side decorations can't be resized
  on Unity. I think it's because the frame extents hint is not
  supported.

  gnome-clocks and gnome-tweak-tool are two apps in the archive that
  have this problem.

  [ Test Case ]

  Run one of the abovementioned applications.  Their windows should be
  resizable.

  [ Regression Potential ]

  Any modifications to the Unity desktop shell could potentially
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity, where it has been in production use in Ubuntu "Vivid Vervet"
  dev release for some time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1276177/+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 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered

[Nekhelesh Ramananthan]

** Branch linked: lp:~nik90/ubuntu-clock-app/update-alarm-page-ui-
correctly

-- 
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/1362341

Title:
  OneTime alarms are not automatically dismissed or delete after they
  are triggered

Status in the base for Ubuntu mobile products:
  Fix Released
Status in The Date and Time Indicator:
  Fix Released
Status in Clock application for Ubuntu devices:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Create a one time alarm to ring in a few minutes
  2. Let the alarm ring
  3. Dismiss the alarm

  What happens:
  The OneTime alarm is still shown as enabled and as a result shows the wrong 
status in the clock app. The alarm is no longer shown in the indicator-datetime.

  What should happen:
  The OneTime alarm is either disabled or deleted from the alarm model.

  The clock app cannot disable the alarm since most likely the clock app
  is not even open at the time the alarm is triggered. Since the alarm
  is no longer shown in the indicator-datetime, my intuition tells me
  that indicator-datetime and EDS did its job. Its now up to the SDK
  Alarms API to update the alarm model correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+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 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered

[Nekhelesh Ramananthan]

** Changed in: ubuntu-clock-app
   Status: Confirmed => In Progress

-- 
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/1362341

Title:
  OneTime alarms are not automatically dismissed or delete after they
  are triggered

Status in the base for Ubuntu mobile products:
  Fix Released
Status in The Date and Time Indicator:
  Fix Released
Status in Clock application for Ubuntu devices:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Create a one time alarm to ring in a few minutes
  2. Let the alarm ring
  3. Dismiss the alarm

  What happens:
  The OneTime alarm is still shown as enabled and as a result shows the wrong 
status in the clock app. The alarm is no longer shown in the indicator-datetime.

  What should happen:
  The OneTime alarm is either disabled or deleted from the alarm model.

  The clock app cannot disable the alarm since most likely the clock app
  is not even open at the time the alarm is triggered. Since the alarm
  is no longer shown in the indicator-datetime, my intuition tells me
  that indicator-datetime and EDS did its job. Its now up to the SDK
  Alarms API to update the alarm model correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
13.10.0+15.04.20150115~rtm-0ubuntu1

---
indicator-datetime (13.10.0+15.04.20150115~rtm-0ubuntu1) 14.09; urgency=low

  [ Charles Kerr ]
  * Fix bug that misidentified repeating alarms as one-time alarms,
causing them to be disabled after triggering. (LP: #1411171)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
20:57:21 +

** Changed in: indicator-datetime (Ubuntu RTM)
   Status: New => Fix Released

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1276177] Re: Applications using client-side decorations are not resizable in Unity

[Jim Nelson]

This update solves this specific Unity problem for California.

-- 
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/1276177

Title:
  Applications using client-side decorations are not resizable in Unity

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  [ Impact ]

  GNOME applications that use client-side decorations can't be resized
  on Unity. I think it's because the frame extents hint is not
  supported.

  gnome-clocks and gnome-tweak-tool are two apps in the archive that
  have this problem.

  [ Test Case ]

  Run one of the abovementioned applications.  Their windows should be
  resizable.

  [ Regression Potential ]

  Any modifications to the Unity desktop shell could potentially
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity, where it has been in production use in Ubuntu "Vivid Vervet"
  dev release for some time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1276177/+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 1407192] Re: firefox icon frequently replaced by placeholder

[Andrea Azzarone]

** Changed in: bamf
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1407192

Title:
  firefox icon frequently replaced by placeholder

Status in BAMF Application Matching Framework:
  Confirmed
Status in Unity:
  Confirmed
Status in bamf package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Several times over the last week I have noticed that the when I start 
firefox, the default icon is replaced by a grey square with a question mark in 
the center as shown in the attached image.
  The only fix I've found is to unlock firefox from the launcher, quit the 
program, search for "firefox" in the dash, manually drag the icon onto the 
launcher, and then open it(i.e. if I start firefox directly from the dash, the 
grey icon appears on the launcher again).
  I haven't noticed this occurring with any other program.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-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
  CurrentDesktop: Unity
  Date: Fri Jan  2 21:38:32 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fb43]
  InstallationDate: Installed on 2014-12-11 (23 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
  MachineType: TOSHIBA Satellite L875D
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PLCSC8
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L875D
  dmi.product.version: PSKFQU-003034
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141119-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan  1 20:07:44 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.2.901-1ubuntu3
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1407192/+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 1404730] Re: Dash: some icons are scaled incorrectly

[Brandon Schaefer]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765069
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768256

Looks like a bug it gtk 3.14

** Bug watch added: Debian Bug tracker #765069
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765069

** Bug watch added: Debian Bug tracker #768256
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768256

-- 
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/1404730

Title:
  Dash: some icons are scaled incorrectly

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Please see the enclosed screenshot - the software updater icon is
  oversized compared to others displayed in Dash

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Dec 21 21:13:29 2014
  InstallationDate: Installed on 2014-11-27 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141123)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1404730/+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 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.

[Jennifer Pan]

Greatly appreciate your work.

-- 
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/1410582

Title:
  [Trusty / Unity] Desktop got unlocked on its own.

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have a user reporting an incidence that trusty unity desktop got
  unlocked on its own:

  "In the morning, after coming to my desk, I just pressed the space bar
  on my desktop to get the monitors woken up. The monitors came up with
  the locked screen and then after a while it got unlocked to my
  surprise!"

     There was compiz crash file on his system at that time. However, I
  don't have the right debug symbols to which file (or function) it
  crashed into. Here is the top part of the stack trace when I ran
  apport-retrace -s  on his crash file:

  
---
  --- stack trace ---
  #0  0x7ff17ed06608 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #1  0x7ff17ed06cf3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #2  0x7ff17ed04e2d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #3  0x7ff17f3fdd02 in g_settings_backend_read (backend=, 
key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", 
expected_type=0x7ff1877135a0 , 
default_value=default_value@entry=0) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
  value = 
  #4  0x7ff17f401c7b in g_settings_read_from_backend 
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, 
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) 
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
  value = 
  fixup = 
  path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
  #5  0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, 
key=0x2087618 "disable-lock-screen") at 
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
  skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
"disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
  value = 
  __FUNCTION__ = "g_settings_get_value"
  
-

     The top part of the trash file when viewed in TextEdit has the information 
:
  -
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Dec 12 10:16:52 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/compiz
  ExecutableTimestamp: 1405349348
  ProcCmdline: compiz
  --

     His system is Ubuntu trusty 14.04.1 LTS. Unity installed
  7.2.3+14.04.20140826-0ubuntu1.0.1 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+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 1409121] Re: Cannot drag and drop full screen windows between virtual workspaces anymore after executing 'unity --replace' command

[Andrea Azzarone]

Never mind I was able to reproduce this bug on 15.04.

** Changed in: unity
   Status: Incomplete => Confirmed

** Also affects: unity (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity (Ubuntu)
   Status: New => Confirmed

** Changed in: unity
   Importance: Undecided => Medium

** Changed in: unity
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

** Also affects: compiz
   Importance: Undecided
   Status: New

** Also affects: compiz (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: compiz
   Status: New => Confirmed

** Changed in: compiz (Ubuntu)
   Status: New => Confirmed

** Changed in: compiz (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

** Changed in: compiz
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

** Changed in: unity
Milestone: None => 7.3.1

** Changed in: compiz
Milestone: None => 0.9.12.1

** Changed in: compiz
   Importance: Undecided => Medium

-- 
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/1409121

Title:
  Cannot drag and drop full screen windows between virtual workspaces
  anymore after executing 'unity --replace' command

Status in Compiz:
  Confirmed
Status in Unity:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after I had to execute a unity --replace  command, all open windows
  which are maximized cannot be drawn from one workspace to another in
  the workspace switcher. This would be necessary since after the
  replacment of unity, all windows lost their original position and are
  stacked on one workspace.

  Workaround: One can 'unmaximize' the windows and drag then to the
  designated work space. Afterwards, the window can be maximized again
  and will stay on this workspace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1409121/+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 1408079] Re: The workspace exposé for dragging windows is duplicated in dual monitor setups

[Andrea Azzarone]

Is this [1] more or less what happens there?

[1]
https://bugs.launchpad.net/unity/+bug/919220/+attachment/2721458/+files/919220.png

** Changed in: unity
   Status: New => Incomplete

** Also affects: unity (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity (Ubuntu)
   Status: New => Incomplete

-- 
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/1408079

Title:
  The workspace exposé for dragging windows is duplicated in dual
  monitor setups

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  This bug appears in multi-monitor setups.

  When clicking the workspace button, the user sees an exposé of
  workspaces that can then be used to drag windows around.  In the past
  this would only appear in one monitor, but now it appears duplicated,
  so that when the user moves a window in the left monitor, the window
  also moves in the right monitor, which makes the whole experience
  unnatural and confusing.

  It's not just a mirrored image, it's actually a wrap around, so that
  if you keep dragging to the right you can drag the window from the
  right most workspace in the left monitor, back into the left most
  workspace in the right monitor.

  This happens in Trusty.  Unity version: 7.2.2+14.04.20140714-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1408079/+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 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.

[Andrea Azzarone]

@Jennifer a fix has been released in Ubuntu 15.04. You need to wait the
next SRU (few months likely) to get this fix in 14.04 LTS.

-- 
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/1410582

Title:
  [Trusty / Unity] Desktop got unlocked on its own.

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have a user reporting an incidence that trusty unity desktop got
  unlocked on its own:

  "In the morning, after coming to my desk, I just pressed the space bar
  on my desktop to get the monitors woken up. The monitors came up with
  the locked screen and then after a while it got unlocked to my
  surprise!"

     There was compiz crash file on his system at that time. However, I
  don't have the right debug symbols to which file (or function) it
  crashed into. Here is the top part of the stack trace when I ran
  apport-retrace -s  on his crash file:

  
---
  --- stack trace ---
  #0  0x7ff17ed06608 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #1  0x7ff17ed06cf3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #2  0x7ff17ed04e2d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #3  0x7ff17f3fdd02 in g_settings_backend_read (backend=, 
key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", 
expected_type=0x7ff1877135a0 , 
default_value=default_value@entry=0) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
  value = 
  #4  0x7ff17f401c7b in g_settings_read_from_backend 
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, 
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) 
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
  value = 
  fixup = 
  path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
  #5  0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, 
key=0x2087618 "disable-lock-screen") at 
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
  skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
"disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
  value = 
  __FUNCTION__ = "g_settings_get_value"
  
-

     The top part of the trash file when viewed in TextEdit has the information 
:
  -
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Dec 12 10:16:52 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/compiz
  ExecutableTimestamp: 1405349348
  ProcCmdline: compiz
  --

     His system is Ubuntu trusty 14.04.1 LTS. Unity installed
  7.2.3+14.04.20140826-0ubuntu1.0.1 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+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 1312137] Re: Local menus broken for Qt apps after opening dialog

[Michele Giacomoli]

Any chance to have this bug fixed in Ubuntu 14.04 too?

-- 
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/1312137

Title:
  Local menus broken for Qt apps after opening dialog

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt
  app that produces a dialog, the menu is no longer accessible. e.g.

  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' -> 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
  5. Move mouse over window titlebar -> menu is no longer shown.

  The only way to get the menu back, is to switch to another window, and
  then back to the affected app.

  Note: This does not seem to affect the 'File' dialog from QtCreator -
  I'm assuming this is because it loads the Gtk file dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1312137/+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 860970] Re: Dash called with super key above fullscreen app is not interactive or does not show up at all.

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/860970

Title:
  Dash called with super key above fullscreen app is not interactive or
  does not show up at all.

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  In Progress
Status in Unity 5.0 series:
  Triaged
Status in Unity 6.0 series:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Triaged

Bug description:
  Steps to reproduce :
  - launch an application in fullscreen (Firefox, Totem…)
  - hit the Super key to call the dash

  -> Unity 5.x: The dash is displayed, but it is click through…
  -> Unity 6.x: The dash is not displayed at all.

  In both cases, the cause of this bug is because the Unity Nux windows
  are not being stacked above the fullscreen window.

  -
  Desired resolution:

  - If a window is fullscreen and the Dash is invoked, the Dash should
  be displayed on top of the full screen window.

  - Apps should remain full screen when the dash is opened

  - Any actions the user performs on top of the Dash area should be sent
  to the Dash, not the full screen application.

  - Clicking anywhere on the full screen application should close the
  Dash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/860970/+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 1159249] Re: HUD does not show up over fullscreen window

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1159249

Title:
  HUD does not show up over fullscreen window

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Step to reproduce:

  1. Open some site in firefox

  2. Go to fullscreen mode (F11)

  3. Press "Alt" once.

  The HUD will not appear, but actually it will start and grab the
  keyboard, You will not be able to use F11 again to exit the fullscreen
  mode. You will be able to interact with HUD blindely.

  4. Exit the fullscreen mode using mouse and you will see the HUD
  active and ready.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.03.20-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  Date: Sun Mar 24 02:01:54 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-01 (81 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac 
(20121017.3)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-03-18 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1159249/+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 955193] Re: Menu bar - add option for the global menu to make it always visible

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/955193

Title:
  Menu bar - add option for the global menu to make it always visible

Status in Ayatana Design:
  Triaged
Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  
  1) In System Settings/Appearance/Behavior ( see section 2.2 of 
http://tinyurl.com/7c7nofq ), the "Application Menu" options should be 
"Integrated in menu bar and hidden" (default) and "Integrated in menu bar and 
visible"

  2) If "Integrated in menu bar and visible" is selected, the menus
  should always be shown, in exactly the same manner they are currently
  displayed when the pointer is moved over the menu bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/955193/+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 1238063] Re: compiz crashed with SIGSEGV in operator()

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1238063

Title:
  compiz crashed with SIGSEGV in operator()

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This seemed to happen while I was messing about with an external
  monitor (enabling/disabling, trying to fix a bad resolution
  detection).

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: f24bf886cf6158b8cd6d663f166fcff9
  CheckboxSystem: 3935143777c965daaa64b51f0134f712
  Date: Thu Oct 10 10:35:26 2013
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2010-10-11 (1094 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   nux::Property::Set(bool 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.8
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: compiz crashed with SIGSEGV in nux::Property::Set()
  UpgradeStatus: Upgraded to saucy on 2013-09-04 (36 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare 
sbuild vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1238063/+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 1312137] Re: Local menus broken for Qt apps after opening dialog

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1312137

Title:
  Local menus broken for Qt apps after opening dialog

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt
  app that produces a dialog, the menu is no longer accessible. e.g.

  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' -> 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
  5. Move mouse over window titlebar -> menu is no longer shown.

  The only way to get the menu back, is to switch to another window, and
  then back to the affected app.

  Note: This does not seem to affect the 'File' dialog from QtCreator -
  I'm assuming this is because it loads the Gtk file dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1312137/+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 1374942] Re: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1374942

Title:
  compiz crashed with signal 5 in _XReply() from
  unity::decoration::ForceQuitDialog::ForceQuitDialog

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Unkown cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140915-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 28 16:19:49 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-09-03 (25 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1374942/+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 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1390562

Title:
  Moving the mouse out from the decoration hides the LIMs when Alt is
  pressed

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Prerequisite: from Appearance -> Behavior -> Set menu visible in
  window titlebar

  1. Open a window with menus
  2. Press and keep pressed the Alt key
  3. Menus will show
  4. Move the mouse over the window decoration
  5. Move the mouse out from the window decoration

  Actual behavior:
  6. Menus hides, also if the Alt key is pressed.

  Expected:
  6. Menus should stay visible until the Alt key is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1390562/+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 1401911] Re: When the screen is locked edge barriers should be deactivated.

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1401911

Title:
  When the screen is locked edge barriers should be deactivated.

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  If the screen is locked, launcher/panel edge barriers at the moment
  are active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1401911/+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 1404486] Re: Session dialog does not show up over fullscreen windows.

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1404486

Title:
  Session dialog does not show up over fullscreen windows.

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Unity session dialog does not show up over a fullscreen window if you
  press the hardware button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1404486/+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 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1

---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Andrea Azzarone ]
  * Disable Pointer Barriers during lockscreen. (LP: #1401911)
  * Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
  * Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
  * Show session dialog over fullscreen windows. (LP: #1404486)
  * Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)

  [ Marco Trevisan (Treviño) ]
  * MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
 -- Ubuntu daily releaseThu, 15 Jan 2015 
15:03:31 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1410582

Title:
  [Trusty / Unity] Desktop got unlocked on its own.

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have a user reporting an incidence that trusty unity desktop got
  unlocked on its own:

  "In the morning, after coming to my desk, I just pressed the space bar
  on my desktop to get the monitors woken up. The monitors came up with
  the locked screen and then after a while it got unlocked to my
  surprise!"

     There was compiz crash file on his system at that time. However, I
  don't have the right debug symbols to which file (or function) it
  crashed into. Here is the top part of the stack trace when I ran
  apport-retrace -s  on his crash file:

  
---
  --- stack trace ---
  #0  0x7ff17ed06608 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #1  0x7ff17ed06cf3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #2  0x7ff17ed04e2d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #3  0x7ff17f3fdd02 in g_settings_backend_read (backend=, 
key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", 
expected_type=0x7ff1877135a0 , 
default_value=default_value@entry=0) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
  value = 
  #4  0x7ff17f401c7b in g_settings_read_from_backend 
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, 
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) 
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
  value = 
  fixup = 
  path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
  #5  0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, 
key=0x2087618 "disable-lock-screen") at 
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
  skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
"disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
  value = 
  __FUNCTION__ = "g_settings_get_value"
  
-

     The top part of the trash file when viewed in TextEdit has the information 
:
  -
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Dec 12 10:16:52 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/compiz
  ExecutableTimestamp: 1405349348
  ProcCmdline: compiz
  --

     His system is Ubuntu trusty 14.04.1 LTS. Unity installed
  7.2.3+14.04.20140826-0ubuntu1.0.1 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+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 1374785] Re: Screen-saver fade-to-black does not cover entire screen on HiDPI

[Andreas E.]

Is it planned for this to appear in the current release (utopic
proposed), or is the only option to upgrade at this early stage already
to 15.04?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1374785

Title:
  Screen-saver fade-to-black does not cover entire screen on HiDPI

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [ Impact ]

  When display scaling is set to 2x or greater the fade-to-black
  animation when the screen saver is invoked covers only a fraction of
  the screen.

  [ Test Case ]

  Requires a display with 2x UI scaling (works best with a high-DPI
  display).

  The fade-to-black which occurs prior to the screen shutting off only
  covers the top left quarter of the screen.

  When scaling is set to 1x, the entire screen fades to black.

  [ Regression Potential ]

  An invalid scaling calculation (or rounding error) could result in writing 
outside the screen buffer bounds with resulting unknown impact.  Inpspection 
and code review shows this not to be the case wit this patch.
  [ Other Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been in production use in Ubuntu 'Vivid Vervet' for some time
  and has not shown ergressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1374785/+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 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner

[AndreK]

would somebody kill this stupid logevent soon ?
deletec the folder, purged/reinstalled logrotate,   few minutes later 16GB log 
filling up disk again.
This waste laptop runtime - how to disable this freaking mess ?

-- 
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/1240848

Title:
  ~/.cache/upstart takes up around 70GB of space due to unity and
  mediascanner

Status in Unity:
  New
Status in mediascanner package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I just noticed that ~/.cache/upstart/ folder on my computer is taking
  up 69GB of space. Upon further investigation, I found out that
  mediascanner.log and unity-panel-service.log take 12GB and 54GB of
  space respectively.

  I'm not entirely sure if this is related to upstart as I had removed
  logrotate package because of a conflict.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1240848/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1411171-strengthen-
recurrence-rule-test-rtm-14.09

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411382] [NEW] Applications view not displaying any applications

[Vadim Peretokin]

Public bug reported:

See screenshot included. Just broke down out of the blue.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
Date: Fri Jan 16 05:42:09 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (1028 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-07-26 (173 days ago)

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages trusty

** Attachment added: "Workspace 1_127.png"
   
https://bugs.launchpad.net/bugs/1411382/+attachment/4299456/+files/Workspace%201_127.png

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1411382

Title:
  Applications view not displaying any applications

Status in unity package in Ubuntu:
  New

Bug description:
  See screenshot included. Just broke down out of the blue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Jan 16 05:42:09 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (1028 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-07-26 (173 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411382/+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 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Released

-- 
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/1362341

Title:
  OneTime alarms are not automatically dismissed or delete after they
  are triggered

Status in the base for Ubuntu mobile products:
  Fix Released
Status in The Date and Time Indicator:
  Fix Released
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Create a one time alarm to ring in a few minutes
  2. Let the alarm ring
  3. Dismiss the alarm

  What happens:
  The OneTime alarm is still shown as enabled and as a result shows the wrong 
status in the clock app. The alarm is no longer shown in the indicator-datetime.

  What should happen:
  The OneTime alarm is either disabled or deleted from the alarm model.

  The clock app cannot disable the alarm since most likely the clock app
  is not even open at the time the alarm is triggered. Since the alarm
  is no longer shown in the indicator-datetime, my intuition tells me
  that indicator-datetime and EDS did its job. Its now up to the SDK
  Alarms API to update the alarm model correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+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 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered

[Charles Kerr]

** Changed in: indicator-datetime
   Status: In Progress => Fix Released

-- 
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/1362341

Title:
  OneTime alarms are not automatically dismissed or delete after they
  are triggered

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Date and Time Indicator:
  Fix Released
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Create a one time alarm to ring in a few minutes
  2. Let the alarm ring
  3. Dismiss the alarm

  What happens:
  The OneTime alarm is still shown as enabled and as a result shows the wrong 
status in the clock app. The alarm is no longer shown in the indicator-datetime.

  What should happen:
  The OneTime alarm is either disabled or deleted from the alarm model.

  The clock app cannot disable the alarm since most likely the clock app
  is not even open at the time the alarm is triggered. Since the alarm
  is no longer shown in the indicator-datetime, my intuition tells me
  that indicator-datetime and EDS did its job. Its now up to the SDK
  Alarms API to update the alarm model correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Łukasz Zemczak]

** Also affects: indicator-datetime (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Łukasz Zemczak]

** Tags added: lt-category-visible

** Tags added: lt-blocker

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Charles Kerr]

I suspect nik90's right about this being a regression introduced by bug
#1362341.

Looking at the .ics file after running jibel's recipe, I see that the
alarm's CATEGORIES entry includes the x-canonical-disabled tag.

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Jean-Baptiste Lallement]

I downgraded to  indicator-datetime 13.10.0+14.10.20141009-0ubuntu1 and
cannot reproduce the problem

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Pat McGowan]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww05-2015

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1355995] Re: sound plays on speakers even when sound indicator is set to zero

[Ted Gould]

I'm going to mark this as "Opinion" because I think the behavior
described here is by design. There is a matrix of media profiles and
outputs that effects *which* volume is used. Basically media play back
and alarms (default when media isn't playing) have different volumes. So
when medias not playing, by pressing your hardware keys you're adjusting
the alarm volume. When it is playing, you're adjusting the multimedia
volume. The indicator shows the current volume profile being used.

https://wiki.ubuntu.com/Sound#Indicator_and_menu


** Changed in: indicator-sound (Ubuntu)
   Status: New => Opinion

-- 
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/1355995

Title:
  sound plays on speakers even when sound indicator is set to zero

Status in indicator-sound package in Ubuntu:
  Opinion

Bug description:
  Steps:

  1. Turn sound via sound indicator to zero
  2. Open the music app and start playing a song

  Result:
  the song plays

  Expected:
  You cannot hear the song

  Note that if you adjust the volume via the hardware buttons, the
  indicator visibly changes, but the volume does not.

  This is image 185 on Krilin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1355995/+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 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.

[Margarita Manterola]

** Description changed:

-I have a user reporting an incidence that trusty unity desktop got
+ I have a user reporting an incidence that trusty unity desktop got
  unlocked on its own:
  
-   "Well, I didn't unlock/lock the system before the auto-unlock that morning.
- What I mean is that, on that morning after coming to my desk, I started
- working on my Mac and just press the space bar on my desktop to get the
- monitors woken up. The monitors came up with the locked screen and then
- after a while it got unlocked to my surprise!"
+ "In the morning, after coming to my desk, I just pressed the space bar
+ on my desktop to get the monitors woken up. The monitors came up with
+ the locked screen and then after a while it got unlocked to my
+ surprise!"
  
-There was compiz crash file on his system at that time. However, I
+    There was compiz crash file on his system at that time. However, I
  don't have the right debug symbols to which file (or function) it
  crashed into. Here is the top part of the stack trace when I ran apport-
  retrace -s  on his crash file:
  
  
---
  --- stack trace ---
  #0  0x7ff17ed06608 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #1  0x7ff17ed06cf3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #2  0x7ff17ed04e2d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #3  0x7ff17f3fdd02 in g_settings_backend_read (backend=, 
key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", 
expected_type=0x7ff1877135a0 , 
default_value=default_value@entry=0) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
- value = 
+ value = 
  #4  0x7ff17f401c7b in g_settings_read_from_backend 
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, 
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) 
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
- value = 
- fixup = 
- path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
+ value = 
+ fixup = 
+ path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
  #5  0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, 
key=0x2087618 "disable-lock-screen") at 
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
- skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
"disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
- value = 
- __FUNCTION__ = "g_settings_get_value"
+ skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
"disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
+ value = 
+ __FUNCTION__ = "g_settings_get_value"
  
-
  
-The top part of the trash file when viewed in TextEdit has the information 
:
+    The top part of the trash file when viewed in TextEdit has the information 
:
  -
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Dec 12 10:16:52 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/compiz
  ExecutableTimestamp: 1405349348
  ProcCmdline: compiz
  --
  
-His system is Ubuntu trusty 14.04.1 LTS. Unity installed
+    His system is Ubuntu trusty 14.04.1 LTS. Unity installed
  7.2.3+14.04.20140826-0ubuntu1.0.1 .

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1410582

Title:
  [Trusty / Unity] Desktop got unlocked on its own.

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  I have a user reporting an incidence that trusty unity desktop got
  unlocked on its own:

  "In the morning, after coming to my desk, I just pressed the space bar
  on my desktop to get the monitors woken up. The monitors came up with
  the locked screen and then after a while it got unlocked to my
  surprise!"

     There was compiz crash file on his system at that time. However, I
  don't have the right debug symbols to which file (or function) it
  crashed into. Here is the top part of the stack trace w

[Dx-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

[Amr Ibrahim]

Coeur, you have to update unity from trusty-proposed as instructed in
comment #26
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302885/comments/26

-- 
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/1302885

Title:
  Media keyboard shortcuts not working

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1302885/+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 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.

[Jennifer Pan]

** Information type changed from Private Security to Public Security

-- 
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/1410582

Title:
  [Trusty / Unity] Desktop got unlocked on its own.

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
 I have a user reporting an incidence that trusty unity desktop got
  unlocked on its own:

"Well, I didn't unlock/lock the system before the auto-unlock that morning.
  What I mean is that, on that morning after coming to my desk, I started
  working on my Mac and just press the space bar on my desktop to get the
  monitors woken up. The monitors came up with the locked screen and then
  after a while it got unlocked to my surprise!"

 There was compiz crash file on his system at that time. However, I
  don't have the right debug symbols to which file (or function) it
  crashed into. Here is the top part of the stack trace when I ran
  apport-retrace -s  on his crash file:

  
---
  --- stack trace ---
  #0  0x7ff17ed06608 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #1  0x7ff17ed06cf3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #2  0x7ff17ed04e2d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #3  0x7ff17f3fdd02 in g_settings_backend_read (backend=, 
key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", 
expected_type=0x7ff1877135a0 , 
default_value=default_value@entry=0) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
  value = 
  #4  0x7ff17f401c7b in g_settings_read_from_backend 
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, 
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) 
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
  value = 
  fixup = 
  path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
  #5  0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, 
key=0x2087618 "disable-lock-screen") at 
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
  skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
"disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
  value = 
  __FUNCTION__ = "g_settings_get_value"
  
-

 The top part of the trash file when viewed in TextEdit has the information 
:
  -
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Dec 12 10:16:52 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/compiz
  ExecutableTimestamp: 1405349348
  ProcCmdline: compiz
  --

 His system is Ubuntu trusty 14.04.1 LTS. Unity installed
  7.2.3+14.04.20140826-0ubuntu1.0.1 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+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 1059275] Re: reset now deprecated, man page not updated

[Nekhelesh Ramananthan]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1059275

Title:
  reset now deprecated, man page not updated

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [ Impact ]

  The manpage for the "unity" command reflects the actual available
  options.

  [ Test Case ]

  Run "man unity".  It should not say "--reset" is a valid command-line
  switch (option).

  [ Regression Potential ]

  This is a change to the man page.  I suppose it might be a regression
  if the man page still does not match the option available in the
  'unity' command.  Not terribly serious.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1059275/+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 1350331] Re: Dash doesn't close when Drag and dropping from it to another window

[Nekhelesh Ramananthan]

Fixed in Unity 7.2.4. Thnx for the fix.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1350331

Title:
  Dash doesn't close when Drag and dropping from it to another window

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [ Impact ]

   1. Open one nautilus window and another window, so that nautilus is not 
focused
   2. Open the dash File lens (Super+F)
   3. Start dragging a file from that to the nautilus launcher icon
   4. Wait some delay

  Expected Result:
   4. The dash is closed and nautilus window is focused

  Actual result:
   4. The nautilus window is focused, but the dash is not closed

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change in Unity has the potential to introduce crashes in
  Unity.

  This particular fix has the potential to not close the dash after a
  drag-and-drop operation, which could conceivably result in a desktop
  lock-up requiring a restart.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without apparent
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1350331/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access

[Treviño]

thanks for the extensive testing ;)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1332947

Title:
  HDPI: unity randomly turns on large text in universal access

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [ Impact ]

  Using a display scaling factor of > 1.0 the 'large text' setting is
  sometimes enabled automatically on session start, doubling the scaling
  factor.

  [ Test Case ]

  (1) Using the System Settings > Displays > Scale for menu and title bars 
slider, set the scaling to a value > 1 (for example, 1.88).
  (2) Log out and in several times.

  Since this problem occurs as a result of a race condition somewhere,
  it is not reliably reproducable.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could introduce a new crash
  or lockup.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  demonstrating regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1332947/+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 1404730] Re: Dash: some icons are scaled incorrectly

[Launchpad Bug Tracker]

** Branch linked: lp:~andyrock/unity/lp-1404730

-- 
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/1404730

Title:
  Dash: some icons are scaled incorrectly

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Please see the enclosed screenshot - the software updater icon is
  oversized compared to others displayed in Dash

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Dec 21 21:13:29 2014
  InstallationDate: Installed on 2014-11-27 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141123)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1404730/+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 1404730] Re: Dash: some icons are scaled incorrectly

[Andrea Azzarone]

** Changed in: unity
Milestone: 7.3.2 => 7.3.1

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1404730

Title:
  Dash: some icons are scaled incorrectly

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Please see the enclosed screenshot - the software updater icon is
  oversized compared to others displayed in Dash

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Dec 21 21:13:29 2014
  InstallationDate: Installed on 2014-11-27 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141123)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1404730/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Charles Kerr]

** Changed in: ubuntu-clock-app
 Assignee: (unassigned) => Charles Kerr (charlesk)

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Jean-Baptiste Lallement]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171/+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 1355463] Re: Unity launcher crash after click second open window

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1355463

Title:
  Unity launcher crash after click second open window

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  When there are more than one window opened from the same program,
  let's say gedit and you click on the application launcher expecting a
  kind of previsualizators to choose one of the opened windows, X system
  keeps blocked and I need to open a shell session and kill it.

  Release: Ubuntu 14.04.1 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1355463/+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 1355463] Re: Unity launcher crash after click second open window

[jingles]

I had this problem too - the fix was to change OpenGL -> General ->
Texture Filter from "Good" to "Fast" as Andreas wrote, but when i
changed it back to Good, the problem didn't appear again.

-- 
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/1355463

Title:
  Unity launcher crash after click second open window

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  When there are more than one window opened from the same program,
  let's say gedit and you click on the application launcher expecting a
  kind of previsualizators to choose one of the opened windows, X system
  keeps blocked and I need to open a shell session and kill it.

  Release: Ubuntu 14.04.1 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1355463/+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 1411171] Re: Repeating alarms are disabled after it went off once

[Nekhelesh Ramananthan]

** Summary changed:

- Repeating alarm disabled after it went off once
+ Repeating alarms are disabled after it went off once

** Changed in: ubuntu-clock-app
Milestone: None => ota-1

** Tags added: alarm

** Summary changed:

- Repeating alarms are disabled after it went off once
+ Repeating alarms appear disabled in clock app after it went off once

** Changed in: ubuntu-clock-app
   Importance: Undecided => High

-- 
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/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171/+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 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted

[Nekhelesh Ramananthan]

As of Ubuntu RTM r13, this bug has been fixed. Marking it as fix
released.

** Changed in: ubuntu-clock-app
   Status: Confirmed => Fix Released

-- 
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/1387231

Title:
  [regression][clock] alarm still rings once it's been disabled or
  deleted

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  (r135)

  Steps to reproduce:

  1. Create a single type alarm to ring in the next 5 minutes.
  2. Wait for the alarm to ring.
  3. After dismissing the alarm, delete it from the clock app.

  Actual behaviour:

  Once the alarm's been deleted, it still rings!

  Expected behaviour:

  Once you delete the alarm, this shouldn't ring anymore.

  

  Mako, Image #5 ubuntu rtm,

  Steps to reproduce:

  1. Create an alarm to ring in the next 5 minutes.
  2. Disable the alarm after it is created.

  Actual Behaviour:

  Alarm still rings!

  Expected Behaviour:

  Once you disable an alarm, it shouldn't ring anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387231/+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 1411171] Re: Repeating alarm disabled after it went off once

[Nekhelesh Ramananthan]

I suspect this is a side effect that was introduced while fixing
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362341. Instead of
disabling just one-time alarms after they ring, I presume indicator-
datetime mistakingly disables recurring alarms as well. Clock app merely
displays the EDS data and in this case it seems the EDS is being changed
incorrectly.

** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1411171

Title:
  Repeating alarm disabled after it went off once

Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171/+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 1240016] Re: dash not accessible when using virtualbox seamless mode

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1240016

Title:
  dash not accessible when using virtualbox seamless mode

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 13.10 there is an issue that causes the dash to become
  inaccessible when using virtualbox in seamless mode. Also affects HUD
  (but I don't use it so can't say much on that).

  Reproducable: Yes

  How to reproduce the problem: 
  Open a VM in seamless mode on one of the workspaces. Switch to another 
workspace. Try to access the dash (either with mouse click or super key). The 
result is that the dash will briefly appear (millisecond) and then disappear 
rendering it inaccesible. 

  Workaround: While in a desktop workspace (not the VM) click on super+s
  to open expo and then click super+s again to go back to the ubuntu
  desktop. Now you should be able to access the dash.

  I've tested this on the standard 3.11 kernel as well as the 3.12rc
  kernels with the same result. At least one other perosn has the same
  issue based on a discussion in the ubuntu forums.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1240016/+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 974382] Re: memory leak in unity-panel-service

[James Troup]

I'm still seeing this with Ubuntu 14.10:

 3381 james  20   0  825M  219M 11672 S  0.5  2.8  1h10:23 
/usr/lib/unity/unity-panel-service
 
I've attached  /proc/`pidof unity-panel-service`/maps

** Attachment added: "/proc/`pidof unity-panel-service`/maps"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/974382/+attachment/4299158/+files/unity-panel-service.maps

-- 
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/974382

Title:
  memory leak in unity-panel-service

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  top sorted by memory on my system right now shows:
  top - 11:28:46 up 26 days, 15:58, 16 users,  load average: 0.15, 0.21, 0.49
  Tasks: 280 total,   1 running, 276 sleeping,   0 stopped,   3 zombie
  Cpu(s): 19.8%us,  3.8%sy,  0.0%ni, 75.3%id,  1.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   3941584k total,  3689220k used,   252364k free,   136040k buffers
  Swap:  4096536k total,   783324k used,  3313212k free,   888748k cached

    PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
  29131 smoser20   0 1939m 925m  21m S   34 24.0 292:02.57 firefox
  15273 smoser20   0 1831m 448m  14m S2 11.7  86:51.58 unity-2d-shell
  15329 smoser20   0  701m 134m 6412 S0  3.5  10:26.07 unity-panel-ser
  16495 smoser20   0  446m  48m 1520 S0  1.3   1:04.42 deja-dup-monito
  32551 smoser20   0  496m  46m 7892 S0  1.2 121:52.35 xchat

  $ ls -l /proc/15329/{cmdline,exe}
  -r--r--r-- 1 smoser smoser 0 Mar 15 22:08 /proc/15329/cmdline
  lrwxrwxrwx 1 smoser smoser 0 Mar 16 08:02 /proc/15329/exe -> 
/usr/lib/unity/unity-panel-service (deleted)

  That shows that this has been since upgraded, and that it has been up for ~ 3 
weeks.
  Looking at my apt logs, then this bug is actually against 5.6.0-0ubuntu4 , 
but I'm filing it anyway, as waiting 3 weeks to see if I see this problem again 
probably isn't going to help anyone.


  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity-services 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell]
  Date: Thu Apr  5 11:14:22 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2011-11-07 (150 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/974382/+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 1302885] Re: Media keyboard shortcuts not working

[Coeur Noir]

After todays updates I've lost again the volume keys…

…but this time the sgettings commands had no effects to fix it.

Attached is screenshits of today's updates if any relevant ?

** Attachment added: "historique logitheque"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302885/+attachment/4299148/+files/Capture%20du%202015-01-15%2013%3A14%3A52.png

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1302885

Title:
  Media keyboard shortcuts not working

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1302885/+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 1302885] Re: Media keyboard shortcuts not working

[Coeur Noir]

Sorry - lol - unintended typos ! please read :

gsettings instead of sgettings

and of course

screenshots instead of …

-- 
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/1302885

Title:
  Media keyboard shortcuts not working

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1302885/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop

[muzzol]

I'm affected by this bug too.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename:   trusty

$ uname -a
Linux cprli0792 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l | grep hud
ii  hud   
14.04+14.04.20140604-0ubuntu1   amd64Backend for 
the Unity HUD
ii  libhud2:amd64 
14.04+14.04.20140604-0ubuntu1   amd64library for 
exporting items to the Unity HUD


ask me for further info if you need it

-- 
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/1300722

Title:
  hud-service is eating up 100% of one of my CPUs in a poll loop

Status in Unity HUD:
  Confirmed
Status in hud package in Ubuntu:
  In Progress

Bug description:
  hud-service is polling like crazy:

  Context Switches:
PID  ProcessVoluntary   Involuntary Total
   Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
2295 hud-service  46084.6342.94 46127.58 (very high)
2325 hud-service  0.09 0.00 0.09 (very low)
2329 hud-service  0.07 0.00 0.07 (very low)
2340 hud-service  0.05 0.00 0.05 (very low)
   Total  46084.8442.94 46127.78

  File I/O operations:
   No file I/O operations detected.

  System calls traced:
PID  Process  Syscall   CountRate/Sec
2295 hud-service  poll 83   23124.8503
2295 hud-service  write10   0.2313
2295 hud-service  sendmsg   4   0.0925
2325 hud-service  restart_syscall   1   0.0231
2329 hud-service  restart_syscall   1   0.0231
2340 hud-service  restart_syscall   1   0.0231
   Total  100   23125.2435

  (gdb) where
  #0  0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #2  0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #3  0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #4  0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #5  0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #6  0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #7  0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #8  0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2
  #9  0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() ()
  #17 0x00441e43 in hud::service::WindowImpl::activate() ()
  #18 0x00439f6a in 
hud::service::QueryImpl::updateToken(QSharedPointer) ()
  #19 0x0043a672 in hud::service::QueryImpl::refresh() ()
  #20 0x0044b115 in ?? ()
  #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #22 0x0045662a in 
hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString 
const&, unsigned int) ()
  #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #24 0x00467361 in 
ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, 
QString const&, unsigned int) ()
  #25 0x004678bd in ?? ()
  #26 0x00467c63 in 
ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, 
void**) ()
  #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #28 0x7fda8435e22e in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #29 0x7fda823d5c2c in QApplicationPr

[Dx-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

[Bruno Nova]

I've tested the trusty-proposed update in a VirtualBox virtual machine
(version 7.2.4+14.04.20141217-0ubuntu1).

The update fixes the issue.
Now when I press Super+W, type something until only 1 window is shown (filter) 
and select the window, the title bars of all of the maximized windows are 
correctly merged with the top bar.
It also works when the windows are spread through multiple workspaces and I use 
Super+Shift+W to view all of the windows.
And it works both with the global menu and with locally integrated menus.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1316265

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [ Impact ]

  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  [ Test Case ]

  (1) Open one or more Terminals, place one in maximized mode (eg. by using 
control-super-up or clicking the embiggen button).
  (2) use super-W to enter the spread mode
  (3) select the maximized terminal window
  (4) lookee lookee, separate title bars without the fix!

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce a
  new crash or hangup.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been a part of the Ubuntu "Vivid Vervet" dev
  release for some time now and has demonstrated no regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1316265/+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 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)

[Mathew Hodson]

** Tags removed: saucy trusty-desktop utopic
** Tags added: i386

-- 
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, 
dx-packages
https://bugs.launchpad.net/bugs/1263228

Title:
  icons in indicators are small (difficult to view on FullHD display and
  smaller than was on 12.04)

Status in Application Indicators:
  New
Status in The Date and Time Indicator:
  New
Status in Indicator keyboard:
  New
Status in The Messaging Menu:
  New
Status in The Power Indicator:
  New
Status in The Session Menu:
  New
Status in Sound Menu:
  New
Status in Libindicator:
  New
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-application package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-keyboard package in Ubuntu:
  Triaged
Status in indicator-messages package in Ubuntu:
  Triaged
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Triaged
Status in indicator-sound package in Ubuntu:
  Triaged
Status in libindicator package in Ubuntu:
  Triaged

Bug description:
  I have Ubuntu 14.04 with all updates installed.

  My screen resolution is 1920x1080 (FullHD) at 16.4 inches.
  Icons from the menu of newest indicator-keyboard and other gnome-panel icons 
are very small (difficult to read).

  Please adapt icon sizes to large screen resolutions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Dec 21 00:41:25 2013
  InstallationDate: Installed on 2013-10-20 (61 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-application/+bug/1263228/+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