[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[Yanpas]

!!! I have just booted from live Linux Mint xfce edition - everything is
OK with network there. Also I booted from Xubuntu and this bug appears
there. Is there anyone with Linux Mint with the same bug?

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions

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

[Dx-packages] [Bug 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

[pvdeynse]

a better (less drastic) workaround is to unset the environment variable 
QT_QPA_PLATFORMTHEME, this variable is set to: 
 QT_QPA_PLATFORMTHEME=appmenu-qt5

the following will bring back the missing menu bar
 export QT_QPA_PLATFORMTHEME=

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

Title:
  Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

Status in LyX - The Document Processor:
  New
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed

Bug description:
  1. Open "Qt Creator" Version 3.0.1 at the Gnome3 Desktop
  2. Menu bar is missing.

   workaround --
  After Deinstall appmenu-qt5 is the Menu bar working again.
  Open Terminal:
  sudo apt-get remove appmenu-qt5

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Apr 14 18:52:18 2014
  InstallationDate: Installed on 2014-02-14 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1260978] Re: [Greeter] should be able to control music service from the greeter

[kevin gunn]

retargeting to better match the current state of design and direction.
this feature is already supported by the ui, with a little bit of media-hub 
work on its way in order to support music controls on top of the greeter.

** No longer affects: unity8

** Also affects: media-hub
   Importance: Undecided
   Status: New

** Branch linked: lp:~thomas-voss/media-hub/use-mpris-player-skeleton-
and-register-with-indicator

** Summary changed:

- [Greeter] should be able to control music service from the greeter
+ should be able to control music service while greeter locked

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

** Changed in: ubuntu-music-app (Ubuntu)
   Status: New => Opinion

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: New => Opinion

** Changed in: unity8 (Ubuntu)
   Status: New => Opinion

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

Title:
  should be able to control music service while greeter locked

Status in Media Hub:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in “indicator-sound” package in Ubuntu:
  Opinion
Status in “ubuntu-music-app” package in Ubuntu:
  Opinion
Status in “ubuntu-settings-components” package in Ubuntu:
  Opinion
Status in “unity8” package in Ubuntu:
  Opinion

Bug description:
  Not sure what component to file this against-- please reassign as
  desired.

  I use my phone to play music on random while I'm driving. This works
  great except when I want to advance or pause the song, where I have to
  go through the greeter first to access the player. This can either
  take my attention away from driving or I need to wait until the next
  stop light to advance the song. This is less of a concern when the
  greeter can just be swiped with one gesture, but is a big concern if
  you enable the passcode lock where you have to add the passcode to
  access the player.

  If the music is playing, the greeter should allow rudimentary
  manipulation of the music, eg, pause/play and forward/back. Other
  platforms seem to allow for this (eg android).

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1260978/+subscriptions

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

[Dx-packages] [Bug 780776] Re: Launcher - No feedback when application launched elsewhere

[kevin gunn]

this is corrected in unity8

** Changed in: unity8 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Launcher - No feedback when application launched elsewhere

Status in Ayatana Design:
  Fix Committed
Status in BAMF Application Matching Framework:
  Triaged
Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in “bamf” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  If you launch an application, for example the media player, and it
  take a few seconds to load there is no feedback that the OS is doing
  something.

  In my usual case I am launching by double clicking on a media file and
  the application can take up to 20 seconds to load. I often do not know
  whether I double clicked fast enough and do it again leading to
  multiple copies of the application opening (which leads to a separate
  set of issues)

  In other operating systems this is normally handled by immediately
  showing an hour glass icon or similar while the application is opened.

  Ubuntu 11.04, default setup except desktop effects are turned off. I'm
  not sure if this is easy to fix or not.

  ---
  Desired resolution:

  - As soon as a user chooses to open a file (for example by double clicking on 
the file in Nautilus, or single clicking on the file in the Dash File Lens), 
the 'loading' Launcher effect should be triggered *if* the target application 
is not currently running.
  (the 'loading' Launcher effect is currently triggered when a user clicks on a 
non-running application in the launcher)

  - If the target application is not pinned to the Launcher, it should
  be added to the Launcher instantaneously the moment the user chooses
  to open the file.

  - The 'application loading' should always be triggered instantaneously
  when ever a application starts to load, even if the application is not
  pinned to the Launcher.  This includes when applications are launched
  via either the Dash or the command line.

  - also fix bug #893140

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

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

[Dx-packages] [Bug 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

[Ville Ranki]

Happens also on Siilihai-client - i believe this affects all Qt Widget
apps  that use a menu. Workaround works.

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

Title:
  Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

Status in LyX - The Document Processor:
  New
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed

Bug description:
  1. Open "Qt Creator" Version 3.0.1 at the Gnome3 Desktop
  2. Menu bar is missing.

   workaround --
  After Deinstall appmenu-qt5 is the Menu bar working again.
  Open Terminal:
  sudo apt-get remove appmenu-qt5

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Apr 14 18:52:18 2014
  InstallationDate: Installed on 2014-02-14 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1364225] Re: Shadow applied inconsistently to windows that use XShape

[Launchpad Bug Tracker]

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

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

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

Title:
  Shadow applied inconsistently to windows that use XShape

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

Bug description:
  When using the XShape APIs*, windows that have a rectangular shape are
  treated like normal windows (they get a title bar and shadow) even if
  the rectangular region is much smaller than the window.

  When a non-rectangular window changes its shape to be rectangular, it
  gains a shadow that remains even after changing its shape back to be
  non-rectangular.

  Ideally there would always be a shadow that matches the shape of the
  window.

  In the mean time, the correct behavior might be to remove the shadow
  whenever a shape is applied. If the application wishes to remove an
  applied shape, they could do something like:

XShapeCombineMask(d, w, ShapeBounding, 0, 0, None, ShapeSet);

  Please let me know if you need any more details, or if I'm missing
  something. (Unfortunately, the ubuntu-bug tool wouldn't work when
  filing this bug).

  * http://www.x.org/releases/current/doc/xextproto/shape.html

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

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

[Dx-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[Bruno Nova]

Wait, it's not fixed for me after all.

What happened is that I had Nautilus opened in another workspace, and this made 
it seem that the issue was fixed.
If no Nautilus windows were open before, the issue still occurs.

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

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in Nautilus:
  New
Status in Unity:
  Triaged
Status in “bamf” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

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

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

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

[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[Ben Smith]

I've also seen this problem where the input field is missing on one
monitor, but not on the other.

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

Title:
  After locking screen there is no input field to type password for
  unlock

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

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Dx-packages] [Bug 1365535] Re: Desktop fails to start properly after 14.04 > 14.10

[Chris Johnston]

Stephen, correct.. I installed nvidia-331 and now everything seems to be
working except that the time doesn't show up in the top black bar.

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

Title:
  Desktop fails to start properly after 14.04 > 14.10

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

Bug description:
  Yesterday I upgraded my laptop from 14.04 to 14.10  - after the
  upgrade, when I logged in, I saw Unity on the left with the icons I
  expected, and the bar across the top, however the time and date,
  network indicator icon, sound icon, etc were missing.. Clicking on any
  of the icons in Unity didn't load anything... Couldn't load the dash..
  Keyboard shortcuts such as ctrl+alt+t failed to load the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Thu Sep  4 10:30:43 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-29 (66 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.1
  UpstartRunningSystemVersion: init (upstart 1.13.1)
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-08-28T00:30:06
  mtime.conffile..etc.cron.daily.upstart: 2014-08-28T00:35:25
  mtime.conffile..etc.upstart.xsessions: 2014-08-28T00:30:06

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

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

[Dx-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

[jerrylamos]

U + 1 forums for last few days a number of people on a variety of
hardware booting to black screen or command line or 

Anything we can do to test anything?

Thanks.

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

Title:
  utopic 3.16.0-9 iso boots to desktop no unity

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

Bug description:
  Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre.
  Boots 3.16.0-6 amd64 fine, runs compiz 3D fine.  

  Today's amd64 iso download, 20 August, boots to desktop & cursor.  
  No unity.
  Did ubuntu-bug from command line on the booted iso, saved report.

  Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file.

  Planet Ubuntu asked for results on 3.16.0-9 so this is my result.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-9-generic 3.16.0-9.14
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.341
  Date: Wed Aug 20 16:57:57 2014
  LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140820)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper 
iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

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

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

[Dx-packages] [Bug 1365535] Re: Desktop fails to start properly after 14.04 > 14.10

[Stephen M. Webb]

Just so I'm clear, the symptoms are that unity-panel service is not
running (the contents of the black bar on the top of the screen) and
that unity itself does not react to any input at all (not even when
hovering the mouse over icons in the Launcher)?

if you could attach ~/.cache/upstart/unity7.log and  ~/.cache/upstart
/unity-panel-service.log that would be swell, too.

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

Title:
  Desktop fails to start properly after 14.04 > 14.10

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

Bug description:
  Yesterday I upgraded my laptop from 14.04 to 14.10  - after the
  upgrade, when I logged in, I saw Unity on the left with the icons I
  expected, and the bar across the top, however the time and date,
  network indicator icon, sound icon, etc were missing.. Clicking on any
  of the icons in Unity didn't load anything... Couldn't load the dash..
  Keyboard shortcuts such as ctrl+alt+t failed to load the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Thu Sep  4 10:30:43 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-29 (66 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.1
  UpstartRunningSystemVersion: init (upstart 1.13.1)
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-08-28T00:30:06
  mtime.conffile..etc.cron.daily.upstart: 2014-08-28T00:35:25
  mtime.conffile..etc.upstart.xsessions: 2014-08-28T00:30:06

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

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

[Dx-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/unity/font-scaling-fixes

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

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

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

Bug description:
  I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
  couple of reboots, the 'large text' option in Universal Access gets
  switched on upon login. It happens in roughly 1 out of 5 reboots for 1
  or more users on the computer.

  It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
  Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0

  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  unity-control-center:
Installed: 14.04.3+14.04.20140410-0ubuntu1
Candidate: 14.04.3+14.04.20140410-0ubuntu1
Version table:
   *** 14.04.3+14.04.20140410-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  intel iris pro graphics (lspci -vvv):

  00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 011a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 - 8.00+14.10.20140903.1~rtm-
0ubuntu1

---
unity8 (8.00+14.10.20140903.1~rtm-0ubuntu1) 14.09; urgency=low

  [ Nick Dedekind ]
  * Support for nested prompt session. (LP: #1358388)
 -- Ubuntu daily releaseWed, 03 Sep 2014 
07:58:49 +

** Changed in: unity8 (Ubuntu RTM)
   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, dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1358340

Title:
  [Indicators] Complete greeter profiles

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

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

  This was an accentual change based on a misunderstanding

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

  
  Desired resolution:

  - Revert the change that caused this issue

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

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

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

[Dx-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access

[Treviño]

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

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

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

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

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

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

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

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

Bug description:
  I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
  couple of reboots, the 'large text' option in Universal Access gets
  switched on upon login. It happens in roughly 1 out of 5 reboots for 1
  or more users on the computer.

  It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
  Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0

  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  unity-control-center:
Installed: 14.04.3+14.04.20140410-0ubuntu1
Candidate: 14.04.3+14.04.20140410-0ubuntu1
Version table:
   *** 14.04.3+14.04.20140410-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  intel iris pro graphics (lspci -vvv):

  00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 011a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915

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

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

[Dx-packages] [Bug 1348083] Re: Compiz crash traps general protection ip:7fa6b401eabe sp:7fffe8d30260 error:0 in libunityshell.so[7fa6b3dde000+320000]

[Launchpad Bug Tracker]

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

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

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

Title:
  Compiz crash traps general protection  ip:7fa6b401eabe sp:7fffe8d30260
  error:0 in libunityshell.so[7fa6b3dde000+32]

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

Bug description:
  Since possibly june 2014, on Ubuntu 12.04.4, Unity crashes for no apparent 
reason.
  It seems to be related to using the Super+F key (finding files).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Jul 24 10:27:57 2014
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365576] Re: Have to push mouse cursor really hard to move it between multiple monitors

[mcandre]

I can reproduce this about 60% of the time in Ubuntu 14.04 Trusty Tahr.

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

Title:
  Have to push mouse cursor really hard to move it between multiple
  monitors

Status in “unity” package in Ubuntu:
  New

Bug description:
  I often have to push my mouse cursor really hard, several times, to
  get it to jump between multiple monitors. Please increase the
  sensitivity for this.

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

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

[Dx-packages] [Bug 1365576] [NEW] Have to push mouse cursor really hard to move it between multiple monitors

[mcandre]

Public bug reported:

I often have to push my mouse cursor really hard, several times, to get
it to jump between multiple monitors. Please increase the sensitivity
for this.

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


** Tags: cursor displays monitors mouse multiple

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

Title:
  Have to push mouse cursor really hard to move it between multiple
  monitors

Status in “unity” package in Ubuntu:
  New

Bug description:
  I often have to push my mouse cursor really hard, several times, to
  get it to jump between multiple monitors. Please increase the
  sensitivity for this.

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

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

[Dx-packages] [Bug 1365535] Re: Desktop fails to start properly after 14.04 > 14.10

[Chris Johnston]

James, the paste in comment 3 is .xsession-errors..

For fun, I installed nvidia-331 and I'm not back in business... I guess
I will try upgrading lightdm again and see what it does.

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

Title:
  Desktop fails to start properly after 14.04 > 14.10

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

Bug description:
  Yesterday I upgraded my laptop from 14.04 to 14.10  - after the
  upgrade, when I logged in, I saw Unity on the left with the icons I
  expected, and the bar across the top, however the time and date,
  network indicator icon, sound icon, etc were missing.. Clicking on any
  of the icons in Unity didn't load anything... Couldn't load the dash..
  Keyboard shortcuts such as ctrl+alt+t failed to load the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Thu Sep  4 10:30:43 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-29 (66 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.1
  UpstartRunningSystemVersion: init (upstart 1.13.1)
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-08-28T00:30:06
  mtime.conffile..etc.cron.daily.upstart: 2014-08-28T00:35:25
  mtime.conffile..etc.upstart.xsessions: 2014-08-28T00:30:06

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

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

[Dx-packages] [Bug 1365535] Re: Desktop fails to start properly after 14.04 > 14.10

[James Hunt]

This sounds like a unity issue as I've seen no evidence of Upstart
misbehaving yet. That .xsession-errors log would be useful to have if
you can attach it though.

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

Title:
  Desktop fails to start properly after 14.04 > 14.10

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

Bug description:
  Yesterday I upgraded my laptop from 14.04 to 14.10  - after the
  upgrade, when I logged in, I saw Unity on the left with the icons I
  expected, and the bar across the top, however the time and date,
  network indicator icon, sound icon, etc were missing.. Clicking on any
  of the icons in Unity didn't load anything... Couldn't load the dash..
  Keyboard shortcuts such as ctrl+alt+t failed to load the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Thu Sep  4 10:30:43 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-29 (66 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.1
  UpstartRunningSystemVersion: init (upstart 1.13.1)
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-08-28T00:30:06
  mtime.conffile..etc.cron.daily.upstart: 2014-08-28T00:35:25
  mtime.conffile..etc.upstart.xsessions: 2014-08-28T00:30:06

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

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

[Dx-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[Bruno Nova]

It also seems to be fixed for me 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/1170647

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in Nautilus:
  New
Status in Unity:
  Triaged
Status in “bamf” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

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

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

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

[Dx-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[duroursu]

This bug its now fixed on 14.04,its working normaly on my pc

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

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in Nautilus:
  New
Status in Unity:
  Triaged
Status in “bamf” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

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

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

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

[Dx-packages] [Bug 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

[Treviño]

Unfortunately the stack trace doesn't say much... Would you be able to
install the unity debug symbols and then attach to the process with gdb
[1] to get something more useful?

[1] https://wiki.ubuntu.com/Unity/FilingBugs#Getting_a_stack_trace

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

Title:
  unity-panel-service crashed with SIGSEGV in
  _gtk_marshal_BOOLEAN__BOXED()

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

Bug description:
  I tried to open the panel menus.  Probably by keyboard first.  The
  panel froze & crashed.  No unusual circumstances that I noticed.

  I don't know if this will be relevant, but: since recently trying KDE
  packages on this machine, KDE's settings seemed to have fouled up
  Unity's, when I returned.  Many of the indicator icons were wrong or
  missing.  Attempts to clear the settings, remove KDE packages, and
  restart, didn't make any difference.  But after this crash, weeks
  later, the usual icons were finally restored.  Seems strange.

  Thanks.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar  1 00:14:03 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  MarkForUpload: True
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx
   PC (0x7f8097fa93a6) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago)
  UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo 
wireshark

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

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

[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv

[Treviño]

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

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

Title:
  Cannot uninstall upstart and install systemd-sysv

Status in Unity:
  In Progress
Status in “avahi” package in Ubuntu:
  Fix Released
Status in “dbus” package in Ubuntu:
  Fix Released
Status in “dovecot” package in Ubuntu:
  Fix Released
Status in “friendly-recovery” package in Ubuntu:
  Fix Released
Status in “hockeypuck” package in Ubuntu:
  Fix Released
Status in “pay-service” package in Ubuntu:
  In Progress
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “sysvinit” package in Ubuntu:
  Fix Released
Status in “ubuntu-app-launch” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-lens-applications” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  upstart is currently quite deeply wired into our dependencies. Even in
  a minimally bootstrapped chroot needs it, although this doesn't do any
  booting at all:

  # dpkg -P upstart
  dpkg: dependency problems prevent removal of upstart:
   initscripts depends on upstart.
   plymouth depends on upstart (>= 1.11-0ubuntu3).

  On a desktop the list is quite a bit longer:

   ubuntu-minimal depends on upstart.
   avahi-daemon depends on upstart (>= 0.6.7-4).
   friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd 
script first)
   initscripts depends on upstart.
   ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop 
that along with upstart for systemd images, systemd has readahead built in)
   plymouth depends on upstart (>= 1.11-0ubuntu3).
   dbus depends on upstart (>= 0.6.3-6).
   unity-services depends on upstart.
   init depends on upstart. (Not important right now, switch to alternative 
deps once systemd is ready)

  Most of the latter probably don't need to; versioned depends might be
  converted into equivalent versioned breaks, for others an alternative
  dependency might be considered. The main exception is that we are
  using session upstart on the desktop (unity-services etc.), for this
  we probably need to split out an upstart-sysv (for /sbin/init, reboot,
  halt, etc., similar to systemd-sysv) or an upstart-core (similar to
  sysvinit-core vs. sysvinit).

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

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

[Dx-packages] [Bug 1365410] Re: No French translations in fr.po

[Jean-Baptiste Lallement]

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

Yes it is the same indicator-bluetooth.mo is not in the language pack. I
verified and it is in latest upload (1:14.10+20140903) It should be
fixed on next image build with this version.

** This bug has been marked a duplicate of bug 1365401
   indicator-sound.mo not in language-pack-touch-XX

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

Title:
  No French translations in fr.po

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

Bug description:
  The French strings in fr.po are empty although the project is
  translated in launchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:38:12 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365410] Re: No French translations in fr.po

[Sebastien Bacher]

Where do you look at "fr.po"? Running "msgunfmt /usr/share/locale-
langpack/fr/LC_MESSAGES/indicator-bluetooth.mo" on an utopic desktop
shows that translations are there ... is your issue the same as bug
#1365401, e.g missing translations from the langpacks for touch)?

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

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Critical => High

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

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

Title:
  No French translations in fr.po

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

Bug description:
  The French strings in fr.po are empty although the project is
  translated in launchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:38:12 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1351815] Re: StartTransientUnit signature has changed in systemd 214

[Launchpad Bug Tracker]

This bug was fixed in the package systemd-shim - 7-2

---
systemd-shim (7-2) unstable; urgency=medium


  * Fix Start TransientUnit signature for systemd >= 209. Check systemd
version during package build. Patch from upstream git. (LP: #1351815)
  * Add systemd build dep for above configure check to work.
  * Generate Breaks: to systemd >= or << 209, depending on which version we
build against.

 -- Martin Pitt   Wed, 03 Sep 2014 08:07:00 +0200

** Changed in: systemd-shim (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  StartTransientUnit signature has changed in systemd 214

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

Bug description:
  This will be required when systemd gets updated to 214

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 6-4bzr1
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  3 14:05:50 2014
  InstallationDate: Installed on 2012-09-23 (679 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365530] Re: Time in indicator out of sync on resume from suspend

[Sebastien Bacher]

reassigning to unity8, using that command

"gdbus call --session --dest com.canonical.indicator.datetime --object-
path /com/canonical/indicator/datetime --method org.gtk.Actions.Describe
phone-header"

show that the indicator/dbus info are correct, it's the lockscreen/unity
panel which are behind

** Package changed: indicator-datetime (Ubuntu) => unity8 (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
https://bugs.launchpad.net/bugs/1365530

Title:
  Time in indicator out of sync on resume from suspend

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646

  When the device is resumed by pressing the power button and the device
  is not connected over USB to any power source the clock on the greeter
  and the date/time indicator is out of sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode
  3. Wait a moment (several minutes)
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 13:57:35 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365530] Re: Time in indicator out of sync on resume from suspend

[Sebastien Bacher]

Confirmed, I had a case today where it was a difference of 6 minutes,
it's not a lot but you are checking to clock to e.g catch a bus it might
be enough to make you be late

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

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

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

Title:
  Time in indicator out of sync on resume from suspend

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646

  When the device is resumed by pressing the power button and the device
  is not connected over USB to any power source the clock on the greeter
  and the date/time indicator is out of sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode
  3. Wait a moment (several minutes)
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 13:57:35 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365530] [NEW] Time in indicator out of sync on resume from suspend

[Jean-Baptiste Lallement]

Public bug reported:

mako: 221
krillin: 16
last known good build: ?
Similar defect: bug 1328646

When the device is resumed by pressing the power button and the device
is not connected over USB to any power source the clock on the greeter
and the date/time indicator is out of sync.

TEST CASE
1. Unplug the device from its USB cable
2. Press the power button to switch to suspend mode
3. Wait a moment (several minutes)
4. Press the power button again to resume the device
5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.

EXPECTED RESULT
Clocks are in sync

ACTUAL RESULT
Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Thu Sep  4 13:57:35 2014
InstallationDate: Installed on 2014-09-04 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity8 (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: apport-bug armhf qa-daily-testing rtm14 utopic

** Attachment added: "clock_out_of_sync.jpg"
   
https://bugs.launchpad.net/bugs/1365530/+attachment/4195423/+files/clock_out_of_sync.jpg

** Description changed:

  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646
  
  When the device is resumed by pressing the power button and the device
- is not connected over USB the clock on the greeter and the date/time
- indicator is out of sync
+ is not connected over USB to any power source the clock on the greeter
+ and the date/time indicator is out of sync
  
  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait a moment (several minutes)
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.
  
  EXPECTED RESULT
  Clocks are in sync
  
  ACTUAL RESULT
  Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 13:57:35 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646
  
  When the device is resumed by pressing the power button and the device
  is not connected over USB to any power source the clock on the greeter
- and the date/time indicator is out of sync
+ and the date/time indicator is out of sync.
  
  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait a moment (several minutes)
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.
  
  EXPECTED RESULT
  Clocks are in sync
  
  ACTUAL RESULT
  Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 13:57:35 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646
  
  When the device is resumed by pressing the power button and the device
  is not connected over USB to any power 

[Dx-packages] [Bug 1285951] Re: bluetooth indicator disappears after turning off bluetooth

[Sebastien Bacher]

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

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

Title:
  bluetooth indicator disappears after turning off bluetooth

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

Bug description:
  Although bug 1126108 is marked as "Fix released", my indicator-
  bluetooth icon disappears after I use it to turn bluetooth off. See
  the attached animated gif.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-bluetooth 0.0.6+13.10.20131016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Feb 27 22:37:17 2014
  InstallationDate: Installed on 2013-01-12 (411 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-bluetooth
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (127 days ago)

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

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

[Dx-packages] [Bug 1365039] Re: Could not get session id for session

[Martin Pitt]

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

Wile systemd-shim 7-1 → 7-2 is essentially a no-op (i. e. harmless), you
really shouldn't have gotten that version automatically yet -- it's
still in proposed. Pretty pretty please do *not* run utopic-proposed!
It's pretty much guaranteed to break your computer and is not supported.
As for the lightdm failure, I just heard from Chris confirming that
there's apparently some trouble with last night's version (bug 1365336).

For this, please run "sudo apt-get -f install" to fix a (probably) half-
broken installation, and disable -proposed.

** This bug has been marked a duplicate of bug 1365336
   Lightdm update=No desktop

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

Title:
  Could not get session id for session

Status in Light Display Manager:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed

Bug description:
  A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm 
(1.11.8-0ubuntu1).
  On that pc, i've closed the session then shutdown: everything was stable, and 
its a fresh standard installation using upstart for booting.

  Here are the troubles met at the next cold boot (verbosy mode):

  - the boot process goes well until "Add swap on /dev/sdb2" as
  expected, but then nothing, only hdd activity continuing hardly
  scanning, and no errors/warnings printed.  Had to force a hardware's
  reset, can't call tty1-6 (system not responsive ??)

  - second cold boot: the system load fsck on the /home partition, then
  the process continue to boot, made a pause at load the swap partition
  again, the hdd was activity working a few (long) seconds, so i've
  tried to switch to tty1 and successed. I've reconfigured lightdm and
  tried  startx : it seemed to continue its processes even if the hdd
  was again hardly scanning unsually. But i only got a black screen: no
  mouse pointer, no tty. So reboot again.

  - third try: same issue, but was able to open tty when it did a pause
  at swap partition loading: so i reconfigured lightdm and choose gdm as
  default that time. Startx was ran and after some hard hdd scanning, it
  finally loaded a degraded login screen: no mouse but the keyboard was
  working. After login validation, gnome-shell appeared as expected, but
  again no mouse; a ctrl+alt+T opened a terminal, where i'm right now,
  to report that issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 7-2
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic i686
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Sep  3 17:15:43 2014
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[Jung-Kyu Park]

Nope, I have a issue on single monitor and even it is related to
language ubiquity check this report

related to single monitor)
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1251213

related to language select ubiquity)
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1327690

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

Title:
  After locking screen there is no input field to type password for
  unlock

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

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

-- 
Mailing list: https://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 1311316] Re: After locking screen there is no input field to type password for unlock

[Anders Sandblad]

I've used my laptop with built in display since the release of 14.04
(upgraded from 13.10) and did never see this issue until I started connect
a second display, then I've been getting this issue. It's definitely dual
screen related.

I've also been seeing this issue on my computer at work, also with dual
screen.

/Anders
On Sep 4, 2014 3:01 PM, "ubuntu-tester"  wrote:

> This morning, I made a standard Ubuntu 14.04 installation on a dual-screen
> computer.
> I launched processes in order to use 100% of the CPUs, and I reprocuded
> this bug twice (I don't know if this bug is related to the CPUs usage). I
> also found this bug on other computers using local or LDAP accounts.
>
> I tryed to reproduce this bug on a single-screen computer but I didn't
> see any problem, so I think this bug is related to the dual-screen
> configuration. To ensure : Someone has this bug on a single-screen
> computer ?
>
> I know somebody who uses Ubuntu 14.04/Unity on a dual-screen computer
> and seems do not have this bug, do you need specific informations about
> the configuration of his system ?
>
> Is there a possibility to use another locker than the Unity locker ?
>
> If you need me for information or make tests/debugging, don't hesitate
> to contact me.
>
> Thanks.
>
> Attachement => sysinfo.txt :
> 1. system information about the computer impacted by this bug
> 2. system information about the computer which seems NOT impacted by this
> bug
> 3. additionnal packages installed on the computer which seems NOT impacted
> by this bug
>
> ** Attachment added: "sysinfo.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316/+attachment/4195367/+files/sysinfo.txt
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1311316
>
> Title:
>   After locking screen there is no input field to type password for
>   unlock
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions
>

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

Title:
  After locking screen there is no input field to type password for
  unlock

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

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[ubuntu-tester]

This morning, I made a standard Ubuntu 14.04 installation on a dual-screen 
computer.
I launched processes in order to use 100% of the CPUs, and I reprocuded this 
bug twice (I don't know if this bug is related to the CPUs usage). I also found 
this bug on other computers using local or LDAP accounts.

I tryed to reproduce this bug on a single-screen computer but I didn't
see any problem, so I think this bug is related to the dual-screen
configuration. To ensure : Someone has this bug on a single-screen
computer ?

I know somebody who uses Ubuntu 14.04/Unity on a dual-screen computer
and seems do not have this bug, do you need specific informations about
the configuration of his system ?

Is there a possibility to use another locker than the Unity locker ?

If you need me for information or make tests/debugging, don't hesitate
to contact me.

Thanks.

Attachement => sysinfo.txt :
1. system information about the computer impacted by this bug
2. system information about the computer which seems NOT impacted by this bug
3. additionnal packages installed on the computer which seems NOT impacted by 
this bug

** Attachment added: "sysinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316/+attachment/4195367/+files/sysinfo.txt

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

Title:
  After locking screen there is no input field to type password for
  unlock

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

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Dx-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access

[Ben]

as of the latest updates published about 2014-09-03, this now happens
after every reboot. It used to be just after an update, then you'd turn
off large text, and it would be fine. Now, every time I reboot, it turns
itself back on. I tried adding
/home/ben/.config/autostart/largetextfix.desktop but that did not fix
it.

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

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

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

Bug description:
  I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
  couple of reboots, the 'large text' option in Universal Access gets
  switched on upon login. It happens in roughly 1 out of 5 reboots for 1
  or more users on the computer.

  It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
  Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0

  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  unity-control-center:
Installed: 14.04.3+14.04.20140410-0ubuntu1
Candidate: 14.04.3+14.04.20140410-0ubuntu1
Version table:
   *** 14.04.3+14.04.20140410-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  intel iris pro graphics (lspci -vvv):

  00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 011a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915

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

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

[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[Pablo180]

@David or anyone else having this problem, I too didn't have any luck
with "nmcli nm sleep false" in my script under /etc/pm/sleep.d/ either
but when I used "service network-manager restart" instead it worked
flawlessly. I have not had any problems for almost five months and it
doesn't cause any side effects.

I've added the script that I use to this post.

** Attachment added: "Script for restarting networking manager on resume"
   
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/4195364/+files/10_restart-networkmanager

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions

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

[Dx-packages] [Bug 1365039] Re: Could not get session id for session

[dino99]

@lbssousa

as per the initial description: "and its a fresh standard installation
using upstart for booting."

so that is, no fancy things except the default ones (seems these 2
packages have not been able the cleanly upgrade, as the system was fine
before using these upgrades)

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

Title:
  Could not get session id for session

Status in Light Display Manager:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed

Bug description:
  A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm 
(1.11.8-0ubuntu1).
  On that pc, i've closed the session then shutdown: everything was stable, and 
its a fresh standard installation using upstart for booting.

  Here are the troubles met at the next cold boot (verbosy mode):

  - the boot process goes well until "Add swap on /dev/sdb2" as
  expected, but then nothing, only hdd activity continuing hardly
  scanning, and no errors/warnings printed.  Had to force a hardware's
  reset, can't call tty1-6 (system not responsive ??)

  - second cold boot: the system load fsck on the /home partition, then
  the process continue to boot, made a pause at load the swap partition
  again, the hdd was activity working a few (long) seconds, so i've
  tried to switch to tty1 and successed. I've reconfigured lightdm and
  tried  startx : it seemed to continue its processes even if the hdd
  was again hardly scanning unsually. But i only got a black screen: no
  mouse pointer, no tty. So reboot again.

  - third try: same issue, but was able to open tty when it did a pause
  at swap partition loading: so i reconfigured lightdm and choose gdm as
  default that time. Startx was ran and after some hard hdd scanning, it
  finally loaded a degraded login screen: no mouse but the keyboard was
  working. After login validation, gnome-shell appeared as expected, but
  again no mouse; a ctrl+alt+T opened a terminal, where i'm right now,
  to report that issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 7-2
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic i686
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Sep  3 17:15:43 2014
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365401] Re: indicator-sound.mo not in language-pack-touch-XX

[Martin Pitt]

Affects all touch langpacks, just randomly picking the French one to
track :-)

** Package changed: indicator-sound (Ubuntu) => language-pack-touch-fr
(Ubuntu)

** Changed in: language-pack-touch-fr (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: language-pack-touch-fr (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  indicator-sound.mo not in language-pack-touch-XX

Status in “language-pack-touch-fr” package in Ubuntu:
  In Progress

Bug description:
  indicator-sound.mo is not present in language-pack-touch-fr and the
  indicator is not translated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ActionStates: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-touch-fr/+bug/1365401/+subscriptions

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

[Dx-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

[jerrylamos]

4 September amd64 .iso boots to flashing desktop, no unity.

3.16.0-12 kernel  in the .iso according to ls /boot fails to start
unity.

My -11 updated to -12 does work.

Now the .iso is usually behind apt-get update.  Past experience if the
.iso isn't running correctly the install won't either.  Not sure it's
worth my while to install the non-unity .iso and try an update.

Bummer.

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

Title:
  utopic 3.16.0-9 iso boots to desktop no unity

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

Bug description:
  Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre.
  Boots 3.16.0-6 amd64 fine, runs compiz 3D fine.  

  Today's amd64 iso download, 20 August, boots to desktop & cursor.  
  No unity.
  Did ubuntu-bug from command line on the booted iso, saved report.

  Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file.

  Planet Ubuntu asked for results on 3.16.0-9 so this is my result.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-9-generic 3.16.0-9.14
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.341
  Date: Wed Aug 20 16:57:57 2014
  LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140820)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper 
iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

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

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

[Dx-packages] [Bug 1365401] Re: indicator-sound.mo not in language-pack-touch-XX

[Jean-Baptiste Lallement]

Sorry, I've been confused by a link from a spreadsheet to the upstream
project instead of the ubuntu project. The translations are corrects.
The problem is that indicator-sound.mo is not installed on the device.
It should probably be installed by language-pack-touch-XX

** Summary changed:

- No POT file in source tree
+ indicator-sound.mo not in language-pack-touch-XX

** Changed in: indicator-sound (Ubuntu)
   Status: Incomplete => Confirmed

** Description changed:

- There is no POT file for this application in the source tree and it is
- not translatable.
+ indicator-sound.mo is not present in language-pack-touch-fr and the
+ indicator is not translated.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ActionStates: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

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

Title:
  indicator-sound.mo not in language-pack-touch-XX

Status in “language-pack-touch-fr” package in Ubuntu:
  In Progress

Bug description:
  indicator-sound.mo is not present in language-pack-touch-fr and the
  indicator is not translated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ActionStates: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-touch-fr/+bug/1365401/+subscriptions

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

[Dx-packages] [Bug 1365469] [NEW] Unity prevents usage of "Super R" as "Switch to next source" keyboard shortcut

[Kabanov Dmitry]

Public bug reported:

I set "Super R" key as my shortcut to change keyboard layouts. See
attached screenshot.

What happens:

Whenever I press "Super R" key, Unity intercepts it and use it to open
the Dash. I haven't found any options in Unity Tweak Tool or Compiz
Settings Manager to prevent Unity from doing this. Aforementioned
utilities do not distinguish between Left Super and Right Super keys.

Expected behavior:
Unity should use only left Super key for opening the Dash.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu Sep  4 15:09:57 2014
InstallationDate: Installed on 2014-08-28 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Attachment added: "Shows that I set "Super R" key to switch keyboard layouts"
   
https://bugs.launchpad.net/bugs/1365469/+attachment/4195359/+files/unity_bug.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/1365469

Title:
  Unity prevents usage of "Super R" as "Switch to next source" keyboard
  shortcut

Status in “unity” package in Ubuntu:
  New

Bug description:
  I set "Super R" key as my shortcut to change keyboard layouts. See
  attached screenshot.

  What happens:

  Whenever I press "Super R" key, Unity intercepts it and use it to open
  the Dash. I haven't found any options in Unity Tweak Tool or Compiz
  Settings Manager to prevent Unity from doing this. Aforementioned
  utilities do not distinguish between Left Super and Right Super keys.

  Expected behavior:
  Unity should use only left Super key for opening the Dash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Sep  4 15:09:57 2014
  InstallationDate: Installed on 2014-08-28 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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/1365469/+subscriptions

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

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

[Petr Jac]

Any chance to get fix this bug?
I'm also affected by this bus - running ubuntu 14.04.1 i386 as LTSP. 
Indicator-session crashs with SIGSEGV (acces memory not permited).
VERSION: 12.10.5+14.04.20140410-0ubuntu1

** Changed in: indicator-session (Ubuntu)
   Status: Expired => Confirmed

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

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

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

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140214-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Mar 11 14:48:23 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2014-03-05 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140304)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  SegvAnalysis:
   Segfault happened at: 0x8056643 <_start+945>:movzbl (%edi),%eax
   PC (0x08056643) ok
   source "(%edi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  Stacktrace:
   #0  0x08056643 in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1365401] Re: No POT file in source tree

[Sebastien Bacher]

Thanks for the bug report, what do you mean "not translatable"?

The template is generated during the package build by dh_translations,
https://launchpadlibrarian.net/177420379/buildlog_ubuntu-utopic-i386.indicator-sound_12.10.2%2B14.10.20140611-0ubuntu1_UPLOADING.txt.gz

"   dh_translations -O--parallel -O--fail-missing
Building indicator-sound.pot...
...
Wrote indicator-sound.pot"

The project is translatable then on
https://translations.launchpad.net/ubuntu/utopic/+source/indicator-sound

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

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

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

Title:
  No POT file in source tree

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

Bug description:
  There is no POT file for this application in the source tree and it is
  not translatable.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ActionStates: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

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

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

[Dx-packages] [Bug 1365039] Re: Could not get session id for session

[Elfy]

I appear to see the same thing - though in an install I accepted ALL
except lightdm update.

This is an Xubuntu install - nothing in lightdm.conf.d/ and no
/etc/lightdm/lightdm.conf at all

reported lp:1365336 against lightdm

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

Title:
  Could not get session id for session

Status in Light Display Manager:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed

Bug description:
  A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm 
(1.11.8-0ubuntu1).
  On that pc, i've closed the session then shutdown: everything was stable, and 
its a fresh standard installation using upstart for booting.

  Here are the troubles met at the next cold boot (verbosy mode):

  - the boot process goes well until "Add swap on /dev/sdb2" as
  expected, but then nothing, only hdd activity continuing hardly
  scanning, and no errors/warnings printed.  Had to force a hardware's
  reset, can't call tty1-6 (system not responsive ??)

  - second cold boot: the system load fsck on the /home partition, then
  the process continue to boot, made a pause at load the swap partition
  again, the hdd was activity working a few (long) seconds, so i've
  tried to switch to tty1 and successed. I've reconfigured lightdm and
  tried  startx : it seemed to continue its processes even if the hdd
  was again hardly scanning unsually. But i only got a black screen: no
  mouse pointer, no tty. So reboot again.

  - third try: same issue, but was able to open tty when it did a pause
  at swap partition loading: so i reconfigured lightdm and choose gdm as
  default that time. Startx was ran and after some hard hdd scanning, it
  finally loaded a degraded login screen: no mouse but the keyboard was
  working. After login validation, gnome-shell appeared as expected, but
  again no mouse; a ctrl+alt+T opened a terminal, where i'm right now,
  to report that issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 7-2
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic i686
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Sep  3 17:15:43 2014
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365039] Re: Could not get session id for session

[Launchpad Bug Tracker]

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

** Changed in: systemd-shim (Ubuntu)
   Status: New => Confirmed

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

Title:
  Could not get session id for session

Status in Light Display Manager:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed

Bug description:
  A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm 
(1.11.8-0ubuntu1).
  On that pc, i've closed the session then shutdown: everything was stable, and 
its a fresh standard installation using upstart for booting.

  Here are the troubles met at the next cold boot (verbosy mode):

  - the boot process goes well until "Add swap on /dev/sdb2" as
  expected, but then nothing, only hdd activity continuing hardly
  scanning, and no errors/warnings printed.  Had to force a hardware's
  reset, can't call tty1-6 (system not responsive ??)

  - second cold boot: the system load fsck on the /home partition, then
  the process continue to boot, made a pause at load the swap partition
  again, the hdd was activity working a few (long) seconds, so i've
  tried to switch to tty1 and successed. I've reconfigured lightdm and
  tried  startx : it seemed to continue its processes even if the hdd
  was again hardly scanning unsually. But i only got a black screen: no
  mouse pointer, no tty. So reboot again.

  - third try: same issue, but was able to open tty when it did a pause
  at swap partition loading: so i reconfigured lightdm and choose gdm as
  default that time. Startx was ran and after some hard hdd scanning, it
  finally loaded a degraded login screen: no mouse but the keyboard was
  working. After login validation, gnome-shell appeared as expected, but
  again no mouse; a ctrl+alt+T opened a terminal, where i'm right now,
  to report that issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 7-2
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic i686
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Sep  3 17:15:43 2014
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1358890] Re: [Notifications] Competing notifications when two alarms kick at the same time

[Giorgio Venturi]

** Description changed:

  A cousin of bug #1354406
  
  Some of the early testers are hitting a use case that we didn't account
  for, that of multiple alarms set for the same time.
  
  Indicator-datetime currently tries to pull up notifications for, and
  play sounds for, both notifications. That's happening by accident and is
  clearly not the right approach.
  
  I can think of a couple of approaches we might take:
  
- (1) Queue the alarms such that only one triggers at a time. This has the
- advantage of being simple, both in concept and in code. I'm not certain
- this is the most user-friendly approach, as it could be frustrating have
- to dismiss a queue of alarms.
+ -- SOLUTION --
+ If 2 or more alarms have been triggered, the notification at any time will 
display:
+   Title: 2 Alarms
+   Subtitle: [Label 1] 10:00, [Label 2] 10:01
  
- (2) Somehow fold multiple alarms together. This has the advantage of
- being friendlier to the user as only a single snooze/dismiss prompt
- would be given. However it opens other questions, e.g. which of the
- alarms' sounds should play?
- 
- Of these two I slghtly prefer (1) for its simplicity; however, neither
- of these options seems perfect and I'm hoping Design may have a better
- suggestion
+ The sound of the first alarm will be played. If they have the same time,
+ the one that has been created first.

** Changed in: ubuntu-ux
   Status: Confirmed => Fix Committed

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

Title:
  [Notifications] Competing notifications when two alarms kick at the
  same time

Status in The Date and Time Indicator:
  Triaged
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  A cousin of bug #1354406

  Some of the early testers are hitting a use case that we didn't
  account for, that of multiple alarms set for the same time.

  Indicator-datetime currently tries to pull up notifications for, and
  play sounds for, both notifications. That's happening by accident and
  is clearly not the right approach.

  I can think of a couple of approaches we might take:

  -- SOLUTION --
  If 2 or more alarms have been triggered, the notification at any time will 
display:
Title: 2 Alarms
Subtitle: [Label 1] 10:00, [Label 2] 10:01

  The sound of the first alarm will be played. If they have the same
  time, the one that has been created first.

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

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

[Dx-packages] [Bug 1365039] Re: Could not get session id for session

[Laércio de Sousa]

Reading your lightdm log, it seems LightDM cannot load seat0 for your
case.

Do you have any custom config file under /etc/lightdm/lightdm.conf.d (or
/etc/lightdm/lightdm.conf)? Specially, do you set option "start-default-
seat=false" explicitly?

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

Title:
  Could not get session id for session

Status in Light Display Manager:
  New
Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm 
(1.11.8-0ubuntu1).
  On that pc, i've closed the session then shutdown: everything was stable, and 
its a fresh standard installation using upstart for booting.

  Here are the troubles met at the next cold boot (verbosy mode):

  - the boot process goes well until "Add swap on /dev/sdb2" as
  expected, but then nothing, only hdd activity continuing hardly
  scanning, and no errors/warnings printed.  Had to force a hardware's
  reset, can't call tty1-6 (system not responsive ??)

  - second cold boot: the system load fsck on the /home partition, then
  the process continue to boot, made a pause at load the swap partition
  again, the hdd was activity working a few (long) seconds, so i've
  tried to switch to tty1 and successed. I've reconfigured lightdm and
  tried  startx : it seemed to continue its processes even if the hdd
  was again hardly scanning unsually. But i only got a black screen: no
  mouse pointer, no tty. So reboot again.

  - third try: same issue, but was able to open tty when it did a pause
  at swap partition loading: so i reconfigured lightdm and choose gdm as
  default that time. Startx was ran and after some hard hdd scanning, it
  finally loaded a degraded login screen: no mouse but the keyboard was
  working. After login validation, gnome-shell appeared as expected, but
  again no mouse; a ctrl+alt+T opened a terminal, where i'm right now,
  to report that issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 7-2
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic i686
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Sep  3 17:15:43 2014
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1365435] Re: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1365435/+attachment/4195276/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1365435/+attachment/4195278/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1365435/+attachment/4195280/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1365435/+attachment/4195281/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1365435/+attachment/4195282/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1365435/+attachment/4195283/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1365435/+attachment/4195284/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1298654

** Tags removed: need-amd64-retrace

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

Title:
  unity-panel-service crashed with SIGSEGV in ffi_call_unix64()

Status in “unity” package in Ubuntu:
  New

Bug description:
  This happened at the same time as LP:1364285
  (except in shotwell, not nautilus)

  Possibly related to menu items changing?

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-services 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Sep  4 20:39:16 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2014-09-03 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa78364ae1f:mov(%r12),%rdi
   PC (0x7fa78364ae1f) ok
   source "(%r12)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1365435] [NEW] unity-panel-service crashed with SIGSEGV in ffi_call_unix64()

[Michael Blennerhassett]

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

Public bug reported:

This happened at the same time as LP:1364285
(except in shotwell, not nautilus)

Possibly related to menu items changing?

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-services 7.3.1+14.10.20140811-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
Uname: Linux 3.16.0-12-generic x86_64
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu Sep  4 20:39:16 2014
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationDate: Installed on 2014-09-03 (1 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_AU:en
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa78364ae1f:  mov(%r12),%rdi
 PC (0x7fa78364ae1f) ok
 source "(%r12)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash utopic

** Information type changed from Private to Public

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

Title:
  unity-panel-service crashed with SIGSEGV in ffi_call_unix64()

Status in “unity” package in Ubuntu:
  New

Bug description:
  This happened at the same time as LP:1364285
  (except in shotwell, not nautilus)

  Possibly related to menu items changing?

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-services 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Sep  4 20:39:16 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2014-09-03 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa78364ae1f:mov(%r12),%rdi
   PC (0x7fa78364ae1f) ok
   source "(%r12)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

Bug description:
  Happened after initial log on after power up.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140324-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  2 16:02:54 2014
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2014-03-28 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f729bc0392a :movdqu (%rax),%xmm12
   PC (0x7f729bc0392a) ok
   source "(%rax)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%xmm12" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: indicator-session-service crashed with SIGSEGV in strlen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Dx-packages] [Bug 906472] Re: Emoticons not shown on global menu

[Launchpad Bug Tracker]

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

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

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

Title:
  Emoticons not shown on global menu

Status in Unity:
  New
Status in Unity GTK+ module:
  New
Status in “empathy” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Whilst focused on a conversation window, going to Conversation >
  Insert smiley in the global menu, will display a list of blank entires
  where there should be emoticons.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.2.0.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Mon Dec 19 18:39:11 2011
  ExecutablePath: /usr/lib/empathy/empathy-chat
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: empathy
  UpgradeStatus: Upgraded to oneiric on 2011-11-08 (41 days ago)

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

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

[Dx-packages] [Bug 1365421] [NEW] If you move an app icon in unity panel it is pinned in panel automatically

[Giannis]

Public bug reported:

If you open an unpinned app from dash and during work you move this icon
between other pinned icons/apps, it is pinned automatically by its own
and stays there after application close.

For example If I open a .pdf  file with pdf viewer and move "pdf viewer"
icon closer to "Firefox" for productivity purposes, doesn't mean that I
want this icon to stay there after I finish my work.

If I wanted it to stay there I would pin it there on my own.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
Date: Thu Sep  4 13:07:29 2014
InstallationDate: Installed on 2013-04-19 (502 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-21 (135 days ago)

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


** Tags: amd64 apport-bug trusty

** Description changed:

  If you open an unpinned app from dash and during work you move this icon
  between other pinned icons/apps, it is pinned automatically by its own
  and stays there after application close.
  
  For example If I open a .pdf  file with pdf viewer and move "pdf viewer"
  icon closer to "Firefox" for productivity purposes, doesn't mean that I
  want this icon to stay there after I finish my work.
  
- If I wanted to stay there I would pin it there on my own.
+ If I wanted it to stay there I would pin it there on my own.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Thu Sep  4 13:07:29 2014
  InstallationDate: Installed on 2013-04-19 (502 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (135 days 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/1365421

Title:
  If you move an app icon in unity panel it is pinned in panel
  automatically

Status in “unity” package in Ubuntu:
  New

Bug description:
  If you open an unpinned app from dash and during work you move this
  icon between other pinned icons/apps, it is pinned automatically by
  its own and stays there after application close.

  For example If I open a .pdf  file with pdf viewer and move "pdf
  viewer" icon closer to "Firefox" for productivity purposes, doesn't
  mean that I want this icon to stay there after I finish my work.

  If I wanted it to stay there I would pin it there on my own.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Thu Sep  4 13:07:29 2014
  InstallationDate: Installed on 2013-04-19 (502 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (135 days ago)

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

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

[Dx-packages] [Bug 896402] Re: Unity should provide an API for summoning the Dash

[Gizmo Chicken]

What's the status of this request?  Was an  API for summoning the Dash
ever added?  Would be great if the the dash could be summoned directly
from a replacement launcher, such as from Cairo-Dock.

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

Title:
  Unity should provide an API for summoning the Dash

Status in Ayatana Design:
  Confirmed
Status in LibUnity:
  Confirmed
Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  The Unity Dash is slated to replace file browsers as the primary way
  users find and access data. Currently, it is possible for third-party
  applications to request a file browser open, looking for a certain
  extension of file. It should also be possible for third-party
  applications to request the Dash open, looking at a certain scope,
  lens, and filters-combination. Ideally, libunity would provide a D-bus
  API for such a task.

  This was originally an AskUbuntu question, but since sabdfl encouraged
  me to file a bug for this problem, I figure I might as well. The
  question  [ http://askubuntu.com/q/72266/24694 ] provides one example
  of how this API might be used.

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

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

[Dx-packages] [Bug 1350544] Re: Some translations are not loaded

[Jean-Baptiste Lallement]

** Tags added: rtm-i18n

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

Title:
  Some translations are not loaded

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

Bug description:
  The translations for some messages don't seem to be loaded. E.g.
  "Tomorrow" always appears in English in the list of upcoming events
  when sliding down the indicator.

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

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

[Dx-packages] [Bug 1365410] [NEW] No French translations in fr.po

[Jean-Baptiste Lallement]

Public bug reported:

The French strings in fr.po are empty although the project is translated
in launchpad.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Thu Sep  4 09:38:12 2014
InstallationDate: Installed on 2014-09-04 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
SourcePackage: indicator-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf rtm-i18n utopic

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

Title:
  No French translations in fr.po

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

Bug description:
  The French strings in fr.po are empty although the project is
  translated in launchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:38:12 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1350544] Re: Some translations are not loaded

[Jean-Baptiste Lallement]

What is the status of this bug, 'Tomorrow' is still untranslated on
krillin #15 and apparently the string is not extracted from the source
code.

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

Title:
  Some translations are not loaded

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

Bug description:
  The translations for some messages don't seem to be loaded. E.g.
  "Tomorrow" always appears in English in the list of upcoming events
  when sliding down the indicator.

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

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

[Dx-packages] [Bug 1365401] [NEW] No POT file in source tree

[Jean-Baptiste Lallement]

Public bug reported:

There is no POT file for this application in the source tree and it is
not translatable.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ActionStates: ({'desktop-settings': (true, signature '', @av []), 'mic-volume': 
(true, '', [<1.0>]), 'mute': (true, '', []), 'phone-settings': (true, 
'', []), 'volume': (true, 'i', [<0.9399871826171875>]), 'root': (true, '', 
[<{'title': <'Sound'>, 'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Thu Sep  4 09:21:17 2014
InstallationDate: Installed on 2014-09-04 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

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


** Tags: apport-bug armhf rtm-i18n utopic

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

Title:
  No POT file in source tree

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

Bug description:
  There is no POT file for this application in the source tree and it is
  not translatable.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ActionStates: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

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

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

[Dx-packages] [Bug 1327245] Re: No password prompt after session lock

[Launchpad Bug Tracker]

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

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

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

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

Title:
  No password prompt after session lock

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

Bug description:
  After a time of inactivity, my screen lock and i can reopen my session by 
typing my password.
  But sometimes , the password prompt is just missing and i can't type anything.

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

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

[Dx-packages] [Bug 1365039] Re: Could not get session id for session

[dino99]

latest lightdm.log before switching to gdm

** Attachment added: "lightdm.log.old"
   
https://bugs.launchpad.net/lightdm/+bug/1365039/+attachment/4195088/+files/lightdm.log.old

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

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

Title:
  Could not get session id for session

Status in Light Display Manager:
  New
Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm 
(1.11.8-0ubuntu1).
  On that pc, i've closed the session then shutdown: everything was stable, and 
its a fresh standard installation using upstart for booting.

  Here are the troubles met at the next cold boot (verbosy mode):

  - the boot process goes well until "Add swap on /dev/sdb2" as
  expected, but then nothing, only hdd activity continuing hardly
  scanning, and no errors/warnings printed.  Had to force a hardware's
  reset, can't call tty1-6 (system not responsive ??)

  - second cold boot: the system load fsck on the /home partition, then
  the process continue to boot, made a pause at load the swap partition
  again, the hdd was activity working a few (long) seconds, so i've
  tried to switch to tty1 and successed. I've reconfigured lightdm and
  tried  startx : it seemed to continue its processes even if the hdd
  was again hardly scanning unsually. But i only got a black screen: no
  mouse pointer, no tty. So reboot again.

  - third try: same issue, but was able to open tty when it did a pause
  at swap partition loading: so i reconfigured lightdm and choose gdm as
  default that time. Startx was ran and after some hard hdd scanning, it
  finally loaded a degraded login screen: no mouse but the keyboard was
  working. After login validation, gnome-shell appeared as expected, but
  again no mouse; a ctrl+alt+T opened a terminal, where i'm right now,
  to report that issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 7-2
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic i686
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Sep  3 17:15:43 2014
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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