[Dx-packages] [Bug 1176078] Re: Cannot send file by email using unity dash

[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/1176078

Title:
  Cannot send file by email using unity dash

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

Bug description:
  When searching for file using unity dash, and after finding the file,
  and clicking with the right button of the mouse and select email,
  nothing happens.

  This occurs when setting other email client as default other than
  thunderbird in system settings. Using the thunderbird as default email
  software, and proceding like described, behaves like expected.

  i installed the evolution email client and configured as default email
  client.

  It sould send email using other email client like evolution other than
  thunderbird.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri May  3 17:01:37 2013
  InstallationDate: Installed on 2013-05-03 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1176078/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1176078] Re: Cannot send file by email using unity dash

[Benjamin Beelitz]

Effects me too, with the Geary eMail Client. Is there any soulutions?

By the Way i´m using 14.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/1176078

Title:
  Cannot send file by email using unity dash

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

Bug description:
  When searching for file using unity dash, and after finding the file,
  and clicking with the right button of the mouse and select email,
  nothing happens.

  This occurs when setting other email client as default other than
  thunderbird in system settings. Using the thunderbird as default email
  software, and proceding like described, behaves like expected.

  i installed the evolution email client and configured as default email
  client.

  It sould send email using other email client like evolution other than
  thunderbird.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri May  3 17:01:37 2013
  InstallationDate: Installed on 2013-05-03 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1176078/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 674138] Re: "Global" appmenu breaks sloppy focus

[Stephan Henningsen]

Horrible bug that causes data loss:

1) Open a Nautilus file browser window.
2) Focus a directory or file.
3) Create a file or directory on the desktop, while the Nautilus window is open.
4) Click on the file or directory on the desktop.
5) Press the Delete key on the keyboard to delete the newly selected item on 
the desktop.
6) RESULT: The selected item in the *Nautilus window* gets deleted!

Please fix sloppy mouse focus on desktop. Please fix it now. It's about
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/674138

Title:
  "Global" appmenu breaks sloppy focus

Status in Unity:
  Won't Fix
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  An option I heavily use in GNOME 2.x is so called "sloppy focus" or
  "focus follows mouse" (ffm). This feature allows me to have multiple
  windows overlapping and easily switch between them by 'nudging' the
  mouse over the window I wish to type in. I do not bring the window to
  the front.

  Example scenarios

  * Whilst watching a TV programme in a large window, I wish to
  microblog about the TV programme to my followers without distracting
  myself from the programme. I can hover the mouse over twitter client
  dialog box without it obscuring the video window.

  * I am working on a document and need input from a co-worker so I get
  them on IM. As they explain in the IM window I can be typing in the
  document window. When I need to acknowledge receipt of the IM I can
  easily switch to the IM window without losing sight of my document.

  As I understand it, with global appmenu enabled the menu for a window
  is placed at the top of the screen and changes as the window focus
  changes. If I am using focus follows mouse and wish to select a menu
  item for Window A, then as the mouse moves over Window B en-route to
  the menu, the menu content will change, making it challenging to
  select menu options for WIndow A. Under certain circumstances it may
  be possible to take a circuitous route to get the mouse to the appmenu
  so the menu content doesn't change, but this is suboptimal.

  I would like to file a bug to petition for the inclusion of a system
  whereby:-

  * Focus follows mouse feature is included in Unity
  * A system which caters for users of focus follows mouse, and suppresses the 
sub-optimal behaviour.

  My personal suggestion is as follows:-

  * By default Unity be setup with ffm disabled, to use the traditional 
behaviour as default in current GNOME 2
  * An option made available to enable ffm
  * An option made available to configure a key which can suppress the menu 
change
  * Behaviour adopted in Unity whereby when the modifier key is pressed, the 
user can throw the mouse to the menu and know that the menu will be frozen 
(i.e. focus changes will be ignored) until the modifier key is released.

  Whilst I appreciate that the vast majority of users do not use sloppy
  focus, or indeed many don't even know it exists, for those of us that
  do, it's an integral way in which the desktop is used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/674138/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1376099] [NEW] Unity panel is unclickable while any window is maximized.

[inferrna]

Public bug reported:

Sometimes panel works as on video attached.

ProblemType: Bug
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Oct  1 13:59:47 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-17 (13 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140916)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

** Attachment added: "Screencast"
   
https://bugs.launchpad.net/bugs/1376099/+attachment/4221023/+files/output.webm

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

Title:
  Unity panel is unclickable while any window is maximized.

Status in “unity” package in Ubuntu:
  New

Bug description:
  Sometimes panel works as on video attached.

  ProblemType: Bug
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Oct  1 13:59:47 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-17 (13 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140916)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1376099/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1376086] Re: Comically large fonts in Unity

[Vadim Peretokin]

*** This bug is a duplicate of bug 1332947 ***
https://bugs.launchpad.net/bugs/1332947

** This bug has been marked a duplicate of bug 1332947
   HDPI: unity randomly turns on large text in universal access

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

Title:
  Comically large fonts in Unity

Status in “unity” package in Ubuntu:
  New

