[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon

[Sam Hewitt]

We cannot "scratch this itch" in Unity Tweak Tool, for all the re-
reiterated reasons above.

** Changed in: unity-tweak-tool
   Status: New => Won't Fix

** Changed in: unity-tweak-tool
 Assignee: (unassigned) => Sam Hewitt (snwh)

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

Title:
  Minimize Application's Windows upon clicking its Launcher Icon

Status in Ayatana Design:
  Won't Fix
Status in Canonical Design:
  New
Status in Unity:
  Won't Fix
Status in Unity Tweak Tool:
  Won't Fix
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  What I do miss in Unity is the possibility to click on the app. icon on the 
Unity launcher bar to minimize all windows of that application, not only to 
launch/restore it.
  mlaverdiere's futher addition: 
https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2

  My suggestion would be to modify the interaction-design/process like
  this (*=my modification proposal/2 cents!):

  1) start it, if it hasn't been started yet;
  *2) restore it, if it is minimized;
  *3) focus the app, if it's started, not minimized and has not the focus yet;
  4) spread windows (of app), if app is focused and has multiple windows open;
  *5) minimize it if it is in spread-mode (see 4).

  Note that this bug has over 300 comments and several working but
  rejected patches. This means that this feature probably will never
  land in official Unity! So if you want it, you have to use a patched
  version of Unity.

  There is a working patch for 13.04 ( from comment #322,
  https://bugs.launchpad.net/ayatana-
  design/+bug/733349/+attachment/3573380/+files/minimize.patch ).
  Somebody should set up a PPA (and note it here) to make it easy to
  install the patched version.

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

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

[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon

[Thomas]

Roland, may I ask which environment you have chosen?

(It is sad how little the attention of the developers is in this. Is it
arrogance? The community has a wish but no one cares.)

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

Title:
  Minimize Application's Windows upon clicking its Launcher Icon

Status in Ayatana Design:
  Won't Fix
Status in Canonical Design:
  New
Status in Unity:
  Won't Fix
Status in Unity Tweak Tool:
  New
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  What I do miss in Unity is the possibility to click on the app. icon on the 
Unity launcher bar to minimize all windows of that application, not only to 
launch/restore it.
  mlaverdiere's futher addition: 
https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2

  My suggestion would be to modify the interaction-design/process like
  this (*=my modification proposal/2 cents!):

  1) start it, if it hasn't been started yet;
  *2) restore it, if it is minimized;
  *3) focus the app, if it's started, not minimized and has not the focus yet;
  4) spread windows (of app), if app is focused and has multiple windows open;
  *5) minimize it if it is in spread-mode (see 4).

  Note that this bug has over 300 comments and several working but
  rejected patches. This means that this feature probably will never
  land in official Unity! So if you want it, you have to use a patched
  version of Unity.

  There is a working patch for 13.04 ( from comment #322,
  https://bugs.launchpad.net/ayatana-
  design/+bug/733349/+attachment/3573380/+files/minimize.patch ).
  Somebody should set up a PPA (and note it here) to make it easy to
  install the patched version.

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

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

[Dx-packages] [Bug 1225104] Re: i can't write in french on dashboard with ibus, but i can write in chinese since 13.10 upgrade

[zubozrout]

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

I suppose it I have a related problem. I can type verywhere except for
the dash (& alt+F2) - that is some weird bug in Unity. Also, I made no
changes in my configuration, it stopped working just after I upgraded to
13.10. Arrows work as well.

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

Title:
  i can't write in french on dashboard with ibus, but i can write in
  chinese since 13.10 upgrade

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Since i have upgrade ubuntu 13.04 => 13.10
  it have modify the way unity and ibus work

  when i am on chinese mode =>  i can write everywhere (unity and apps)
  when i am on french mode (azerty) =>  i can write everywhere, excepte on 
dashboard of unity
  but  when i use the arrows of keyboard, i can navigate in dashboard, it just 
when i type letter or number or whatever else it won't write

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Sep 13 19:29:36 2013
  InstallationDate: Installed on 2013-08-15 (28 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-09-13 (0 days ago)

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

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

[Dx-packages] [Bug 1225104] Re: i can't write in french on dashboard with ibus, but i can write in chinese since 13.10 upgrade

[zubozrout]

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

Oh, and I can copy and paste things in the searchbox, also I can delete
characters using backspace and delete.

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

Title:
  i can't write in french on dashboard with ibus, but i can write in
  chinese since 13.10 upgrade

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Since i have upgrade ubuntu 13.04 => 13.10
  it have modify the way unity and ibus work

  when i am on chinese mode =>  i can write everywhere (unity and apps)
  when i am on french mode (azerty) =>  i can write everywhere, excepte on 
dashboard of unity
  but  when i use the arrows of keyboard, i can navigate in dashboard, it just 
when i type letter or number or whatever else it won't write

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Sep 13 19:29:36 2013
  InstallationDate: Installed on 2013-08-15 (28 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-09-13 (0 days ago)

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

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

[Dx-packages] [Bug 1225104] Re: i can't write in french on dashboard with ibus, but i can write in chinese since 13.10 upgrade

[Launchpad Bug Tracker]

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

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

Title:
  i can't write in french on dashboard with ibus, but i can write in
  chinese since 13.10 upgrade

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Since i have upgrade ubuntu 13.04 => 13.10
  it have modify the way unity and ibus work

  when i am on chinese mode =>  i can write everywhere (unity and apps)
  when i am on french mode (azerty) =>  i can write everywhere, excepte on 
dashboard of unity
  but  when i use the arrows of keyboard, i can navigate in dashboard, it just 
when i type letter or number or whatever else it won't write

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Sep 13 19:29:36 2013
  InstallationDate: Installed on 2013-08-15 (28 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-09-13 (0 days ago)

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

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

[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout

[Misha Bazanov]

Are you testing Ubuntu 13.10? May be i'm wrong and this issue it is not
related to layout changer.

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

Title:
  Hotkeys not functional in non-latin keyboard layout

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

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

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

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

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

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

[Dx-packages] [Bug 1223995] Re: compiz crashed with SIGSEGV in unity::launcher::LauncherModel::ReorderAfter()

[Stephen M. Webb]

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

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

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

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

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

Title:
  compiz crashed with SIGSEGV in
  unity::launcher::LauncherModel::ReorderAfter()

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

Bug description:
  Dragged desktop icon to the top of the launcher: freezed

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  Date: Wed Sep 11 18:37:56 2013
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-09-11 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130911)
  MarkForUpload: True
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0xb1282ac2 
<_ZN5unity8launcher13LauncherModel12ReorderAfterERKN3nux9ObjectPtrINS0_20AbstractLauncherIconEEES7_+338>:
   mov(%eax),%edx
   PC (0xb1282ac2) ok
   source "(%eax)" (0x01f5) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   
unity::launcher::LauncherModel::ReorderAfter(nux::ObjectPtr
 const&, nux::ObjectPtr const&) () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
   unity::launcher::LauncherDragWindow::CancelDrag() () from 
/usr/lib/compiz/libunityshell.so
   sigc::internal::slot_call1 >, void, 
unsigned long>::call_it(sigc::internal::slot_rep*, unsigned long const&) () 
from /usr/lib/compiz/libunityshell.so
   sigc::internal::signal_emit1::emit(sigc::internal::signal_impl*, unsigned long const&) () from 
/usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in 
unity::launcher::LauncherModel::ReorderAfter()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1196314] Re: indicator-sync-service crashed with signal 5 in g_simple_async_result_complete()

[Stephen M. Webb]

** Information type changed from Private to Public

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

Title:
  indicator-sync-service crashed with signal 5 in
  g_simple_async_result_complete()

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

Bug description:
  on start session

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-sync 12.10.5daily13.06.19-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic x86_64
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Sun Jun 30 16:56:32 2013
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sync/indicator-sync-service
  InstallationDate: Installed on 2013-03-09 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130120)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sync/indicator-sync-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   LANG=pt_BR.UTF-8
  Signal: 5
  SourcePackage: indicator-sync
  StacktraceTop:
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: indicator-sync-service crashed with signal 5 in 
g_simple_async_result_complete()
  UpgradeStatus: Upgraded to saucy on 2013-06-30 (0 days ago)
  UserGroups: libvirtd lp lpadmin nbd sudo vboxusers vde2-net

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

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

[Dx-packages] [Bug 1047327] Re: Dash - Previews for many file types not yet working

[Stephen M. Webb]

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

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

Title:
  Dash - Previews for many file types not yet working

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  The file previews is missing support for many file types.  Ideally the
  Dash File Preview  we will support previewing all the file types
  supported by preview applications like Gloobus ( http://gloobus.net
  /gloobus-preview/ ) or Gnome Sushi e.g.

  Images: jpeg / png / icns / bmp / svg / gif / psd / xcf
  Documents: pdf / cbr / cbz / doc / xls / odf / ods / odp / ppt
  Source Code: c++ / c# / java / javascript / php / xml / log / sh / python
  Other: folders / ttf / srt / plain text

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

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

[Dx-packages] [Bug 1045269] Re: Dash - Keyboard navigation for the flow view is broken

[Stephen M. Webb]

reducing importance because flow view is no longer a priority

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

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

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

Title:
  Dash - Keyboard navigation for the flow view is broken

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Keyboard navigation for the flow view is currently broken

  When a user moves the focus down to the flow view the far left icon
  should become focused, with the white highlight we use to designate
  that an item is focused in the Dash.  The behaviour of how the flow
  moves using focus should be identical to the interactions used in
  Ubuntu TV, e.g. there should not be any movement when the focus in the
  middle group of icons, and the flow view should start to move when the
  focus reaches the left or right of the visible area.  Review the
  Ubuntu TV interface for details of exactly how this should work.

  The App Lens and the 'Apps Available for Download' category header was
  used to test the above.

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

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

[Dx-packages] [Bug 1045282] Re: Dash - In the flow view, dragging a icon upwards should de-couple the icon so that it can be dragged and dropped

[Stephen M. Webb]

dropping the importance because flow view is no longer a priority

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

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

Title:
  Dash - In the flow view, dragging a icon upwards should de-couple the
  icon so that it can be dragged and dropped

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  In the Flow view, dragging a icon upwards should de-couple the icon so
  that it can be dragged and dropped

  This is so that a user can for example install an application from
  under the 'Apps available to download' category header by dragging one
  of the app icons to the Launcher.  This should trigger the install
  process for that application.

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

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

[Dx-packages] [Bug 1224643] Re: Some TestIconLoader unit tests intermittently fail during Jenkins CI

[PS Jenkins bot]

Fix committed into lp:unity at revision None, scheduled for release in
unity, milestone 7.1.1

** Changed in: unity
   Status: Confirmed => Fix Committed

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

Title:
  Some TestIconLoader unit tests intermittently fail during Jenkins CI

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

Bug description:
  During Jenkins Continuous Integration, we get intermittent
  TestIconLoader unit test failures.  It's usually one or more of the
  following tests:

  TestIconLoader.TestGetOneIcon
  TestIconLoader.TestGetAnnotatedIcon
  TestIconLoader.TestGetColorizedIcon

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

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

[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon

[Roland (Rolandixor) Taylor]

You know, we can stop commenting on this bug as it will never be fixed.
Use another desktop environment. (That's what I'm doing).

Unity Tweak Tool can't fix it, because it requires upstream work which
Canonical driven devs will continually reject.

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

Title:
  Minimize Application's Windows upon clicking its Launcher Icon

Status in Ayatana Design:
  Won't Fix
Status in Canonical Design:
  New
Status in Unity:
  Won't Fix
Status in Unity Tweak Tool:
  New
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  What I do miss in Unity is the possibility to click on the app. icon on the 
Unity launcher bar to minimize all windows of that application, not only to 
launch/restore it.
  mlaverdiere's futher addition: 
https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2

  My suggestion would be to modify the interaction-design/process like
  this (*=my modification proposal/2 cents!):

  1) start it, if it hasn't been started yet;
  *2) restore it, if it is minimized;
  *3) focus the app, if it's started, not minimized and has not the focus yet;
  4) spread windows (of app), if app is focused and has multiple windows open;
  *5) minimize it if it is in spread-mode (see 4).

  Note that this bug has over 300 comments and several working but
  rejected patches. This means that this feature probably will never
  land in official Unity! So if you want it, you have to use a patched
  version of Unity.

  There is a working patch for 13.04 ( from comment #322,
  https://bugs.launchpad.net/ayatana-
  design/+bug/733349/+attachment/3573380/+files/minimize.patch ).
  Somebody should set up a PPA (and note it here) to make it easy to
  install the patched version.

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

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

