[Dx-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application

[Khurshid Alam]

In Progress? Wow! I would love to see this bug gets fixed in Trusty.

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

Title:
  Launcher, Window management - Dragging and holding a selection over an
  entry in the Launcher should spread out windows belonging to that
  application

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  In Progress
Status in One Hundred Papercuts:
  Fix Released
Status in Unity:
  In Progress
Status in “compiz” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  If the user drags and hold a file over a running application in the
  Launcher, all the windows of that application should be shown with the
  spread. The user should then be able to drag and drop the file in a
  windows in the spread to load the file into that specific window.

  Bug #727903 needs to be fixed at the same time.

  ---

  History:

  This bug had been previously fixed as "buggybutclosed" for Unity on 
2011-04-18, leaving this function with other bugs:
  https://bugs.launchpad.net/ayatana-design/+bug/727903
  https://bugs.launchpad.net/ayatana-design/+bug/727904
  https://bugs.launchpad.net/ayatana-design/+bug/727902
  https://bugs.launchpad.net/ayatana-design/+bug/764424
  https://bugs.launchpad.net/ayatana-design/+bug/832988

  On 2011-10-18, it was reopened for regression in Oneiric.

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

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

[Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy

[William Hua]

Hi matthieu, thanks, I managed to replicate it thanks to your
instructions. I'll see if I can figure out what's happening...

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

Title:
  Eclipse menus doesn't show up in Saucy

Status in Eclipse:
  Confirmed
Status in Unity GTK+ module:
  In Progress
Status in “oracle-jdk7-installer” package in Ubuntu:
  Triaged
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released

Bug description:
  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify "/usr/share/applications/eclipse.desktop" to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks

[Giovanni Mellini]

** Attachment added: "same problem with dash fullscreen"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308850/+attachment/4085919/+files/unity_problem_dash-fulscreen_locksreen.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/1308850

Title:
  Dash is visible on top of the lockscreen after screen monitor auto
  locks

Status in “unity” package in Ubuntu:
  New

Bug description:
  This is 100% reproducible on my side with an updated 14.04

  I have a laptop that after 3 minutes of inactivity shutdown the screen
  and lock-it.

  If I press the SUPER button to activate the dash and then I wait 3 minutes 
for auto screen locking the screen become black.
  After that when I move the mouse to go to lockscreen and unlock my session, I 
see the dash on top of the lockscreen.
  I can digit my password and unlock the laptop pressing enter but I cannot see 
the username, box, dots etc
  I think that the screenshot attached explain very whell what I'm writing.

  I think that this is a security problem because as you can see from my
  screenshot other people can see my personal data (file and folders)
  without authorization.

  Giovanni

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

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

[Dx-packages] [Bug 1308850] [NEW] Dash is visible on top of the lockscreen after screen monitor auto locks

[Giovanni Mellini]

Public bug reported:

This is 100% reproducible on my side with an updated 14.04

I have a laptop that after 3 minutes of inactivity shutdown the screen
and lock-it.

If I press the SUPER button to activate the dash and then I wait 3 minutes for 
auto screen locking the screen become black.
After that when I move the mouse to go to lockscreen and unlock my session, I 
see the dash on top of the lockscreen.
I can digit my password and unlock the laptop pressing enter but I cannot see 
the username, box, dots etc
I think that the screenshot attached explain very whell what I'm writing.

I think that this is a security problem because as you can see from my
screenshot other people can see my personal data (file and folders)
without authorization.

Giovanni

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

** Attachment added: "unity_problem_dash_locksreen.jpg"
   
https://bugs.launchpad.net/bugs/1308850/+attachment/4085917/+files/unity_problem_dash_locksreen.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/1308850

Title:
  Dash is visible on top of the lockscreen after screen monitor auto
  locks

Status in “unity” package in Ubuntu:
  New

Bug description:
  This is 100% reproducible on my side with an updated 14.04

  I have a laptop that after 3 minutes of inactivity shutdown the screen
  and lock-it.

  If I press the SUPER button to activate the dash and then I wait 3 minutes 
for auto screen locking the screen become black.
  After that when I move the mouse to go to lockscreen and unlock my session, I 
see the dash on top of the lockscreen.
  I can digit my password and unlock the laptop pressing enter but I cannot see 
the username, box, dots etc
  I think that the screenshot attached explain very whell what I'm writing.

  I think that this is a security problem because as you can see from my
  screenshot other people can see my personal data (file and folders)
  without authorization.

  Giovanni

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

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

[Dx-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

[Brandon Schaefer]

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

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

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

[Dx-packages] [Bug 1203355] Re: Session menu has both 'restart' & 'shutdown' options though both open the same dialog window

[Doug McMahon]

The restart option is not really gone in 14.04 though the current behavior is 
just as good.
On boot up or login there are  still both  restart & shutdown options
As soon as something is done,  (open a folder, switch workspaces, ect) the 
restart option disappears from the indicator

So in practice this is resolved.

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

Title:
  Session menu has both 'restart' & 'shutdown' options though both open
  the same dialog window

Status in One Hundred Papercuts:
  New
Status in The Session Menu:
  New
Status in “indicator-session” package in Ubuntu:
  Confirmed

Bug description:
  if it's now intended to have both that's cool but then the 'Restart' option 
should open with focus on "Restart', not "Shut Down"
  If not intended  you should remove the Restart option

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-session 12.10.5+13.10.20130717-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 20 14:24:58 2013
  InstallationDate: Installed on 2013-07-13 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130712)
  MarkForUpload: True
  SourcePackage: indicator-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/gnome-session/remove-compiz-requiriment

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

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

[Dx-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

[Treviño]

** Changed in: gnome-session (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-session (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/1308800

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

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

[Dx-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

[Treviño]

** Branch linked: lp:~3v1n0/unity/always-use-upstart

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  In Progress
Status in “gnome-session” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Treviño]

robru: the fact that unity doesn't reload properly after some crashes
it's related to to bug #1308800 (it seems upstart is not loading unity,
so gnome-session is not reliable at all for this).

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

[Treviño]

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

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  In Progress
Status in “gnome-session” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

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

[Dx-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

[Treviño]

** Changed in: unity
Milestone: 7.1.2 => 7.2.1

** Description changed:

- killall -9 compiz repeatedly doesn't make unity to reload all the times.
+ [Impact]
+ Killing compiz repeatedly doesn't make unity to reload all the times.
  
  This is caused by the fact that due to a regression unity7 is not loaded
  anymore by upstart (but by gnome-session) and thus it seems that
  sometimes it doesn't properly gets restarted.
  
  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.
+ 
+ [Test Case]
+ From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.
+ 
+ [Regression Potential]
+ The fix is about always making unity to be launched by upstart.
+ Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  Triaged
Status in “gnome-session” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.2.0+14.04.20140416-0ubuntu1

---
unity (7.2.0+14.04.20140416-0ubuntu1) trusty; urgency=low

  [ Andrea Azzarone ]
  * Do not allow to activate twice the same entry! (LP: #1308572)

  [ Marco Trevisan (Treviño) ]
  * UnityScreen: save a locked.stamp file when locking/unlocking, to
relock on startup This makes unity to relocks if it was locked
before crashing... (LP: #1308572)
 -- Ubuntu daily releaseWed, 16 Apr 2014 
22:41:19 +

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

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1308800] [NEW] Unity doesn't respawn all the times on crashes

[Treviño]

*** This bug is a security vulnerability ***

Public security bug reported:

killall -9 compiz repeatedly doesn't make unity to reload all the times.

This is caused by the fact that due to a regression unity7 is not loaded
anymore by upstart (but by gnome-session) and thus it seems that
sometimes it doesn't properly gets restarted.

This is also a security issue, because if the session was locked, and
unity is not reloaded the session won't be locked anymore.

** Affects: unity
 Importance: Critical
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Triaged

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity (Ubuntu)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

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

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

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

** Also affects: gnome-session (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  Triaged
Status in “gnome-session” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  killall -9 compiz repeatedly doesn't make unity to reload all the
  times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Treviño]

** Branch unlinked: lp:~3v1n0/unity/relocks-on-crashes

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1308750] Re: When unity crashes while in the lockscreen, it is by passed.

[Treviño]

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

** Changed in: unity (Ubuntu)
 Assignee: Andrea Azzarone (andyrock) => Marco Trevisan (Treviño) (3v1n0)

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

** Branch linked: lp:~3v1n0/unity/relocks-on-crashes

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

Title:
  When unity crashes while in the lockscreen, it is by passed.

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

Bug description:
  To reproduce:
  1) Open the lockscreen (Super+L)
  2) Hold Enter down
   wait .

  *Crash*

  Expected:
  *No crash*

  
  Stacktrace:
  http://paste.ubuntu.com/7263684/

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Robert Bruce Park]

So both the linked branches built in silo 8, and when I tested it, this
is what I found:

1. start unity

2. open terminal (Ctrl+alt+T)

3. type 'sleep 15 && killall -9 compiz'

4. lock screen

observe: screen locks, then unity crashes, then unity restarts locked.
so far so good.

5. issue the same command in the terminal again

6. lock the screen again

observe: screen locks, then unity crashes... and doesn't come back.

I'm told this is not a regression (eg it's known that unity does not
restart after the first crash) however this is significant because when
unity does not restart, that terminal just stays open right there, and
while it doesn't respond to keyboard input, it does respond to mouse
input, so it's possible to issue commands as the logged-in user by copy
& pasting (eg, select some text, right click -> copy, right click ->
paste).

So if I'm an attacker and I'm in a position to trigger a crash in
compiz, the whole "restarting locked" thing seems kind of weak, because
all I have to do is crash compiz... twice. Granted the unity-free UI is
quite limited, maybe there's a browser open and I can access the user's
email, or whatever. it's still an attack vector.

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1308791] Re: Black screen and only pointer at startup

[legaliz_me]