Bug description:
  Unity somehow screwed up and decided to show everything in a super-
  large font, despite me setting the scaling of UI elements back to 1
  for both monitors and rebooting several times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  Uname: Linux 3.17.0-031700rc3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  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: Wed Oct  1 13:19:17 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 13.350.1, 3.13.0-35-generic, x86_64: installed
   fglrx, 13.350.1, 3.13.0-36-generic, x86_64: installed
   fglrx, 13.350.1, 3.17.0-031700rc3-generic, x86_64: installed
   i915-3.15-3.13, 0.01, 3.13.0-35-generic, x86_64: installed
   i915-3.15-3.13, 0.01, 3.13.0-36-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-06-26 (96 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ZBook 14
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.0-031700rc3-generic 
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: 04/29/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.11
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.54
  dmi.chassis.asset.tag: CNU424B3ZZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 14
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Oct  1 11:51:36 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: Screen 1 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.1
  xserver.video_driver: fglrx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1376086/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1376086] [NEW] Comically large fonts in Unity

[Vadim Peretokin]

*** This bug is a duplicate of bug 1332947 ***
https://bugs.launchpad.net/bugs/1332947

Public bug reported:

Unity somehow screwed up and decided to show everything in a super-large
font, despite me setting the scaling of UI elements back to 1 for both
monitors and rebooting several times.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
Uname: Linux 3.17.0-031700rc3-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
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: Wed Oct  1 13:19:17 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 13.350.1, 3.13.0-35-generic, x86_64: installed
 fglrx, 13.350.1, 3.13.0-36-generic, x86_64: installed
 fglrx, 13.350.1, 3.17.0-031700rc3-generic, x86_64: installed
 i915-3.15-3.13, 0.01, 3.13.0-35-generic, x86_64: installed
 i915-3.15-3.13, 0.01, 3.13.0-36-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:198f]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev 
ff) (prog-if ff)
InstallationDate: Installed on 2014-06-26 (96 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ZBook 14
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.0-031700rc3-generic 
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: 04/29/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.11
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.54
dmi.chassis.asset.tag: CNU424B3ZZ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ZBook 14
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Oct  1 11:51:36 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors: Screen 1 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: fglrx

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu

** Attachment added: "Workspace 1_083.png"
   
https://bugs.launchpad.net/bugs/1376086/+attachment/4220972/+files/Workspace%201_083.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/1376086

Title:
  Comically large fonts in Unity

Status in “unity” package in Ubuntu:
  New

Bug description:
  Unity somehow screwed up and decided to show everything in a super-
  large font, despite me setting the scaling of UI elements back to 1
  for both monitors and rebooting several times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  Uname: Linux 3.17.0-031700rc3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  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: Wed Oct  1 13:19:17 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 13.350.1, 3.13.0-35-generic, x86_64: installed
   fglrx, 13.350.1, 3.13.0-36-generic, x86_64: installed
   fglrx, 13.350.1, 3.17.0-031700rc3-generic, x86_64: installed
   i915-3.15-3.13, 0.01, 3.13.0-35-generic, x86_64: installed
   i915-3.15-3.13, 0.01, 3.13.0-36-generic, x86_64: instal

[Dx-packages] [Bug 1276177] Re: Applications using client-side decorations are not resizable in Unity

[Treviño]

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

** Branch linked: lp:~l3on/ubuntu-themes/gnome-shell-fixes

** Changed in: ubuntu-themes
 Assignee: (unassigned) => Leo Iannacone (l3on)

** Changed in: ubuntu-themes
   Status: New => In Progress

** Changed in: ubuntu-themes
   Importance: Undecided => High

** Changed in: ubuntu-themes
   Importance: High => Medium

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

** Changed in: unity
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity
   Status: New => In Progress

-- 
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:
  In Progress
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  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.

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 778054] Re: Trouble when removing transitional packages

[Mathew Hodson]

Verified that system-config-printer-gnome 1.4.3+20140219-0ubuntu2.2
doesn't depend on python-gobject.

** 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 zeitgeist in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/778054

Title:
  Trouble when removing transitional packages

Status in “aptdaemon” package in Ubuntu:
  Fix Released
Status in “desktopcouch” package in Ubuntu:
  Invalid
Status in “eglibc” package in Ubuntu:
  Invalid
Status in “gnome-utils” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “system-config-printer” package in Ubuntu:
  Fix Released
Status in “wine1.4” package in Ubuntu:
  Fix Released
Status in “zeitgeist” package in Ubuntu:
  New
Status in “aptdaemon” source package in Trusty:
  Fix Released
Status in “desktopcouch” source package in Trusty:
  Invalid
Status in “eglibc” source package in Trusty:
  New
Status in “gnome-utils” source package in Trusty:
  Invalid
Status in “libreoffice” source package in Trusty:
  Fix Released
Status in “openoffice.org” source package in Trusty:
  Invalid
Status in “system-config-printer” source package in Trusty:
  Fix Committed
Status in “wine1.4” source package in Trusty:
  Invalid
Status in “zeitgeist” source package in Trusty:
  New

Bug description:
  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled

[Tony Espy]

So I think this bug should be split into two different bugs.

First, the original reporter filed this on an x86 machine running
Desktop, not Touch.As urfkill is still not used on the Desktop as of
the latest utopic images, I'm splitting this into a urfkill bug for the
problems described by myself and Renato on phones, and a rfkill bug for
the desktop issue ( although this could actually be a driver/hardware-
specific bug vs. a bug in the rfkill package ).

Bug #1376063 has been created to track the urfkill problem seen with the
phone images and the urfkill task in this bug marked Invalid.  All
phone-related tags have been copied to the new bug and removed from this
bug.

** Tags removed: beta qa-daily-testing rtm14 touch-2014-10-09