[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon

[Lonnie Lee Best]

** Tags added: saucy

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

Title:
  Minimize Application's Windows upon clicking its Launcher Icon

Status in Ayatana Design:
  Won't Fix
Status in Canonical Design:
  New
Status in Unity:
  Won't Fix
Status in Unity Tweak Tool:
  New
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  What I do miss in Unity is the possibility to click on the app. icon on the 
Unity launcher bar to minimize all windows of that application, not only to 
launch/restore it.
  mlaverdiere's futher addition: 
https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2

  My suggestion would be to modify the interaction-design/process like
  this (*=my modification proposal/2 cents!):

  1) start it, if it hasn't been started yet;
  *2) restore it, if it is minimized;
  *3) focus the app, if it's started, not minimized and has not the focus yet;
  4) spread windows (of app), if app is focused and has multiple windows open;
  *5) minimize it if it is in spread-mode (see 4).

  Note that this bug has over 300 comments and several working but
  rejected patches. This means that this feature probably will never
  land in official Unity! So if you want it, you have to use a patched
  version of Unity.

  There is a working patch for 13.04 ( from comment #322,
  https://bugs.launchpad.net/ayatana-
  design/+bug/733349/+attachment/3573380/+files/minimize.patch ).
  Somebody should set up a PPA (and note it here) to make it easy to
  install the patched version.

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

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

[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon

[Lonnie Lee Best]

I've added the Unity-Tweak-Tool project to this bug report. Maybe they
can scratch this itch.

I suggest focusing on post #335.

** Also affects: unity-tweak-tool
   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/733349

Title:
  Minimize Application's Windows upon clicking its Launcher Icon

Status in Ayatana Design:
  Won't Fix
Status in Canonical Design:
  New
Status in Unity:
  Won't Fix
Status in Unity Tweak Tool:
  New
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  What I do miss in Unity is the possibility to click on the app. icon on the 
Unity launcher bar to minimize all windows of that application, not only to 
launch/restore it.
  mlaverdiere's futher addition: 
https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2

  My suggestion would be to modify the interaction-design/process like
  this (*=my modification proposal/2 cents!):

  1) start it, if it hasn't been started yet;
  *2) restore it, if it is minimized;
  *3) focus the app, if it's started, not minimized and has not the focus yet;
  4) spread windows (of app), if app is focused and has multiple windows open;
  *5) minimize it if it is in spread-mode (see 4).

  Note that this bug has over 300 comments and several working but
  rejected patches. This means that this feature probably will never
  land in official Unity! So if you want it, you have to use a patched
  version of Unity.

  There is a working patch for 13.04 ( from comment #322,
  https://bugs.launchpad.net/ayatana-
  design/+bug/733349/+attachment/3573380/+files/minimize.patch ).
  Somebody should set up a PPA (and note it here) to make it easy to
  install the patched version.

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

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

[Dx-packages] [Bug 1227056] Re: Many autopilot failures on the unity stack (mostly IBus)

[PS Jenkins bot]

Fix committed into lp:unity at revision None, scheduled for release in
unity, milestone 7.1.1

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

Title:
  Many autopilot failures on the unity stack (mostly IBus)

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

Bug description:
  There are many many AP failures, mostly all IBus tests. For instance:

  http://jenkins.qa.ubuntu.com/job/autopilot-saucy-
  daily_release/1840/testReport/

  This is bad! I guess IBus problems. Maybe new version? Or something
  changed again?

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

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

[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout

[Brandon Schaefer]

Testing in Firefox with Afghani, ctrl+t for new tab works. Though
ctrl+alt+t does now...which would is possibly under gnome-compatibilty
in compiz but one would think things should still work? As im not
sure what the new layout changer did that would cause it to stop
working. Unless it hadn't worked before...as we should still be getting
the same events as before through compiz/unity. A new keyboard layout
changer shouldn't change the type of events we get hmmm. I need to test
if Ctrl+Alt+t worked before the new layouts...

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

Title:
  Hotkeys not functional in non-latin keyboard layout

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

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

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

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

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

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

[Dx-packages] [Bug 1223630] Re: [Alt+Tab] Hover mouse bump accordion icons steals icon focus

[Brandon Schaefer]

** Branch linked: lp:~brandontschaefer/unity/lp.1223630-fix

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

Title:
  [Alt+Tab] Hover mouse bump accordion icons steals icon focus

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

Bug description:
  Same problem as bug 1215630, but only when icons are in accordion
  mode.

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

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

[Dx-packages] [Bug 1227106] Re: indicator-datetime doesn't allow to set time or date

[Nicholas Skaggs]

it is valid that none of it's options work, but as Omer said, the
functionality to set date/time isn't correct.

** Description changed:

- When trying to change date or time from t he datetime indicator the
- clock or calendar app don't open, neither do the indicator settings.
+ None of the links inside the datetime indicator work. Press the clock or
+ calendar app don't open, neither do the indicator settings.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Wed Sep 18 12:44:27 2013
  InstallationDate: Installed on 2013-09-17 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130917.1)
  MarkForUpload: True
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
+  TERM=linux
+  PATH=(custom, no user)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- indicator-datetime doesn't allow to set time or date
+ indicator-datetime menu buttons do nothing

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

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

Title:
  indicator-datetime menu buttons do nothing

Status in The Date and Time Indicator:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  None of the links inside the datetime indicator work. Press the clock
  or calendar app don't open, neither do the indicator settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Wed Sep 18 12:44:27 2013
  InstallationDate: Installed on 2013-09-17 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130917.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1227056] Re: Many autopilot failures on the unity stack (mostly IBus)

[PS Jenkins bot]

Fix committed into lp:unity at revision None, scheduled for release in
unity, milestone 7.1.1

** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  Many autopilot failures on the unity stack (mostly IBus)

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

Bug description:
  There are many many AP failures, mostly all IBus tests. For instance:

  http://jenkins.qa.ubuntu.com/job/autopilot-saucy-
  daily_release/1840/testReport/

  This is bad! I guess IBus problems. Maybe new version? Or something
  changed again?

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

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

[Dx-packages] [Bug 1227106] Re: indicator-datetime doesn't allow to set time or date

[Omer Akram]

indicator datetime is not supposed to do that, rather clicking its
entries should take us to the clock app to be able to set time.

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

Title:
  indicator-datetime menu buttons do nothing

Status in The Date and Time Indicator:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  None of the links inside the datetime indicator work. Press the clock
  or calendar app don't open, neither do the indicator settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Wed Sep 18 12:44:27 2013
  InstallationDate: Installed on 2013-09-17 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130917.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1227306] Re: Unable to tpye character in Unity lense

[박정규]

it is similar with this issue ,elementary os luna's slingshot ibus issue
https://bugs.launchpad.net/slingshot/+bug/1213321

And now I can type in unity lense with this method
sudo apt-get install nabi

and instead of default or ibus
nabi works

** Description changed:

  It is unanle to type character in Unity lense and also connected with unity 
lense such as Alt + F2
  it is unable to type in the Alt + F2 window as well
- 
- it is similar with this issue ,elementary os luna's slingshot ibus issue
- https://bugs.launchpad.net/slingshot/+bug/1213321
- 
- And now I can type in unity lense with this method
- sudo apt-get install nabi 
- 
- and instead of default or ibus
- nabi works   
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 19 03:33:08 2013
  InstallationDate: Installed on 2013-09-18 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130613)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unable to tpye character in Unity lense

Status in “unity” package in Ubuntu:
  New

Bug description:
  It is unanle to type character in Unity lense and also connected with unity 
lense such as Alt + F2
  it is unable to type in the Alt + F2 window as well

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 19 03:33:08 2013
  InstallationDate: Installed on 2013-09-18 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130613)
  MarkForUpload: True
  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/1227306/+subscriptions

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

[Dx-packages] [Bug 1224643] Re: Some TestIconLoader unit tests intermittently fail during Jenkins CI

[Launchpad Bug Tracker]

** Branch linked: lp:~townsend/unity/disable-icon-loader-tests

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

Title:
  Some TestIconLoader unit tests intermittently fail during Jenkins CI

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

Bug description:
  During Jenkins Continuous Integration, we get intermittent
  TestIconLoader unit test failures.  It's usually one or more of the
  following tests:

  TestIconLoader.TestGetOneIcon
  TestIconLoader.TestGetAnnotatedIcon
  TestIconLoader.TestGetColorizedIcon

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

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

[Dx-packages] [Bug 1227306] Re: Unable to tpye character in Unity lense

[박정규]

** Description changed:

- It is unanle to type character in Unity lense and also connected with unity 
lense such as Alt + F2 
+ It is unanle to type character in Unity lense and also connected with unity 
lense such as Alt + F2
  it is unable to type in the Alt + F2 window as well
+ 
+ it is similar with this issue ,elementary os luna's slingshot ibus issue
+ https://bugs.launchpad.net/slingshot/+bug/1213321
+ 
+ And now I can type in unity lense with this method
+ sudo apt-get install nabi 
+ 
+ and instead of default or ibus
+ nabi works   
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 19 03:33:08 2013
  InstallationDate: Installed on 2013-09-18 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130613)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unable to tpye character in Unity lense

Status in “unity” package in Ubuntu:
  New

Bug description:
  It is unanle to type character in Unity lense and also connected with unity 
lense such as Alt + F2
  it is unable to type in the Alt + F2 window as well

  it is similar with this issue ,elementary os luna's slingshot ibus issue
  https://bugs.launchpad.net/slingshot/+bug/1213321

  And now I can type in unity lense with this method
  sudo apt-get install nabi 

  and instead of default or ibus
  nabi works   

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 19 03:33:08 2013
  InstallationDate: Installed on 2013-09-18 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130613)
  MarkForUpload: True
  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/1227306/+subscriptions

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

[Dx-packages] [Bug 1224643] Re: Some TestIconLoader unit tests intermittently fail during Jenkins CI

[Christopher Townsend]

So, this is STILL an issue even with a 15 second timeout:
https://jenkins.qa.ubuntu.com/job/unity-
saucy-i386-autolanding/249/consoleFull

I think something else is going on.

Maybe this in the console log is clue??
ERROR 2013-09-18 19:29:43 unity.glib.dbus.proxy GLibDBusProxy.cpp:194 Unable to 
connect to proxy: Could not connect: No such file or directory
ERROR 2013-09-18 19:29:44 unity.glib.dbus.proxy GLibDBusProxy.cpp:194 Unable to 
connect to proxy: Could not connect: No such file or directory

