[Dx-packages] [Bug 1134202] Re: Removing overlay-scrollbar causes lots of noise

2014-04-21 Thread Elemer
It is still in Ubuntu 14.04 64bit if I try to run skype from terminal
for example.

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

Title:
  Removing overlay-scrollbar causes lots of noise

Status in “overlay-scrollbar” package in Ubuntu:
  Confirmed

Bug description:
  The overlay-scrollbar package can be removed to disable the modified
  scrollbar, reverting to classic scrollbars. If this is done, nearly
  every GTK application will emit the following error when started:

  Gtk-Message: Failed to load module overlay-scrollbar

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: overlay-scrollbar (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Wed Feb 27 17:44:39 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-26 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225)
  MarkForUpload: True
  SourcePackage: overlay-scrollbar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1134202/+subscriptions

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


[Dx-packages] [Bug 1291302] Re: password never match since IM is on in unity lockscreen

2014-04-21 Thread 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/1291302

Title:
  password never match since IM is on in unity lockscreen

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  With a combination of ibus-mozc and unity, password never match until
  making IM off manually.

  How to reproduce:
   1. set ibus-mozc as a default IM
   2. lock screen with unity (Ctrl+Alt+L)
   3. input your password to unlock screen

  Expected result:
   screen unlocked.

  Actual result:
   password never match until making IM off manually.

  ibus-mozc:
Installed: 1.13.1651.102-2
Candidate: 1.13.1651.102-2
Version table:
   *** 1.13.1651.102-2 0
  500 http://jp.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status
  unity:
Installed: 7.1.2+14.04.20140311-0ubuntu1
Candidate: 7.1.2+14.04.20140311-0ubuntu1
Version table:
   *** 7.1.2+14.04.20140311-0ubuntu1 0
  500 http://jp.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Mar 12 05:58:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-15 (148 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014)
  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/1291302/+subscriptions

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


[Dx-packages] [Bug 1309769] Re: Network doesn't return after sleep

2014-04-21 Thread nicolas kleinklaus
*** This bug is a duplicate of bug 1286552 ***
https://bugs.launchpad.net/bugs/1286552

Not a isolated problem :

http://ubuntuforums.org/showthread.php?t=2218043
http://ubuntuforums.org/showthread.php?t=2218445

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

Title:
  Network doesn't return after sleep

Status in The Linux Kernel:
  Unknown
Status in NetworkManager:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed

Bug description:
  14.04 same thing WIFI doesn't come back after sleep/suspend... Editing
  /etc/pm/config.d/config with the SUSPEND_MODULES=your_driver_here
  in my case rtl8192ce used to work sometimes, now its not working
  at all. After every suspend it seems to be unable to connect. Seth
  Arnold suggested that my issue was unrelated to any of  the other fail
  after suspends and should open another ticket.

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

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


[Dx-packages] [Bug 1310490] [NEW] indicator-messages is hidden on 14.04 LTS

2014-04-21 Thread Bortnyák Roland
Public bug reported:

I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've
noticed, that the mail icon is hidden. I've reinstalled the package:
`sudo apt-get install --reinstall indicator-messages` - it was
successful, but didn't change anything. Tried to install thunderbird,
but nothing changed.

If I want to run it manually ($ indicator-messages or with Alt+F2) the
command not found...

I know, that it is hidden, because I'm using GMail Notifier, which
displays itself, and it works.

Package info:
indicator-messages:
  Installed: 13.10.1+14.04.20140410-0ubuntu1
  Candidate: 13.10.1+14.04.20140410-0ubuntu1
  Version table:
 *** 13.10.1+14.04.20140410-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status


Please fix this issue!