** Changed in: urfkill (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1296114

Title:
  Bluetooth is always enabled after reboot even if it was disabled

Status in Bluetooth Menu:
  Invalid
Status in “indicator-bluetooth” package in Ubuntu:
  Invalid
Status in “rfkill” package in Ubuntu:
  Triaged
Status in “urfkill” package in Ubuntu:
  Invalid

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated

[Nekhelesh Ramananthan]

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

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

Title:
  [Indicators] Missed calendar or alarm events need to be properly
  indicated

Status in The Date and Time Indicator:
  Confirmed
Status in Clock application for Ubuntu devices:
  Triaged
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  New
Status in “ubuntu-themes” package in Ubuntu:
  New

Bug description:
  Imagine a scenario where you have a calendar event or a clock alarm to
  go of at 10:00. If you get a call at the same time, then obviously the
  call gets the highest priority and the alarm or calendar audible
  notification is suppressed by the system. So a phone user can actually
  miss the event.

  This can be resolved by turning the alarm icon shown in the indicator
  to blue similar to messages to indicate that an alarm or event was
  missed by the user.

  ---

  Desired solution:

  The alarm icon turns its state to active like notification
  center/messages indicator as suggested in the bug description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1321309/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 674138] Re: "Global" appmenu breaks sloppy focus

[Antonin Chambolle]