Is this because of DBus acting up or Jenkins acting up?

** Changed in: unity
   Status: Fix Committed => 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/1224643

Title:
  Some TestIconLoader unit tests intermittently fail during Jenkins CI

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

Bug description:
  During Jenkins Continuous Integration, we get intermittent
  TestIconLoader unit test failures.  It's usually one or more of the
  following tests:

  TestIconLoader.TestGetOneIcon
  TestIconLoader.TestGetAnnotatedIcon
  TestIconLoader.TestGetColorizedIcon

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

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

[Dx-packages] [Bug 1227214] Re: Three- and four-finger gestures on touch screen gone

[Till Kamppeter]

Same problem independent whether I run Mir or X.

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

Title:
  Three- and four-finger gestures on touch screen gone

Status in “unity” package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad Twist (convertible with touch screen) running
  Saucy with standard Unity desktop. Formerly, tapping on a window with
  three fingers added some resize buttons to it, dragging with three
  fingers dragged the window, and tapping anywhere with four fingers
  opened Dash. All this does not work any more.

  What works is a right click by holding a finger on the place where the
  right click should happen and then tapping anywhere else with a second
  finger.

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

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

[Dx-packages] [Bug 1227100] Re: Messy error messages when store has problem

[Omer Akram]

** Package changed: unity-lens-applications (Ubuntu) => unity-scope-
click (Ubuntu)

** Also affects: unity-scope-click
   Importance: Undecided
   Status: New

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

Title:
  Messy error messages when store has problem

Status in Unity Click Scope:
  New
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  Last night there was a prodstack outage causing problems for the
  store, but as a normal user I would not know this.

  I tried to install an app and got a messy error.  See screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-click/+bug/1227100/+subscriptions

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

[Dx-packages] [Bug 1227106] Re: indicator-datetime doesn't allow to set time or date

[Omer Akram]

** Also affects: indicator-datetime
   Importance: Undecided
   Status: New

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

Title:
  indicator-datetime doesn't allow to set time or date

Status in The Date and Time Indicator:
  New
Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  When trying to change date or time from t he datetime indicator the
  clock or calendar app don't open, neither do the indicator settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Wed Sep 18 12:44:27 2013
  InstallationDate: Installed on 2013-09-17 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130917.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 789123] Re: Eclipse crashes/quits without any error messages

[Alexey Khoroshilov]

In my case the problem happens when I launch 32-bit eclipse (Eclipse 3.7.2) on 
64-bit system.
When I launch 64-bit eclipse, it works fine.

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

Title:
  Eclipse crashes/quits without any error messages

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

Bug description:
  Binary package hint: eclipse

  Installed software:
CollabNet Merge Client  2.2.3   
com.collabnet.subversion.merge.feature.feature.group
Eclipse IDE for Java Developers 1.3.2.20110301-1807 epp.package.java
Eclipse Web Developer Tools 
3.2.3.v201102160541-7O7CFbWEMf84qYjGDyP3DNEwcgFU
org.eclipse.wst.web_ui.feature.feature.group
ERMaster1.0.0.v20101001-0024org.insightech.er.feature.feature.group
Google App Engine Java SDK 1.4.01.4.0.v201012021502 
com.google.appengine.eclipse.sdkbundle.e36.feature.1.4.0.feature.group
Google Plugin for Eclipse 3.6   2.3.0.r36v201104261928  
com.google.gdt.eclipse.suite.e36.feature.feature.group
Google Web Toolkit SDK 2.1.12.1.1.v201012170127 
com.google.gwt.eclipse.sdkbundle.e36.feature.2.1.1.feature.group
JNA Library 3.2.7   com.sun.jna.feature.group
Maven Integration for Eclipse (Required)0.12.1.20110112-1712
org.maven.ide.eclipse.feature.feature.group
Subversive Revision Graph (Optional) (Incubation)   0.7.9.I20110124-1700
org.eclipse.team.svn.revision.graph.feature.group
Subversive SVN Connectors   2.2.2.I20110124-1700
org.polarion.eclipse.team.svn.connector.feature.group
Subversive SVN Integration for the Mylyn Project (Optional) (Incubation)
0.7.9.I20110207-1700org.eclipse.team.svn.mylyn.feature.group
Subversive SVN JDT Ignore Extensions (Optional) (Incubation)
0.7.9.I20101203-1700
org.eclipse.team.svn.resource.ignore.rules.jdt.feature.group
Subversive SVN Team Provider (Incubation)   0.7.9.I20110207-1700
org.eclipse.team.svn.feature.group
SVNKit 1.3.5 Implementation (Optional)  2.2.2.I20110124-1700
org.polarion.eclipse.team.svn.connector.svnkit16.feature.group


  Problem:
  When working on Java-classes my Eclipse can suddenly decide to just quit. No 
"Saving workspace" or nothing, it just disappears just like that. This 
typically happens around twice per day. The latest crash today came when i was 
asking for code completion pop-up to appear for a class i was working on.

  I have not found any logs or anything that gives any information about
  these crashes, so please give me some tips for logs you want me to
  check. (This is not serious enough to get in the syslog/dmesg)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: eclipse (not installed)
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri May 27 14:59:00 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eclipse
  UpgradeStatus: Upgraded to natty on 2011-04-29 (28 days ago)
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 11.04
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  NonfreeKernelModules: nvidia
  Package: openjdk-6-jre-headless 6b22-1.10.1-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Tags:  natty
  Uname: Linux 2.6.38-8-generic x86_64
  UpgradeStatus: Upgraded to natty on 2011-04-29 (31 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Dx-packages] [Bug 1227056] Re: Many autopilot failures on the unity stack (mostly IBus)

[Launchpad Bug Tracker]

** Branch linked: lp:~townsend/unity/fix-failing-ap-drag-test

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

Title:
  Many autopilot failures on the unity stack (mostly IBus)

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

Bug description:
  There are many many AP failures, mostly all IBus tests. For instance:

  http://jenkins.qa.ubuntu.com/job/autopilot-saucy-
  daily_release/1840/testReport/

  This is bad! I guess IBus problems. Maybe new version? Or something
  changed again?

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

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

[Dx-packages] [Bug 1227306] [NEW] Unable to tpye character in Unity lense

[박정규]

Public bug reported:

It is unanle to type character in Unity lense and also connected with unity 
lense such as Alt + F2 
it is unable to type in the Alt + F2 window as well

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu Sep 19 03:33:08 2013
InstallationDate: Installed on 2013-09-18 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130613)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 saucy

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

Title:
  Unable to tpye character in Unity lense

Status in “unity” package in Ubuntu:
  New

Bug description:
  It is unanle to type character in Unity lense and also connected with unity 
lense such as Alt + F2 
  it is unable to type in the Alt + F2 window as well

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 19 03:33:08 2013
  InstallationDate: Installed on 2013-09-18 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130613)
  MarkForUpload: True
  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/1227306/+subscriptions

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

[Dx-packages] [Bug 1227056] Re: Many autopilot failures on the unity stack (mostly IBus)

[Brandon Schaefer]

** Branch linked: lp:~brandontschaefer/unity/get-real-ibus-activate-
shortcut

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

Title:
  Many autopilot failures on the unity stack (mostly IBus)

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

Bug description:
  There are many many AP failures, mostly all IBus tests. For instance:

  http://jenkins.qa.ubuntu.com/job/autopilot-saucy-
  daily_release/1840/testReport/

  This is bad! I guess IBus problems. Maybe new version? Or something
  changed again?

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

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

[Dx-packages] [Bug 1227056] Re: Many autopilot failures on the unity stack (mostly IBus)

[Brandon Schaefer]

What changed? Im not sure, possibly ibus went from Ctrl+Space (which the
default was changed to Super+Space, but there was a patch to keep it
Ctrl+Space for some amount of time?). Im linking a branch that gets the
shortcut not matter what it is...hopefully this fixes this issue. As the
issue looks like ibus is not activating.

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

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

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

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

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

Title:
  Many autopilot failures on the unity stack (mostly IBus)

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

Bug description:
  There are many many AP failures, mostly all IBus tests. For instance:

  http://jenkins.qa.ubuntu.com/job/autopilot-saucy-
  daily_release/1840/testReport/

  This is bad! I guess IBus problems. Maybe new version? Or something
  changed again?

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

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

[Dx-packages] [Bug 1224643] Re: Some TestIconLoader unit tests intermittently fail during Jenkins CI

[PS Jenkins bot]

Fix committed into lp:unity at revision None, scheduled for release in
unity, milestone 7.1.1

** Changed in: unity
   Status: Confirmed => Fix Committed

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

Title:
  Some TestIconLoader unit tests intermittently fail during Jenkins CI

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

Bug description:
  During Jenkins Continuous Integration, we get intermittent
  TestIconLoader unit test failures.  It's usually one or more of the
  following tests:

  TestIconLoader.TestGetOneIcon
  TestIconLoader.TestGetAnnotatedIcon
  TestIconLoader.TestGetColorizedIcon

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

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

[Dx-packages] [Bug 1215644] Re: Messaging menu does not change icon when a new message appears

[Launchpad Bug Tracker]

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

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

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

Title:
  Messaging menu does not change icon when a new message appears

Status in The Messaging Menu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “indicator-messages” source package in Saucy:
  Fix Released
Status in “unity8” source package in Saucy:
  Confirmed

Bug description:
  I just pulled indicator-messages from trunk (bzr360) and installed it
  on the phone and rebooted. Now when a new message appears, I get the
  OSD notification and when I open the messaging menu there is indeed a
  pending sms there but The color of the messaging menu did not change.
  See the attached screenshot.

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

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

[Dx-packages] [Bug 1215644] Re: Messaging menu does not change icon when a new message appears

[Omer Akram]

** Changed in: unity8 (Ubuntu Saucy)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Tags added: avengers qa-touch

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

Title:
  Messaging menu does not change icon when a new message appears

Status in The Messaging Menu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “indicator-messages” source package in Saucy:
  Fix Released
Status in “unity8” source package in Saucy:
  Confirmed

Bug description:
  I just pulled indicator-messages from trunk (bzr360) and installed it
  on the phone and rebooted. Now when a new message appears, I get the
  OSD notification and when I open the messaging menu there is indeed a
  pending sms there but The color of the messaging menu did not change.
  See the attached screenshot.

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

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

[Dx-packages] [Bug 1220313] Re: Missed call doesn't highlight messaging icon

[Omer Akram]

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

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

** This bug has been marked a duplicate of bug 1215644
   Messaging menu does not change icon when a new message appears

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

Title:
  Missed call doesn't highlight messaging icon

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

Bug description:
  Unknown version (phablet-flash cdimage-touch --pending on 2013-09-03)

  1. From another phone, call your phone. Do not answer.
  2. On the other phone, hang up.
  3. Look at your phone.

  What you see: The messaging indicator is grey as usual.

  What you should see: The messaging indicator is highlighted.

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

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

[Dx-packages] [Bug 1225387] Re: Multiple entries for each application

[PS Jenkins bot]

Fix committed into lp:unity-lens-applications at revision 368, scheduled
for release in unity-lens-applications, milestone 7.0.0

** Changed in: unity-lens-applications
   Status: Confirmed => Fix Committed

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

Title:
  Multiple entries for each application

Status in Unity Applications Lens:
  Fix Committed
Status in “unity-lens-applications” package in Ubuntu:
  Confirmed