** Affects: indicator-messages (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  indicator-messages is hidden on 14.04 LTS

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

Bug description:
  I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've
  noticed, that the mail icon is hidden. I've reinstalled the package:
  `sudo apt-get install --reinstall indicator-messages` - it was
  successful, but didn't change anything. Tried to install thunderbird,
  but nothing changed.

  If I want to run it manually ($ indicator-messages or with Alt+F2) the
  command not found...

  I know, that it is hidden, because I'm using GMail Notifier, which
  displays itself, and it works.

  Package info:
  indicator-messages:
Installed: 13.10.1+14.04.20140410-0ubuntu1
Candidate: 13.10.1+14.04.20140410-0ubuntu1
Version table:
   *** 13.10.1+14.04.20140410-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Please fix this issue!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1310490/+subscriptions

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


[Dx-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

2014-04-21 Thread Norbert
** Description changed:

  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.
  
  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)
+ 
+ --
+ For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
+ --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in Gnome Settings Daemon:
  Won't Fix
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions

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


[Dx-packages] [Bug 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys

2014-04-21 Thread Norbert
** Description changed:

  There are shortcuts to open lenses in Unity, for example Super + A for
  App Lens, or Super + F for Files Lens, etc. There are also shortcuts
  in the Launcher Super + 1 to 9 to launch apps from the Launcher. These
  shortcuts don't work if the keyboard layout is set to a non-Latin
  layout, in my case Persian, where almost all the keys are mapped to new
  characters.
  
  HOW TO REPRODUCE:
  Add a new Persian keyboard layout to the system, in addition to English, via 
keyboard layout indicator -- Text Entry Settings.
  Switch to the Persian layout (by clicking on the keyboard layout indicator).
  Press Super + F.
  
  WHAT HAPPENS:
  Dash is not open. Nothing happens.
  
  WHAT SHOULD HEPPEN:
  The Files Lens in the dash should open.
  The shortcuts should be associated with the keys on the keyboard, not to the 
characters they are associated with (which depends on the active keyboard 
layout).
  When I am typing something in Persian, and I want to search for a file, it is 
not reasonable that I should first switch back to the English layout before I 
can use a particular shortcut.
  
  
  This problem does not happen in some other apps like gedit or Firefox.
  
  COMPARE TO GEDIT:
  Open gedit text editor.
  Write something.
  Switch to the Persian layout.
  Press Ctrl + S (the shortcut to save the document).
  
  WHAT HAPPENS, AND WHAT SHOULD HAPPEN:
  The save dialoge box appears.
  
  
- I think this problem happens for all keyboard layouts that don't use Latin 
characters. 
+ I think this problem happens for all keyboard layouts that don't use Latin 
characters.
  Layout-wise, when I press Ctrl + S while Persian layout is active, I am 
typing Ctrl + س.
  But keyboard-wise, I am always pressing the same keyboard binding.
+ 
+ --
+ For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
+ --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 16 12:04:10 2014
  InstallationDate: Installed on 2014-02-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  SourcePackage: libunity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in
  Trusty - shortcuts are defined via keyboard layout, not the keys

Status in Unity Settings Daemon:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  There are shortcuts to open lenses in Unity, for example Super + A
  for App Lens, or Super + F for Files Lens, etc. There are also
  shortcuts in the Launcher Super + 1 to 9 to launch apps from the
  Launcher. These shortcuts don't work if the keyboard layout is set to
  a non-Latin layout, in my case Persian, where almost all the keys are
  mapped to new characters.

  HOW TO REPRODUCE:
  Add a new Persian keyboard layout to the system, in addition to English, via 
keyboard layout indicator -- Text Entry Settings.
  Switch to the Persian layout (by clicking on the keyboard layout indicator).
  Press Super + F.

  WHAT HAPPENS:
  Dash is not open. Nothing happens.

  WHAT SHOULD HEPPEN:
  The Files Lens in the dash should open.
  The shortcuts should be associated with the keys on the keyboard, not to the 
characters they are associated with (which depends on the active keyboard 
layout).
  When I am typing something in Persian, and I want to search for a file, it is 
not reasonable that I should first switch back to the English layout before I 
can use a particular shortcut.

  
  This problem does not happen in some other apps like gedit or Firefox.

  COMPARE TO GEDIT:
  Open gedit text editor.
  Write something.
  Switch to the Persian layout.
  Press Ctrl + S (the shortcut to save the document).

  WHAT HAPPENS, AND WHAT SHOULD HAPPEN:
  The save dialoge box appears.

  
  I think this problem happens for all keyboard layouts that don't use Latin 
characters.
  Layout-wise, when I press Ctrl + S while Persian layout is active, I am 
typing Ctrl + س.
  But keyboard-wise, I am always pressing the same keyboard binding.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  

[Dx-packages] [Bug 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys

2014-04-21 Thread Norbert
** Tags added: keyboard-layout-switching-related

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

Title:
  Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in
  Trusty - shortcuts are defined via keyboard layout, not the keys

Status in Unity Settings Daemon:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  There are shortcuts to open lenses in Unity, for example Super + A
  for App Lens, or Super + F for Files Lens, etc. There are also
  shortcuts in the Launcher Super + 1 to 9 to launch apps from the
  Launcher. These shortcuts don't work if the keyboard layout is set to
  a non-Latin layout, in my case Persian, where almost all the keys are
  mapped to new characters.

  HOW TO REPRODUCE:
  Add a new Persian keyboard layout to the system, in addition to English, via 
keyboard layout indicator -- Text Entry Settings.
  Switch to the Persian layout (by clicking on the keyboard layout indicator).
  Press Super + F.

  WHAT HAPPENS:
  Dash is not open. Nothing happens.

  WHAT SHOULD HEPPEN:
  The Files Lens in the dash should open.
  The shortcuts should be associated with the keys on the keyboard, not to the 
characters they are associated with (which depends on the active keyboard 
layout).
  When I am typing something in Persian, and I want to search for a file, it is 
not reasonable that I should first switch back to the English layout before I 
can use a particular shortcut.

  
  This problem does not happen in some other apps like gedit or Firefox.

  COMPARE TO GEDIT:
  Open gedit text editor.
  Write something.
  Switch to the Persian layout.
  Press Ctrl + S (the shortcut to save the document).

  WHAT HAPPENS, AND WHAT SHOULD HAPPEN:
  The save dialoge box appears.

  
  I think this problem happens for all keyboard layouts that don't use Latin 
characters.
  Layout-wise, when I press Ctrl + S while Persian layout is active, I am 
typing Ctrl + س.
  But keyboard-wise, I am always pressing the same keyboard binding.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 16 12:04:10 2014
  InstallationDate: Installed on 2014-02-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  SourcePackage: libunity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1280759/+subscriptions

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


[Dx-packages] [Bug 1309769] Re: Network doesn't return after sleep

2014-04-21 Thread nicolas kleinklaus
*** This bug is a duplicate of bug 1286552 ***
https://bugs.launchpad.net/bugs/1286552

kernel 3.14-1 from http://kernel.ubuntu.com/~kernel-ppa/mainline does'nt
resolve the problem

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

Title:
  Network doesn't return after sleep

Status in The Linux Kernel:
  Unknown
Status in NetworkManager:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed

Bug description:
  14.04 same thing WIFI doesn't come back after sleep/suspend... Editing
  /etc/pm/config.d/config with the SUSPEND_MODULES=your_driver_here
  in my case rtl8192ce used to work sometimes, now its not working
  at all. After every suspend it seems to be unable to connect. Seth
  Arnold suggested that my issue was unrelated to any of  the other fail
  after suspends and should open another ticket.

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

-- 
Mailing list: https://launchpad.net/~dx-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

2014-04-21 Thread Chris
I don't know what all the fuss is about, it's great not being able to
see where things are that you need to click on. I heard that for 15.04
the next phase of this brilliant plan will go into effect - entire
windows will be invisible until you mouse over them. Just imagine how
slick and stylish your deskop will look, it's gonna be awesome! And
that's not all... for 16.04, rumor has it that the whole screen will
remain black until you move your mouse. Can you imagine how much space
that will save on small screens? I just can't wait, the innovative-
thinking of Ubuntu UI designers blows my mind!

But seriously now, this is the worst idea ever (and I've seen many bad
ideas since this whole Unity nonsense started). It boggles my mind that
menus used to actually be shown all the time, and then somebody sat down
and spent the time, going out of their way to implement the auto-hide.
It would be fine if we could just agree to disagree by selecting the
behavior we prefer (given that the old behavior already existed, my mind
boggles even more that such an option was not added at the time this
genius made the change).

fwiw I'm still happily using Fedora14, which may seem ancient by many
measurements, but when it comes to getting things done efficiently I
have no complaints at all. Every now and then I take a look at Ubuntu,
but it usually only lasts about 20 minutes before I get sick of having
to go along with epic fail decisions like this. In fact right now I am
typing this on 14.04, probably the last thing I'll be doing on Ubuntu
until next year :-)

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

Title:
  Menus are hidden by default

Status in Ayatana Design:
  Confirmed
Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-2d” 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
  http://www.techrepublic.com/blog/opensource/gnome-shell-vs-ubuntu-
  unity-which-desktop-wins/2291: 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
  

[Dx-packages] [Bug 1310518] [NEW] Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

2014-04-21 Thread Tim Chen
Public bug reported:


Touch screen and touchpad lost click function after quickly tapped dash
home repeatly by touch screen, Installed 14.04, still have same issue.

Quickly tapped dash home more than three times by touch screen.Found
touch screen and touchpad lost click function.

Note:
1.When this issue occured, cursor still can be moved by touch screen/touchpad.
2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

Steps to Reproduce:
1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
2.Quickly tapped dash home more than three times by touch screen.
3.Found touch screen and touchpad lost click function.

This bug is reported from private OEM project, also check
https://launchpad.net/bugs/1297067

==

using xinput --query-state can actually see the button press event

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ syntp id=6  [slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=11  [slave pointer (2)]

#xinput --query-state 11
2 classes :
ButtonClass
 button[1]=up
 button[2]=up
 button[3]=up
 button[4]=up
 button[5]=up
ValuatorClass Mode=Absolute Proximity=In
 valuator[0]=398
 valuator[1]=1652
 valuator[2]=5
 valuator[3]=3
 valuator[4]=0
 valuator[5]=399
 valuator[6]=1653

#xinput --query-state 6
2 classes :
ButtonClass
 button[1]=down
 button[2]=up
 button[3]=up
 button[4]=up
 button[5]=up
 button[6]=up
 button[7]=up
 button[8]=up
ValuatorClass Mode=Relative Proximity=In
 valuator[0]=1
 valuator[1]=394

touchpad's button and touchpanel's
valuator[2] and valuator[3] will changed after we press the button (or monitor)

Also I found press super on keyboard will recover the
touchscreen/touchpad loss.


ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.20.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Mon Apr 21 16:50:04 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-stella-daan2-precise-amd64-20140416-1
InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise running-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/1310518

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in “unity” package in Ubuntu:
  New

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 classes :
  ButtonClass
   button[1]=up
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
  ValuatorClass Mode=Absolute Proximity=In
   valuator[0]=398
   valuator[1]=1652
   valuator[2]=5
   valuator[3]=3
   valuator[4]=0
   valuator[5]=399
   valuator[6]=1653

  #xinput --query-state 6
  2 classes :
  ButtonClass
   button[1]=down
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
   button[6]=up
   button[7]=up
   button[8]=up
  ValuatorClass Mode=Relative Proximity=In
   valuator[0]=1

[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

2014-04-21 Thread Tim Chen
** Description changed:

+ 
  Touch screen and touchpad lost click function after quickly tapped dash
- home repeatly by touch screen
+ home repeatly by touch screen, Installed 14.04, still have same issue.
+ 
+ Quickly tapped dash home more than three times by touch screen.Found
+ touch screen and touchpad lost click function.
+ 
+ Note:
+ 1.When this issue occured, cursor still can be moved by touch screen/touchpad.
+ 2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.
+ 
+ Steps to Reproduce:
+ 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
+ 2.Quickly tapped dash home more than three times by touch screen.
+ 3.Found touch screen and touchpad lost click function.
+ 
+ This bug is reported from private OEM project, also check
+ https://launchpad.net/bugs/1297067
+ 
+ ==
+ 
+ using xinput --query-state can actually see the button press event
+ 
+ ⎡ Virtual core pointer id=2   [master pointer (3)]
+ ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
+ ⎜ ↳ syntp id=6[slave pointer (2)]
+ ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]
+ 
+ #xinput --query-state 11
+ 2 classes :
+ ButtonClass
+  button[1]=up
+  button[2]=up
+  button[3]=up
+  button[4]=up
+  button[5]=up
+ ValuatorClass Mode=Absolute Proximity=In
+  valuator[0]=398
+  valuator[1]=1652
+  valuator[2]=5
+  valuator[3]=3
+  valuator[4]=0
+  valuator[5]=399
+  valuator[6]=1653
+ 
+ #xinput --query-state 6
+ 2 classes :
+ ButtonClass
+  button[1]=down
+  button[2]=up
+  button[3]=up
+  button[4]=up
+  button[5]=up
+  button[6]=up
+  button[7]=up
+  button[8]=up
+ ValuatorClass Mode=Relative Proximity=In
+  valuator[0]=1
+  valuator[1]=394
+ 
+ touchpad's button and touchpanel's
+ valuator[2] and valuator[3] will changed after we press the button (or 
monitor)
+ 
+ Also I found press super on keyboard will recover the
+ touchscreen/touchpad loss.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr 21 16:50:04 2014
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-stella-daan2-precise-amd64-20140416-1
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-stella-daan2-precise-amd64-20140416-1
  InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140416-06:52
  MarkForUpload: True
  ProcEnviron:
-  LANGUAGE=en_US:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project precise series:
  New
Status in OEM Priority Project trusty series:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 

[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

2014-04-21 Thread Tim Chen
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/precise
   Importance: Undecided
   Status: New

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Changed in: oem-priority/precise
   Importance: Undecided = High

** Changed in: oem-priority/trusty
   Importance: Undecided = High

** Changed in: oem-priority
   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/1310518

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project precise series:
  New
Status in OEM Priority Project trusty series:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 classes :
  ButtonClass
   button[1]=up
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
  ValuatorClass Mode=Absolute Proximity=In
   valuator[0]=398
   valuator[1]=1652
   valuator[2]=5
   valuator[3]=3
   valuator[4]=0
   valuator[5]=399
   valuator[6]=1653

  #xinput --query-state 6
  2 classes :
  ButtonClass
   button[1]=down
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
   button[6]=up
   button[7]=up
   button[8]=up
  ValuatorClass Mode=Relative Proximity=In
   valuator[0]=1
   valuator[1]=394

  touchpad's button and touchpanel's
  valuator[2] and valuator[3] will changed after we press the button (or 
monitor)

  Also I found press super on keyboard will recover the
  touchscreen/touchpad loss.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr 21 16:50:04 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-daan2-precise-amd64-20140416-1
  InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140416-06:52
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions

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


[Dx-packages] [Bug 1310540] [NEW] Screen brightness not restored after turning screen off (by inactivity)

2014-04-21 Thread kolen
Public bug reported:

Encountered that after screen is turned off by inactivity, then after
restoring, its brightness was very dim. After looking into Brightness
and lock settings panel, discovered that Brightness was set to 0.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140416-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Apr 21 13:51:45 2014
DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21bb]
InstallationDate: Installed on 2013-10-23 (180 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: LENOVO 4403RP2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
dmi.bios.date: 12/08/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 81ET60WW (1.36 )
dmi.board.name: 4403RP2
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:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4403RP2
dmi.product.version: ThinkPad L412
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Apr 21 12:01:33 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


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

** Attachment added: Screenshot - 21.04.2014 - 13:56:01.png
   
https://bugs.launchpad.net/bugs/1310540/+attachment/4090828/+files/Screenshot%20-%2021.04.2014%20-%2013%3A56%3A01.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/1310540

Title:
  Screen brightness not restored after turning screen off (by
  inactivity)

Status in “unity” package in Ubuntu:
  New

Bug description:
  Encountered that after screen is turned off by inactivity, then after
  restoring, its brightness was very dim. After looking into Brightness
  and lock settings panel, discovered that Brightness was set to 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 21 13:51:45 2014
  DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (180 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 4403RP2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
  

[Dx-packages] [Bug 1310280] Re: hud and dash don't take keyboard input

2014-04-21 Thread Pete Woods
It doesn't sound like a HUD backend issue here, so I'm re-assigning to
unity so someone who understands the UI side of things can look at it.

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

** Changed in: hud (Ubuntu)
   Status: New = Invalid

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

Title:
  hud and dash don't take keyboard input

Status in Unity:
  New
Status in “hud” package in Ubuntu:
  Invalid

Bug description:
  Hud and dash (key Alt or key Super) appear correctly, can also be
  closed with the same key, but I can't type anything. Sometimes one or
  two letters can be entered (if I'm fast), but any further input does
  absolutely nothing.

  I've seen a bug related to ibus with same symptoms, but that one is
  fixed (and my problem is not). Further I selected scim with im-config,
  so ibus should not be running at all (but I see ibus related processes
  on my system). Killing those does not solve the problem. SCIM is
  running (but not activated), but killing it does not make hud or dash
  accept keyboard input either. -- I see no other keyboard related
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hud 13.10.1+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Apr 20 21:52:18 2014
  InstallationDate: Installed on 2009-12-23 (1579 days ago)
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 
(20091028.4)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1310540] Re: Screen brightness not restored after turning screen off (by inactivity)

2014-04-21 Thread kolen
Seems that occurs every 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/1310540

Title:
  Screen brightness not restored after turning screen off (by
  inactivity)

Status in “unity” package in Ubuntu:
  New

Bug description:
  Encountered that after screen is turned off by inactivity, then after
  restoring, its brightness was very dim. After looking into Brightness
  and lock settings panel, discovered that Brightness was set to 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 21 13:51:45 2014
  DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (180 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 4403RP2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
  dmi.bios.date: 12/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET60WW (1.36 )
  dmi.board.name: 4403RP2
  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:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4403RP2
  dmi.product.version: ThinkPad L412
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 12:01:33 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

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


[Dx-packages] [Bug 1310540] Re: Screen brightness not restored after turning screen off (by inactivity)

2014-04-21 Thread kolen
** Description changed:

  Encountered that after screen is turned off by inactivity, then after
  restoring, its brightness was very dim. After looking into Brightness
  and lock settings panel, discovered that Brightness was set to 0.
+ 
+ Seems that related to Dim screen to save power functionality.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 21 13:51:45 2014
  DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:21bb]
+  Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (180 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 4403RP2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
  dmi.bios.date: 12/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET60WW (1.36 )
  dmi.board.name: 4403RP2
  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:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4403RP2
  dmi.product.version: ThinkPad L412
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 12:01:33 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

Title:
  Screen brightness not restored after turning screen off (by
  inactivity)

Status in “unity” package in Ubuntu:
  New

Bug description:
  Encountered that after screen is turned off by inactivity, then after
  restoring, its brightness was very dim. After looking into Brightness
  and lock settings panel, discovered that Brightness was set to 0.

  Seems that related to Dim screen to save power functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 21 13:51:45 2014
  DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (180 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 4403RP2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet 

[Dx-packages] [Bug 1310540] Re: Screen brightness not restored after turning screen off (by inactivity)

2014-04-21 Thread kolen
** Bug watch added: GNOME Bug Tracker #665055
   https://bugzilla.gnome.org/show_bug.cgi?id=665055

** Also affects: gnome-power via
   https://bugzilla.gnome.org/show_bug.cgi?id=665055
   Importance: Unknown
   Status: Unknown

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

Title:
  Screen brightness not restored after turning screen off (by
  inactivity)

Status in Gnome Powermanager:
  Unknown
Status in “unity” package in Ubuntu:
  New

Bug description:
  Encountered that after screen is turned off by inactivity, then after
  restoring, its brightness was very dim. After looking into Brightness
  and lock settings panel, discovered that Brightness was set to 0.

  Seems that related to Dim screen to save power functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 21 13:51:45 2014
  DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (180 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 4403RP2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
  dmi.bios.date: 12/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET60WW (1.36 )
  dmi.board.name: 4403RP2
  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:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4403RP2
  dmi.product.version: ThinkPad L412
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 12:01:33 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1310540/+subscriptions

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


[Dx-packages] [Bug 1304026] Re: When apps are started some have the close button and such under the upper bar

2014-04-21 Thread Stephen M. Webb
*** This bug is a duplicate of bug 1303462 ***
https://bugs.launchpad.net/bugs/1303462

** This bug has been marked a duplicate of bug 1303462
   [Regression] Window titlebars placed behind panel

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

Title:
  When apps are started some have the close button and such under the
  upper bar

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  The window from an opened app, for example virt-manager , the close and 
minimize button are under the upper bar in the screen.
  To reach it, I can use the alt key to drag the window down, but for a lot of 
new users this might be difficult, not knowing this.
  I noticed this with other apps to. 
  Seems to be some windowing issue thus I reported it against unity.
  I have this on multiple systems with various video cards.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140404-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Apr  7 22:40:19 2014
  InstallationDate: Installed on 2014-04-06 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140303)
  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/1304026/+subscriptions

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


[Dx-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel

2014-04-21 Thread Stephen M. Webb
** Changed in: unity
Milestone: None = 7.2.1

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

Title:
  [Regression] Window titlebars placed behind panel

Status in Compiz:
  Triaged
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Windows with a height of (Display Height - Panel Height) get placed at y=0 
(behind the top panel)
  which means window titlebars are not reachable without alt-moving the window.
  I assume this happens with windows that want to resize themselves if their 
height exceeds the display resolution.
  Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop 
application I'm working on.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr  6 21:45:41 2014
  InstallationDate: Installed on 2014-04-04 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1084451] Re: xmodmap modifications get reset once and a while

2014-04-21 Thread Vulpes
I am on 14.04, this happens to me every time I switch input between
English and Korean (Hangul).

This happens no matter which keyboard layout I use for English input.
I've tried English(US), Korean, and Korean (101/104 Key Compatible) from
the Text Entry Settings and in all scenarios, xmodmap setting was reset
when I switched to and from Korean (Hangul)

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

Title:
  xmodmap modifications get reset once and a while

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I change my keyboard layout using and .Xmodmap file. First of all, after 
upgrading to quantal,
  the changes were no longer applied when logging in with lightdm, so I have to 
manually run
  xmodmap ~/.Xmodmap in a termina.. This might be related to lightdm, but I 
suspect not, since
  also, once in a while being logged in for a long time, the keyboard layout 
changes are completely
  gone, and I have to rerun xmodmap ~/.Xmodmap again.

  I haven't yet found a reliable way of reproducing it, apart from that it 
usually happens a few
  times each day.

  I don't know whether this bug is related to unity, but if you give me some 
hints on how
  to find out where the bug is, I'd be happy to investigate.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,regex,mousepoll,resize,vpswitch,imgpng,place,resizeinfo,move,animation,grid,workarounds,wall,unitymtgrabhandles,expo,session,fade,ezoom,scale,unityshell]
  Date: Thu Nov 29 11:50:04 2012
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2012-09-18 (71 days ago)

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

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


[Dx-packages] [Bug 1310540] Re: Screen brightness not restored after turning screen off (by inactivity)

2014-04-21 Thread Bug Watch Updater
** Changed in: gnome-power
   Status: Unknown = New

** Changed in: gnome-power
   Importance: Unknown = 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/1310540

Title:
  Screen brightness not restored after turning screen off (by
  inactivity)

Status in Gnome Powermanager:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  Encountered that after screen is turned off by inactivity, then after
  restoring, its brightness was very dim. After looking into Brightness
  and lock settings panel, discovered that Brightness was set to 0.

  Seems that related to Dim screen to save power functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 21 13:51:45 2014
  DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (180 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 4403RP2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
  dmi.bios.date: 12/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET60WW (1.36 )
  dmi.board.name: 4403RP2
  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:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4403RP2
  dmi.product.version: ThinkPad L412
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 12:01:33 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1310540/+subscriptions

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


[Dx-packages] [Bug 1303325] Re: clicking on its launcher icon doesn't open it (occured after closing app before)

2014-04-21 Thread Christopher Townsend
Can anyone subscribed to this confirm that they have only one Launcher
that is not visible on the left most monitor?

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

Title:
  clicking on its launcher icon doesn't open it (occured after closing
  app before)

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  steps to reproduce:

  1. open any apps from launcher (gedit for example) by clicking gedit icon 
with left mouse button (LMB)
  2. close this apps  (gedit)
  3. try to open gedit again by clicking LMB - !!gedit doesn't open again!! 
(not shake, nothing to happens)

  NOTE: if i clicking RIGHT mouse button, I can open gedit from context
  menu open a new window

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-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-17ubuntu2)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.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: Sun Apr  6 15:54:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:83b5]
  InstallationDate: Installed on 2014-03-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  MachineType: System manufacturer Rampage Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic 
root=UUID=035868ff-323c-42a4-80bf-43c3eb7f719d ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Rampage Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd07/08/2008:svnSystemmanufacturer:pnRampageExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageExtreme:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: Rampage Extreme
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Apr  6 15:38:37 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Unifying Device. Wireless PID:101a MOUSE, id 8
   inputLogitech Unifying Device. Wireless PID:4003 KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Dx-packages] [Bug 1309701] Re: Can't reopen applications from launcher

2014-04-21 Thread Christopher Townsend
Can you please confirm that you have only one Launcher that is *not*
visible on the left most monitor?

Thanks!

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

Title:
  Can't reopen applications from launcher

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  To recreate this bug, all I need to do is open an application from the
  launcher. I then close it. Left clicking on the application does not
  work. I have even confirmed multiple times that the program was
  closed. The only way I can reopen the application is with the middle
  mouse button. I am using Ubuntu 14.04, upgraded from a fresh install
  of 13.10. I also just recently came across a post by another user
  having the same problem:
  http://askubuntu.com/questions/449719/ubuntu-14-04-unity-launcher-
  problem-after-1st-launch

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr 18 13:58:30 2014
  InstallationDate: Installed on 2014-03-12 (37 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago)

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

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


[Dx-packages] [Bug 1309613] Re: Ubuntu 14.04 - Applications not visible after clicking on “move to another workspace” or “move to workspace right”

2014-04-21 Thread Christopher Townsend
Hi,

I believe you are using CCSM-General Options-Desktop Size-Number of
Desktops to set the number of workspaces.  This option is broken when
setting it greater than 1 and the next update should have this removed.
Set Number of Desktops to 1 and set the Horizontal/Vertical Virtual Size
to your desired configuration.

Please let me know if this fixes it for you.

Thanks!

** 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/1309613

Title:
  Ubuntu 14.04 - Applications not visible after clicking on “move to
  another workspace” or “move to workspace right”

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  In Unity I have total 6 workspaces. If I open an application and click
  on move to another workspace or move to workspace right, the
  application disappears. However I can still see that the application
  is running in system monitor. I eventually had to kill and reopen the
  application.

  Also, I only see 2 workspaces after clicking Move to another
  workspace even though I have 6 workspaces.

  I lost all data on a file after clicking on Move to workspace right.

  I also asked this question in askubuntu:

  http://askubuntu.com/questions/449852/ubuntu-14-04-applications-not-
  visible-after-clicking-on-move-to-another-works

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

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


[Dx-packages] [Bug 1309701] Re: Can't reopen applications from launcher

2014-04-21 Thread Christopher Townsend
** Changed in: unity (Ubuntu)
   Status: Confirmed = 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/1309701

Title:
  Can't reopen applications from launcher

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  To recreate this bug, all I need to do is open an application from the
  launcher. I then close it. Left clicking on the application does not
  work. I have even confirmed multiple times that the program was
  closed. The only way I can reopen the application is with the middle
  mouse button. I am using Ubuntu 14.04, upgraded from a fresh install
  of 13.10. I also just recently came across a post by another user
  having the same problem:
  http://askubuntu.com/questions/449719/ubuntu-14-04-unity-launcher-
  problem-after-1st-launch

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr 18 13:58:30 2014
  InstallationDate: Installed on 2014-03-12 (37 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago)

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

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


[Dx-packages] [Bug 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.

2014-04-21 Thread Christopher Townsend
** Changed in: unity
   Status: Triaged = In Progress

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

Title:
  Apps locked to launcher only launch once per session on dual monitor
  system.

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

Bug description:
  In Trusty:

  On a dual monitor system with the launcher on the right hand screen,
  an application that has been locked to launcher, (including those
  there by default) can only be clicked on once per session to actually
  launch the application. After that it's unresponsive to clicks,
  although right-click actions work.

  Seems to affect all apps, including Files.

  To repeat, for any application not already on the launcher bar:

  Launch the application using the dash.

  Right-click on its launcher icon and select Lock to Launcher

  Quit the application.

  Click on its launcher icon. It should launch again.

  Quit it again.

  Click on its launcher icon again. It won't work this time. It looks
  like dragging would work, but its operation as a launcher will not.

  NB: I haven't installed any hacks eg: click-to-minimise. Seen this on
  two systems upgraded from saucy to trusty. (One with AMD graphics, one
  with Intel, so I doubt that's relevant either.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:10:56 2014
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

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


[Dx-packages] [Bug 1310145] [NEW] applications do not activate from the launcher after the first activation

2014-04-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Once Ubuntu 14.04 LTS Desktop session is activated the following is a
problem:

If an application icon is clicked on the Application Launcher, the
application is activated - as would be expected.

If the SAME application is closed, then opened a second time, from the
Applicaiton Launcher, the application DOES NOT RUN.

No applications work from the Application Launcher when activated more
than once during a session for Ubuntu 14.04 LTS...

Other info:
Release:  14.04

Don't know what package the application launcher is from...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: compiz-core 1:0.9.11+14.04.20140409-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Apr 19 20:12:19 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3a02]
   Subsystem: Lenovo Device [17aa:3a02]
InstallationDate: Installed on 2014-04-19 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Lenovo INVALID
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=424fe656-d099-4d0d-a258-6c5ec7de087d ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2008
dmi.bios.vendor: Lenovo
dmi.bios.version: 10CN38WW
dmi.board.asset.tag: Lenovo Assert TAG
dmi.board.name: INVALID
dmi.board.vendor: Lenovo
dmi.board.version: 10CN37WW
dmi.chassis.asset.tag: Lenovo Assert TAG
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: 10CN38WW
dmi.modalias: 
dmi:bvnLenovo:bvr10CN38WW:bd10/08/2008:svnLenovo:pnINVALID:pvrLenovoIdeaPadY530:rvnLenovo:rnINVALID:rvr10CN37WW:cvnLenovo:ct10:cvr10CN38WW:
dmi.product.name: INVALID
dmi.product.version: Lenovo IdeaPad Y530
dmi.sys.vendor: Lenovo
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Apr 19 18:52:08 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   33140 
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu
-- 
applications do not activate from the launcher after the first activation
https://bugs.launchpad.net/bugs/1310145
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

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


[Dx-packages] [Bug 1310145] Re: applications do not activate from the launcher after the first activation

2014-04-21 Thread Christopher Townsend
Do you have a multi-monitor setup with the Launcher *not* visible on the
left most monitor?

Thanks!

** Package changed: compiz (Ubuntu) = unity (Ubuntu)

** 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/1310145

Title:
  applications do not activate from the launcher after the first
  activation

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  Once Ubuntu 14.04 LTS Desktop session is activated the following is a
  problem:

  If an application icon is clicked on the Application Launcher, the
  application is activated - as would be expected.

  If the SAME application is closed, then opened a second time, from the
  Applicaiton Launcher, the application DOES NOT RUN.

  No applications work from the Application Launcher when activated more
  than once during a session for Ubuntu 14.04 LTS...

  Other info:
  Release:  14.04

  Don't know what package the application launcher is from...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140409-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:12:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3a02]
 Subsystem: Lenovo Device [17aa:3a02]
  InstallationDate: Installed on 2014-04-19 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Lenovo INVALID
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=424fe656-d099-4d0d-a258-6c5ec7de087d ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2008
  dmi.bios.vendor: Lenovo
  dmi.bios.version: 10CN38WW
  dmi.board.asset.tag: Lenovo Assert TAG
  dmi.board.name: INVALID
  dmi.board.vendor: Lenovo
  dmi.board.version: 10CN37WW
  dmi.chassis.asset.tag: Lenovo Assert TAG
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: 10CN38WW
  dmi.modalias: 
dmi:bvnLenovo:bvr10CN38WW:bd10/08/2008:svnLenovo:pnINVALID:pvrLenovoIdeaPadY530:rvnLenovo:rnINVALID:rvr10CN37WW:cvnLenovo:ct10:cvr10CN38WW:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo IdeaPad Y530
  dmi.sys.vendor: Lenovo
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Apr 19 18:52:08 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   33140 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

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

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


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

2014-04-21 Thread Adolfo Jayme
Seems to be bad interaction with focus/unfocus under Gtk+ 3.10.

** Also affects: overlay-scrollbar (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: overlay-scrollbar (Ubuntu)
   Importance: Undecided = Medium

** Changed in: overlay-scrollbar (Ubuntu)
   Status: New = Triaged

** Tags removed: grey overlay-scrollbar unity
** Tags added: ubuntu-desktop-trusty

** Changed in: overlay-scrollbar (Ubuntu)
 Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)

-- 
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 1310656] [NEW] Holding super key does not show shortcuts overlay.

2014-04-21 Thread Sudeepto Dutta
Public bug reported:

I have a freshly installed Ubuntu 14.04 x64 . Recently I noticed that
while holding Super key (Windows key by default)  the shortcuts overlay
does not appear anymore. The launcher along with the icon numbers appear
just fine but the shortcuts overlay is not visible anymore.

Now when I disable the workspace switcher from  System setttings  -
Appearance -  Behaviour Tab - Uncheck Enable Workspace , everything
works just fine .


I have a 1366 x 768 monitor .

I want shortcuts overlay to appear irrespective of whether workspace is
enabled or not.

I am attaching Image file when Workspace switcher is enabled (shortcut
overlay does not appear).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140416-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Apr 21 20:01:32 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
InstallationDate: Installed on 2014-04-20 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=8311719c-e1f9-43f6-9ae8-87056736ed26 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX3 R2.0
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.:bvr1106:bd11/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0: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.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Apr 21 19:31:38 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   19440 
 vendor GSM
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Attachment added: Screenshot from 2014-04-21 20:17:17.png
   
https://bugs.launchpad.net/bugs/1310656/+attachment/4091280/+files/Screenshot%20from%202014-04-21%2020%3A17%3A17.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/1310656

Title:
  Holding super key does not show shortcuts overlay.

Status in “unity” package in Ubuntu:
  New

Bug description:
  I have a freshly installed Ubuntu 14.04 x64 . Recently I noticed that
  while holding Super key (Windows key by default)  the shortcuts
  overlay does not appear anymore. The launcher along with the icon
  numbers appear just fine but the shortcuts overlay is not visible
  anymore.

  Now when I disable the workspace switcher from  System setttings  -
  Appearance -  Behaviour Tab - Uncheck Enable Workspace ,
  everything works just fine .

  
  I have a 1366 x 768 monitor .

  I want shortcuts overlay to appear irrespective of whether 

[Dx-packages] [Bug 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.

2014-04-21 Thread Launchpad Bug Tracker
** Branch linked: lp:~townsend/unity/fix-lp1291362

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

Title:
  Apps locked to launcher only launch once per session on dual monitor
  system.

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

Bug description:
  In Trusty:

  On a dual monitor system with the launcher on the right hand screen,
  an application that has been locked to launcher, (including those
  there by default) can only be clicked on once per session to actually
  launch the application. After that it's unresponsive to clicks,
  although right-click actions work.

  Seems to affect all apps, including Files.

  To repeat, for any application not already on the launcher bar:

  Launch the application using the dash.

  Right-click on its launcher icon and select Lock to Launcher

  Quit the application.

  Click on its launcher icon. It should launch again.

  Quit it again.

  Click on its launcher icon again. It won't work this time. It looks
  like dragging would work, but its operation as a launcher will not.

  NB: I haven't installed any hacks eg: click-to-minimise. Seen this on
  two systems upgraded from saucy to trusty. (One with AMD graphics, one
  with Intel, so I doubt that's relevant either.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:10:56 2014
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

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


[Dx-packages] [Bug 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken

2014-04-21 Thread Christopher Townsend
** Also affects: compiz (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: compiz (Ubuntu)
   Status: New = In Progress

** Changed in: compiz (Ubuntu)
   Importance: Undecided = High

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

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

Title:
  Launcher, Window management - Switching between spreads when dragging
  a file over the Launcher is broken

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  To reproduce:

  Open two Chrome windows and two Firefox windows.  Drag a .html file
  over the Chrome icon in the Launcher.  A spread of the two Chrome
  windows should appear.  Then continue the same drag, and drag the file
  over the Firefox icon in the Launcher.  Nothing happens, the Chrome
  spread is still displayed.

  Desired behaviour;

  After a spread appears as a result of the user dragging a file over a
  application icon in the Launcher, if the user then drags the file over
  a different application icon (where the application is also a valid
  drop receptacle for the file type) the spread should switch to the
  newly selected application.

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

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


[Dx-packages] [Bug 1310690] [NEW] Lock screen password field does not capture key press - password is disclosed in background application

2014-04-21 Thread Fabio Machado
*** This bug is a security vulnerability ***

Public security bug reported:

The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 
times already) that the password field doesn't capture the key presses 
sometimes. Key presses are not registered by the field and it looks like it is 
frozen (except by the cursor blinking). What I had to do when this happened was 
to wait until the tentative expires (screen goes blank) and then try again - 
then it worked.
However the application running in the foregroung (or background, if you 
consider the lockscreen is on top) received the key presses, i.e, my whole 
password - you can imagine the implications if it was a chat window.

I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated.

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

** 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/1310690

Title:
  Lock screen password field does not capture key press - password is
  disclosed in background application

Status in “unity” package in Ubuntu:
  New

Bug description:
  The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 
times already) that the password field doesn't capture the key presses 
sometimes. Key presses are not registered by the field and it looks like it is 
frozen (except by the cursor blinking). What I had to do when this happened was 
to wait until the tentative expires (screen goes blank) and then try again - 
then it worked.
  However the application running in the foregroung (or background, if you 
consider the lockscreen is on top) received the key presses, i.e, my whole 
password - you can imagine the implications if it was a chat window.

  I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated.

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

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


[Dx-packages] [Bug 1310690] Re: Lock screen password field does not capture key press - password is disclosed in background application

2014-04-21 Thread Andrea Azzarone
Do you remember how did you lock the screen when it happened?

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

Title:
  Lock screen password field does not capture key press - password is
  disclosed in background application

Status in “unity” package in Ubuntu:
  New

Bug description:
  The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 
times already) that the password field doesn't capture the key presses 
sometimes. Key presses are not registered by the field and it looks like it is 
frozen (except by the cursor blinking). What I had to do when this happened was 
to wait until the tentative expires (screen goes blank) and then try again - 
then it worked.
  However the application running in the foregroung (or background, if you 
consider the lockscreen is on top) received the key presses, i.e, my whole 
password - you can imagine the implications if it was a chat window.

  I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated.

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

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


[Dx-packages] [Bug 1310490] Re: indicator-messages is hidden on 14.04 LTS

2014-04-21 Thread Lars Uebernickel
Hey, thanks for reporting this issue. The messaging menu hides itself
when no applications are using it. The output of

  gsettings get com.canonical.indicator.messages applications

shows a list of applications that have registered to appear in the menu.
Do Thunderbird and gmail-notifier appear in that list?

Also, is indicator-messages-service running?

** Changed in: indicator-messages (Ubuntu)
   Status: New = Incomplete

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

Title:
  indicator-messages is hidden on 14.04 LTS

Status in “indicator-messages” package in Ubuntu:
  Incomplete

Bug description:
  I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've
  noticed, that the mail icon is hidden. I've reinstalled the package:
  `sudo apt-get install --reinstall indicator-messages` - it was
  successful, but didn't change anything. Tried to install thunderbird,
  but nothing changed.

  If I want to run it manually ($ indicator-messages or with Alt+F2) the
  command not found...

  I know, that it is hidden, because I'm using GMail Notifier, which
  displays itself, and it works.

  Package info:
  indicator-messages:
Installed: 13.10.1+14.04.20140410-0ubuntu1
Candidate: 13.10.1+14.04.20140410-0ubuntu1
Version table:
   *** 13.10.1+14.04.20140410-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Please fix this issue!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1310490/+subscriptions

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


[Dx-packages] [Bug 1309851] [NEW] Cursor doesn't load when switching accounts

2014-04-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Recently upgraded from 12.04 to 14.04.  When logged into one account and
switch to guest account, my mouse cursor does not display.  If I log out
of my first account before logging into the guest account, the cursor
does display

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Sat Apr 19 00:52:11 2014
InstallationDate: Installed on 2014-01-25 (83 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: Error creating textual authentication agent: Error opening current 
controlling terminal for the process (`/dev/tty'): No such device or address
VarLogDistupgradeApttermlog: Error: [Errno 13] Permission denied: 
'/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade trusty
-- 
Cursor doesn't load when switching accounts
https://bugs.launchpad.net/bugs/1309851
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

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


[Dx-packages] [Bug 1309701] Re: Can't reopen applications from launcher

2014-04-21 Thread Paul McSpadden
That is correct I have 2 monitors. Only one has the launcher. The
monitor that has the launcher is the right monitor.

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

Title:
  Can't reopen applications from launcher

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  To recreate this bug, all I need to do is open an application from the
  launcher. I then close it. Left clicking on the application does not
  work. I have even confirmed multiple times that the program was
  closed. The only way I can reopen the application is with the middle
  mouse button. I am using Ubuntu 14.04, upgraded from a fresh install
  of 13.10. I also just recently came across a post by another user
  having the same problem:
  http://askubuntu.com/questions/449719/ubuntu-14-04-unity-launcher-
  problem-after-1st-launch

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr 18 13:58:30 2014
  InstallationDate: Installed on 2014-03-12 (37 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago)

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

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


[Dx-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

2014-04-21 Thread peleng
this bug affects fresh Ubuntu 14.04 installation on Dell Inspiron M5110
laptop after enabling multiple workspaces via System Settings 
Appearance

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up
  the help overlay. Holding Super worked before upgrading. Tapping the
  Super key still brings up the HUD, and holding it down still brings up
  the Launcher and after a second or so shows the numbers on the
  applications. In Compiz Config Manager, under Ubuntu Unity Plugin -
  Launcher, the Key to show the Dash, Launcher and Help Overlay is set
  to Super. Under Ubuntu Unity Plugin - General, Enable Shortcut Hints
  Overlay is checked.

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

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


[Dx-packages] [Bug 1310490] Re: indicator-messages is hidden on 14.04 LTS

2014-04-21 Thread Bortnyák Roland
$ gsettings get com.canonical.indicator.messages applications
@as []

It's empty. But the GMail Notifier notifies me on new e-mails. How can I
add it? (This issue is reproduced more of my machines...)

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

Title:
  indicator-messages is hidden on 14.04 LTS

Status in “indicator-messages” package in Ubuntu:
  Incomplete

Bug description:
  I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've
  noticed, that the mail icon is hidden. I've reinstalled the package:
  `sudo apt-get install --reinstall indicator-messages` - it was
  successful, but didn't change anything. Tried to install thunderbird,
  but nothing changed.

  If I want to run it manually ($ indicator-messages or with Alt+F2) the
  command not found...

  I know, that it is hidden, because I'm using GMail Notifier, which
  displays itself, and it works.

  Package info:
  indicator-messages:
Installed: 13.10.1+14.04.20140410-0ubuntu1
Candidate: 13.10.1+14.04.20140410-0ubuntu1
Version table:
   *** 13.10.1+14.04.20140410-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Please fix this issue!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1310490/+subscriptions

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


[Dx-packages] [Bug 1310690] Re: Lock screen password field does not capture key press - password is disclosed in background application

2014-04-21 Thread Seth Arnold
This may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292217

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

Title:
  Lock screen password field does not capture key press - password is
  disclosed in background application

Status in “unity” package in Ubuntu:
  New

Bug description:
  The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 
times already) that the password field doesn't capture the key presses 
sometimes. Key presses are not registered by the field and it looks like it is 
frozen (except by the cursor blinking). What I had to do when this happened was 
to wait until the tentative expires (screen goes blank) and then try again - 
then it worked.
  However the application running in the foregroung (or background, if you 
consider the lockscreen is on top) received the key presses, i.e, my whole 
password - you can imagine the implications if it was a chat window.

  I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated.

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

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


[Dx-packages] [Bug 1310490] Re: indicator-messages is hidden on 14.04 LTS

2014-04-21 Thread Lars Uebernickel
The gmail-notifier doesn't register to use the messaging menu, then.
Reassigning this bug to that project.

** Package changed: indicator-messages (Ubuntu) = gm-notify (Ubuntu)

** Changed in: gm-notify (Ubuntu)
   Status: Incomplete = New

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

Title:
  indicator-messages is hidden on 14.04 LTS

Status in “gm-notify” package in Ubuntu:
  New

Bug description:
  I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've
  noticed, that the mail icon is hidden. I've reinstalled the package:
  `sudo apt-get install --reinstall indicator-messages` - it was
  successful, but didn't change anything. Tried to install thunderbird,
  but nothing changed.

  If I want to run it manually ($ indicator-messages or with Alt+F2) the
  command not found...

  I know, that it is hidden, because I'm using GMail Notifier, which
  displays itself, and it works.

  Package info:
  indicator-messages:
Installed: 13.10.1+14.04.20140410-0ubuntu1
Candidate: 13.10.1+14.04.20140410-0ubuntu1
Version table:
   *** 13.10.1+14.04.20140410-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Please fix this issue!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gm-notify/+bug/1310490/+subscriptions

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


[Dx-packages] [Bug 1310690] Re: Lock screen password field does not capture key press - password is disclosed in background application

2014-04-21 Thread Andrea Azzarone
Can you run 
apt-cache policy unity

and
apt-cache policy gnome-screensaver

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

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

** Changed in: unity
   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/1310690

Title:
  Lock screen password field does not capture key press - password is
  disclosed in background application

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

Bug description:
  The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 
times already) that the password field doesn't capture the key presses 
sometimes. Key presses are not registered by the field and it looks like it is 
frozen (except by the cursor blinking). What I had to do when this happened was 
to wait until the tentative expires (screen goes blank) and then try again - 
then it worked.
  However the application running in the foregroung (or background, if you 
consider the lockscreen is on top) received the key presses, i.e, my whole 
password - you can imagine the implications if it was a chat window.

  I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated.

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

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


[Dx-packages] [Bug 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.

2014-04-21 Thread MaXiMuS
Same bug affects me, running 14.04 with a tripple monitor setup,
RadeonHD 5830 and default driver that is installed (not running the
proprietary AMD driver yet but will give it a try)

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

Title:
  Apps locked to launcher only launch once per session on dual monitor
  system.

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

Bug description:
  In Trusty:

  On a dual monitor system with the launcher on the right hand screen,
  an application that has been locked to launcher, (including those
  there by default) can only be clicked on once per session to actually
  launch the application. After that it's unresponsive to clicks,
  although right-click actions work.

  Seems to affect all apps, including Files.

  To repeat, for any application not already on the launcher bar:

  Launch the application using the dash.

  Right-click on its launcher icon and select Lock to Launcher

  Quit the application.

  Click on its launcher icon. It should launch again.

  Quit it again.

  Click on its launcher icon again. It won't work this time. It looks
  like dragging would work, but its operation as a launcher will not.

  NB: I haven't installed any hacks eg: click-to-minimise. Seen this on
  two systems upgraded from saucy to trusty. (One with AMD graphics, one
  with Intel, so I doubt that's relevant either.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:10:56 2014
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

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


[Dx-packages] [Bug 1303325] Re: clicking on its launcher icon doesn't open it (occured after closing app before)

2014-04-21 Thread Alexander Borodetsky
** Attachment added: I confirm it. See screenshot ()
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303325/+attachment/4091740/+files/Screenshot%20from%202014-04-22%2001%3A12%3A29_.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/1303325

Title:
  clicking on its launcher icon doesn't open it (occured after closing
  app before)

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  steps to reproduce:

  1. open any apps from launcher (gedit for example) by clicking gedit icon 
with left mouse button (LMB)
  2. close this apps  (gedit)
  3. try to open gedit again by clicking LMB - !!gedit doesn't open again!! 
(not shake, nothing to happens)

  NOTE: if i clicking RIGHT mouse button, I can open gedit from context
  menu open a new window

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-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-17ubuntu2)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.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: Sun Apr  6 15:54:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:83b5]
  InstallationDate: Installed on 2014-03-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  MachineType: System manufacturer Rampage Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic 
root=UUID=035868ff-323c-42a4-80bf-43c3eb7f719d ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Rampage Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd07/08/2008:svnSystemmanufacturer:pnRampageExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageExtreme:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: Rampage Extreme
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Apr  6 15:38:37 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Unifying Device. Wireless PID:101a MOUSE, id 8
   inputLogitech Unifying Device. Wireless PID:4003 KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Dx-packages] [Bug 1303325] Re: clicking on its launcher icon doesn't open it (occured after closing app before)

2014-04-21 Thread Alexander Borodetsky
** Attachment removed: I confirm it. See screenshot ()
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303325/+attachment/4091740/+files/Screenshot%20from%202014-04-22%2001%3A12%3A29_.png

** Attachment added: How it looks like
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303325/+attachment/4091752/+files/Screenshot%20from%202014-04-22%2001%3A12%3A29_.jpg

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

Title:
  clicking on its launcher icon doesn't open it (occured after closing
  app before)

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  steps to reproduce:

  1. open any apps from launcher (gedit for example) by clicking gedit icon 
with left mouse button (LMB)
  2. close this apps  (gedit)
  3. try to open gedit again by clicking LMB - !!gedit doesn't open again!! 
(not shake, nothing to happens)

  NOTE: if i clicking RIGHT mouse button, I can open gedit from context
  menu open a new window

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-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-17ubuntu2)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.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: Sun Apr  6 15:54:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:83b5]
  InstallationDate: Installed on 2014-03-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  MachineType: System manufacturer Rampage Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic 
root=UUID=035868ff-323c-42a4-80bf-43c3eb7f719d ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Rampage Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd07/08/2008:svnSystemmanufacturer:pnRampageExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageExtreme:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: Rampage Extreme
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Apr  6 15:38:37 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Unifying Device. Wireless PID:101a MOUSE, id 8
   inputLogitech Unifying Device. Wireless PID:4003 KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Dx-packages] [Bug 1310838] [NEW] Power/battery indicator icon doesn't match the percentage value

2014-04-21 Thread Fikrul Arif
Public bug reported:

I attach the screenshot that shows 73% but the icon used to show the
battery is full. It was the same (i.e. the icon indicates full) when the
percentage was about 66%.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 22 05:47:24 2014
InstallationDate: Installed on 2012-11-04 (533 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
SourcePackage: indicator-power
UpgradeStatus: Upgraded to trusty on 2014-04-21 (0 days ago)

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: Screenshot
   
https://bugs.launchpad.net/bugs/1310838/+attachment/4091809/+files/indicator.png

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

Title:
  Power/battery indicator icon doesn't match the percentage value

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

Bug description:
  I attach the screenshot that shows 73% but the icon used to show the
  battery is full. It was the same (i.e. the icon indicates full) when
  the percentage was about 66%.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 22 05:47:24 2014
  InstallationDate: Installed on 2012-11-04 (533 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1310838/+subscriptions

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


[Dx-packages] [Bug 1310837] Re: compiz crashed with SIGSEGV

2014-04-21 Thread Apport retracing service
*** This bug is a duplicate of bug 1289798 ***
https://bugs.launchpad.net/bugs/1289798

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1289798, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1310837/+attachment/4091801/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1310837/+attachment/4091803/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1310837/+attachment/4091804/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1310837/+attachment/4091805/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1310837/+attachment/4091806/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1310837/+attachment/4091807/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1310837/+attachment/4091808/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1289798
   compiz crashed with SIGSEGV in gray_find_cell()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV

Status in “unity” package in Ubuntu:
  New

Bug description:
  Using Ubuntu 14.04 LTS 64bit.  
  Unity version: unity 7.2.0+14.04.20140416-0ubuntu1

  After booting into ubuntu tried to open terminal several times with
  ctrl+alt+t, nothing happened.  So went into dash to search for
  terminal but froze as I started typing, eventually the error message
  appeared with Ubuntu 14.04 experienced internal error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Apr 21 22:09:18 2014
  ExecutablePath: /usr/bin/compiz
  ExecutableTimestamp: 1397083158
  InstallationDate: Installed on 2013-05-21 (335 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  ProcCmdline: compiz
  ProcCwd: /home/laurenceubuntu
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8f1c0b33ce:mov%rcx,(%rsi)
   PC (0x7f8f1c0b33ce) ok
   source %rcx ok
   destination (%rsi) (0x0da0) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Dx-packages] [Bug 1310232] [NEW] Unauthorized user can view a list of processes

2014-04-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On lightdm screen click on battery indicator in top right corner. Select
the first menu item. gnome-power-statistic window should be opened.
Select processor menu item in left side.

Unathorized user should not view process list.
OS version: Ubuntu 12.04

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm 1.2.3-0ubuntu2.4
ProcVersionSignature: Ubuntu 3.8.0-38.56~precise1-generic 3.8.13.19
Uname: Linux 3.8.0-38-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Sun Apr 20 13:21:17 2014
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise
-- 
Unauthorized user can view a list of processes
https://bugs.launchpad.net/bugs/1310232
You received this bug notification because you are a member of DX Packages, 
which is subscribed to indicator-power in Ubuntu.

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


[Dx-packages] [Bug 1071634] Re: In datetime indicator and control-center panel, it could be easier to distinguish between locations that share the same name

2014-04-21 Thread Robert Ancell
** No longer affects: unity-control-center

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

** Changed in: unity-control-center (Ubuntu)
 Assignee: (unassigned) = Matthew Paul Thomas (mpt)

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = Low

** Changed in: unity-control-center (Ubuntu)
   Status: New = Confirmed

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

Title:
  In datetime indicator and control-center panel, it could be easier to
  distinguish between locations that share the same name

Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “unity-control-center” package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using
  $ lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2) The version of the package you are using
  $ apt-cache policy indicator-datetime
  indicator-datetime:
Установлен: 0.3.94-0ubuntu2
Кандидат:   0.3.94-0ubuntu2
Таблица версий:
   *** 0.3.94-0ubuntu2 0
  500 http://mirror.yandex.ru/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  4) What happened instead
  Name of city/town, country in locations for cities/towns which have 
duplicate names in different countries.
  It's impossible to understand which country the city/town is in locations 
drop down menu in notifications area and in the settings of showing locations 
in time/date settings (when locations is already selected, the only way is: 
remove all current locations for duplicate cities/towns, reassign location, but 
you still can't understand which time is showing in drop down menu of datetime 
indicator in case of cities/towns with duplicate names but in different 
counties).

  3) What you expected to happen: one of these:
   a) auto detect cities/towns, which has duplicates in different countries, 
and always showing country for them everywhere.
   b) manual option to show counties for all locations everywhere.
   c) manual option to show country for user selected locations from all 
locations, which user selected (and always showing countries in settings of 
setup locations).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-datetime 0.3.94-0ubuntu2
  Uname: Linux 3.5.7-zen-proxym-3 i686
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: i386
  Date: Fri Oct 26 11:01:23 2012
  InstallationMedia: Ubuntu-Studio 10.10 Maverick Meerkat - Release i386 
(20101008)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to precise on 2012-10-23 (3 days ago)

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

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


[Dx-packages] [Bug 1310232] Re: Unauthorized user can view a list of processes

2014-04-21 Thread Robert Ancell
This does not occur in 14.04

** Package changed: lightdm (Ubuntu) = indicator-power (Ubuntu)

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

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

Title:
  Unauthorized user can view a list of processes

Status in “indicator-power” package in Ubuntu:
  New
Status in “indicator-power” source package in Precise:
  New

Bug description:
  On lightdm screen click on battery indicator in top right corner.
  Select the first menu item. gnome-power-statistic window should be
  opened. Select processor menu item in left side.

  Unathorized user should not view process list.
  OS version: Ubuntu 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.4
  ProcVersionSignature: Ubuntu 3.8.0-38.56~precise1-generic 3.8.13.19
  Uname: Linux 3.8.0-38-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Apr 20 13:21:17 2014
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1310232/+subscriptions

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


[Dx-packages] [Bug 1309603] Re: Occasionally applications will not close using “X” on upper left of window.

2014-04-21 Thread Greg Gilfillan
** Description changed:

  I'm using Ubuntu 14.04 64bit on a Dell Latitude Laptop with an Intel
  Core i5 and 4G RAM installed.
  
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  
  unity:
    Installed: 7.2.0+14.04.20140416-0ubuntu1
    Candidate: 7.2.0+14.04.20140416-0ubuntu1
    Version table:
   *** 7.2.0+14.04.20140416-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  
  Seemingly randomly I will not be able to close an application using the
  X button of the upper left of the screen.  Sometimes it requires
  multiple clicks, but usually when this happens I have to right click the
  application icon on the quick launcher and select quit to close the
  window.  This has occurred on multiple applications firefox,
  nautilus, pithos, and software center are the most recent that I
  can remember for example, and I am assuming this is an issue with Unity
  on my system.
  
  I expect windows to always close within a short amount of time after
  clicking the X.
  
- Other possible Unity related oddities which are occurring on my system
- which may be related to this issue...
- 
- Control-Alt-T will sometimes not open a terminal, I might have to
- press the combination 4 or 5 times to get terminal to open.
- 
-  Pithos music player will not display icon in notification area on
- the top bar (although it behaves as if it did, i.e. will continue
- playing after closing the main window when show nofication area icon
- option is selected).  I have also submitted this particular bug to the
- Pithos development team.
- 
  These are all new issues that I did not have when using Ubuntu 12.04.
  I am being sufficiently patient with allowing plenty of time (several
  seconds) for applications to close before clicking anything else again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr 18 10:10:24 2014
  InstallationDate: Installed on 2014-04-13 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I'm using Ubuntu 14.04 64bit on a Dell Latitude Laptop with an Intel
  Core i5 and 4G RAM installed.
  
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  
  unity:
    Installed: 7.2.0+14.04.20140416-0ubuntu1
    Candidate: 7.2.0+14.04.20140416-0ubuntu1
    Version table:
   *** 7.2.0+14.04.20140416-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  
  Seemingly randomly I will not be able to close an application using the
- X button of the upper left of the screen.  Sometimes it requires
- multiple clicks, but usually when this happens I have to right click the
- application icon on the quick launcher and select quit to close the
- window.  This has occurred on multiple applications firefox,
- nautilus, pithos, and software center are the most recent that I
- can remember for example, and I am assuming this is an issue with Unity
- on my system.
+ X button of the upper left of the screen when Show the menus for a
+ window - in the window's title bar option is selected in the appearance
+ settings.  Sometimes it requires multiple clicks, but usually when this
+ happens I have to right click the application icon on the quick launcher
+ and select quit to close the window.  This has occurred on multiple
+ applications firefox, nautilus, pithos, and software center are
+ the most recent that I can remember for example, and I am assuming this
+ is an issue with Unity on my system.
  
- I expect windows to always close within a short amount of time after
- clicking the X.
- 
- These are all new issues that I did not have when using Ubuntu 12.04.
- I am being sufficiently patient with allowing plenty of time (several
- seconds) for applications to close before clicking anything else again.
+ I expect windows to always close within a short amount of time after clicking 
the X.
+ This is a new issue that I did not have using Ubuntu 12.04.   I am being 
sufficiently patient with allowing plenty of time (several seconds) for 
applications to close before clicking anything else again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 

[Dx-packages] [Bug 1310871] [NEW] Music lens does not play music through default music player.

2014-04-21 Thread JaSauders
Public bug reported:

Ubuntu 14.04 64 bit. Fresh install, all updates applied.

If I browse for music in the music lens and play them, they open in
Rhythmbox. System Settings  Details  Default Applications has the
default music player set to Clementine.

I should also note that the Rhythmbox dash plugin is DISABLED, while the
Clementine dash plugin is ENABLED, and even still it pipes the music
through Rhythmbox.

Thank you for your time!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-lens-music 6.9.0+13.10.20131011-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 21 21:46:45 2014
InstallationDate: Installed on 2014-04-04 (17 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330)
SourcePackage: unity-lens-music
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-lens-music (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  Music lens does not play music through default music player.

Status in “unity-lens-music” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04 64 bit. Fresh install, all updates applied.

  If I browse for music in the music lens and play them, they open in
  Rhythmbox. System Settings  Details  Default Applications has the
  default music player set to Clementine.

  I should also note that the Rhythmbox dash plugin is DISABLED, while
  the Clementine dash plugin is ENABLED, and even still it pipes the
  music through Rhythmbox.

  Thank you for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-lens-music 6.9.0+13.10.20131011-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 21 21:46:45 2014
  InstallationDate: Installed on 2014-04-04 (17 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330)
  SourcePackage: unity-lens-music
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1302291] Re: Unity 7 Dash garbles or omits letters in text

2014-04-21 Thread Stephen M. Webb
** Summary changed:

- The letter 'n' is garbled in search lens
+ Unity 7 Dash garbles or omits letters in text

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

Title:
  Unity 7 Dash garbles or omits letters in text

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When typing the letter n into the search lens it comes out garbled
  but everywhere else appears to be ok. Using the US_EN keyboard layout.

  See atttached

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

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


[Dx-packages] [Bug 1302291] Re: The letter 'n' is garbled in search lens

2014-04-21 Thread 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/1302291

Title:
  Unity 7 Dash garbles or omits letters in text

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When typing the letter n into the search lens it comes out garbled
  but everywhere else appears to be ok. Using the US_EN keyboard layout.

  See atttached

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

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


[Dx-packages] [Bug 1310237] Re: unity dash search does not show R-character

2014-04-21 Thread Stephen M. Webb
*** This bug is a duplicate of bug 1302291 ***
https://bugs.launchpad.net/bugs/1302291

** This bug has been marked a duplicate of bug 1302291
   The letter 'n' is garbled in search lens

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

Title:
  unity dash search does not show R-character

Status in “unity” package in Ubuntu:
  New

Bug description:
  After upgrading from 13.10 to 14.04 unity dash search does not show
  R-character anymore. See the attachment.

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

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


[Dx-packages] [Bug 1304073] Re: 14.04 Unity pips (white dots in bar) are now too small.

2014-04-21 Thread Stephen M. Webb
** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Importance: Undecided = Medium

** Changed in: unity
   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/1304073

Title:
  14.04 Unity pips (white dots in bar) are now too small.

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

Bug description:
  On all 14.04 installs I've tinkered with so far they've all exhibited
  this behavior. The pips (white dots) next to the icons in the Unity
  bar are too small. I never noticed this before, so I went back to a
  13.10 install to compare. The pips on 14.04 are so small that they,
  quite frankly, feel useless. They need to be of adequate size in an
  effort to be easily seen by the user, regardless of the actual icon
  size.

  Take note of the size of the white pips on the Unity launcher in the
  following screenshots.

  https://www.dropbox.com/sh/mc4k4yyjm5nbbzk/4t6SgqVN8H

  Here's an alternative 'direct download' link to the images just in
  case: http://skynetcore.org/shared/pips.tar.gz

  In an effort to present an accurate comparison I included the following 
screenshots
  (note that 48 px on both 13.10 and 14.04 seem identical, it's just the 
smaller sizes that down-scale too far)
  13.10 - 32 px
  14.04 - 32 px

  13.10 - 48 px
  14.04 - 48 px

  I also included a 5th screenshot of 26 px in 14.04 in case it helps
  further show what I'm referencing.

  While scaling the size of the pips makes sense to a certain degree,
  the current behavior scales them far too small. I feel as though they
  should have (at minimal) a 13.10 oriented type of scaling so they are
  more easily viewable, and therefore, more useful. If they could be
  adjusted in size, that would be a monumental bonus as well, but I have
  a feeling that might be a stretch for the given time frame. :)

  Thank you for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.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: Mon Apr  7 17:41:39 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:0009]
  InstallationDate: Installed on 2014-04-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330)
  MachineType: TOSHIBA PORTEGE Z835
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic 
root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.60
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z835
  dmi.product.version: PT224U-013021
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr  7 17:24:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

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

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : 

[Dx-packages] [Bug 1302602] Re: compiz crashed with SIGSEGV in _int_malloc()

2014-04-21 Thread Stephen M. Webb
** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in _int_malloc()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Searching an app on unitiy

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Apr  4 15:39:08 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-20 (15 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140319)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=es
   PATH=(custom, user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f32602a3b27 _int_malloc+103:  mov
0x10(%rcx),%rdi
   PC (0x7f32602a3b27) ok
   source 0x10(%rcx) (0xc71e1a00a4b283) not located in a known VMA region 
(needed readable region)!
   destination %rdi ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f321020, bytes=bytes@entry=2) at 
malloc.c:3351
   __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3219
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
   pango_log2vis_get_embedding_levels () from 
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
  Title: compiz crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video

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

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


[Dx-packages] [Bug 1303519] Re: compiz crashed with signal 7 in strlen()

2014-04-21 Thread Stephen M. Webb
** Information type changed from Private to Public

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

Title:
  compiz crashed with signal 7 in strlen()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Just recently updated to 14.04 from 13.10 and immediately after the
  installation and restarting of my computer I am unable to get to my
  desktop or any other function besides a blank screen of just my
  wallpaper. After I log in a pop up comes up saying that there has been
  a system error, and nothing loads up. I have since tried a few more
  restarts to see if it was a slight bug but I can't get past loading
  after the log in.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sun Apr  6 20:30:01 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-10-27 (161 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 7
  SourcePackage: unity
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   std::basic_stringchar, std::char_traitschar, std::allocatorchar 
::basic_string(char const*, std::allocatorchar const) () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/compiz/libunityshell.so
   call_init (l=optimized out, argc=argc@entry=1, 
argv=argv@entry=0x7fff9c0d2b98, env=env@entry=0xc2f880) at dl-init.c:78
   call_init (env=optimized out, argv=optimized out, argc=optimized out, 
l=optimized out) at dl-init.c:36
  Title: compiz crashed with signal 7 in strlen()
  UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Dx-packages] [Bug 1303063] Re: compiz crashed with SIGSEGV in _int_malloc()

2014-04-21 Thread Stephen M. Webb
** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in _int_malloc()

Status in “unity” package in Ubuntu:
  New

Bug description:
  I tried to drag an icon from dash to launcher

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  5 16:17:20 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-04-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7fe3c1b7ad71 _int_malloc+689:  mov
%r14,0x10(%r9)
   PC (0x7fe3c1b7ad71) ok
   source %r14 ok
   destination 0x10(%r9) (0x00ac) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   _int_malloc (av=0x7fe3c1eb9760 main_arena, bytes=60) at malloc.c:3489
   __GI___libc_malloc (bytes=60) at malloc.c:2891
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: compiz crashed with SIGSEGV in _int_malloc()
  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/unity/+bug/1303063/+subscriptions

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


[Dx-packages] [Bug 1302739] Re: compiz crashed with SIGSEGV in malloc_consolidate()

2014-04-21 Thread Stephen M. Webb
** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in malloc_consolidate()

Status in “unity” package in Ubuntu:
  New

Bug description:
  - Press on SUPER+A;
  - Started typing (Firefox in this case);
  - Unity froze, then crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-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 13:44:02 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-01-31 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140130)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f3c7b440702 malloc_consolidate+258:   mov
0x8(%rbx),%rax
   PC (0x7f3c7b440702) ok
   source 0x8(%rbx) (0x0024) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f3c2420) at malloc.c:4149
   _int_free (av=0x7f3c2420, p=optimized out, have_lock=0) at 
malloc.c:4057
   pixman_image_unref () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: compiz crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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


[Dx-packages] [Bug 1304118] Re: compiz crashed with SIGSEGV in assign_to_own()

2014-04-21 Thread Stephen M. Webb
*** This bug is a duplicate of bug 1302891 ***
https://bugs.launchpad.net/bugs/1302891

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1302891
   compiz crashed with SIGSEGV in assign_to_own()

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

Title:
  compiz crashed with SIGSEGV in assign_to_own()

Status in “unity” package in Ubuntu:
  New

Bug description:
  attempted to set wobbly windows in trusty.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140404-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 21:04:11 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-04-07 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis: Failure: invalid literal for int() with base 10: 'bad'
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? ()
   CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123
   unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::MultiActionList::InitiateAll(std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in CompAction::initiate()
  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/unity/+bug/1304118/+subscriptions

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


[Dx-packages] [Bug 1302891] Re: compiz crashed with SIGSEGV in assign_to_own()

2014-04-21 Thread 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/1302891

Title:
  compiz crashed with SIGSEGV in assign_to_own()

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  on ubuntu 14.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 20:16:26 2014
  Disassembly: = 0x0:  No se puede acceder a la memoria en la dirección 0x0
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-29 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   No se puede acceder a la memoria en la 
dirección 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
   source 0x0 (0x) not located in a known VMA region (needed readable 
region)!
  SegvReason:
   executing NULL VMA
   reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? ()
   CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123
   unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::MultiActionList::InitiateAll(std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in CompAction::initiate()
  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/unity/+bug/1302891/+subscriptions

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


[Dx-packages] [Bug 1302891] Re: compiz crashed with SIGSEGV in assign_to_own()

2014-04-21 Thread Stephen M. Webb
** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in assign_to_own()

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  on ubuntu 14.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 20:16:26 2014
  Disassembly: = 0x0:  No se puede acceder a la memoria en la dirección 0x0
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-29 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   No se puede acceder a la memoria en la 
dirección 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
   source 0x0 (0x) not located in a known VMA region (needed readable 
region)!
  SegvReason:
   executing NULL VMA
   reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? ()
   CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123
   unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::MultiActionList::InitiateAll(std::vectorCompOption, 
std::allocatorCompOption  const, int) const () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in CompAction::initiate()
  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/unity/+bug/1302891/+subscriptions

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


[Dx-packages] [Bug 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.

2014-04-21 Thread Alex
Updated to Trusty today, using Sandybridge, two monitors, same behaviour
as everyone else.

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

Title:
  Apps locked to launcher only launch once per session on dual monitor
  system.

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

Bug description:
  In Trusty:

  On a dual monitor system with the launcher on the right hand screen,
  an application that has been locked to launcher, (including those
  there by default) can only be clicked on once per session to actually
  launch the application. After that it's unresponsive to clicks,
  although right-click actions work.

  Seems to affect all apps, including Files.

  To repeat, for any application not already on the launcher bar:

  Launch the application using the dash.

  Right-click on its launcher icon and select Lock to Launcher

  Quit the application.

  Click on its launcher icon. It should launch again.

  Quit it again.

  Click on its launcher icon again. It won't work this time. It looks
  like dragging would work, but its operation as a launcher will not.

  NB: I haven't installed any hacks eg: click-to-minimise. Seen this on
  two systems upgraded from saucy to trusty. (One with AMD graphics, one
  with Intel, so I doubt that's relevant either.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:10:56 2014
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

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


[Dx-packages] [Bug 1310892] [NEW] indicator-sound crashes with uncaught error

2014-04-21 Thread KVV
Public bug reported:

After upgrade to 14.04, sound indicator used to work but then suddenly
disappeared. Logout/login/reboot and cleaning pulse directories doesn't
help. Sound indicator still works on the login screen though.

From .cache/upstart/indicator-sound.log:

(process:5579): GLib-GObject-CRITICAL **: g_object_unref: assertion
'G_IS_OBJECT (object)' failed

** (process:6534): CRITICAL **: volume_control_set_volume_internal:
assertion '_tmp1_ == PA_CONTEXT_READY' failed

** (process:6534): CRITICAL **: file /build/buildd/indicator-
sound-12.10.2+14.04.20140401/obj-x86_64-linux-gnu/src/volume-control.c:
line 1775: uncaught error:
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface (g
-dbus-error-quark, 16)

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  indicator-sound crashes with uncaught error

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

Bug description:
  After upgrade to 14.04, sound indicator used to work but then suddenly
  disappeared. Logout/login/reboot and cleaning pulse directories
  doesn't help. Sound indicator still works on the login screen though.

  From .cache/upstart/indicator-sound.log:

  (process:5579): GLib-GObject-CRITICAL **: g_object_unref: assertion
  'G_IS_OBJECT (object)' failed

  ** (process:6534): CRITICAL **: volume_control_set_volume_internal:
  assertion '_tmp1_ == PA_CONTEXT_READY' failed

  ** (process:6534): CRITICAL **: file /build/buildd/indicator-
  sound-12.10.2+14.04.20140401/obj-x86_64-linux-gnu/src/volume-
  control.c: line 1775: uncaught error:
  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface
  (g-dbus-error-quark, 16)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1310892/+subscriptions

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


[Dx-packages] [Bug 1233199] Re: lock to launcher / unlock from launcher not working...

2014-04-21 Thread Tom Close
Also works for me with 14.04, thanks!

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

Title:
  lock to launcher / unlock from launcher not working...

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

Bug description:
  When I either click on Lock to Launcher or Unlock from Launcher
  nothing happens.

  Ubuntu Version: 13.10
  Unity Version: 7

  Steps Taken:

  - reinstall unity / ubuntu-desktop
  - reset unity icons

  Other Info:

  The only way I'm able to change the icons currently is manually
  through gconf which often requires me to logout and login to take
  effect.

  -Peter

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg: [   48.845411] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
  Date: Mon Sep 30 07:16:12 2013
  DistUpgraded: 2013-09-02 00:45:43,852 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-20 (40 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Gigabyte Technology Co., Ltd. H61N-USB3
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic 
root=UUID=227939ab-2f00-4536-87e2-e2c048aac315 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-09-02 (28 days ago)
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: H61N-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd05/15/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61N-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61N-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H61N-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.2-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep 30 00:36:18 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputDell Dell USB Keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 723 
   vendor ACR
  xserver.version: 2:1.14.2.901-2ubuntu6

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

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


[Dx-packages] [Bug 1302663] Re: Unity's Scale UI function problematic on some devices.

2014-04-21 Thread Robert Ancell
** No longer affects: unity-control-center

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

Title:
  Unity's Scale UI function problematic on some devices.

Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-control-center” package in Ubuntu:
  New

Bug description:
  I'm running a fully updated (as of 4/1/2014) install of Ubuntu 14.04
  64 bit. This is on a Toshiba ultrabook with a mobile i5 processor and
  a 13.3 screen @ 1366x768.

  Earlier I was messing with the scale UI mode of the system settings 
  display field. I set my UI scale to be maxed out at 4. Once done,
  windows were so large it was impossible to see. I couldn't even see
  any options within system settings besides two. Scrolling of course
  helped a bit but it was largely cumbersome.

  Once I went into the displays section to turn UI scaling back down to
  1, I realized the function was far out of reach on my screen. I tried
  to hold down ALT and click to drag the window up beyond the top edge,
  but Unity crashed. In fact, every single time I hit the ALT key and
  clicked to drag, Unity crashed. Once Unity crashes 2 or 3 times, it
  doesn't come back without a hard power down and full startup.

  On the flip side, I plugged in an external monitor with a resolution
  of 1440x900. Once done, suddenly ALT worked and I had no crashes. I
  was able to drag the displays window up until I could see the UI
  scaling feature and turn it back down to 1.

  There's a few issues here that I feel need to be addressed, since
  there's little doubt that people will tinker with these functions.
  After all, these features are baked directly in to the interface as
  available parameters, but as notated above, settings (such as 4)
  render the system into a non-usable (and non-fixable without accessive
  tinkering) state.

  Is there a way higher UI scaling modes can be altered for easier
  scrolling or maneuvering of windows to reset it back if need be?
  Perhaps a work around could even be a reset to defaults button at
  the top bar? After all, with a UI scaling of 4, I could see the top of
  the window - just very little else. If I could have reset to default
  that would have alleviated any headaches.

  Thanks for all of your hard work! It's appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-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 Apr  4 11:10:27 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:0009]
  InstallationDate: Installed on 2014-04-01 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330)
  MachineType: TOSHIBA PORTEGE Z835
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic 
root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.60
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z835
  dmi.product.version: PT224U-013021
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri 

[Dx-packages] [Bug 1296111] Re: Bluetooth on/off switcher in System Settings is always OFF and has no effect on the bluetooth indicator

2014-04-21 Thread Robert Ancell
** No longer affects: unity-control-center

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

Title:
  Bluetooth on/off switcher in System Settings is always OFF and has no
  effect on the bluetooth indicator

Status in Bluetooth Menu:
  Confirmed
Status in “indicator-bluetooth” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  Bluetooth on/off switcher in System Settings is always OFF. When I
  turn it ON, leave bluetooth settings and then return back, I see that
  the switcher is OFF. Moreover, there is no effect on the bluetooth
  indicator, i.e. changing of the switcher on/off state does not modify
  the bluetooth indicator enabled/disabled state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140319-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:16:32 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   deja-dup   29.5-0ubuntu2
   gnome-control-center   1:3.6.3-0ubuntu54
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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


[Dx-packages] [Bug 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.

2014-04-21 Thread md_5
GTX 770 with proprietry 319, same issue.

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

Title:
  Apps locked to launcher only launch once per session on dual monitor
  system.

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

Bug description:
  In Trusty:

  On a dual monitor system with the launcher on the right hand screen,
  an application that has been locked to launcher, (including those
  there by default) can only be clicked on once per session to actually
  launch the application. After that it's unresponsive to clicks,
  although right-click actions work.

  Seems to affect all apps, including Files.

  To repeat, for any application not already on the launcher bar:

  Launch the application using the dash.

  Right-click on its launcher icon and select Lock to Launcher

  Quit the application.

  Click on its launcher icon. It should launch again.

  Quit it again.

  Click on its launcher icon again. It won't work this time. It looks
  like dragging would work, but its operation as a launcher will not.

  NB: I haven't installed any hacks eg: click-to-minimise. Seen this on
  two systems upgraded from saucy to trusty. (One with AMD graphics, one
  with Intel, so I doubt that's relevant either.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:10:56 2014
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

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