Dave Gilbert : Indy is right 
the f-f-m option sets the focus on the last window visited, and as long as 
windows are open the desktop never gets the focus. It means it is impossible to 
rename an icon on the desktop (or you need to open a file browser and open the 
desktop inside the file browser)
What I don't understand is that this issue would be solved with a very simple 
variant of focus-follows-mouse :
the behavior should be that
1- it focuses on the window under the mouse
2- it keeps the focus on the last window visited when the pointer is on the 
desktop
3- it focuses on the desktop if you click on it (and in general on any window 
you click in, since sometimes some bug makes the focus loose the mouse). In 
particular, when you click on an icon in the background (or create it) the 
focus should be automatically transferred to that icon...
currently the behavior is 1+2, but not 3.
to sum up, "focus follow mouse" should be a layer onto "click to focus", not an 
exclusive option.
this would still allow to visit the upper bar (for the crazy users who disable 
the menu-in-window feature).
The truth is that f-f-m is so handy that once one has tried it, it is hard to 
change back. (I first tried it on X-10... hmm, in '91?)

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

Title:
  "Global" appmenu breaks sloppy focus

Status in Unity:
  Won't Fix
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  An option I heavily use in GNOME 2.x is so called "sloppy focus" or
  "focus follows mouse" (ffm). This feature allows me to have multiple
  windows overlapping and easily switch between them by 'nudging' the
  mouse over the window I wish to type in. I do not bring the window to
  the front.

  Example scenarios

  * Whilst watching a TV programme in a large window, I wish to
  microblog about the TV programme to my followers without distracting
  myself from the programme. I can hover the mouse over twitter client
  dialog box without it obscuring the video window.

  * I am working on a document and need input from a co-worker so I get
  them on IM. As they explain in the IM window I can be typing in the
  document window. When I need to acknowledge receipt of the IM I can
  easily switch to the IM window without losing sight of my document.

  As I understand it, with global appmenu enabled the menu for a window
  is placed at the top of the screen and changes as the window focus
  changes. If I am using focus follows mouse and wish to select a menu
  item for Window A, then as the mouse moves over Window B en-route to
  the menu, the menu content will change, making it challenging to
  select menu options for WIndow A. Under certain circumstances it may
  be possible to take a circuitous route to get the mouse to the appmenu
  so the menu content doesn't change, but this is suboptimal.

  I would like to file a bug to petition for the inclusion of a system
  whereby:-

  * Focus follows mouse feature is included in Unity
  * A system which caters for users of focus follows mouse, and suppresses the 
sub-optimal behaviour.

  My personal suggestion is as follows:-

  * By default Unity be setup with ffm disabled, to use the traditional 
behaviour as default in current GNOME 2
  * An option made available to enable ffm
  * An option made available to configure a key which can suppress the menu 
change
  * Behaviour adopted in Unity whereby when the modifier key is pressed, the 
user can throw the mouse to the menu and know that the menu will be frozen 
(i.e. focus changes will be ignored) until the modifier key is released.

  Whilst I appreciate that the vast majority of users do not use sloppy
  focus, or indeed many don't even know it exists, for those of us that
  do, it's an integral way in which the desktop is used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/674138/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1367817] Re: Revert icon to previous 'envelope' design

[Pat McGowan]

Looks fixed to me

** Changed in: ubuntu-themes
   Status: In Progress => Fix Released

** Changed in: indicator-messages (Ubuntu)
   Status: In Progress => Invalid

** Changed in: indicator-messages (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  Revert icon to previous 'envelope' design

Status in Themes for Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “ubuntu-themes” package in Ubuntu:
  Fix Released

Bug description:
  "The previous 'envelope' icon worked better".

  UX Testing Finding: "All participants associated the icon with an
  alarm or reminder.  They all failed to interact with it when looking
  for missed calls and unread messages. They had to go to the dialer and
  messages separately to check."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1367817/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 778054] Re: Trouble when removing transitional packages

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/system-config-printer

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

Title:
  Trouble when removing transitional packages

Status in “aptdaemon” package in Ubuntu:
  Fix Released
Status in “desktopcouch” package in Ubuntu:
  Invalid
Status in “eglibc” package in Ubuntu:
  Invalid
Status in “gnome-utils” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “system-config-printer” package in Ubuntu:
  Fix Released
Status in “wine1.4” package in Ubuntu:
  Fix Released
Status in “zeitgeist” package in Ubuntu:
  New
Status in “aptdaemon” source package in Trusty:
  Fix Released
Status in “desktopcouch” source package in Trusty:
  Invalid
Status in “eglibc” source package in Trusty:
  New
Status in “gnome-utils” source package in Trusty:
  Invalid
Status in “libreoffice” source package in Trusty:
  Fix Released
Status in “openoffice.org” source package in Trusty:
  Invalid
Status in “system-config-printer” source package in Trusty:
  Fix Committed
Status in “wine1.4” source package in Trusty:
  Invalid
Status in “zeitgeist” source package in Trusty:
  New

Bug description:
  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 778054] Re: Trouble when removing transitional packages

[Chris J Arges]

Hello Fred, or anyone else affected,

Accepted system-config-printer into trusty-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/system-config-printer/1.4.3+20140219-0ubuntu2.2 in a few hours, and
then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: system-config-printer (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Trouble when removing transitional packages

Status in “aptdaemon” package in Ubuntu:
  Fix Released
Status in “desktopcouch” package in Ubuntu:
  Invalid
Status in “eglibc” package in Ubuntu:
  Invalid
Status in “gnome-utils” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “openoffice.org” package in Ubuntu:
  Won't Fix
Status in “system-config-printer” package in Ubuntu:
  Fix Released
Status in “wine1.4” package in Ubuntu:
  Fix Released
Status in “zeitgeist” package in Ubuntu:
  New
Status in “aptdaemon” source package in Trusty:
  Fix Released
Status in “desktopcouch” source package in Trusty:
  Invalid
Status in “eglibc” source package in Trusty:
  New
Status in “gnome-utils” source package in Trusty:
  Invalid
Status in “libreoffice” source package in Trusty:
  Fix Released
Status in “openoffice.org” source package in Trusty:
  Invalid
Status in “system-config-printer” source package in Trusty:
  Fix Committed
Status in “wine1.4” source package in Trusty:
  Invalid
Status in “zeitgeist” source package in Trusty:
  New

Bug description:
  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1313446] Re: window disappears on toggle shade

[Paarvai Naai]

Hi all,

Is there any update on this bug?  Can this be fixed easily somehow?
I've been using window shading for 10+ years on various window managers
and this issue is really disruptive to my flow.  Thanks.

Paarvai

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

Title:
  window disappears on toggle shade

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

Bug description:
  I used Unity Tweak Tool to enable Toggle Shade using middle click.
  When I click to top of the window, it rolls up and disappears. A
  "ghost" outline of the window appears and the only way to get the
  window back is by using Alt-tab. Sometimes, when reselecting the
  window using Alt-tab, Ubuntu freezes (crashes) and an internal error
  is generated. It seems to be related to Compiz but I'm not sure. An
  error report was generated and sent.

  Description:  Ubuntu 14.04 LTS (64-bit)
  Release:  14.04
  unity-tweak-tool 0.0.6ubuntu1

  I expected the window would "roll up" and I'd be left with the
  window's top bar like with previous versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1313446/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1301751] Re: indicator-session-service crashed with SIGSEGV in get_user_label()

[Sebastien Bacher]

** Information type changed from Private to Public

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

Title:
  indicator-session-service crashed with SIGSEGV in get_user_label()

Status in “indicator-session” package in Ubuntu:
  New

Bug description:
  Not sure what happened.
  Installed Ubuntu 14.04 as a VM in VMware Player.
  After logging in, I was presented with the option to report a bug.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140324-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Apr  3 13:56:02 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2014-04-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  SegvAnalysis:
   Segfault happened at: 0x8056f4a <_start+3256>:   movzbl 0x0(%ebp),%eax
   PC (0x08056f4a) ok
   source "0x0(%ebp)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  StacktraceTop:
   _start ()
   ?? ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  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/ubuntu/+source/indicator-session/+bug/1301751/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles

[Jamie Strandboge]

"So I'm interpreting this as "Messages on Welcome Screen" is related to
the data being shown on the welcome screen. Where the messages and
notification settings is a Unity setting which just blocks the whole
panel."

I'm confused by this comment. The information presented in the
inforgraphics/welcome screen is considerably different than those in the
indicators as mentioned here: https://lists.launchpad.net/ubuntu-
phone/msg09966.html.

I'm very much hoping that these won't be grouped under a single
checkbox. Infographics by default seems fine since there is no specific
information that can be gleaned, but I recognize some people will want
to disable it. Indicators, particularly those for messaging, calendar
and connecting to networks via indicator-network, should be different.
Messaging and calendar should be configurable, but indicator-network
should not. (Please see aforementioned thread for context).

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Confirmed
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  Confirmed
Status in Transfer Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “indicator-messages” package in Ubuntu:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “indicator-transfer” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed

[Greg Williams]

Let me first draw attention to the edit I made to my initial Bug
Description: I have expanded the Bug scope to the fact that the popup-
dialog repeats itself AND the power-cog icon does not turn red. After a
system updates, only one restart-popup should present (it serves
informational purposes while offering the user with an immediate way to
reboot, should they want to). If the user declines this popup, then the
power-cog should turn red and no further popups asking for restart
should present at any time.

Matthew, many of the examples you use do not bolster the case for a
repeating popup-dialog. When a battery is getting moderately low, the
battery status icon goes red. This is as it should be. When the battery
is critically low (and your computer is going to turn itself off or
change its runlevel state), you get a dialog. This is as it should be.
When you update your system and a restart is needed (but your computer
is not going to change its runlevel state if you fail to interact with
the dialog) the dialog is purely informational and offering a choice. If
the user declines to reboot, the appropriate response is to give a red
icon indicating the need to address the issue at a later time, like when
the battery is moderately low.

Likewise, when I am connected to Wi-Fi, the icon changes, as it should.
When I need to enter a Wi-Fi password, it is because I am trying to
connect to Wi-Fi. That intention cannot happen unless I enter a
password. Hence a dialog. The analogy here is that after a system is
updated, one can argue that the update cannot "fully" happen unless the
user reboots. But this is not true in the sense that the reboot has to
happen at that very moment. The system will finish the update whenever
the system is next rebooted; hence, the important thing is the user be
made aware of the need to reboot. With respect to the Wi-Fi password,
the user cannot access Wi-Fi unless they enter the Wi-Fi password. It's
something that has to happen at that very moment.

Many of your arguments appear to gloss over or ignore an important
principle in Unity design. Of course if someone never shuts down or
restarts unless explicitly prompted, shutdown and restart will never
occur at the power-cog. But this is a moot point. For someone who only
shuts down and restarts from the power-cog, the only place the events
occur is at the power-cog. The point is in the conformity to the overall
design of Unity. The indicators in the right-corner of the top panel
(along with NotifyOSD) is the informational hub in Unity for system-
related matters. This is basic Unity design principle. This is where
system-related messages SHOULD present. You seem to be arguing that how
one particular user may choose to use the system warrants ignoring this
design criteria/principle of Unity. If the system needs to be rebooted
to accomplish something, this "longterm" state should to be communicated
to users via the established Unity design principle of a red system-
indicator.

Many people hate popups when Google Docs use them. And they hate them
when advertisements use them. And they hate them when they land at a
website and the screen grays and there's some stupid popup telling them
to "Like" them on Facebook (forcing them to click an X to get rid of the
popup). Popups should only present when input is REQUIRED to prevent a
change in runlevel or to complete a REQUIRED objective to achieve said
state (i.e., something that will disrupt what the user is trying to
accomplish at that moment). Other popups are nothing more than nuisances
and serve mostly as an interruption. A popup announcing that a reboot is
needed may be a permissible exception because it is informational while
simultaneously serving as a "shortcut" to accomplish the act. If the
user chooses not to reboot, however, repeating the popup-dialog is
introducing a nuisance and needlessly interrupting the work of Ubuntu
users while simultaneously failing to utilize the proper communication
channels that Unity Design Principles stipulate. The power-cog turning
red is the appropriate way to handle the communication of the system's
state in this regard.


** Description changed:

- Bug = the restart-popup-dialog that sometimes occurs after a system-
- update should only run once. If the user declines to reboot from the
- popup, then the power-cog should turn red until reboot occurs. Repeated
- popups asking to reboot should not occur.
+ Bug = a popup-dialog asking the user to reboot the system after an
+ update should not repeat (popup again) at a later time if the user
+ chooses not to reboot. Instead, the power-cog should turn the color red
+ and no further popup-dialogs should present at any time.
  
  In ubuntu 12.04 the power-cog turned red when a reboot/restart was
  needed. This was a helpful feature because it informed users that they
  needed to restart the computer. But this helpful indicator is gone in
  14.04 and it has resulted in me never remembering to restart my compute

[Dx-packages] [Bug 1348039] Re: shim does not implement 'Subscribe' method called by logind

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1348039

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1348039

Title:
  shim does not implement 'Subscribe' method called by logind

Status in “systemd-shim” package in Ubuntu:
  Fix Released

Bug description:
  Get that error logged at the end of the dmesg file. That error seems
  to have no sad effect on the system:

  [   30.793181] systemd-logind[1006]: Failed to enable subscription: No
  such method 'Subscribe'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-6ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Jul 24 07:25:46 2014
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed

[Greg Williams]

** Description changed:

+ Bug = the restart-popup-dialog that sometimes occurs after a system-
+ update should only run once. If the user declines to reboot from the
+ popup, then the power-cog should turn red until reboot occurs. Repeated
+ popups asking to reboot should not occur.
+ 
  In ubuntu 12.04 the power-cog turned red when a reboot/restart was
  needed. This was a helpful feature because it informed users that they
  needed to restart the computer. But this helpful indicator is gone in
  14.04 and it has resulted in me never remembering to restart my computer
  because there is no helpful feedback from ubuntu that a restart is
  needed.
  
  In 14.04, I will perform an update and a popup tells me a Restart is
  needed but I usually select to restart-later because I am in the middle
  of working. By the the time I am done working I have forgotten that a
  restart is needed. Later when I am working again a popup occurs
  informing me that a restart is needed (but again I am in the middle of
  working so I don't restart). Bottom line: when the power-cog turned red,
  it reminded me that I needed to restart the computer. When I finished my
  work I look up and see the red power-cog and "Oh yeah, I need to
  restart. Now is a good time." In 14.04 this doesn't happen. Instead I'm
  perpetually bugged by a popup (which is useless because it's never a
  good time to restart when it pops up). The red power-cog was a much
  BETTER design choice.
  
  The removal of the power-cog turning red has negatively affected the
  management of ubuntu updates and it should be fixed so that it behaves
  like 12.04.

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

Title:
  14.04 power-cog does not turn red when restart is needed

Status in The Session Menu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Bug = the restart-popup-dialog that sometimes occurs after a system-
  update should only run once. If the user declines to reboot from the
  popup, then the power-cog should turn red until reboot occurs.
  Repeated popups asking to reboot should not occur.

  In ubuntu 12.04 the power-cog turned red when a reboot/restart was
  needed. This was a helpful feature because it informed users that they
  needed to restart the computer. But this helpful indicator is gone in
  14.04 and it has resulted in me never remembering to restart my
  computer because there is no helpful feedback from ubuntu that a
  restart is needed.

  In 14.04, I will perform an update and a popup tells me a Restart is
  needed but I usually select to restart-later because I am in the
  middle of working. By the the time I am done working I have forgotten
  that a restart is needed. Later when I am working again a popup occurs
  informing me that a restart is needed (but again I am in the middle of
  working so I don't restart). Bottom line: when the power-cog turned
  red, it reminded me that I needed to restart the computer. When I
  finished my work I look up and see the red power-cog and "Oh yeah, I
  need to restart. Now is a good time." In 14.04 this doesn't happen.
  Instead I'm perpetually bugged by a popup (which is useless because
  it's never a good time to restart when it pops up). The red power-cog
  was a much BETTER design choice.

  The removal of the power-cog turning red has negatively affected the
  management of ubuntu updates and it should be fixed so that it behaves
  like 12.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/1346355/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1290535] Re: [FFE] Webapps support for the new Oxide container

[Olivier Tilloy]

** Changed in: oxide-qt (Ubuntu)
   Status: New => Invalid

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity-webapps in Ubuntu.
https://bugs.launchpad.net/bugs/1290535

Title:
  [FFE] Webapps support for the new Oxide container

Status in WebApps: libunity:
  Fix Released
Status in Unity WebApps QML component:
  Fix Released
Status in “libunity-webapps” package in Ubuntu:
  Fix Released
Status in “oxide-qt” package in Ubuntu:
  Invalid
Status in “unity-webapps-qml” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Invalid

Bug description:
  This is a feature freeze exception request to integrate the following
  feature in the upcoming Ubuntu 14.04 release.

  The overall web application support in Ubuntu currently relies on
  various components and a web container(s) in particular.  So far we
  have been using Firefox and Chromium, by way of browser extensions, to
  detect, host and integrate web applications in Ubuntu.

  On mobile devices however, we have already switched to using our own webapp 
container, based on webbrowser-app.
  The integration itself has been present as an option since 13.10. However we 
have been using the QtWebkit engine so far.

  This request is to also enable and use our webapp-container by
  defaullt, with the Oxide engine, on the desktop edition.

  The change impacts a set of packages linked to this bug report.

  NOTE: This request is not complete and serves to let the release team
  know of the impact and scope of changes, while the individual MPs with
  fixes are being consolidated. It will be updated at the beginning of
  next week when the landing silo is ready for a potential landing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity-webapps/+bug/1290535/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1125442] Re: Always Visible and On Top Windows Steal Focus on Workspace Switch

[Treviño]

I guess this is something that would affect also other VP
implementations (such as cube), so I think it's better to do this at
core level (if applicable).

I'm ok with the setting, so we could even enable it by default,
eventually.

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

** Changed in: unity
   Status: Triaged => Won't Fix

** Changed in: unity (Ubuntu)
   Status: Confirmed => Won't Fix

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

** Changed in: unity (Ubuntu Precise)
   Status: Confirmed => Won't Fix

** Changed in: compiz
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

** No longer affects: unity (Ubuntu Precise)

** No longer affects: unity (Ubuntu)

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

Title:
  Always Visible and On Top Windows Steal Focus on Workspace Switch

Status in Ayatana Design:
  New
Status in Compiz:
  Triaged
Status in Unity:
  Won't Fix
Status in Xubuntu:
  New

Bug description:
  1. Open any application (e.g. TextEditor)
  2. Right click the title bar
   2a. Select "Always on Visible Workspace"
  3. Right click the title bar
   3a. Select "Always on Top"
  4. Open a different application (e.g. Terminal)
  5. Ensure that window has focus
  6. Switch workspaces (Notice: the first application now has focus)
  7. Return to first workspace (Notice: the second application does not regain 
focus)

  Expected:

  The initial application should not have ever regained focus, and
  certainly the second application should have it when returning to that
  workspace.

  antarus@mach ~ $ lsb_release -rd
  Description:Ubuntu 12.04.1 LTS
  Release:12.04

  antarus@mach ~ $ apt-cache policy unity
  unity:
Installed: 5.18.0-0ubuntu2
Candidate: 5.18.0-0ubuntu2
Version table:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1125442/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.

[Launchpad Bug Tracker]

** Branch linked: lp:~nux-team/nux/lp-1228093

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

Title:
  Dash content flickers when the touchpad is used to scroll it.

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in “nux” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Dash content flickers when two-finger scrolling on the touchpad

  [Test case]
  1. Enable two fingers scroll from Unity Control Center -> Mouse and Touchpad
  2. Open the unity dash, expand the search results and start scrolling 
vertically
  3. Content should not flicker and should ignore horizontal scroll events

  [Regression potential]
  Scrolling on dash content does not work properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1228093/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected

[Launchpad Bug Tracker]

** Branch linked: lp:~nux-team/nux/lp-1228093

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

Title:
  Horizontal Scrolling over Indicator-ng (and sound) does not work as
  expected

Status in Libindicator:
  In Progress
Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “libindicator” package in Ubuntu:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “libindicator” source package in Trusty:
  New
Status in “nux” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  When scrolling on indicator-sound using the horizontal scrolling the result 
is the opposite to what we expect in unity (left scrolling increases the volume 
and right scrolling decreases it), while in general is not handled at all for 
indicator-ng indicators as both left and right scrolling always ends up in a 
"+1" delta scroll.

  [Test case]
  1. Hover Indicator-sound in unity
  2. Scroll left: the volume should be reduced
  3. Scroll right: the volume should be increased

  [Regression potential]
  The horizontal scroll direction might be inverted with some touchpads

To manage notifications about this bug go to:
https://bugs.launchpad.net/libindicator/+bug/1342731/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Launchpad Bug Tracker]

** Branch linked: lp:~nux-team/nux/lp-1337244

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

Status in Nux:
  In Progress
Status in Nux trusty series:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Unity crashes when unlocking the session

  [Test case]
  1. Lock the session
  2. Unlock the session
  3. No crash should happen

  [Regression potential]
  None

  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that
  I was still seeing it quite a while ago, but got no reply to that.

  Crashes are being experienced in multiple machines, while unlocking
  the screen.  The stacktraces vary, but they always fail in the same
  function and same line.

  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int)
     () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
    from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
    from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) ()
    from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x7fd4df29f30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7fd4e127b0eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #17 0x00401971 in main ()

  Second stacktrace (different machine):
  #0  0x7f0058407ed0 in nux_area_accessible_check_pending_notification () 