Bug description:
  In each part of the application scope, applications are listed
  multiple times. When doing a search, etc... See screenshot for an
  example in the Installed lens. This also happens when doing a search.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1225387/+subscriptions

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

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

[Daniel Winzen]

Public bug reported:

This crash report was open in the background for a while. After closing
some windows I saw this and I don't know when it happened.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-services 7.1.0+13.10.20130903.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Sep 18 18:25:11 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 13.101, 3.11.0-6-generic, x86_64: installed
 fglrx, 13.101, 3.11.0-7-generic, x86_64: installed
ExecutablePath: /usr/lib/unity/unity-panel-service
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 
6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobility Radeon HD 5650 [1025:0379]
InstallationDate: Installed on 2013-02-27 (203 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130226)
MachineType: Packard Bell EasyNote LM85
MarkForUpload: True
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic 
root=UUID=860ee3d0-2395-44d7-a861-e5341debdde4 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fd23acc826c :  mov
(%rax),%rdi
 PC (0x7fd23acc826c) ok
 source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
dmi.bios.date: 04/28/2011
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.26
dmi.board.asset.tag: No Asset Tag
dmi.board.name: SJV71_CP
dmi.board.vendor: Packard Bell
dmi.board.version: V1.26
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V1.26
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.26:bd04/28/2011:svnPackardBell:pnEasyNoteLM85:pvrV1.26:rvnPackardBell:rnSJV71_CP:rvrV1.26:cvnPackardBell:ct10:cvrV1.26:
dmi.product.name: EasyNote LM85
dmi.product.version: V1.26
dmi.sys.vendor: Packard Bell
version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Fri Sep 13 15:59:39 2013
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.2.901-2ubuntu4
xserver.video_driver: fglrx

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


** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace saucy ubuntu

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

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

Status in “unity” package in Ubuntu:
  New

Bug description:
  This crash report was open in the background for a while. After
  closing some windows I saw this and I don't know when it happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-services 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning

[Dx-packages] [Bug 1227214] Re: Three- and four-finger gestures on touch screen gone

[Stephen M. Webb]

There have been no changes to the Unity stack regarding these gestures.
They continue to work with the latest Saucy packages on my Dell Latitude
XT2.

Can you run the Compiz config settings manager (ccsm) and verify the
"Unity MT Grab Handles" plugin is still enabled?

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

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

Title:
  Three- and four-finger gestures on touch screen gone

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  I have a Lenovo Thinkpad Twist (convertible with touch screen) running
  Saucy with standard Unity desktop. Formerly, tapping on a window with
  three fingers added some resize buttons to it, dragging with three
  fingers dragged the window, and tapping anywhere with four fingers
  opened Dash. All this does not work any more.

  What works is a right click by holding a finger on the place where the
  right click should happen and then tapping anywhere else with a second
  finger.

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

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

[Dx-packages] [Bug 1227214] Re: Three- and four-finger gestures on touch screen gone

[Till Kamppeter]

"Unity MT Grab Handles" plugin is still enabled, but when I click on it
there are three items in it which are all disabled. When I try to enable
one it wants that I choose a keyboard combination for it, but I only
want to use this feature via touch screen gesture.


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

Title:
  Three- and four-finger gestures on touch screen gone

Status in “unity” package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad Twist (convertible with touch screen) running
  Saucy with standard Unity desktop. Formerly, tapping on a window with
  three fingers added some resize buttons to it, dragging with three
  fingers dragged the window, and tapping anywhere with four fingers
  opened Dash. All this does not work any more.

  What works is a right click by holding a finger on the place where the
  right click should happen and then tapping anywhere else with a second
  finger.

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

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

[Dx-packages] [Bug 1140060] Re: SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not installed

[Martin Pitt]

That's by design in GSettings, the GLib developers have repeatedly said
that they won't change this. You  get an assertion about the missing
schema, which is why I originally moved that to Unity as it seems it
just took away that schema.

** Changed in: glib
   Status: New => Opinion

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

Title:
  SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not
  installed

Status in The "G" Library - GLib:
  Opinion
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  This is apparently triggered by SpiderOak 4.8.4.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.3-15ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic i686
  ApportVersion: 2.9-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Sat Mar  2 16:14:44 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2012-05-30 (275 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120421)
  MarkForUpload: True
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2012-11-19 (102 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1225388] Re: More Suggestions is often blank

[Omer Akram]

Right, but in some cases on reboot the 'More suggestions' header does
not appear at all so that's something problematic in the click-scope
that needs fixing.

** No longer affects: unity-lens-applications

** No longer affects: unity-lens-applications (Ubuntu)

** Changed in: unity-scope-click
   Importance: Undecided => Medium

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

** Changed in: unity-scope-click
   Status: New => Confirmed

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

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

Title:
  More Suggestions is often blank

Status in Unity Click Scope:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  Confirmed

Bug description:
  Frequently the More Suggestions scope is empty. Doing a search may
  cause it to fill in. I suspect that poor network connectivity may be a
  factor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-click/+bug/1225388/+subscriptions

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

[Dx-packages] [Bug 331369] Re: regression vs. notification-daemon: positioning when multiple screens are available

[Rael]

Can someone nominate it to Precise too?

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

Title:
  regression vs. notification-daemon: positioning when multiple screens
  are available

Status in Ayatana Design:
  Fix Released
Status in Notify OSD:
  Fix Released
Status in Notify OSD trunk series:
  Fix Released
Status in “notify-osd” package in Ubuntu:
  Fix Released
Status in “notify-osd” source package in Natty:
  Fix Released
Status in “notify-osd” source package in Oneiric:
  Fix Released
Status in “notify-osd” source package in Jaunty:
  Won't Fix

Bug description:
  Binary package hint: notify-osd

  I use nvidia TwinView (one X desktop across two monitors).
  notification-daemon was apparently sensitive to this (presumably
  through Xinerama info?) and would popup on my primary screen.

  notify-osd seems to be unaware of this, and appears in the top right
  of the overall viewport, which is on my secondary screen, and less
  visible, so less useful as a notifier.

  ---

  : "If any windows are
  open, a bubble should appear on whichever display contains the largest
  fraction of the area of the focused window at the moment the bubble
  starts appearing. If no windows are open, a bubble should appear on
  whichever display the first pointer is on at the moment the bubble
  starts appearing."

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

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

[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen

[Ara Pulido]

** Also affects: unity (Ubuntu Precise)
   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/1223739

Title:
  Launcher - unable to reveal Launcher under autohide after using the
  touch screen

Status in OEM Priority Project:
  Confirmed
Status in Unity 5.0 series:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity” source package in Precise:
  New

Bug description:
  To Reproduce (in a system with a touch screen)

  1. Boot the system and don't touch the screen
  2. Set the Launcher to autohide
  3. Move the cursor to the left (using the touchpad or an external mouse)
  4. The Launcher is revealed successfully
  5. Wait until the launcher hides again
  6. Now, touch the screen for the first time (no matter where you touch the 
screen)
  7. Now, use again the touchpad or external mouse to move the cursor to the 
left to reveal the Launcher

  Expected result: Launcher is revealed
  Actual result: Launcher cannot be revealed.

  Additional information:
  1. When the issue happens, can press window key to show dash and launcher (or 
alt-f1 to reveal the launcher), but moving cursor to the left side still can't 
show launcher
  2. There is no crash is observed so far on X or Compiz
  3. Switch to ttyl1 and restart lightdm can recover

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

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

[Dx-packages] [Bug 926793] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Taras]

Recurfaced in Saucy AMD64 Intel graphics card.

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

Title:
  compiz crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

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

Bug description:
  It just crashed when I was in the "run" windows (ALT+F2) and whanted
  to paste my command there

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
  Uname: Linux 3.2.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Sat Feb  4 19:02:18 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(20120201.1)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/i386-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: compiz crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1227214] [NEW] Three- and four-finger gestures on touch screen gone

[Till Kamppeter]

Public bug reported:

I have a Lenovo Thinkpad Twist (convertible with touch screen) running
Saucy with standard Unity desktop. Formerly, tapping on a window with
three fingers added some resize buttons to it, dragging with three
fingers dragged the window, and tapping anywhere with four fingers
opened Dash. All this does not work any more.

What works is a right click by holding a finger on the place where the
right click should happen and then tapping anywhere else with a second
finger.

** Affects: unity (Ubuntu)
 Importance: High
 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/1227214

Title:
  Three- and four-finger gestures on touch screen gone

Status in “unity” package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad Twist (convertible with touch screen) running
  Saucy with standard Unity desktop. Formerly, tapping on a window with
  three fingers added some resize buttons to it, dragging with three
  fingers dragged the window, and tapping anywhere with four fingers
  opened Dash. All this does not work any more.

  What works is a right click by holding a finger on the place where the
  right click should happen and then tapping anywhere else with a second
  finger.

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

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

[Dx-packages] [Bug 1221871] Re: indicator-power-service is a lightly busy all the time

[Alan Pope ㋛]

** No longer affects: touch-preview-images

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

Title:
  indicator-power-service is a lightly busy all the time

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

Bug description:
  In a vain attempt to reduce power on these phone devices I noticed
  that indicator-power-service is using just under 1% of one CPU all the
  time.

   CPU usage:
    PID  ProcessUSR%   SYS%  TOTAL%
    1358 indicator-power-serv   0.05   0.04   0.08 (very light load)

  It seems to be waiting on poll() on a couple of threads which
  cumulatively add up to about 1.68 wakeups a second over a 1 hour
  analysis:

  Top polling system calls:

  PID 
    1369 indicator-power-serv poll1.3462 polls/sec
    1358 indicator-power-serv poll0.3376 polls/sec
   Total  1.6838 polls/sec

  This contributes to a bunch of context switching by these threads:

  Context Switches:
    PID  ProcessVoluntary   Involuntary Total
   Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
    1369 indicator-power-serv10.75 0.1510.90 (moderate)
    1358 indicator-power-serv 3.53 0.07 3.60 (low)
    1372 indicator-power-serv 0.00 0.00 0.00 (idle)
   Total 14.29 0.2214.50

  [ See the attached log, launchpad formatting sucks ]

  I also observed a couple of brk() calls, and a small amount of heap
  growth which may indicate it has a small memory leak, but I am
  speculating on this.

  Attached is a full report from a 1 hour of monitoring indicator-power-
  service for reference.

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

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

[Dx-packages] [Bug 1215638] Re: indicator-sync-service crashed with signal 5 in g_simple_async_result_complete()

[Taras]

Also affects AMD64

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

Title:
  indicator-sync-service crashed with signal 5 in
  g_simple_async_result_complete()

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

Bug description:
  crashed on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-sync 12.10.5daily13.06.19-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  Date: Thu Aug 22 01:48:34 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
  InstallationDate: Installed on 2011-08-23 (730 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
  Signal: 5
  SourcePackage: indicator-sync
  StacktraceTop:
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: indicator-sync-service crashed with signal 5 in 
g_simple_async_result_complete()
  UpgradeStatus: Upgraded to saucy on 2013-05-14 (100 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Dx-packages] [Bug 926793] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Alberto Salvia Novella]

El 18/09/13 18:04, Taras escribió:
> Recurfaced in Saucy AMD64 Intel graphics card.
>
You can then open a new report as explained at 
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  compiz crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

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

Bug description:
  It just crashed when I was in the "run" windows (ALT+F2) and whanted
  to paste my command there

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
  Uname: Linux 3.2.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Sat Feb  4 19:02:18 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(20120201.1)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/i386-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: compiz crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1227106] Re: indicator-datetime doesn't allow to set time or date