Syslog containg the segfaults I presume or the problem

** Description changed:

  After updating, I get a black screen on startup, my pointer and multiple
  "Report a problem" box. Checking apport.log it seems that unity-panel-
  service is crashing all the time.
  
- Anybody else experiencing this?
+ in syslog I got those segfaults :
  
- I'm on Ubuntu 14.04 64bits
+ [  335.294203] bamfdaemon[9462]: segfault at 7f89e0a5a254 ip 7f89a8ae1b7a 
sp 7fff9f25a108 error 4 in libc-2.19.so[7f89a8a49000+1bc000]
+ [  343.121528] unity-panel-ser[10433]: segfault at 7ff2dd493712 ip 
7ff20b065df2 sp 7fffb733b398 error 4 in 
libc-2.19.so[7ff20afcd000+1bc000]
+ 
+ which concord with apport.log so it might be the problem. Anybody else
+ experiencing this?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140414.1-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'
  Date: Thu Apr 17 01:07:00 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed
-  virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
+  virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed
+  virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:220d]
-  NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Lenovo Device [17aa:220d]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:220d]
+  NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Lenovo Device [17aa:220d]
  InstallationDate: Installed on 2014-03-26 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140320)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=d2b432e3-5760-4ca4-bd44-722994373b4d ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET64WW (2.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET64WW(2.14):bd11/12/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  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: Thu Apr 17 00:43:26 2014
  xserver.configfile: default
  xserver.errors:
-  Failed to load module "nvidia" (module does not exist, 0)
-  Failed to load module "nvidia" (module does not exist, 0)
-  NOUVEAU(G0): Error creating GPU channel: -19
-  NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
+  Failed to load module "nvidia" (module does not exist, 0)
+  Failed to load module "nvidia" (module does not exist, 0)
+  NOUVEAU(G0): Error creating GPU channel: -19
+  NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id4669 
-  vendor AUO
+  product id4669
+  vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308791/+attachment/4085817/+files/syslog

-- 
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.launchp

[Dx-packages] [Bug 1308791] [NEW] Black screen and only pointer at startup

[legaliz_me]

Public bug reported:

After updating, I get a black screen on startup, my pointer and multiple
"Report a problem" box. Checking apport.log it seems that unity-panel-
service is crashing all the time.

Anybody else experiencing this?

I'm on Ubuntu 14.04 64bits

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-services 7.2.0+14.04.20140414.1-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'
Date: Thu Apr 17 01:07:00 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:220d]
 NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:220d]
InstallationDate: Installed on 2014-03-26 (21 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140320)
MachineType: LENOVO 20AQCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=d2b432e3-5760-4ca4-bd44-722994373b4d ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/12/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET64WW (2.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET64WW(2.14):bd11/12/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
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: Thu Apr 17 00:43:26 2014
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): Error creating GPU channel: -19
 NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4669 
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  Black screen and only pointer at startup

Status in “unity” package in Ubuntu:
  New

Bug description:
  After updating, I get a black screen on startup, my pointer and
  multiple "Report a problem" box. Checking apport.log it seems that
  unity-panel-service is crashing all the time.

  Anybody else experiencing this?

  I'm on Ubuntu 14.04 64bits

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140414.1-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'
  Date: Thu Apr 17 01:07:00 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:220d]
   NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:220d]
  InstallationDate: Installed on 2014-03-26 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alph

[Dx-packages] [Bug 1210077] Re: Screen freeze and garbled after resume from suspend

[Bartosz Kosiorek]

The problem with suspend was solved in nvidia driver 331.67 (not this one 
331.38)
http://www.nvidia.com/Download/driverResults.aspx/75019/en-us
http://www.nvidia.com/object/unix.html

Here is chunk from release notes (331.67):
"Fixed a bug that could cause display corruption when resuming from suspend on 
systems using RandR 1.4 display offloading with recent Linux kernels."

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

Title:
  Screen freeze and garbled after resume from suspend

Status in HWE Next Project:
  Fix Released
Status in HWE Next trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” source package in Precise:
  Fix Committed

Bug description:
  [Impact]
  Users of nvidia graphics drivers can see graphics freezes or corruption after 
suspend/resume. Switching to a VT and back to X can potentially solve freeze 
issues, but corruption may result.

  [Test Case]
  Suspend/Resume many times with nvidia graphics and see if the problem happens.

  [Regression Potential]
  This is already in Trusty.

  --

  Perform regular suspend, either from system menu or close laptop lid,
  when system resuming from suspend, it will freeze.

  Switch to VT and back to X can solve freeze issue,
  but the screen are gabled and some character rendering are strange,
  however whole system can perform usual task.

  found affected graphics:
  gf108m
  gf117m
  gk107glm

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1210077/+subscriptions

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

[Dx-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open

[Andrea Azzarone]

** Attachment added: "Screenshot from 2014-04-17 00:00:09.png"
   
https://bugs.launchpad.net/unity/+bug/1281058/+attachment/4085764/+files/Screenshot%20from%202014-04-17%2000%3A00%3A09.png

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

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

Status in Ayatana Design:
  Fix Committed
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in Unity:
  In Progress
Status in “indicator-session” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-greeter” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

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

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

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

  --
  Desired resolution:

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

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/unity/relocks-on-crashes

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Launchpad Bug Tracker]

** Branch linked: lp:~andyrock/unity/fix-1308572

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Andrea Azzarone]

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

** Changed in: unity (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => Andrea Azzarone (andyrock)

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1268167] Re: No Autohide Launcher Bar Mouse Reveal on Secondary Monitor

[Mike Hanson]

I can confirm I am experiencing the same issue since I updated a couple
of weeks ago.

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

Title:
  No Autohide Launcher Bar Mouse Reveal on Secondary Monitor

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

Bug description:
  Since several updates performed on 1/8/2014, I am no longer able to
  reveal the launcher bar on my secondary (right) display with the mouse
  auto-reveal function.  Under display settings, both monitors are set
  to display a launcher bar.  Auto reveal works fine with the mouse on
  the primary (left) monitor.  The sticky edge works fine with the
  secondary (right) monitor, but no auto reveal for the launcher bar.  I
  can bring up the secondary (right) monitor launcher bar with the super
  key and alt+f1.

  So far I've reverted to Nvidia 3.04 drivers from 3.19 by purging from
  terminal and re-installing to no avail, and now back to 3.19 and it's
  still not working.

  Ubuntu 12.04.4 LTS
  32-bit
  AMD Athlon 64x2 Dual Core Processor 6000+
  Nvidia GT630 PCIe
  2GB RAM

  Any outputs you'd like from me, please let me know.

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

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

[Dx-packages] [Bug 1308296] Re: Allow for other calendar applications to register with Unity calendar indicator

[Jim Nelson]

I agree, these are all important considerations.  Perhaps the calendar
application can register itself as "indicator-datetime compatible" with
an X- entry in its .desktop file, indicating that it meets the above
criteria?  Something like this:

X-Unity-Indicator-Datetime-Date: calendar --date %D
X-Unity-Indicator-Datetime-Event: calendar --uid %U

Verbose, and I'm sure more concise key names could be devised, but
hopefully this would satisfy the requirements.  This still requires the
app writer to understand that they have to use EDS as their back-end.
(We have a similar issue with GNOME Shell's calendar, by the way.)

Yes, Yorba is looking at calendar integration.  We've begun a new
project toward that end: http://blogs.gnome.org/jnelson/2014/03/21
/introducing-california-a-new-gnome-3-calendar/  It uses EDS, so we're
good on that point, but we'd need to add command-line support for
opening to a date or an event (which we certainly would make happen if
it would mean Unity integration).

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

Title:
  Allow for other calendar applications to register with Unity calendar
  indicator

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

Bug description:
  It appears that Unity's calendar indicator (in the global menu, right-
  side of the screen) is hardwired to launch Evolution if an event is
  selected.  In System Settings, the only checkbox relevant to this is
  to show "Coming events from Evolution Calendar".

  It'd be nice if instead the Unity calendar indicator would launch the
  user's chosen default calendar application.

  I'm not suggesting that the calendar indicator quit using Evolution
  Data Server for calendar information, just which application is
  launched in response to a user event.

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

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

[Dx-packages] [Bug 1308750] Re: When unity crashes while in the lockscreen, it is by passed.

[Brandon Schaefer]

** Description changed:

  To reproduce:
  1) Open the lockscreen (Super+L)
  2) Hold Enter down
   wait .
  
  *Crash*
  
  Expected:
  *No crash*
+ 
+ 
+ Stacktrace:
+ http://paste.ubuntu.com/7263684/

** Changed in: unity
 Assignee: Brandon Schaefer (brandontschaefer) => Andrea Azzarone (andyrock)

** Changed in: unity (Ubuntu)
 Assignee: Brandon Schaefer (brandontschaefer) => Andrea Azzarone (andyrock)

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

Title:
  When unity crashes while in the lockscreen, it is by passed.

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

Bug description:
  To reproduce:
  1) Open the lockscreen (Super+L)
  2) Hold Enter down
   wait .

  *Crash*

  Expected:
  *No crash*

  
  Stacktrace:
  http://paste.ubuntu.com/7263684/

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

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

[Dx-packages] [Bug 1308750] [NEW] When unity crashes while in the lockscreen, it is by passed.

[Brandon Schaefer]

Public bug reported:

To reproduce:
1) Open the lockscreen (Super+L)
2) Hold Enter down
 wait .

*Crash*

Expected:
*No crash*


Stacktrace:
http://paste.ubuntu.com/7263684/

** Affects: unity
 Importance: Critical
 Assignee: Andrea Azzarone (andyrock)
 Status: In Progress

** Affects: unity (Ubuntu)
 Importance: Critical
 Assignee: Andrea Azzarone (andyrock)
 Status: In Progress

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

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

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

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

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