from /usr/lib/compiz/libunityshell.so
  #1  0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x1d530e0) at ./WindowThread.cpp:318
  #2  0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627
  #3  0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7f00583e6748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
  #5  0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
    from /usr/lib/compiz/libopengl.so
  #6  0x7f00705e2ed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
    from /usr/lib/compiz/libopengl.so
  #7  0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) ()
    from /usr/lib/compiz/libcomposite.so
  #8  0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7f007879b53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7f007879b5ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7f0076c8735f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), v

[Dx-packages] [Bug 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher

[Launchpad Bug Tracker]

** Branch linked: lp:~nux-team/nux/lp-1228093

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

Title:
  Scroll wheel uses inverted logic to switch between
  applications/windows in the switcher

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “nux” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “nux” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Scrolling on the Alt+Tab has invalid behavior:
  - Scrolling down, moves to the previous icon/window
  - Scrolling up, moves to the next icon/window
  - Scrolling left, moves to the next icon/window
  - Scrolling right, moves to the previous icon/window

  [Test case]
  1. Press Alt+Tab
  2. While pressing the keys, use mouse scroll wheel to scroll vertically (and, 
if possible, horizontally)

  Expected behavior:
  - Scrolling down, moves to the next icon/window
  - Scrolling up, moves to the previous icon/window
  - Scrolling left, moves to the previous icon/window
  - Scrolling right, moves to the next icon/window

  [Regression potential]
  Vertical scrolling has not been touched by the change, so there's no 
possibility to regress in this sense.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1342208/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1283979] Re: moving windows causes the top bar and the launcher bar to flicker