[Gema Gomez]

** Tags added: touch-needs-autopilot

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

Title:
  indicator-datetime doesn't allow to set time or date

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

Bug description:
  When trying to change date or time from t he datetime indicator the
  clock or calendar app don't open, neither do the indicator settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Wed Sep 18 12:44:27 2013
  InstallationDate: Installed on 2013-09-17 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130917.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  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/indicator-datetime/+bug/1227106/+subscriptions

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

[Dx-packages] [Bug 1226527] Re: An empty battery is displayed when the device is connected even if it is fully charged

[Max Brustkern]

I think this may be a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1223560
But this has mroe system info.

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

Title:
  An empty battery is displayed when the device is connected even if it
  is fully charged

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

Bug description:
  Mako Build 20130916.3

  TEST CASE:
  1. Connect a fully charged device (in this case mako) to a host over USB
  2. Flash the device
  3. Reboot
  4. Check the state of the battery indicator

  ACTUAL RESULT:
  The battery indicator shows an empty battery (cf screenshot)

  EXPECTED RESULT
  It shows a fully charged battery

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-power 12.10.6+13.10.20130913-0ubuntu2
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Tue Sep 17 10:35:26 2013
  InstallationDate: Installed on 2013-09-16 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130916.3)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1221971] Re: Webapps won't install (Firefox)

[Edwin Pujols]

With the latest update (with -proposed enabled), I can confirm the
prospect looks better. Gmail and Launchpad and Twitter webapps are
installing correctly. ^^

Of course, might need more testing to be 100% sure.

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

Title:
  Webapps won't install (Firefox)

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

Bug description:
  I go to a webapp-able site (say Launchpad.net), Firefox presents me
  the installation dialog. When I click "Install" nothing happens, I
  wait but the webapp icon won't appear on the Launcher (nor within the
  Dash). The .desktop file won't appear on
  `/home/user/.local/share/applications` either.

  After I launched Firefox from the terminal and tried installing a
  webapp I get:

  (firefox:2363): GLib-CRITICAL **: g_variant_get_uint64: assertion
  'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT64)' failed

  (firefox:2363): GLib-CRITICAL **: g_variant_get_uint64: assertion
  'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT64)' failed

  (firefox:2363): GLib-CRITICAL **: g_variant_get_uint32: assertion
  'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT32)' failed

  (firefox:2363): GLib-CRITICAL **: g_variant_get_uint64: assertion
  'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT64)' failed

  ** (firefox:2363): WARNING **: Error resolving package name

  (I am not sure if this is a unity-webapps-service bug or if the bug
  resides in the individual webapps. I have tried with gmail, launchpad,
  twitter.)

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  unity-webapps-service:
    Installed: 2.5.0~+13.10.20130828-0ubuntu1
    Candidate: 2.5.0~+13.10.20130828-0ubuntu1
    Version table:
   *** 2.5.0~+13.10.20130828-0ubuntu1 0
  500 http://do.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-webapps-service 2.5.0~+13.10.20130828-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.10-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  Date: Fri Sep  6 19:16:33 2013
  InstallationDate: Installed on 2013-08-31 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830)
  MarkForUpload: True
  SourcePackage: libunity-webapps
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1182742] Re: compiz crashed with SIGSEGV in std::_Rb_tree, std::_Select1st >,

[Alberto Salvia Novella]

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1182742/+attachment/3683563/+files/CoreDump.gz

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

Title:
  compiz crashed with SIGSEGV in std::_Rb_tree,
  std::_Select1st >,
  std::less, std::allocator > >::find()

Status in “unity” package in Ubuntu:
  New