** Changed in: unity
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

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

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

Title:
  When unity crashes while in the lockscreen, it is by passed.

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

Bug description:
  To reproduce:
  1) Open the lockscreen (Super+L)
  2) Hold Enter down
   wait .

  *Crash*

  Expected:
  *No crash*

  
  Stacktrace:
  http://paste.ubuntu.com/7263684/

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Brandon Schaefer]

** Description changed:

  affects ubuntu
  
  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.
  
  --
  Marco Agnese
+ 
+ This bug is about the lockscreen being bypassed when unity
+ crashes/restarts, which is a critcal security issue. The crash will be
+ handled from bug 1308750

** Changed in: unity
 Assignee: Brandon Schaefer (brandontschaefer) => (unassigned)

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

** Changed in: unity (Ubuntu)
 Assignee: Brandon Schaefer (brandontschaefer) => 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/1308572

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

  This bug is about the lockscreen being bypassed when unity
  crashes/restarts, which is a critcal security issue. The crash will be
  handled from bug 1308750

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Brandon Schaefer]

** Changed in: unity
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

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

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

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Adam Conrad]

To be clear, the "always restart locked" half of the fix is the more
important bit.  The crash is embarrassing, but crashes will happen, and
we'll find others.  Having it restart unlocked is bordering on
unforgivable, and we should focus on fixing that first.

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Brandon Schaefer]

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

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

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

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

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

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

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

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

[Dx-packages] [Bug 1308572] Re: Ubuntu 14.04: security problem in the lock screen

[Iain Lane]

** Package changed: gnome-screensaver (Ubuntu) => unity (Ubuntu)

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

Title:
  Ubuntu 14.04: security problem in the lock screen

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

Bug description:
  affects ubuntu

  Hello,
  I am running Ubuntu 14.04 with all the packages updated.
  When the screen is locked with password, if I hold ENTER after some
  seconds the screen freezes and the lock screen crashes. After that I
  have the computer fully unlocked.

  --
  Marco Agnese

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

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

[Dx-packages] [Bug 1308572] [NEW] Ubuntu 14.04: security problem in the lock screen

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

affects ubuntu

Hello,
I am running Ubuntu 14.04 with all the packages updated.
When the screen is locked with password, if I hold ENTER after some
seconds the screen freezes and the lock screen crashes. After that I
have the computer fully unlocked.

--
Marco Agnese

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

-- 
Ubuntu 14.04: security problem in the lock screen
https://bugs.launchpad.net/bugs/1308572
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 1306472] Re: QToolBar Icons not loaded properly.

[Łukasz Zemczak]

** Changed in: appmenu-qt5
   Status: In Progress => Fix Released

** Changed in: appmenu-qt5 (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  QToolBar Icons not loaded properly.

Status in Application menu for Qt5:
  Fix Released
Status in “appmenu-qt5” package in Ubuntu:
  Fix Released

Bug description:
  When using a QToolBar with a basic Qt application, the icons can be
  populated from a theme. Either using QIcon::FromTheme(), or setting
  them in the associated action using the forms designer in Qt. (The
  name given for the icon is the freedesktop.org standard naming
  convention)

  Under appmenu-qt5 these icons do not appear to be being loaded
  correctly, resulting in a toolbar populated with just the action text.

  A minimal example illustrates the problem here:
  https://github.com/GilesBathgate/appmenu-bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1306472/+subscriptions

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

[Dx-packages] [Bug 1308296] Re: Allow for other calendar applications to register with Unity calendar indicator

[Charles Kerr]

Jim, this would be a great change if we have a clean way to do it. In
order to support more apps, indicator-datetime would need:

1. a way to launch the calendar to a specific date. If you double-click
on a date in the menu's calendar widget, $calendar-app is invoked with
command-line arguments to go to that date.

2. it to be compatible with an EDS backend; otherwise a user would open
the calendar app and not see the same events that are being shown in the
indicator

So maybe it makes more sense to consider "should we add support for app
X" rather than "should we allow all calendar apps." Do you have an X in
mind? (Is Geary still looking at calendar integration?)

On the other hand, just thinking out loud, maybe we could get indicator-
datetime the information it needs (eg, how to launch the calendar to a
specific day or to specific appointment) by adding something to the
apps' .desktop files?


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

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

Title:
  Allow for other calendar applications to register with Unity calendar
  indicator

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

Bug description:
  It appears that Unity's calendar indicator (in the global menu, right-
  side of the screen) is hardwired to launch Evolution if an event is
  selected.  In System Settings, the only checkbox relevant to this is
  to show "Coming events from Evolution Calendar".

  It'd be nice if instead the Unity calendar indicator would launch the
  user's chosen default calendar application.

  I'm not suggesting that the calendar indicator quit using Evolution
  Data Server for calendar information, just which application is
  launched in response to a user event.

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

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

[Dx-packages] [Bug 1308667] Re: indicator incoming can be taken out of action from the welcome screen

[Michał Sawicz]

** Also 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/1308667

Title:
  indicator incoming can be taken out of action from the welcome screen

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

Bug description:
  PREREQUISITE:
  2 phones

  STEPS:
  1. On the Ubuntu Touch Phone (Phone A) add the other phone (Phone B) as a 
contact
  2. Put Phone A to sleep
  3. Send an sms from Phone B to Phone A
  4. Notice that it very briefly displays SMS from +0123445678999 instead of 
the contact deatials.
  5. Hit the notification for the Incoming SMS
  6. Send another message now and you get no Blue icon, No notification, No Ping

  2 things might be happening here from what I can tell so far:
  1. The indicator dies and is in the midst of a restart when the second text 
comes through (no crash log for indicators just one of the only things I can 
think of)
  2. Something is broken in the interaction of the sms system (Possibly 
relating to "The QT bug")

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.85+14.04.20140415.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: armhf
  Date: Wed Apr 16 18:06:06 2014
  InstallationDate: Installed on 2014-04-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140416.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Norbert]

Ubuntu 14.04 with all updates for today - bug exists. Please fix it as
soon as possible.

-- 
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)

  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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[Norbert]

Ubuntu 14.04 with all updates for today - problems described in my comment 162 
and 164 exist. 
Please fix them as soon as possible.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+subscriptions

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

[Dx-packages] [Bug 1308615] Re: unity dash not finding apps

[Olli Ries]

there is always ctrl-alt-t to launch a terminal

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

Title:
  unity dash not finding apps

Status in “unity” package in Ubuntu:
  New

Bug description:
  I just install Trusty Desktop 64-bit from this daily ISO:

  0a884e0fe10f703493a4f8ff993be5fd *trusty-desktop-amd64.iso

  After booting into the new desktop, I'm not able to search and find
  any apps.

  In particular, I'm searching for "terminal", trying to launch a Gnome
  Terminal.  I'm offered The Terminator movie, for sale, but there's no
  terminal app returned.

  In a separate issue, I search for Gimp, and I receive some not-safe-
  for-work results.

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

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

[Dx-packages] [Bug 982434] Re: Opening the dash causes memory usage to climb dramatically, and never comes back down

[Sasa Stamenkovic]

Dash is PITA from the beginning. I really don't understand why, it is
really slow and consumes more memory comparing to Gnome.

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

Title:
  Opening the dash causes memory usage to climb dramatically, and never
  comes back down

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

Bug description:
  This may not be a bug at all, but thought I'd report it anyway.

  I am NOT reporting a memory leak - at least, I don't think so.  I am
  simply reporting this:

  When I start a desktop session, Compiz uses 85M of memory.  It stays
  there as long as I *do not open the Dash*.

  Once I open the Dash - simply pushing the Ubuntu button, and then
  closing immediately - the memory usage climbs to ~120-150.

  If I go through every page in the Dash and open every sub-page and see
  every icon available, the memory usage clibms to ~185M.

  Re-visiting the Dash, no matter how often, doesn't cause a further
  increase, but I'm not certain the Dash should use ~100M of RAM all by
  itself.  I'm not sure how much it *should* use, but it just seems a
  bit excessive.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,place,grid,snap,vpswitch,move,animation,gnomecompat,resize,mousepoll,session,imgpng,workarounds,wall,fade,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  Date: Sun Apr 15 11:26:09 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-03-26 (20 days ago)

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

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

[Dx-packages] [Bug 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)

[Norbert]

Ubuntu 14.04 with all updates for today - bug exists. Please fix it as
soon as possible.

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

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

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

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

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

  Please adapt icon sizes to large screen resolutions.

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

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

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

[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

[Norbert]

Ubuntu 14.04 with all updates for today - bu exists. Please fix it as
soon as possible.

-- 
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.

  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 1296431] Re: Phone doesn't alert user of critical power situations

[Charles Kerr]

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

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

Title:
  Phone doesn't alert user of critical power situations

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

Bug description:
  The phone doesn't currently alert the user when the battery is critical.
  This leads to power loss at times and the user doesn't know it's about to 
happen or had happened.
  e.g. during a call, or while listening to music. Also if the phone is sat on 
the desk unplugged from power connection.

  : "When the device’s
  battery/batteries are discharging and reach — or begin discharging and
  already have — 1 hour or less remaining (PC) or 20% or less remaining
  (phone/tablet), a notification bubble should appear ... When the
  device’s battery/batteries are discharging and reach — or begin
  discharging and already have — 30 minutes or less remaining (PC) or
  10% or less remaining (phone/tablet), an alert should appear..."

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

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