[Silviu C.]

I found out that it ceases to act up when using the native Steam client.
Starts to flicker when moving windows when I quit the Steam client.

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

Title:
  moving windows causes the top bar and the launcher bar to flicker

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

Bug description:
  As the title says, when I grab a window and move it around the top bar
  and the launcher disappear and then re-appear. Unity does not crash.
  During the move these elements flicker on and off. It looks more like
  a graphical glitch.

  This seems to have started after I got the packages that introduced
  the anti-aliased window corners.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  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: Mon Feb 24 09:49:18 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:843b]
  InstallationDate: Installed on 2014-02-13 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140111)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=c59b4ac8-ab41-40df-aa23-ee39891ed79c ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67 LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0X
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1104:bd10/27/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67LE:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 09:44:57 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283979/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1125442] Re: Always Visible and On Top Windows Steal Focus on Workspace Switch

[Dariusz Gadomski]

@Marco
I am thinking about a fix for this:
* Add a setting to change the current behavior (e.g. Remember viewport focus)
* Before changing viewport save the currently focused window
* When coming back to a viewport instead of focusing the default window do:
i) if the new setting is enabled try to restore the focus (if the window is 
still there)
ii) else fallback to the default behavior (focusDefaultWindow)

I want to know your opinion on this approach before starting the
implementation.