Bug description:
  I don't know the cause of this crash, but after restarting compiz by
  hand it crashed again several times before I was finally able to get
  my session back on its feet.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue May 21 21:52:41 2013
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2010-09-24 (970 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MarkForUpload: True
  ProcCmdline: compiz --sm-client-id 
1094a19fdf1aaee48f13650563418145090038250047
  SegvAnalysis:
   Segfault happened at: 0x7f85171b7b54 
<_ZNKSt8_Rb_treeImSt4pairIKmP10CompWindowESt10_Select1stIS4_ESt4lessImESaIS4_EE4findERS1_+36>:
  cmp%rcx,0x20(%rdx)
   PC (0x7f85171b7b54) ok
   source "%rcx" ok
   destination "0x20(%rdx)" (0x8020) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   std::_Rb_tree, 
std::_Select1st >, 
std::less, std::allocator > >::find(unsigned long const&) const () from 
/usr/lib/libcompiz_core.so.ABI-20130125
   compiz::private_screen::WindowManager::findWindow(unsigned long) const () 
from /usr/lib/libcompiz_core.so.ABI-20130125
   PrivateCompositeScreen::handleEvent(_XEvent*) () from 
/usr/lib/compiz/libcomposite.so
   CompScreen::handleEvent(_XEvent*) () from 
/usr/lib/libcompiz_core.so.ABI-20130125
   PrivateGLScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in std::_Rb_tree, std::_Select1st >, std::less, 
std::allocator > >::find()
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (15 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev 
sambashare src sudo

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

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

[Dx-packages] [Bug 1179490] Re: [feature request] Prefer exact matches in dash search

[Alberto Salvia Novella]

You're welcome ☔

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

Title:
  [feature request] Prefer exact matches in dash search

Status in One Hundred Paper Cuts:
  New
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When I type terminal I get "Byobu Terminal, Terminal, etc.".

  I want "Terminal" that's why I typed "terminal".

  So I think that search should prefer exact matches (case insensitive,
  of course).

  So that when I want "Terminal" I type "terminal" and press enter.

  Otherwise I need to type "term..." and either select "Terminal" with
  the keyboard or mouse (touch is now a big thing as well).

  Thanks,
  Shahar

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.10-0ubuntu3
  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: Mon May 13 15:41:14 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-12 (943 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (5 days ago)

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

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

[Dx-packages] [Bug 1189038] Re: Dash: music lens needs a source filter

[Alberto Salvia Novella]

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

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

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

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

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

Title:
  Dash: music lens needs a source filter

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Triaged
Status in unity-lens-music:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-lens-music” package in Ubuntu:
  Triaged

Bug description:
  With the new 'smart scopes' & the addition of several music player scopes the 
Music lens can get quite unwieldy & somewhat incomprehensible
  If more than 1 supported player (scope) is installed then tracks & albums get 
duplicated for each with no clear way to discern which icon goes with which 
player, the preview window is similarly uninformative

  --
  Desired resolution:

  - Yes all Lenses with more than one scope should have a "Source" filter 
category
  - This of course also applies to the Music Lens

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

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

[Dx-packages] [Bug 1189041] Re: Inconsistent use of "Sources" in Filter Results in Unity lenses

[Alberto Salvia Novella]

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

** Also affects: ayatana-design
   Importance: Undecided
   Status: New

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

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

Title:
  Inconsistent use of "Sources" in Filter Results in Unity lenses

Status in Ayatana Design:
  New
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  With current Saucy, only the Home lens and the Applications lens has a
  Sources filter in Filter Results.

  For consistency, I recommend that either all lenses use the Sources
  filter or none do. (If you choose to remove the Sources filter, we
  could just direct people to the Search Plugins filter in the
  Applications lens for them to disable scopes that they don't want.)

  Perhaps the Sources filter could be automatically generated from
  scopes that opt-in to a particular lens. In that case, bug1189026 and
  bug 1189040 are probably pre-requisites.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.06.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
  Uname: Linux 3.9.0-4-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun  8 16:55:21 2013
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (31 days ago)

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

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

[Dx-packages] [Bug 1226033] Re: Indicator Panel icons in incorrect order.

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/saucy-proposed/indicator-location

** Branch linked: lp:ubuntu/saucy-proposed/indicator-network

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

Title:
  Indicator Panel icons in incorrect order.

Status in “indicator-bluetooth” package in Ubuntu:
  Invalid
Status in “indicator-location” package in Ubuntu:
  In Progress
Status in “indicator-network” package in Ubuntu:
  In Progress

Bug description:
  Status bar order is given by:
  https://wiki.ubuntu.com/StatusBar

  The network, bluetooth and location have incorrect positions.

  Currently it is (left to right):
  location, bluetooth, network

  Should be (left to right):
  network, bluetooth, location

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

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

[Dx-packages] [Bug 1205097] Re: HUD isn't working

[Launchpad Bug Tracker]

This bug was fixed in the package hud - 13.10.1+13.10.20130918-0ubuntu1

---
hud (13.10.1+13.10.20130918-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Handle searches that result in no tokens as NULL searches. (LP:
#1193700)

  [ Antti Kaijanmäki ]
  * Fix search results when application starts and also include
ALL_WINDOWS context on different searches. (LP: #1205097). (LP:
#1205097)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 320
 -- Ubuntu daily releaseWed, 18 Sep 2013 
07:10:50 +

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

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

Title:
  HUD isn't working

Status in Unity HUD:
  Fix Committed
Status in The Unity 8 shell:
  Invalid
Status in “hud” package in Ubuntu:
  Fix Released

Bug description:
  The HUD doesn't seem to be working at all in the current images.

  Please investigate whether this is an API break / backend issue / UI
  issue and reassign as appropriate.

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

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

[Dx-packages] [Bug 1220215] Re: Stray "Mute" item in Sound menu on Touch

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/saucy-proposed/indicator-sound

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

Title:
  Stray "Mute" item in Sound menu on Touch

Status in Sound Menu:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  Triaged

Bug description:
  ubuntu-touch/20130828.1/saucy-preinstalled-touch-armhf.zip

  1. Open the Sound menu.

  What you see: A "Mute" checkbox item.
  What you should see: No such item.

  

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

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

[Dx-packages] [Bug 1193700] Re: hud-service crashed with SIGSEGV in hud_token_list_distance()

[Launchpad Bug Tracker]

This bug was fixed in the package hud - 13.10.1+13.10.20130918-0ubuntu1

---
hud (13.10.1+13.10.20130918-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Handle searches that result in no tokens as NULL searches. (LP:
#1193700)

  [ Antti Kaijanmäki ]
  * Fix search results when application starts and also include
ALL_WINDOWS context on different searches. (LP: #1205097). (LP:
#1205097)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 320
 -- Ubuntu daily releaseWed, 18 Sep 2013 
07:10:50 +

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

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

Title:
  hud-service crashed with SIGSEGV in hud_token_list_distance()

Status in Unity HUD:
  Fix Committed
Status in “hud” package in Ubuntu:
  Fix Released

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: hud 13.10.1daily13.06.19-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  Date: Sun Jun 23 00:52:20 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service
  InstallationDate: Installed on 2012-12-22 (182 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service
  SegvAnalysis:
   Segfault happened at: 0x42494a : mov
(%rdx),%rsi
   PC (0x0042494a) ok
   source "(%rdx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: hud
  StacktraceTop:
   hud_token_list_distance ()
   hud_result_get_if_matched ()
   ?? ()
   ?? ()
   ?? ()
  Title: hud-service crashed with SIGSEGV in hud_token_list_distance()
  UpgradeStatus: Upgraded to saucy on 2013-06-19 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1215980] Re: [FFe] Freeze exception for converged indicators

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/saucy-proposed/indicator-power

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

Title:
  [FFe] Freeze exception for converged indicators

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

Bug description:
  All indicators on phone, except the networking, are fully converged
  meaning they share the same backend with desktop indicators. While
  we'll be feature complete on the indicator side until FF, we still
  need an exception as the settings application on the phone utilize the
  very same backends. We don't plan to change the code path required for
  the desktop indicators, but only add some more functionality required
  for phone settings. In particular, we're asking for FFe for the
  following packages:

  - indicator-bluetooth
  - indicator-network
  - indicator-location
  - indicator-datetime
  - indicator-power

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

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

[Dx-packages] [Bug 1215980] Re: [FFe] Freeze exception for converged indicators

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-power -
12.10.6+13.10.20130918.2-0ubuntu1

---
indicator-power (12.10.6+13.10.20130918.2-0ubuntu1) saucy; urgency=low

  [ Timo Jyrinki ]
  * The dependency url-dispatcher was fixed to not pull in extra packages
on the desktop images, fixing the issue that caused the previous revert
(FFe bug - LP: #1215980)

  [ Ted Gould ]
  * Use URL dispatcher to show settings on the phone.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 201
 -- Ubuntu daily releaseWed, 18 Sep 2013 
13:57:00 +

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

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

Title:
  [FFe] Freeze exception for converged indicators

Status in “indicator-bluetooth” package in Ubuntu:
  New
Status in “indicator-datetime” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Fix Released

Bug description:
  All indicators on phone, except the networking, are fully converged
  meaning they share the same backend with desktop indicators. While
  we'll be feature complete on the indicator side until FF, we still
  need an exception as the settings application on the phone utilize the
  very same backends. We don't plan to change the code path required for
  the desktop indicators, but only add some more functionality required
  for phone settings. In particular, we're asking for FFe for the
  following packages:

  - indicator-bluetooth
  - indicator-network
  - indicator-location
  - indicator-datetime
  - indicator-power

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

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

[Dx-packages] [Bug 1220215] Re: Stray "Mute" item in Sound menu on Touch

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-sound -
12.10.2+13.10.20130918-0ubuntu1

---
indicator-sound (12.10.2+13.10.20130918-0ubuntu1) saucy; urgency=low

  [ Lars Uebernickel ]
  * Don't show the "Mute" menu item in the phone profile. (LP: #1220215)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 377
 -- Ubuntu daily releaseWed, 18 Sep 2013 
06:24:34 +

** Changed in: indicator-sound (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Stray "Mute" item in Sound menu on Touch

Status in Sound Menu:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-touch/20130828.1/saucy-preinstalled-touch-armhf.zip

  1. Open the Sound menu.

  What you see: A "Mute" checkbox item.
  What you should see: No such item.

  

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

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

[Dx-packages] [Bug 1226033] Re: Indicator Panel icons in incorrect order.

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-network -
0.5.0+13.10.20130918-0ubuntu1

---
indicator-network (0.5.0+13.10.20130918-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Add a phone settings menu to the DBus interface.
  * Moving indicator to be on the far left. (LP: #1226033)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 284
 -- Ubuntu daily releaseWed, 18 Sep 2013 
06:24:28 +

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

Title:
  Indicator Panel icons in incorrect order.

Status in “indicator-bluetooth” package in Ubuntu:
  Invalid
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-network” package in Ubuntu:
  Fix Released

Bug description:
  Status bar order is given by:
  https://wiki.ubuntu.com/StatusBar

  The network, bluetooth and location have incorrect positions.

  Currently it is (left to right):
  location, bluetooth, network

  Should be (left to right):
  network, bluetooth, location

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

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

[Dx-packages] [Bug 1226033] Re: Indicator Panel icons in incorrect order.

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-location -
13.10.0+13.10.20130918-0ubuntu1

---
indicator-location (13.10.0+13.10.20130918-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Moving indicator to be on the right of bluetooth. (LP: #1226033)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 46
 -- Ubuntu daily releaseWed, 18 Sep 2013 
06:23:42 +

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

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

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

Title:
  Indicator Panel icons in incorrect order.

Status in “indicator-bluetooth” package in Ubuntu:
  Invalid
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-network” package in Ubuntu:
  Fix Released

Bug description:
  Status bar order is given by:
  https://wiki.ubuntu.com/StatusBar

  The network, bluetooth and location have incorrect positions.

  Currently it is (left to right):
  location, bluetooth, network

  Should be (left to right):
  network, bluetooth, location

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

-- 
Mailing list: https://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 1179490] Re: [feature request] Prefer exact matches in dash search

[Shahar Or]

Thanks for tending to this.

Sent from mobile נשלח מנייד
On Sep 18, 2013 5:56 PM, "Alberto Salvia Novella" 
wrote:

> ** Changed in: unity (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: unity (Ubuntu)
>Status: Confirmed => Triaged
>
> ** Also affects: hundredpapercuts
>Importance: Undecided
>Status: New
>
> ** Changed in: hundredpapercuts
>  Assignee: (unassigned) => Paper Cuts Ninja (papercuts-ninja)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1179490
>
> Title:
>   [feature request] Prefer exact matches in dash search
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hundredpapercuts/+bug/1179490/+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/1179490

Title:
  [feature request] Prefer exact matches in dash search

Status in One Hundred Paper Cuts:
  New
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When I type terminal I get "Byobu Terminal, Terminal, etc.".

  I want "Terminal" that's why I typed "terminal".

  So I think that search should prefer exact matches (case insensitive,
  of course).

  So that when I want "Terminal" I type "terminal" and press enter.

  Otherwise I need to type "term..." and either select "Terminal" with
  the keyboard or mouse (touch is now a big thing as well).

  Thanks,
  Shahar

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.10-0ubuntu3
  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: Mon May 13 15:41:14 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-12 (943 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (5 days ago)

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

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

[Dx-packages] [Bug 1213220] Re: Power Button: Shut down without confirmation

[Till Kamppeter]

Lifting duplicate status as the bug still persists.

** This bug is no longer a duplicate of bug 1201180
   Pressing power button turns off the PC ignoring the presence of another 
session manager

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

Title:
  Power Button: Shut down without confirmation

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

Bug description:
  I am using Saucy with the standard Unity desktop on the Lenovo
  Thinkpad Twist convertible ultrabook (Intel Core i7).

  Problem is that if I press the power button, the device immediately
  shuts down, without confirmation dialog. There should be a dialog
  asking whether to shut down, reboot, lock screen, suspend, or log out,
  at least in the laptop mode. In tablet mode it should suspend
  immediately (see bug 1213218).

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

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

[Dx-packages] [Bug 1179490] Re: [feature request] Prefer exact matches in dash search

[Alberto Salvia Novella]

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

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

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

** Changed in: hundredpapercuts
 Assignee: (unassigned) => Paper Cuts Ninja (papercuts-ninja)

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

Title:
  [feature request] Prefer exact matches in dash search

Status in One Hundred Paper Cuts:
  New
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When I type terminal I get "Byobu Terminal, Terminal, etc.".

  I want "Terminal" that's why I typed "terminal".

  So I think that search should prefer exact matches (case insensitive,
  of course).

  So that when I want "Terminal" I type "terminal" and press enter.

  Otherwise I need to type "term..." and either select "Terminal" with
  the keyboard or mouse (touch is now a big thing as well).

  Thanks,
  Shahar

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.10-0ubuntu3
  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: Mon May 13 15:41:14 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-12 (943 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (5 days ago)

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

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

[Dx-packages] [Bug 1224340] Re: Visual corruption of Dash

[PS Jenkins bot]

Fix committed into lp:unity at revision None, scheduled for release in
unity, milestone 7.1.1

** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  Visual corruption of Dash

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

Bug description:
  Dash has a visual corruption on the bottom.

  I attached video to see it clearly.

  In Ubuntu 13.04 there were no such problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep 12 11:20:32 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1203]
  InstallationDate: Installed on 2013-07-31 (42 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730)
  JockeyStatus:
   kmod:nvidia_319_updates - nvidia_319_updates (Проприетарные, Активирован, Не 
используется)
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Проприетарные, Выключен, Не используется)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Проприетарные, Выключен, Не используется)
   kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Проприетарные, Выключен, Не используется)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic 
root=UUID=69cd82a7-9a60-46b8-b39a-0985ac8652aa ro noresume ipv6.disable=1
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: SABERTOOTH X58
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Sep 11 22:58:10 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputRuling Technologies Sdn. Bhd. SteelSeries Gaming Device MOUSE, 
id 8
   inputRuling Technologies Sdn. Bhd. SteelSeries Gaming Device 
KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.14.2.901-2ubuntu4

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

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

[Dx-packages] [Bug 1149545] Re: Launcher number for the last (not-locked) application doesn't show up

[Alberto Salvia Novella]

Please execute the following command in a terminal, as it will automatically 
gather debugging information:
apport-collect 1149545
You can learn more about this at https://wiki.ubuntu.com/ReportingBugs

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

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

** Also affects: hundredpapercuts
   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/1149545

Title:
  Launcher number for the last (not-locked) application doesn't show up

Status in One Hundred Paper Cuts:
  New
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  Holding super key shows numbers on each app icon of the launcher.
  In Ubuntu 13.04 daily builds this number for the last application doesn't 
show up and doesn't work as well (see the screenshot attached).
  This never occurs for locked apps. And becomes right when another not-locked 
application is just closed.

  I've seen this problem doesn't occur with GIMP which opens more than
  one window simultaneously and also webapps.

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

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

[Dx-packages] [Bug 1179113] Re: unity crashes with Bus Error when I enable my second monitor.

[Alberto Salvia Novella]

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

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

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

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

Title:
  unity crashes with Bus Error when I enable my second monitor.

Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  My Setup:

  Version: Ubuntu 13.10
  Video Card:  ATI Radeon 2600XT on Open Source Drivers (fglrx is unavailable 
for this card on 13.10)
  Montor #1@1920x1080  
  Monitor #2:@1440x900  on left of Monitor #1

  How to reproduce:

  Open "Displays" from the dash.  Select the secondary monitor.  Turn the 
secondary monitor off (in the settings, not the physical button on the 
monitor), and click "Apply."
  Close "Displays".  Reopen it.  
  Select the secondary monitor.  Turn the secondary monitor on (in the 
settings; not on the monitor, itself.) 
  Put the secondary monitor to the left of the primary monitor. 
  Click "Apply"

  
  Expected Results:
  Secondary Display turns on, and I am prompted to keep my settings or revert.

  Actual Results:
  Brief screen garbage, followed by unity crashing.  Whenever I try to 
resurrect Unity from a either VT or a terminal emulator running in X, I see 
"Bus Error (core dumped)".  This continues until I end my session.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1
  Uname: Linux 3.9.0-1-generic x86_64
  ApportVersion: 2.10-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,grid,mousepoll,place,imgpng,gnomecompat,session,move,resize,regex,vpswitch,unitymtgrabhandles,animation,wall,wobbly,workarounds,fade,expo,scale,ezoom,unityshell,dbus]
  Date: Sat May 11 18:20:31 2013
  InstallationDate: Installed on 2013-02-28 (72 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130225)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-05 (6 days ago)

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

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

[Dx-packages] [Bug 1224621] Re: Removing libunity9 also removes nautilus and other packages

[Launchpad Bug Tracker]

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

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

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

Title:
  Removing libunity9 also removes nautilus and other packages

Status in “libunity” package in Ubuntu:
  Confirmed

Bug description:
  $ apt-get -s remove libunity9
  The following packages will be REMOVED:
brasero brasero-cdrkit deja-dup
deja-dup-backend-gvfs deja-dup-backend-ubuntuone empathy
indicator-appmenu indicator-sound libbrasero-media3-1
libunity9 mcp-account-manager-uoa nautilus nautilus-sendto 
nautilus-sendto-empathy
nautilus-share rhythmbox-plugin-cdrecorder shotwell telepathy-indicator 
xchat-indicator

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libunity9 6.90.2daily13.04.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.4
  Architecture: amd64
  Date: Thu Sep 12 20:05:10 2013
  InstallationDate: Installed on 2011-10-21 (692 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: libunity
  UpgradeStatus: Upgraded to raring on 2013-01-20 (234 days ago)

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

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

[Dx-packages] [Bug 1227159] [NEW] Keyboard shortcuts to switch workspaces borked

[fyo]

Public bug reported:

The keyboard shortcuts to change workspaces have been ctrl-alt-arrow for
a long time now. As of 13.10, the shortcuts for up/down have been
changed to Super-pgup/pgdn. This change makes it exceptionally
cumbersome to quickly switch between different workspaces to the extent
that it is essentially broken and one is limited to either vertical or
horizontal workspaces.

Whereas one could previously cycle through all 4 workspaces in the
default 2x2 grid, this is now practically impossible without a level of
finger dexterity I doubt anyone short of a concert pianist possesses.

I realize that one could argue that this is not a bug, but rather an
"opinion". That would be naive, however, as using all four workspaces
with just keyboard shortcuts is not effectively broken.

The fix is easy. Either revert to ctr-alt-arrow or switch to super-arrow
(in all four directions).

The currently 13.10 mix-and-match approach, however, is a usability
nightmare.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Wed Sep 18 15:42:07 2013
InstallationDate: Installed on 2013-09-14 (3 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130911)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug saucy

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

Title:
  Keyboard shortcuts to switch workspaces borked

Status in “unity” package in Ubuntu:
  New

Bug description:
  The keyboard shortcuts to change workspaces have been ctrl-alt-arrow
  for a long time now. As of 13.10, the shortcuts for up/down have been
  changed to Super-pgup/pgdn. This change makes it exceptionally
  cumbersome to quickly switch between different workspaces to the
  extent that it is essentially broken and one is limited to either
  vertical or horizontal workspaces.

  Whereas one could previously cycle through all 4 workspaces in the
  default 2x2 grid, this is now practically impossible without a level
  of finger dexterity I doubt anyone short of a concert pianist
  possesses.

  I realize that one could argue that this is not a bug, but rather an
  "opinion". That would be naive, however, as using all four workspaces
  with just keyboard shortcuts is not effectively broken.

  The fix is easy. Either revert to ctr-alt-arrow or switch to super-
  arrow (in all four directions).

  The currently 13.10 mix-and-match approach, however, is a usability
  nightmare.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Sep 18 15:42:07 2013
  InstallationDate: Installed on 2013-09-14 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130911)
  MarkForUpload: True
  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/1227159/+subscriptions

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

[Dx-packages] [Bug 1224643] Re: Some TestIconLoader unit tests intermittently fail during Jenkins CI

[Launchpad Bug Tracker]

** Branch linked: lp:~townsend/unity/fix-icon-loader-test2

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

Title:
  Some TestIconLoader unit tests intermittently fail during Jenkins CI

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

Bug description:
  During Jenkins Continuous Integration, we get intermittent
  TestIconLoader unit test failures.  It's usually one or more of the
  following tests:

  TestIconLoader.TestGetOneIcon
  TestIconLoader.TestGetAnnotatedIcon
  TestIconLoader.TestGetColorizedIcon

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

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

[Dx-packages] [Bug 1225387] Re: Multiple entries for each application

[Launchpad Bug Tracker]

** Branch linked: lp:~alecu/unity-lens-applications/deduplicate-clicks

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

Title:
  Multiple entries for each application

Status in Unity Applications Lens:
  Confirmed
Status in “unity-lens-applications” package in Ubuntu:
  Confirmed

Bug description:
  In each part of the application scope, applications are listed
  multiple times. When doing a search, etc... See screenshot for an
  example in the Installed lens. This also happens when doing a search.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1225387/+subscriptions

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

[Dx-packages] [Bug 1226527] Re: An empty battery is displayed when the device is connected even if it is fully charged

[Nicholas Skaggs]

** Tags added: avengers

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

Title:
  An empty battery is displayed when the device is connected even if it
  is fully charged

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

Bug description:
  Mako Build 20130916.3

  TEST CASE:
  1. Connect a fully charged device (in this case mako) to a host over USB
  2. Flash the device
  3. Reboot
  4. Check the state of the battery indicator

  ACTUAL RESULT:
  The battery indicator shows an empty battery (cf screenshot)

  EXPECTED RESULT
  It shows a fully charged battery

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-power 12.10.6+13.10.20130913-0ubuntu2
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Tue Sep 17 10:35:26 2013
  InstallationDate: Installed on 2013-09-16 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130916.3)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1225388] Re: More Suggestions is often blank

[Michał Sawicz]

I believe this might actually be bug #1225391 in unity8 - if you can
*see* the "More suggestions" header, but it's blank (but the size you
would expect - just transparent), that's probably it.

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

Title:
  More Suggestions is often blank

Status in Unity Applications Lens:
  Invalid
Status in Unity Click Scope:
  New
Status in “unity-lens-applications” package in Ubuntu:
  Invalid
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  Frequently the More Suggestions scope is empty. Doing a search may
  cause it to fill in. I suspect that poor network connectivity may be a
  factor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1225388/+subscriptions

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

[Dx-packages] [Bug 1191565] Re: show OSD all skipped tracks, showing wrong thumbnails, repeating, very annoying

[Launchpad Bug Tracker]

This bug was fixed in the package notify-osd -
0.9.35+13.10.20130917.1-0ubuntu1

---
notify-osd (0.9.35+13.10.20130917.1-0ubuntu1) saucy; urgency=low

  [ Sami Jaktholm ]
  * Return correct notification ID to clients. (LP: #1191565)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 470
 -- Ubuntu daily releaseTue, 17 Sep 2013 
22:04:19 +

** Changed in: notify-osd (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  show OSD all skipped tracks, showing wrong thumbnails, repeating, very
  annoying

Status in “notify-osd” package in Ubuntu:
  Fix Released

Bug description:
  Release of Ubuntu: 13.10
  Package Version: Installed: 2.99.1-0ubuntu1
  Expected Results: don't show skipped tracks
  Actual Results: it buffer and show them

  
  Hallo

  TESTCASE
  -open a playlist
  -start playing first song
  -with buttons in sound control skip some tracks
  -the skipped tracks are shown as playing in On Screen Display (or whatever 
its name)

  See attached screencast.

  Thanks
  Fabio

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sun Jun 16 21:09:57 2013
  EcryptfsInUse: Yes
  MarkForUpload: True
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 777594] Re: unity tries to kill all unity-panel-service processes on startup (even other users’)

[Alberto Salvia Novella]

** Tags added: saucy

** Tags added: lucid precise quantal raring

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

Title:
  unity tries to kill all unity-panel-service processes on startup (even
  other users’)

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

Bug description:
  Binary package hint: unity

  The run_unity function in /usr/bin/unity tries to do:
  subprocess.Popen(["killall", "unity-panel-service"])
  If there are other users logged into the system, this spews “Operation not 
permitted” errors (unless you’re logging in as root, in which case it will 
probably actually kill every user’s panel process!).  The killall should at 
least be limited by username, and ideally by session as well.

  By the way, it’s rather sloppy that wait() isn’t called on that subprocess 
object; that results in a zombie killall process being leaked:
  jarthur  25886 25884  0 01:42 ?00:00:00 [killall] 

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 3.8.12-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.39-0.5-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  NonfreeKernelModules: openafs
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  Date: Thu May  5 01:47:46 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.utf8
   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/777594/+subscriptions

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

[Dx-packages] [Bug 1218289] Re: [dialer app] Incoming call (snap decision) not to spec

[Christina Li]

updated bug description

** Description changed:

  Current situation:
  Incoming call appears in snap decision format, but missing:
- - Current screen becomes inactive, except for incoming call snap decision
  - Decision buttons not the right visual colours and assets (missing colour 
and combo button)
+ - background is currently transparent, so can see content below.
  
  Desired solution:
- - As per spec, when receiving an incoming call the snap decision should make 
the current screen inactive (eg grey out) except for the notification. And the 
notification buttons and style should be as per design.
+ - As per spec, when receiving an incoming call the snap decision should be 
solid background. And the notification buttons and style should be as per 
design.
  - See Notification and Snap Decision spec for full details of the final 
signed off design, 
https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit

** Tags added: dialer-app-sept-2013

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

Title:
  [dialer app] Incoming call (snap decision) not to spec

Status in Dialer app for Ubuntu Touch:
  Triaged
Status in Notify OSD:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  New
Status in “dialer-app” package in Ubuntu:
  Triaged
Status in “notify-osd” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Current situation:
  Incoming call appears in snap decision format, but missing:
  - Decision buttons not the right visual colours and assets (missing colour 
and combo button)
  - background is currently transparent, so can see content below.

  Desired solution:
  - As per spec, when receiving an incoming call the snap decision should be 
solid background. And the notification buttons and style should be as per 
design.
  - See Notification and Snap Decision spec for full details of the final 
signed off design, 
https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1218289/+subscriptions

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

[Dx-packages] [Bug 1200773] Re: python2.7 crashed with signal 5 in g_object_new_valist()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_new_valist()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  python2.7:
Installed: 2.7.5-5ubuntu1
Candidate: 2.7.5-5ubuntu1
Version table:
   *** 2.7.5-5ubuntu1 0
  500 http://in.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: python2.7-minimal 2.7.5-5ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic i686
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: i386
  Date: Sat Jul 13 02:24:19 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2012-09-09 (306 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2)
  MarkForUpload: True
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_settings_new () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: Upgraded to saucy on 2013-05-15 (58 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1186363] Re: python2.7 crashed with signal 5 in g_object_newv()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  I tried to open the SpiderOak client.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4-2ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 31 12:55:10 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2010-05-10 (1116 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  MarkForUpload: True
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2013-05-20 (11 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse logcheck lp lpadmin 
mail netdev plugdev powerdev sambashare tape vboxusers video

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

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

[Dx-packages] [Bug 1165132] Re: python2.7 crashed with signal 5 in g_object_newv()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Same crash report has opened every time I start 13.04 for the past
  month or more. Startup applications are SpiderOak (I believe this is a
  python application), Google Music Manager and Dropbox.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4~rc1-4ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr  5 11:03:14 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2011-12-16 (475 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2013-02-21 (42 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin 
plex plugdev sambashare tape video

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

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

[Dx-packages] [Bug 1162897] Re: python2.7 crashed with signal 5 in g_object_newv()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  First boot after upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4~rc1-4ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  1 17:54:42 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2013-03-29 (3 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2013-04-01 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1162940] Re: python2.7 crashed with signal 5 in g_object_newv()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  I don't know what's wrong with python. Automatic bug report took care
  of this.  I haven't noticed any abnormal behavior from my computer.
  Hope this helps.  Please let me know if further info could be used.

  $ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04

  $ uname -a
  Linux ThinkPad-T60 3.8.0-14-generic #24-Ubuntu SMP Fri Mar 22 19:21:28 UTC 
2013 i686 i686 i686 GNU/Linux

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4~rc1-4ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  Date: Mon Apr  1 12:47:43 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2012-12-01 (121 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2013-03-23 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1163571] Re: python2.7 crashed with signal 5 in g_object_newv()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  no extra info, fresh instaled 13.04

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4~rc1-4ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  2 22:39:52 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2013-04-02 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402)
  MarkForUpload: True
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  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/1163571/+subscriptions

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

[Dx-packages] [Bug 1140060] Re: SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not installed

[Stephen M. Webb]

The problem is that glib has a policy of terminating a program (calling
abort()) when settings schemata are not found.  This has nothing to do
with Unity, even though the string 'Unity' can be found in a file in the
commercial SpiderOak package.


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

** Also affects: glib
   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/1140060

Title:
  SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not
  installed

Status in The "G" Library - GLib:
  New
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  This is apparently triggered by SpiderOak 4.8.4.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.3-15ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic i686
  ApportVersion: 2.9-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Sat Mar  2 16:14:44 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2012-05-30 (275 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120421)
  MarkForUpload: True
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2012-11-19 (102 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1165543] Re: python2.7 crashed with signal 5 in g_object_newv()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  The crash occured when I logged in the first time after upgrading from
  QQ to RR final beta. I don't observe any problems occuring to the
  desktop due to that, however.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4~rc1-4ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 23:44:15 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2013-03-26 (10 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2013-04-06 (0 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1167274] Re: python2.7 crashed with signal 5 in g_object_newv()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1140060
   SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not 
installed

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Tks for support ! I love Ubuntu :-)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4-1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 10 06:44:49 2013
  ExecutablePath: /usr/bin/python2.7
  MarkForUpload: True
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2013-03-28 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1225388] Re: More Suggestions is often blank

[Alejandro J. Cura]

** Also affects: unity-scope-click
   Importance: Undecided
   Status: New

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

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: unity-scope-click
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: unity-lens-applications
   Status: Confirmed => Invalid

** Changed in: unity-lens-applications (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  More Suggestions is often blank

Status in Unity Applications Lens:
  Invalid
Status in Unity Click Scope:
  New
Status in “unity-lens-applications” package in Ubuntu:
  Invalid
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  Frequently the More Suggestions scope is empty. Doing a search may
  cause it to fill in. I suspect that poor network connectivity may be a
  factor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1225388/+subscriptions

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

[Dx-packages] [Bug 1227106] [NEW] indicator-datetime doesn't allow to set time or date

[Gema Gomez]

Public bug reported:

When trying to change date or time from t he datetime indicator the
clock or calendar app don't open, neither do the indicator settings.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.1-0ubuntu4
Architecture: armhf
Date: Wed Sep 18 12:44:27 2013
InstallationDate: Installed on 2013-09-17 (0 days ago)
InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130917.1)
MarkForUpload: True
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf avengers qa-touch saucy

** Tags added: avengers qa-touch

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

Title:
  indicator-datetime doesn't allow to set time or date

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

Bug description:
  When trying to change date or time from t he datetime indicator the
  clock or calendar app don't open, neither do the indicator settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20130913-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: armhf
  Date: Wed Sep 18 12:44:27 2013
  InstallationDate: Installed on 2013-09-17 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130917.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  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/indicator-datetime/+bug/1227106/+subscriptions

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

[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen

[Stephen M. Webb]

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

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

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

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

** No longer affects: unity

** Changed in: unity/5.0
   Status: New => Confirmed

** Changed in: unity/5.0
   Importance: Undecided => High

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

Title:
  Launcher - unable to reveal Launcher under autohide after using the
  touch screen

Status in OEM Priority Project:
  Confirmed
Status in Unity 5.0 series:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  To Reproduce (in a system with a touch screen)

  1. Boot the system and don't touch the screen
  2. Set the Launcher to autohide
  3. Move the cursor to the left (using the touchpad or an external mouse)
  4. The Launcher is revealed successfully
  5. Wait until the launcher hides again
  6. Now, touch the screen for the first time (no matter where you touch the 
screen)
  7. Now, use again the touchpad or external mouse to move the cursor to the 
left to reveal the Launcher

  Expected result: Launcher is revealed
  Actual result: Launcher cannot be revealed.

  Additional information:
  1. When the issue happens, can press window key to show dash and launcher (or 
alt-f1 to reveal the launcher), but moving cursor to the left side still can't 
show launcher
  2. There is no crash is observed so far on X or Compiz
  3. Switch to ttyl1 and restart lightdm can recover

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

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

[Dx-packages] [Bug 1227108] [NEW] mplayer makes mouse pointer disappear and sometimes alt-tab switcher

[Rick Spencer]

Public bug reported:

steps:
1. play a video with mplayer
2. use escape to quite mplayer

Result:
the mouse cursor is not visible (though roll over effects are visible)

Note that switching to Vt1 and back again restores the mouse cursor
Note also that sometimes the alt-tab switching GUI disappears

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Sep 18 08:47:21 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3903]
InstallationDate: Installed on 2013-06-18 (92 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130617)
MachineType: LENOVO Lenovo IdeaPad U310 Touch
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic.efi.signed 
root=UUID=f26c50a8-eb98-479c-ad80-1906e5d1e626 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 65CN97WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad U310 Touch
dmi.modalias: 
dmi:bvnLENOVO:bvr65CN97WW:bd01/29/2013:svnLENOVO:pnLenovoIdeaPadU310Touch:pvrLenovoIdeaPadU310Touch:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadU310Touch:
dmi.product.name: Lenovo IdeaPad U310 Touch
dmi.product.version: Lenovo IdeaPad U310 Touch
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Wed Sep 18 08:29:19 2013
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4140 
 vendor AUO
xserver.version: 2:1.14.2.901-2ubuntu4

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


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

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

Title:
  mplayer makes mouse pointer disappear and sometimes alt-tab switcher

Status in “unity” package in Ubuntu:
  New

Bug description:
  steps:
  1. play a video with mplayer
  2. use escape to quite mplayer

  Result:
  the mouse cursor is not visible (though roll over effects are visible)

  Note that switching to Vt1 and back again restores the mouse cursor
  Note also that sometimes the alt-tab switching GUI disappears

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Sep 18 08:47:21 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3903]
  InstallationDate: Installed on 2013-06-18 (92 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130617)
  MachineType: LENOVO Lenovo IdeaPad U310 Touch
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic.efi.signed 
root=UUID=f26c50a8-eb98-479c-ad80-1906e5d1e626 ro quiet splash vt.handoff=7
  SourcePackage: un

[Dx-packages] [Bug 1224756] Re: pulseaudio should give a visual indication when it is recording

[Matthew Paul Thomas]

** Changed in: indicator-sound (Ubuntu Saucy)
 Assignee: (unassigned) => Matthew Paul Thomas (mpt)

** Changed in: indicator-sound (Ubuntu Saucy)
   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/1224756

Title:
  pulseaudio should give a visual indication when it is recording

Status in “indicator-sound” package in Ubuntu:
  Incomplete
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “indicator-sound” source package in Saucy:
  Incomplete
Status in “pulseaudio” source package in Saucy:
  Invalid

Bug description:
  David and the security team (inspired by an observation from Rick)
  discussed that when recording, pulseaudio should somehow unobtrusively
  show the user that it is recording. The easiest thing to do would be
  for pulseaudio to alert indicator-sound which would then turn its icon
  red (similar to indicator-message turning blue with new messages).
  Marking 'high' because apps with access to pulseaudio can currently
  eavedrop on users. If the app is allowed to do networking (the default
  for apps), then it can ship that information off to a server
  somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

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

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

[Dx-packages] [Bug 1227100] [NEW] Messy error messages when store has problem

[Alan Pope ㋛]

Public bug reported:

Last night there was a prodstack outage causing problems for the store,
but as a normal user I would not know this.

I tried to install an app and got a messy error.  See screenshot.

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


** Tags: avengers

** Attachment added: "device-2013-09-18-002651.png"
   
https://bugs.launchpad.net/bugs/1227100/+attachment/3827007/+files/device-2013-09-18-002651.png

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

Title:
  Messy error messages when store has problem

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

Bug description:
  Last night there was a prodstack outage causing problems for the
  store, but as a normal user I would not know this.

  I tried to install an app and got a messy error.  See screenshot.

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

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

[Dx-packages] [Bug 1158291] Re: 13.04 unity is impossibly slow on Eee PC. Was fine under 12.04

[Christopher Barrington-Leigh]

Interestingly, then, 13.10 seems better for me on my machine (see o.p.)

GraphicsCard:
 Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be1] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:84a9]

However, it still fails badly when asked to drive an external monitor.
I've listed that as a new bug
(https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1225095)

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

Title:
  13.04 unity is impossibly slow on Eee PC. Was fine under 12.04

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I'm attaching a video to show the performance under 13.04 on my
  netbook. It's practically unusable under these (essentially default)
  unity settings.  It was fine (in that regard) under 12.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar 21 09:00:06 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be1] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84a9]
  InstallationDate: Installed on 2013-03-19 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130319)
  MachineType: ASUSTeK COMPUTER INC. X101CH
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic 
root=UUID=0f33b064-ba52-4531-a4a5-f6580ff1efef ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X101CH.0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X101CH
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX101CH.0701:bd03/08/2012:svnASUSTeKCOMPUTERINC.:pnX101CH:pvrx.x:rvnASUSTeKCOMPUTERINC.:rnX101CH:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
  dmi.product.name: X101CH
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1
  version.libdrm2: libdrm2 2.4.42-0ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3b1
  xserver.bootTime: Thu Mar 21 08:51:21 2013
  xserver.configfile: default
  xserver.errors: Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu2b1
  xserver.video_driver: modesetting

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

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

[Dx-packages] [Bug 1186363] Re: python2.7 crashed with signal 5 in g_object_newv()

[Matthias Klose]

** Package changed: python2.7 (Ubuntu) => unity (Ubuntu)

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

Title:
  python2.7 crashed with signal 5 in g_object_newv()

Status in “unity” package in Ubuntu:
  New

Bug description:
  I tried to open the SpiderOak client.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: python2.7-minimal 2.7.4-2ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 31 12:55:10 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2010-05-10 (1116 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  MarkForUpload: True
  ProcEnviron:
   LD_LIBRARY_PATH=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_newv()
  UpgradeStatus: Upgraded to raring on 2013-05-20 (11 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse logcheck lp lpadmin 
mail netdev plugdev powerdev sambashare tape vboxusers video

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

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

[Dx-packages] [Bug 1200773] Re: python2.7 crashed with signal 5 in g_object_new_valist()

[Matthias Klose]

looks like a unity issue according the command line

** Package changed: python2.7 (Ubuntu) => unity (Ubuntu)

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

Title:
  python2.7 crashed with signal 5 in g_object_new_valist()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  python2.7:
Installed: 2.7.5-5ubuntu1
Candidate: 2.7.5-5ubuntu1
Version table:
   *** 2.7.5-5ubuntu1 0
  500 http://in.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: python2.7-minimal 2.7.5-5ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic i686
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: i386
  Date: Sat Jul 13 02:24:19 2013
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2012-09-09 (306 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2)
  MarkForUpload: True
  Signal: 5
  SourcePackage: python2.7
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_settings_new () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: python2.7 crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: Upgraded to saucy on 2013-05-15 (58 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1226969] Re: can not change keyboard layout in lock screen

[Misha Bazanov]

I hope screen lock will use lightdm instead of lock window and this bug
dissapear automatically.

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

Title:
  can not change keyboard layout in lock screen

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

Bug description:
  I have two keyboard layouts: english and russian.  My password consist of 
english chars.
  New ubuntu layout changer did not work on lock screen, so if i lock screen 
when russian keyboard layout selected, i can not unlock it. 

  Workaround: click "switch user" and login to own user from lightdm.

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

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