[Dx-packages] [Bug 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist

[Charles Kerr]

seb128, I think the question should be, what's a realistic timeline for
a fix in GIO?

I was sympathetic to workarounds for the sake of Trusty (and, for that
reason, did one in indicator-datetime). But now that the window for
landing things in Trusty has passed, workarounds lose a lot of their
raison d'être. I think we should look to actually fixing this in GIO.

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

Title:
  indicator-messages-service is waking up every 4 seconds adding
  inotifies on paths that don't exist

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

Bug description:
  I've observed that an "idle" indicator-messages-services is waking up
  every 4 seconds on a poll() and doing two inotify_add_watch() calls on
  paths that don't exist, which wastes power on devices such as phones.

  strace shows:

  clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
  poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
  clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
  inotify_add_watch(9, "/usr/local/share/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  inotify_add_watch(9, "/usr/share/ubuntu-touch/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
  poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
  clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
  inotify_add_watch(9, "/usr/local/share/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  inotify_add_watch(9, "/usr/share/ubuntu-touch/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0

  Can these redundant polling checks be reduced or removed?  Polling
  every 4 seconds is a little bit heavy handed IMHO.

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

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

[Dx-packages] [Bug 1300864] Re: Duplicate webapps launcher confuses bamf

[Alexandre Abreu]

** Changed in: libunity-webapps (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: libunity-webapps (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: libunity-webapps
   Status: Fix Committed => Fix Released

** Changed in: unity-webapps-qml
   Status: New => Fix Released

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

Title:
  Duplicate webapps launcher confuses bamf

Status in BAMF Application Matching Framework:
  New
Status in WebApps: libunity:
  Fix Released
Status in Unity WebApps QML component:
  Fix Released
Status in “libunity-webapps” package in Ubuntu:
  Fix Released
Status in “unity-webapps-qml” package in Ubuntu:
  Fix Released

Bug description:
  Even with the recent fixes to bamf, I can still be in cases where my
  webapp launcher does not associate correctly on the launcher.

  It happens for no particular webapp. However it stops occuring as soon
  as I suppress the duplicate desktop file we generate in
  ~/.local/share/applications.

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

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

Re: [Dx-packages] [Bug 1241101]

[auspex]

Fingers crossed, David!  Simply installing libgtk-3-0 worked for the
trivial case I described above, where I could always make it fail (I
haven't upgraded oxygen, yet, and probably won't if this works without
it—I'm still using the override
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc).


On Wed, Apr 16, 2014 at 8:49 AM, David Matějček
<1241...@bugs.launchpad.net>wrote:

> It seems it is fixed in newer GTK, but after my recent experiences I am
> not so optimistic. But after upgrade to 1.3.5 and also GTK 3.10 and
> restarting the system Eclipse still did not crash (10 hours yesterday, 5
> hours today, switching git branches on massive project, debugging,
> refactoring).
>
> Can you try it someone too? (package is big, you need fast connection)
> sudo add-apt-repository ppa:gnome3-team/gnome3
> sudo apt-get install libgtk-3-0
> Download 1.3.5: https://launchpad.net/ubuntu/+source/oxygen-gtk3
> Unpack and see instructions in the file INSTALL.
>
> I hope Eclipse will be stable on Kubuntu 14.04 without these experiments
> ...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1241101
>
> Title:
>   Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions
>


-- 
derek

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

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

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

[Dx-packages] [Bug 1307226] Re: LibreOffice Writer menubar dont work perfectly.

[Marcelo Odir]

After to change the Unity´s top bar to fully transparent, I realized
that the title bar of the Writer is apparent behind it.

Can anyone confirm this?

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

Title:
  LibreOffice Writer menubar dont work perfectly.

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Hello guys,

  I tripped over a bug this morning in the LibreOffice Writer.

  Every time when I open it the menubar dont work perfectly. The minimize 
button, close button and maximize button dont appear.
  When you enable to show de menus in the window's title bar, all de menus 
simply disappear.

  This problem happens only in LibreOffice Writer, other applications
  are running smoothly.

  Sorry my english.

  Bye.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 13 17:29:50 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-04-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140412)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 982434] Re: Opening the dash causes memory usage to climb dramatically, and never comes back down

[Anca Emanuel]

Just use it. Search something. Use the browser to read 1000+ emails, you
will get the swap of death
http://ubuntuforums.org/showthread.php?t=2028617

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

Title:
  Opening the dash causes memory usage to climb dramatically, and never
  comes back down

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

Bug description:
  This may not be a bug at all, but thought I'd report it anyway.

  I am NOT reporting a memory leak - at least, I don't think so.  I am
  simply reporting this:

  When I start a desktop session, Compiz uses 85M of memory.  It stays
  there as long as I *do not open the Dash*.

  Once I open the Dash - simply pushing the Ubuntu button, and then
  closing immediately - the memory usage climbs to ~120-150.

  If I go through every page in the Dash and open every sub-page and see
  every icon available, the memory usage clibms to ~185M.

  Re-visiting the Dash, no matter how often, doesn't cause a further
  increase, but I'm not certain the Dash should use ~100M of RAM all by
  itself.  I'm not sure how much it *should* use, but it just seems a
  bit excessive.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,place,grid,snap,vpswitch,move,animation,gnomecompat,resize,mousepoll,session,imgpng,workarounds,wall,fade,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  Date: Sun Apr 15 11:26:09 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-03-26 (20 days ago)

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

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

[Dx-packages] [Bug 1308615] Re: unity dash not finding apps

[Pawel Stolowski]

Is this a new installation of entire system, or was user home directory
preserved?

In case this is reproducible, it would be useful to capture standard
output & standard error of unity-lens-applications, e.g. kill existing
process and start a new one from a terminal like this:

/usr/bin/unity-scope-loader applications/applications.scope
applications/scopes.scope commands.scope

But I realise it can be challenging if terminal cannot be launched... To
overcome that, app lens could be started from a text console, after
setting DBUS_SESSION_BUS_ADDRESS environment variable to the one current
X session uses...

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

Title:
  unity dash not finding apps

Status in “unity” package in Ubuntu:
  New

Bug description:
  I just install Trusty Desktop 64-bit from this daily ISO:

  0a884e0fe10f703493a4f8ff993be5fd *trusty-desktop-amd64.iso

  After booting into the new desktop, I'm not able to search and find
  any apps.

  In particular, I'm searching for "terminal", trying to launch a Gnome
  Terminal.  I'm offered The Terminator movie, for sale, but there's no
  terminal app returned.

  In a separate issue, I search for Gimp, and I receive some not-safe-
  for-work results.

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

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

[Dx-packages] [Bug 1283236] Re: Alarms are triggered in UTC tz despite saving in local tz

[PS Jenkins bot]

Fix committed into lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/staging at
revision 1010, scheduled for release in ubuntu-ui-toolkit, milestone
Unknown

** Changed in: ubuntu-ui-toolkit
   Status: In Progress => Fix Committed

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

Title:
  Alarms are triggered in UTC tz despite saving in local tz

Status in The Date and Time Indicator:
  In Progress
Status in Clock application for Ubuntu devices:
  Invalid
Status in Ubuntu UI Toolkit:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Confirmed

Bug description:
  Setting an alarm in the local timezone is not respected by the system
  since the alarms is triggered in the equivalent UTC timezone.

  Mako build 200, 205

  Steps to reproduce: 
  1. Ensure that phone timezone is something other than UTC. For instance 
eastern tz (UTC-5)
  2. Set an alarm for 3:00 PM in the ubuntu clock app.
  3. Indicator shows a pending alarm for 3:00 PM
  4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM

  What happens:
  The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM

  What should happen:
  The alarm is triggered at 3:00 PM

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

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

[Dx-packages] [Bug 1308615] Re: unity dash not finding apps

[Christian Reis]

One log out and one log back in and it's fixed, and unfortunately that
means we couldn't verify this with bustle. Do other users see this?

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

Title:
  unity dash not finding apps

Status in “unity” package in Ubuntu:
  New

Bug description:
  I just install Trusty Desktop 64-bit from this daily ISO:

  0a884e0fe10f703493a4f8ff993be5fd *trusty-desktop-amd64.iso

  After booting into the new desktop, I'm not able to search and find
  any apps.

  In particular, I'm searching for "terminal", trying to launch a Gnome
  Terminal.  I'm offered The Terminator movie, for sale, but there's no
  terminal app returned.

  In a separate issue, I search for Gimp, and I receive some not-safe-
  for-work results.

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

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

[Dx-packages] [Bug 1308633] [NEW] package unity-scopes-runner 7.1.2+13.10.20131010-0ubuntu2 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before atte

[Stefano Gruppuso]

Public bug reported:

installArchives() failed: (Reading database ... 
(Reading database ... 5%%
(Reading database ... 10%%
(Reading database ... 15%%
(Reading database ... 20%%
(Reading database ... 25%%
(Reading database ... 30%%
(Reading database ... 35%%
(Reading database ... 40%%
(Reading database ... 45%%
(Reading database ... 50%%
(Reading database ... 55%%
(Reading database ... 60%%
(Reading database ... 65%%
(Reading database ... 70%%
(Reading database ... 75%%
(Reading database ... 80%%
(Reading database ... 85%%
(Reading database ... 90%%
(Reading database ... 95%%
(Reading database ... 100%%
(Reading database ... 242352 files and directories currently installed.)
Removing banshee-extension-soundmenu ...
Removing banshee ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for shared-mime-info ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support ...
Processing triggers for man-db ...
dpkg: error processing unity-scopes-runner (--configure):
 Package is in a very bad inconsistent state - you should
 reinstall it before attempting configuration.
No apport report written because MaxReports is reached already
Errors were encountered while processing:
 unity-scopes-runner

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: unity-scopes-runner 7.1.2+13.10.20131010-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
Uname: Linux 3.11.0-20-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Wed Apr 16 12:19:04 2014
Dependencies:
 
DuplicateSignature: 
package:unity-scopes-runner:7.1.2+13.10.20131010-0ubuntu2:Package is in a very 
bad inconsistent state - you should  reinstall it before attempting 
configuration.
ErrorMessage: Package is in a very bad inconsistent state - you should  
reinstall it before attempting configuration.
InstallationDate: Installed on 2014-04-06 (9 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: libunity
Title: package unity-scopes-runner 7.1.2+13.10.20131010-0ubuntu2 failed to 
install/upgrade: Package is in a very bad inconsistent state - you should  
reinstall it before attempting configuration.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check saucy

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

Title:
  package unity-scopes-runner 7.1.2+13.10.20131010-0ubuntu2 failed to
  install/upgrade: Package is in a very bad inconsistent state - you
  should  reinstall it before attempting configuration.

Status in “libunity” package in Ubuntu:
  New

Bug description:
  installArchives() failed: (Reading database ... 
  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 242352 files and directories currently installed.)
  Removing banshee-extension-soundmenu ...
  Removing banshee ...
  Processing triggers for hicolor-icon-theme ...
  Processing triggers for shared-mime-info ...
  Unknown media type in type 'all/all'
  Unknown media type in type 'all/allfiles'
  Unknown media type in type 'uri/mms'
  Unknown media type in type 'uri/mmst'
  Unknown media type in type 'uri/mmsu'
  Unknown media type in type 'uri/pnm'
  Unknown media type in type 'uri/rtspt'
  Unknown media type in type 'uri/rtspu'
  Processing triggers for desktop-file-utils ...
  Processing triggers for gnome-menus ...
  Processing triggers for bamfdaemon ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support ...
  Processing triggers for man-db ...
  dpkg: error processing unity-scopes-runner (--configure):
   Package is in a very bad inconsistent state - you should
   reinstall it before attempting configuration.
  No appor

[Dx-packages] [Bug 1308615] Re: unity dash not finding apps

[Christian Reis]

The NSFW comment is a BSDM result in the top line when searching for
Gimp.

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

Title:
  unity dash not finding apps

Status in “unity” package in Ubuntu:
  New

Bug description:
  I just install Trusty Desktop 64-bit from this daily ISO:

  0a884e0fe10f703493a4f8ff993be5fd *trusty-desktop-amd64.iso

  After booting into the new desktop, I'm not able to search and find
  any apps.

  In particular, I'm searching for "terminal", trying to launch a Gnome
  Terminal.  I'm offered The Terminator movie, for sale, but there's no
  terminal app returned.

  In a separate issue, I search for Gimp, and I receive some not-safe-
  for-work results.

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

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

[Dx-packages] [Bug 1308317] Re: applications in full-screen do not align properly after minimization

[Matt]

** Description changed:

  This is a problem with mouse-clicking sections of the firefox window
  that are unresponsive.
  
  I'll try to describe the problem. Firefox is open and set to
  fullscreen/maximize. You press the minimize button to send Firefox to
  the launcher. After opening firefox, by clicking on the launcher icon,
  firefox returns to fullscreen/maximize and appears normal. However, the
  tabs at the top are unclickable. The mouse button is an "I-beam" - or
  text-editing cursor - instead of a pointer when hovering over the tabs.
  Clicking changes the position of the I-beam in the text url below. This
  happens without regard to which programs are open, or whether or not
- anything else is open. There seems to be a 50/50 chance of clicking
- firefox from the launch pad, and having this happen.
+ anything else is open. This happens 100% of the time.
  
  It seems as though the firefox window is adjusting to maximize and leave
  room for the menubar at the top, but the GUI does not anticipate the
  menu bar. There is about a 10 pixel discrepancy between where the mouse
  points, and where it registers.
  
- This happens to ALL applications set to full-screen mode after
- minimization.
+ This also occurs with browser, Chromium.
  
  This video should help shed light on the problem:
  http://tinypic.com/r/2jfcepi/8
  
  I'm running Ubuntu 14.04 beta.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-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-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 15 22:01:26 2014
  DistUpgraded: 2014-04-04 13:01:59,967 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:100d]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:100d]
  InstallationDate: Installed on 2014-03-02 (45 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUSTeK COMPUTER INC. K46CA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=b5739d9f-9c22-4526-8ff5-d851de39247a ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to trusty on 2014-04-04 (11 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CA.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CA.309:bd10/16/2012:svnASUSTeKCOMPUTERINC.:pnK46CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K46CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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-0ubuntu1
  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: Tue Apr 15 11:10:07 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id   12348 
-  vendor AUO
+  product id   12348
+  vendor AUO
  xserver.version: 2:1.15.1-0ubuntu1

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

Title:
  applications in full-screen do not align properly after minimization

Status in “unity” package in Ubuntu:
  New

Bug description:
  This

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

[Christopher Townsend]

I can reproduce as well.  I'll look at getting this fixed for the next
14.04 Unity SRU.

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

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

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

** Changed in: unity
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

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

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

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 982434] Re: Opening the dash causes memory usage to climb dramatically, and never comes back down

[André F . Rendeiro]

On Ubuntu 14.04 with nvidia 337 drivers (not sure if that's relevant) compiz 
doesn't take up so much memory.
See screen atached: http://postimg.org/image/bya7hcepl/

** Attachment added: "memory_usage_14.04"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/982434/+attachment/4085538/+files/Screenshot%20from%202014-04-16%2017%3A14%3A28.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/982434

Title:
  Opening the dash causes memory usage to climb dramatically, and never
  comes back down

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

Bug description:
  This may not be a bug at all, but thought I'd report it anyway.

  I am NOT reporting a memory leak - at least, I don't think so.  I am
  simply reporting this:

  When I start a desktop session, Compiz uses 85M of memory.  It stays
  there as long as I *do not open the Dash*.

  Once I open the Dash - simply pushing the Ubuntu button, and then
  closing immediately - the memory usage climbs to ~120-150.

  If I go through every page in the Dash and open every sub-page and see
  every icon available, the memory usage clibms to ~185M.

  Re-visiting the Dash, no matter how often, doesn't cause a further
  increase, but I'm not certain the Dash should use ~100M of RAM all by
  itself.  I'm not sure how much it *should* use, but it just seems a
  bit excessive.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,place,grid,snap,vpswitch,move,animation,gnomecompat,resize,mousepoll,session,imgpng,workarounds,wall,fade,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  Date: Sun Apr 15 11:26:09 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-03-26 (20 days ago)

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

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

[C de-Avillez]

addition -- forgot to add graphics:

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller (rev 06)

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

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 1308615] [NEW] unity dash not finding apps

[Dustin Kirkland ]

Public bug reported:

I just install Trusty Desktop 64-bit from this daily ISO:

0a884e0fe10f703493a4f8ff993be5fd *trusty-desktop-amd64.iso

After booting into the new desktop, I'm not able to search and find any
apps.

In particular, I'm searching for "terminal", trying to launch a Gnome
Terminal.  I'm offered The Terminator movie, for sale, but there's no
terminal app returned.

In a separate issue, I search for Gimp, and I receive some not-safe-for-
work results.

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

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

Title:
  unity dash not finding apps

Status in “unity” package in Ubuntu:
  New

Bug description:
  I just install Trusty Desktop 64-bit from this daily ISO:

  0a884e0fe10f703493a4f8ff993be5fd *trusty-desktop-amd64.iso

  After booting into the new desktop, I'm not able to search and find
  any apps.

  In particular, I'm searching for "terminal", trying to launch a Gnome
  Terminal.  I'm offered The Terminator movie, for sale, but there's no
  terminal app returned.

  In a separate issue, I search for Gimp, and I receive some not-safe-
  for-work results.

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

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

[C de-Avillez]

easily reproducible. In my case the monitors are vertical, and the lower
one is the laptop's. When setting the launcher to appear on the built-
in, I can reproduce the bug.

Bypass: set launcher to appear on all monitors.

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

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

-- 
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” package in Ubuntu:
  Triaged

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/ubuntu/+source/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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.

[Rachel Greenham]

This was observed with both a RadeonHD 7750 and Intel HD4600; both using
stock opensource drivers/mesa et al. Two separate machines, btw. I'm
afraid I sold my nVidia card that I used to use, but the fact those
can't drive more than 2 monitors at once means I wouldn't have chosen
the configuration that revealed it in the first place (ie: wanting
launcher only on middle of three monitors). I suppose it's possible that
nVidia's TwinView may be having an effect, if it means the logic of how
it handles multi-monitor is reflected up at the levels at which Launcher
is coded. (In that case Nouveau might show it.) But remember from
earlier observations: this only occurs if the launcher is placed on one
screen, not all of them, and that the screen it's placed on is *not* the
one on the left.

Is clearly a bug :-) Can't possibly be a design feature a: that the
launcher behaves differently on different monitors of a multi-monitor
setup, and b: that it works correctly exactly once per session. *Never*
working would at least imply malign design choice! ;-)

Also, it didn't happen in Saucy. I'd had that Launcher-in-the-middle
config for some time before the upgrade to Trusty beta.

-- 
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” package in Ubuntu:
  Triaged

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/ubuntu/+source/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 1078326] Re: Quit and unlock from Unity bar does not function

[Mark]

I confirm this for Ubuntu 14.04 LTS. The icons for Gmail, Facebook and
Twitter are staying in the launcher after closing the site in the
Firefox browser.

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

Title:
  Quit and unlock from Unity bar does not function

Status in “libunity-webapps” package in Ubuntu:
  Confirmed

Bug description:
  Webapps icons that appear in the Unity bar will not go after app is
  closed.

  Example: YOUTUBE icon appear on launch of Chromium, but once Chromium
  is shut down the icon remains and cannot be removed unless I log
  off/on or reboot.

  The Quit option does not function and the Lock/Unlock to launcher
  makes no difference, the icon remains until reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-webapps-service 2.4.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Nov 13 13:37:58 2012
  ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-context-daemon
  InstallationDate: Installed on 2012-10-12 (32 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
  SourcePackage: libunity-webapps
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1306112] Re: calendar sync causing 100% cpu and does not complete

[Charles Kerr]

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

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

Title:
  calendar sync causing 100% cpu and does not complete

Status in Sync monitor for Ubuntu Touch:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “qtorganizer5-eds” package in Ubuntu:
  Fix Released
Status in “sync-monitor” package in Ubuntu:
  Fix Released

Bug description:
  test using canonical google account this is the problem i'm seeing
  with the canonical account

  the calendar sync starts to run first, and it gets about progress of
  70 and then evolution-calendar-factory starts consuming all the CPU -
  100% (run "top -d1") and at the same time the sync-monitor.log shows
  an infinite number of messages about

  static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, 
ViewWatcher*) 0x15468a8 
  virtual QList 
QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*) 
  virtual bool 
QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*) 
  virtual bool 
QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*,
 int) 
  syn requested for account: "bill.fil...@canonical.com" "calendar" 
  Account aready in the queue 

  The sync never finishes, seems that evolution process is stuck. I have to 
kill it.
  http://pastebin.ubuntu.com/7231364/

  Seems we might be in a loop when calendar events are getting added
  because of the sync we see tons of messages in the sync-monitor log
  maybe we're not ignoring the events correctly? or maybe it's a problem
  is the calendar has a recurring event? seems to cause infinite loop.

  This one is critical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sync-monitor/+bug/1306112/+subscriptions

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

[Dx-packages] [Bug 1078326] Re: Quit and unlock from Unity bar does not function

[Launchpad Bug Tracker]

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

** Changed in: libunity-webapps (Ubuntu)
   Status: New => Confirmed

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

Title:
  Quit and unlock from Unity bar does not function

Status in “libunity-webapps” package in Ubuntu:
  Confirmed

Bug description:
  Webapps icons that appear in the Unity bar will not go after app is
  closed.

  Example: YOUTUBE icon appear on launch of Chromium, but once Chromium
  is shut down the icon remains and cannot be removed unless I log
  off/on or reboot.

  The Quit option does not function and the Lock/Unlock to launcher
  makes no difference, the icon remains until reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-webapps-service 2.4.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Nov 13 13:37:58 2012
  ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-context-daemon
  InstallationDate: Installed on 2012-10-12 (32 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
  SourcePackage: libunity-webapps
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1069084] Re: Keyboard layout switcher doesn't work when I log in using the login screen

[Aurel Branzeanu]

This bug still here - could change the language only clicking on the
indicator wit the mouse... Ubuntu 14.04, unity
(7.2.0+14.04.20140414.1-0ubuntu1).

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

Title:
  Keyboard layout switcher doesn't work when I log in using the login
  screen

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have two keyboard layouts enabled on my PC, "English (USA)" and
  "Russian", they are switched by pressing Alt+Shift (the default).

  If automatic login is enabled and I get logged in when the system
  starts, without entering my password on the login screen, everything
  works.

  However, if automatic login is disabled and I log in by entering my
  password then the keyboard layout indicator disappears from the panel
  and keyboard layout won't switch when I press Alt+Shift. Basically,
  I'm stuck with the EN-US layout until I enable automatic login and
  reboot.

  The same problem happens if I log in automatically but then log out
  and log in again manually.

  This does NOT happen when I block the screen and then unblock it
  (although I have to enter the password), nor when I block the screen
  and then switch users. Also, when I start a guest session, the layout
  switcher always works normally there.

  I've tried creating additional user accounts and the problem repeats
  in all of them.

  I'm sorry I can't select the right package, but I don't know what
  causes this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Oct 20 15:35:39 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 982434] Re: Opening the dash causes memory usage to climb dramatically, and never comes back down

[Jaime Marques]

Anca, if you are using nvidia drivers try using the 337 drivers.
it improved for me its using 70/80mb down from 300mb +

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

Title:
  Opening the dash causes memory usage to climb dramatically, and never
  comes back down

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

Bug description:
  This may not be a bug at all, but thought I'd report it anyway.

  I am NOT reporting a memory leak - at least, I don't think so.  I am
  simply reporting this:

  When I start a desktop session, Compiz uses 85M of memory.  It stays
  there as long as I *do not open the Dash*.

  Once I open the Dash - simply pushing the Ubuntu button, and then
  closing immediately - the memory usage climbs to ~120-150.

  If I go through every page in the Dash and open every sub-page and see
  every icon available, the memory usage clibms to ~185M.

  Re-visiting the Dash, no matter how often, doesn't cause a further
  increase, but I'm not certain the Dash should use ~100M of RAM all by
  itself.  I'm not sure how much it *should* use, but it just seems a
  bit excessive.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,place,grid,snap,vpswitch,move,animation,gnomecompat,resize,mousepoll,session,imgpng,workarounds,wall,fade,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  Date: Sun Apr 15 11:26:09 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-03-26 (20 days ago)

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

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

[Dx-packages] [Bug 1292014] Re: Keyboard layout switcher shortcut doesn't work in lock screen

[yotaqa]

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

14.04 confirmed. After update from 12.04

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

Title:
  Keyboard layout switcher shortcut doesn't work in lock screen

Status in “unity” package in Ubuntu:
  New

Bug description:
  I know this bug is known, but I couldn't find a report for it.

  After the big change in the lock-screen (unity greeter instead of
  GNOME-screensaver) the bug introduced with 13.10 still exists: While
  in lock screen, you cannot change keyboard layout by the defined
  shortcut keys. My specific shortcut for switching keyboard layout is
  Alt+Shift (right/left). This doesn't work when the screen is locked
  and I want to enter password for unlocking.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140312-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: Thu Mar 13 14:56:23 2014
  InstallationDate: Installed on 2014-02-15 (25 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
  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/1292014/+subscriptions

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

[Dx-packages] [Bug 982434] Re: Opening the dash causes memory usage to climb dramatically, and never comes back down

[Anca Emanuel]

http://imgur.com/8Qc211i

In the Ubuntu 14.04

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

Title:
  Opening the dash causes memory usage to climb dramatically, and never
  comes back down

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

Bug description:
  This may not be a bug at all, but thought I'd report it anyway.

  I am NOT reporting a memory leak - at least, I don't think so.  I am
  simply reporting this:

  When I start a desktop session, Compiz uses 85M of memory.  It stays
  there as long as I *do not open the Dash*.

  Once I open the Dash - simply pushing the Ubuntu button, and then
  closing immediately - the memory usage climbs to ~120-150.

  If I go through every page in the Dash and open every sub-page and see
  every icon available, the memory usage clibms to ~185M.

  Re-visiting the Dash, no matter how often, doesn't cause a further
  increase, but I'm not certain the Dash should use ~100M of RAM all by
  itself.  I'm not sure how much it *should* use, but it just seems a
  bit excessive.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,place,grid,snap,vpswitch,move,animation,gnomecompat,resize,mousepoll,session,imgpng,workarounds,wall,fade,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  Date: Sun Apr 15 11:26:09 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-03-26 (20 days ago)

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

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

[Dx-packages] [Bug 1308540] Re: the password entry is not shared between screens

[Sebastien Bacher]

** Tags added: security

** Tags removed: security
** Tags added: lockscreen

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

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

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

** Summary changed:

- the password entry is not shared between screens
+ [lockscreen] the password entry is not shared between screens

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

Title:
  [lockscreen] the password entry is not shared between screens

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

Bug description:
  Using trusty candidate on a dual monitor config
  - log into unity
  - lock screen
  - start typing your password on one screen
  - move the pointer on the other screen

  -> the entry is displayed empty

  
  Ideally the same entry would be move so you can keep typing even if you 
happened to have move the focus, that's what lightdm/unity-greeter is doing

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

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

[Dx-packages] [Bug 1306676] Re: error messages from pam get cuts

[Andrea Azzarone]

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

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

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

Title:
  error messages from pam get cuts

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

Bug description:
  Using trusty release candidate in a french locale, if you enter an
  invalid password on the lock screen the error message is cut because
  it doesn't fit on the box where the text is rendered

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

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

[Dx-packages] [Bug 1308265] Re: First password letter not registered in lockscreen if screen off

[Sebastien Bacher]

** Tags added: lockscreen

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

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

Title:
  First password letter not registered in lockscreen if screen off

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

Bug description:
  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1308540] [NEW] the password entry is not shared between screens

[Sebastien Bacher]

Public bug reported:

Using trusty candidate on a dual monitor config
- log into unity
- lock screen
- start typing your password on one screen
- move the pointer on the other screen

-> the entry is displayed empty


Ideally the same entry would be move so you can keep typing even if you 
happened to have move the focus, that's what lightdm/unity-greeter is doing

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

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

Title:
  the password entry is not shared between screens

Status in “unity” package in Ubuntu:
  New

Bug description:
  Using trusty candidate on a dual monitor config
  - log into unity
  - lock screen
  - start typing your password on one screen
  - move the pointer on the other screen

  -> the entry is displayed empty

  
  Ideally the same entry would be move so you can keep typing even if you 
happened to have move the focus, that's what lightdm/unity-greeter is doing

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

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

[Dx-packages] [Bug 1308296] Re: Allow for other calendar applications to register with Unity calendar indicator

[Sebastien Bacher]

** Package changed: unity (Ubuntu) => indicator-datetime (Ubuntu)

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

Title:
  Allow for other calendar applications to register with Unity calendar
  indicator

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

Bug description:
  It appears that Unity's calendar indicator (in the global menu, right-
  side of the screen) is hardwired to launch Evolution if an event is
  selected.  In System Settings, the only checkbox relevant to this is
  to show "Coming events from Evolution Calendar".

  It'd be nice if instead the Unity calendar indicator would launch the
  user's chosen default calendar application.

  I'm not suggesting that the calendar indicator quit using Evolution
  Data Server for calendar information, just which application is
  launched in response to a user event.

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

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

[Dx-packages] [Bug 1306968] Re: After unlocking the desktop, it locks itself again.

[Andrea Azzarone]

Likely your version of gnome-screensaver was outdated. Marking as
invalid.

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

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

Title:
  After unlocking the desktop, it locks itself again.

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

Bug description:
  After idling for some time my desktop locks. When I return and enter
  the password, it unlocks and I briefly see my desktop and open
  applications before it locks itself again. After entering the password
  (again), it seems to work fine.

  Expected behavior:
  The desktop shouldn't lock immediately after unlocking.

  Reproduce:
  1. Let the screen lock on its own. Using CTRL-ALT-L seems to only require 
unlocking once. 
  2. Try to unlock the desktop using your password. It will relock (for me).

  I have a feeling it might have something to do with the monitor going
  to sleep, which might explain why CTRL-ALT-L seems to work (the
  monitor never sleeps.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 11 14:38:30 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:304a]
  InstallationDate: Installed on 2014-04-02 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=e01ba637-d590-489e-ba5a-d0a4f1ed4cae ro quiet splash nomdmonddf 
nomdmonisw
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A74MX-S/A74MX-K
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/05/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnA74MX-S/A74MX-K:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.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-4ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4
  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: Wed Apr  9 08:51:09 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Keyboard KEYBOARD, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech Unifying Device. Wireless PID:1025 MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu7
  xserver.video_driver: radeon

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

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

[Dx-packages] [Bug 1308323] Re: Shutdown/reboot/login/logout notification prompts not scaled after toggling UI scale Edit

[Sebastien Bacher]

** Package changed: ubiquity (Ubuntu) => unity (Ubuntu)

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

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

Title:
  Shutdown/reboot/login/logout notification prompts not scaled after
  toggling UI scale Edit

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

Bug description:
  1. Install Ubuntu-trusty image and boot into OS
  2. Go to System settings > Display
  3. Toggle UI scale up or down
  4. Press power button to launch poweroff notification prompt
  5. Check if the contents of the prompt is also scaled in accordance to the UI 
scale settings

  [Expected results]
  Contents of the poweroff notification prompt should be scaled in accordance 
to the UI scale settings

  [Actual results]
  Contents of the poweroff notification prompt is not scaled

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

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

[Dx-packages] [Bug 1306112] Re: calendar sync causing 100% cpu and does not complete

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
13.10.0+14.04.20140415.3-0ubuntu1

---
indicator-datetime (13.10.0+14.04.20140415.3-0ubuntu1) trusty; urgency=low

  [ Charles Kerr ]
  * If there's a large batch of EDS events coming in, try to wait until
the event storm has passed before running our requery. (LP:
#1306112)
 -- Ubuntu daily releaseTue, 15 Apr 2014 
22:25:42 +

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

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

Title:
  calendar sync causing 100% cpu and does not complete

Status in Sync monitor for Ubuntu Touch:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “qtorganizer5-eds” package in Ubuntu:
  Fix Released
Status in “sync-monitor” package in Ubuntu:
  Fix Released

Bug description:
  test using canonical google account this is the problem i'm seeing
  with the canonical account

  the calendar sync starts to run first, and it gets about progress of
  70 and then evolution-calendar-factory starts consuming all the CPU -
  100% (run "top -d1") and at the same time the sync-monitor.log shows
  an infinite number of messages about

  static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, 
ViewWatcher*) 0x15468a8 
  virtual QList 
QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*) 
  virtual bool 
QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*) 
  virtual bool 
QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*,
 int) 
  syn requested for account: "bill.fil...@canonical.com" "calendar" 
  Account aready in the queue 

  The sync never finishes, seems that evolution process is stuck. I have to 
kill it.
  http://pastebin.ubuntu.com/7231364/

  Seems we might be in a loop when calendar events are getting added
  because of the sync we see tons of messages in the sync-monitor log
  maybe we're not ignoring the events correctly? or maybe it's a problem
  is the calendar has a recurring event? seems to cause infinite loop.

  This one is critical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sync-monitor/+bug/1306112/+subscriptions

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

[Dx-packages] [Bug 1306968] Re: After unlocking the desktop, it locks itself again.

[Andrea Azzarone]

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

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

Title:
  After unlocking the desktop, it locks itself again.

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

Bug description:
  After idling for some time my desktop locks. When I return and enter
  the password, it unlocks and I briefly see my desktop and open
  applications before it locks itself again. After entering the password
  (again), it seems to work fine.

  Expected behavior:
  The desktop shouldn't lock immediately after unlocking.

  Reproduce:
  1. Let the screen lock on its own. Using CTRL-ALT-L seems to only require 
unlocking once. 
  2. Try to unlock the desktop using your password. It will relock (for me).

  I have a feeling it might have something to do with the monitor going
  to sleep, which might explain why CTRL-ALT-L seems to work (the
  monitor never sleeps.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 11 14:38:30 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:304a]
  InstallationDate: Installed on 2014-04-02 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=e01ba637-d590-489e-ba5a-d0a4f1ed4cae ro quiet splash nomdmonddf 
nomdmonisw
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A74MX-S/A74MX-K
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/05/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnA74MX-S/A74MX-K:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.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-4ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4
  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: Wed Apr  9 08:51:09 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Keyboard KEYBOARD, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech Unifying Device. Wireless PID:1025 MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu7
  xserver.video_driver: radeon

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

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

[Dx-packages] [Bug 1307972] Re: Unable to type password after screen lock

[Islam]

unity:
  Installed: 7.2.0+14.04.20140410.1-0ubuntu1
  Candidate: 7.2.0+14.04.20140414.1-0ubuntu1
  Version table:
 7.2.0+14.04.20140414.1-0ubuntu1 0
500 http://mirror.skylink-datacenter.de/ubuntu/ trusty/main amd64 
Packages
 *** 7.2.0+14.04.20140410.1-0ubuntu1 0
100 /var/lib/dpkg/status

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

Title:
  Unable to type password after screen lock

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

Bug description:
  After the screen locks, sometimes I can't type in the password field, no 
characters are showed, I have to click on any other element like the shutdown 
menu then click again on the password field so it can accept typing.
  This is affecting Ubuntu 14.04.

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

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

[Dx-packages] [Bug 1308323] [NEW] Shutdown/reboot/login/logout notification prompts not scaled after toggling UI scale Edit

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

1. Install Ubuntu-trusty image and boot into OS
2. Go to System settings > Display
3. Toggle UI scale up or down
4. Press power button to launch poweroff notification prompt
5. Check if the contents of the prompt is also scaled in accordance to the UI 
scale settings

[Expected results]
Contents of the poweroff notification prompt should be scaled in accordance to 
the UI scale settings

[Actual results]
Contents of the poweroff notification prompt is not scaled

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

-- 
Shutdown/reboot/login/logout notification prompts not scaled after toggling UI 
scale Edit
https://bugs.launchpad.net/bugs/1308323
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 1307118] Re: Unity freezes on resuming from suspend

[Andrea Azzarone]

Yeah can you confirm that tty switching is not working?

** Tags added: lockscreen

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

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

Title:
  Unity freezes on resuming from suspend

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

Bug description:
  After suspending laptop (by closing the laptop screen) and then
  resuming, the screen is black and doesn't seem to take any keyboard or
  mouse input. As a result, the only way to fix the situation is to hard
  reboot the system.

  Steps to reproduce:
  1. Suspend laptop
  2. Wait for at least 10-15 minutes
  3. Try resuming

  What happens:
  Black screen with the mouse cursor visible. However the whole screen is 
frozen. No keyboard or mouse input is accepted. As a result, I cannot switch to 
any vt to reboot or restart the lightdm process

  What should happen:
  Unity lockscreen is shown where one can enter the password and return to the 
user session

  gnome-screensaver: 3.6.1-0ubuntu13 amd64 [Installed]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-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-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 13 13:56:56 2014
  DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2013-09-18 (207 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=63532c2e-8584-466e-8215-2d6770489a00 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-27 (45 days ago)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN32WW(V2.02)
  dmi.board.asset.tag: YB00228460
  dmi.board.name: 20217
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: YB00228460
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  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-4ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4
  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 13 13:51:07 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0)
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 489
   vendor LGD
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Colin Law]

@Rachel what graphics chipset/card are you running?  I know that someone with 
nvidia graphics is unable to replicate the problem.  You can run
lspci
in a terminal to see, it should have a line something like the one below, which 
shows that I have Intel graphics

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09)

-- 
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” package in Ubuntu:
  Confirmed

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/ubuntu/+source/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 1307738] Re: Lockscreen caps lock icon drawn under text entry, should be a white icon.

[Andrea Azzarone]

** Tags added: lockscreen

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

Title:
  Lockscreen caps lock icon drawn under text entry, should be a white
  icon.

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

Bug description:
  Lockscreen caps lock icon drawn under text entry, should be a white
  icon.

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

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

[Dx-packages] [Bug 1308002] Re: Screen quickly autolocks again after unlocking

[Andrea Azzarone]

** Tags added: lockscreen

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

Title:
  Screen quickly autolocks again after unlocking

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

Bug description:
  Yes the title sounds odd, right?

  So I have seen it many times and others have reported that to me as
  well. Mostly after resuming from suspend and entering password to
  unlock the screen, lightdm password screen comes to front just in a
  few seconds after I unlock the screen, so basically i have to enter
  password twice to unlock screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Apr 15 16:06:48 2014
  InstallationDate: Installed on 2014-02-28 (45 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140228)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1307972] Re: Unable to type password after screen lock

[Andrea Azzarone]

Since this bug is believed to have been fixed in a recent version of the
Uniy shell, could you please report the version you have installed?

>From the command line, the command

  apt-cache policy unity

should give this information.

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

** Tags added: lockscreen

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

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

Title:
  Unable to type password after screen lock

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

Bug description:
  After the screen locks, sometimes I can't type in the password field, no 
characters are showed, I have to click on any other element like the shutdown 
menu then click again on the password field so it can accept typing.
  This is affecting Ubuntu 14.04.

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

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

[Dx-packages] [Bug 1308527] [NEW] Unity blocks Hangouts system tray icon, doesn't work

[Konstigt]

Public bug reported:

Trying to use Google Hangouts extension with Google Chrome (or
Chromium).

In other desktop environments (Mac OS X, Windows 7, KDE, Gnome) it adds
a system tray icon which you can use to raise the main window or
conversation windows when minimized.

In Ubuntu, you can open the window from Chrome using the extension icon
on the top right but after closing a window you can't use that again. It
is now depending on being opened via the system tray icon.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140414.1-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-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Apr 16 14:45:34 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-03-26 (20 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity (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 in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308527

Title:
  Unity blocks Hangouts system tray icon, doesn't work

Status in “unity” package in Ubuntu:
  New

Bug description:
  Trying to use Google Hangouts extension with Google Chrome (or
  Chromium).

  In other desktop environments (Mac OS X, Windows 7, KDE, Gnome) it
  adds a system tray icon which you can use to raise the main window or
  conversation windows when minimized.

  In Ubuntu, you can open the window from Chrome using the extension
  icon on the top right but after closing a window you can't use that
  again. It is now depending on being opened via the system tray icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-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-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Apr 16 14:45:34 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-26 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1)
  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/1308527/+subscriptions

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

[Dx-packages] [Bug 1308193] Re: Upcoming recurring alarms on wrong day

[Charles Kerr]

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

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

Title:
  Upcoming recurring alarms on wrong day

Status in Clock application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  New
Status in “ubuntu-clock-app” package in Ubuntu:
  Confirmed

Bug description:
  Open clock
  Set alarm, make it occur every working day - and today is Tuesday.
  Save alarm.
  Pull down indicator, observe that "next" alarm is shown as "Mon" not "Wed" 
which is tomorrow. 

  Expectation would be that the indicator shows the next alarm, not the
  one 4 alarms away.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: armhf
  Date: Tue Apr 15 18:35:01 2014
  InstallationDate: Installed on 2014-04-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140415.1)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1308193/+subscriptions

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

[Dx-packages] [Bug 1241101]

[David Matějček]

It seems it is fixed in newer GTK, but after my recent experiences I am
not so optimistic. But after upgrade to 1.3.5 and also GTK 3.10 and
restarting the system Eclipse still did not crash (10 hours yesterday, 5
hours today, switching git branches on massive project, debugging,
refactoring).

Can you try it someone too? (package is big, you need fast connection)
sudo add-apt-repository ppa:gnome3-team/gnome3
sudo apt-get install libgtk-3-0
Download 1.3.5: https://launchpad.net/ubuntu/+source/oxygen-gtk3
Unpack and see instructions in the file INSTALL.

I hope Eclipse will be stable on Kubuntu 14.04 without these experiments
...

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

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

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

[Dx-packages] [Bug 1306472] Re: QToolBar Icons not loaded properly.

[Launchpad Bug Tracker]

This bug was fixed in the package appmenu-qt5 -
0.3.0+14.04.20140415-0ubuntu1

---
appmenu-qt5 (0.3.0+14.04.20140415-0ubuntu1) trusty; urgency=low

  [ Łukasz 'sil2100' Zemczak ]
  * When working with a Gnome/GTK theme, do the same thing as the gtk2
platformtheme plugin does - fetch the SystemIconThemeName (and its
fallback) from settings in the system (LP: #1306472)
 -- Ubuntu daily releaseTue, 15 Apr 2014 
10:27:05 +

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New => Fix Released

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

Title:
  QToolBar Icons not loaded properly.

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  Fix Released

Bug description:
  When using a QToolBar with a basic Qt application, the icons can be
  populated from a theme. Either using QIcon::FromTheme(), or setting
  them in the associated action using the forms designer in Qt. (The
  name given for the icon is the freedesktop.org standard naming
  convention)

  Under appmenu-qt5 these icons do not appear to be being loaded
  correctly, resulting in a toolbar populated with just the action text.

  A minimal example illustrates the problem here:
  https://github.com/GilesBathgate/appmenu-bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1306472/+subscriptions

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

[Dx-packages] [Bug 1306472] Re: QToolBar Icons not loaded properly.

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/appmenu-qt5

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

Title:
  QToolBar Icons not loaded properly.

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  New

Bug description:
  When using a QToolBar with a basic Qt application, the icons can be
  populated from a theme. Either using QIcon::FromTheme(), or setting
  them in the associated action using the forms designer in Qt. (The
  name given for the icon is the freedesktop.org standard naming
  convention)

  Under appmenu-qt5 these icons do not appear to be being loaded
  correctly, resulting in a toolbar populated with just the action text.

  A minimal example illustrates the problem here:
  https://github.com/GilesBathgate/appmenu-bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1306472/+subscriptions

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

[Dx-packages] [Bug 1296431] Re: Phone doesn't alert user of critical power situations

[Matthew Paul Thomas]

Specification updated.



I'll insert my usual misgiving here about non-indicator-related
notifications being provided by indicator code. We should have low-power
notifications regardless of whether indicator-power is running or even
exists.

** Changed in: indicator-power (Ubuntu)
   Status: In Progress => Triaged

** Changed in: indicator-power (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

** Description changed:

  The phone doesn't currently alert the user when the battery is critical.
  This leads to power loss at times and the user doesn't know it's about to 
happen or had happened.
  e.g. during a call, or while listening to music. Also if the phone is sat on 
the desk unplugged from power connection.
+ 
+ : "When the device’s
+ battery/batteries are discharging and reach — or begin discharging and
+ already have — 1 hour or less remaining (PC) or 20% or less remaining
+ (phone/tablet), a notification bubble should appear ... When the
+ device’s battery/batteries are discharging and reach — or begin
+ discharging and already have — 30 minutes or less remaining (PC) or 10%
+ or less remaining (phone/tablet), an alert should appear..."

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

Title:
  Phone doesn't alert user of critical power situations

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

Bug description:
  The phone doesn't currently alert the user when the battery is critical.
  This leads to power loss at times and the user doesn't know it's about to 
happen or had happened.
  e.g. during a call, or while listening to music. Also if the phone is sat on 
the desk unplugged from power connection.

  : "When the device’s
  battery/batteries are discharging and reach — or begin discharging and
  already have — 1 hour or less remaining (PC) or 20% or less remaining
  (phone/tablet), a notification bubble should appear ... When the
  device’s battery/batteries are discharging and reach — or begin
  discharging and already have — 30 minutes or less remaining (PC) or
  10% or less remaining (phone/tablet), an alert should appear..."

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

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

[Dx-packages] [Bug 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist

[Sebastien Bacher]

What "upstart file watcher"? Upstart doesn't magically watch all files,
you have specify what you want to be notified about, and I don't think
we have a job watching e.g "/usr/local/share/applications" at the moment

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

Title:
  indicator-messages-service is waking up every 4 seconds adding
  inotifies on paths that don't exist

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

Bug description:
  I've observed that an "idle" indicator-messages-services is waking up
  every 4 seconds on a poll() and doing two inotify_add_watch() calls on
  paths that don't exist, which wastes power on devices such as phones.

  strace shows:

  clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
  poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
  clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
  inotify_add_watch(9, "/usr/local/share/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  inotify_add_watch(9, "/usr/share/ubuntu-touch/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
  poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
  clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
  inotify_add_watch(9, "/usr/local/share/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  inotify_add_watch(9, "/usr/share/ubuntu-touch/applications", 
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
 = -1 ENOENT (No such file or directory)
  clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0

  Can these redundant polling checks be reduced or removed?  Polling
  every 4 seconds is a little bit heavy handed IMHO.

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

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

[Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy

[matthieu vidal]

About Source and Refactor Menus the problem seems to appear when you
work with two  files of a different type.

ie. Java file vs a text file.


when focusing the text file as there are not Source and Refactor menus for a 
text file, these two menus are not reactivated when switching back to the Java 
file. They are empty as describes by the initial problem.


The HUD do not work for these menus and I do not see a workaround to reveale 
the content of these two menus.


This is a different problem of #106

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

Title:
  Eclipse menus doesn't show up in Saucy

Status in Eclipse:
  Confirmed
Status in Unity GTK+ module:
  In Progress
Status in “oracle-jdk7-installer” package in Ubuntu:
  Triaged
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released

Bug description:
  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify "/usr/share/applications/eclipse.desktop" to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1186181] Re: battery icon unreliable at low battery levels

[Matthew Paul Thomas]

** Project changed: ubuntu-ux => indicator-power (Ubuntu)

** Changed in: indicator-power (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: indicator-power
   Status: Confirmed => Triaged

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

Title:
  battery icon unreliable at low battery levels

Status in The Power Indicator:
  Triaged
Status in “indicator-power” package in Ubuntu:
  Triaged

Bug description:
  Battery icon does not reliably display correct values at low battery
  levels.

  The icon works fine until you get below 30%. At 10-30% a small red
  icon should be displayed, and another icon should be displayed at
  <10%. Currently, the icon doesn't seem to change to anything smaller
  than the 40% icon.

  I have sometimes seen the red 20% icon, but it's very unreliable, and
  typically switches back to the 40% icon moments after resuming the
  phone.

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

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

[Dx-packages] [Bug 1186181] [NEW] battery icon unreliable at low battery levels

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Battery icon does not reliably display correct values at low battery
levels.

The icon works fine until you get below 30%. At 10-30% a small red icon
should be displayed, and another icon should be displayed at <10%.
Currently, the icon doesn't seem to change to anything smaller than the
40% icon.

I have sometimes seen the red 20% icon, but it's very unreliable, and
typically switches back to the 40% icon moments after resuming the
phone.

** Affects: indicator-power
 Importance: Undecided
 Status: Confirmed

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

-- 
battery icon unreliable at low battery levels
https://bugs.launchpad.net/bugs/1186181
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