Do you think it makes sense to implement this in core (src/) or is it
rather specific to wall plugin and should be implemented there (along
with the setting in wall plugin settings)?

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

Title:
  Always Visible and On Top Windows Steal Focus on Workspace Switch

Status in Ayatana Design:
  New
Status in Unity:
  Triaged
Status in Xubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Confirmed

Bug description:
  1. Open any application (e.g. TextEditor)
  2. Right click the title bar
   2a. Select "Always on Visible Workspace"
  3. Right click the title bar
   3a. Select "Always on Top"
  4. Open a different application (e.g. Terminal)
  5. Ensure that window has focus
  6. Switch workspaces (Notice: the first application now has focus)
  7. Return to first workspace (Notice: the second application does not regain 
focus)

  Expected:

  The initial application should not have ever regained focus, and
  certainly the second application should have it when returning to that
  workspace.

  antarus@mach ~ $ lsb_release -rd
  Description:Ubuntu 12.04.1 LTS
  Release:12.04

  antarus@mach ~ $ apt-cache policy unity
  unity:
Installed: 5.18.0-0ubuntu2
Candidate: 5.18.0-0ubuntu2
Version table:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1125442/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1317253] Re: UI scaling and font scaling sometime get confused/change at random.

[Alex Armstrong]

*** This bug is a duplicate of bug 1310316 ***
https://bugs.launchpad.net/bugs/1310316

This bug is a duplicate. See: https://bugs.launchpad.net/bugs/1310316

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

Title:
  UI scaling and font scaling sometime get confused/change at random.

Status in Unity:
  New
Status in Unity Tweak Tool:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo Yoga 2 Pro, with a 13.3" screen running at 3200x1800
  pixels... I bought this partly to test out the UI scaling in Unity!...
  and I have to say it's very awesome (both the screen and the UI
  scaling)... however I have encountered a strange problem.

  Seemingly at random, I have so far 3 times in 10 days had the font
  size (not UI size) suddenly jump to something much too large.

  UI scaling for the display is set at 1.38x and this is quite perfect
  for me, it sure means no one will be able to read my screen over my
  shoulder, but I that's fine!  I had to install a Firefox plugin to
  apply scaling there, but I realise why that is.

  Anyway... I installed ubuntu-tweak and discovered that the large fonts
  were due to the "Text Scaling Factor" having jumped up to a number
  above 2.5... I also discovered that I could not move the slider
  because every time I moved it the fonts re-scaled the slider moved and
  lost mouse focus... and the slider reset to where it was to begin
  with... I clicked the button on the right to return to 1.0, and it
  returned to 1.4, which I assume is representative of the 1.38 I set in
  the screen scaling... but I have no explanation for why it suddenly
  jumped (when I logged out and back in) from 1.4 to something like
  2.5.)..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed May  7 20:55:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1317253/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1341550] Re: Numpad doesn't work in launcher

[Alexander Buchner]

** Changed in: unity
   Status: New => Fix Released

** Changed in: unity (Ubuntu)
   Status: New => 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/1341550

Title:
  Numpad doesn't work in launcher

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 14.04, with all updates installed:

  1. Start the launcher by hitting "super".
  2. Type something on the numpad (incl. "Enter").
  3. Nothing happens.

  I don't think that this behavior is intended, is it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1341550/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected

[Sebastien Bacher]

(unsubscribing sponsors, I don't think there is anything else ready for
upload on that bu)

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

Title:
  Horizontal Scrolling over Indicator-ng (and sound) does not work as
  expected

Status in Libindicator:
  In Progress
Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “libindicator” package in Ubuntu:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “libindicator” source package in Trusty:
  New
Status in “nux” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  When scrolling on indicator-sound using the horizontal scrolling the result 
is the opposite to what we expect in unity (left scrolling increases the volume 
and right scrolling decreases it), while in general is not handled at all for 
indicator-ng indicators as both left and right scrolling always ends up in a 
"+1" delta scroll.

  [Test case]
  1. Hover Indicator-sound in unity
  2. Scroll left: the volume should be reduced
  3. Scroll right: the volume should be increased

  [Regression potential]
  The horizontal scroll direction might be inverted with some touchpads

To manage notifications about this bug go to:
https://bugs.launchpad.net/libindicator/+bug/1342731/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1317253] Re: UI scaling and font scaling sometime get confused/change at random.

[arfastore]

*** This bug is a duplicate of bug 1310316 ***
https://bugs.launchpad.net/bugs/1310316

Just "up the heat" a bit, I am also experiencing this issue.  Ubuntu
14.04, Acer Aspire S7.  I will certainly try the Tweak tool to rectify
in the meantime, thanks to all who found & posted that.

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

Title:
  UI scaling and font scaling sometime get confused/change at random.

Status in Unity:
  New
Status in Unity Tweak Tool:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo Yoga 2 Pro, with a 13.3" screen running at 3200x1800
  pixels... I bought this partly to test out the UI scaling in Unity!...
  and I have to say it's very awesome (both the screen and the UI
  scaling)... however I have encountered a strange problem.

  Seemingly at random, I have so far 3 times in 10 days had the font
  size (not UI size) suddenly jump to something much too large.

  UI scaling for the display is set at 1.38x and this is quite perfect
  for me, it sure means no one will be able to read my screen over my
  shoulder, but I that's fine!  I had to install a Firefox plugin to
  apply scaling there, but I realise why that is.

  Anyway... I installed ubuntu-tweak and discovered that the large fonts
  were due to the "Text Scaling Factor" having jumped up to a number
  above 2.5... I also discovered that I could not move the slider
  because every time I moved it the fonts re-scaled the slider moved and
  lost mouse focus... and the slider reset to where it was to begin
  with... I clicked the button on the right to return to 1.0, and it
  returned to 1.4, which I assume is representative of the 1.38 I set in
  the screen scaling... but I have no explanation for why it suddenly
  jumped (when I logged out and back in) from 1.4 to something like
  2.5.)..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed May  7 20:55:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1317253/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp