[Dx-packages] [Bug 732653] Re: Menus are hidden by default

2013-09-02 Thread Lonnie Lee Best
I agree.  Any time I installed Ubuntu onto someone's system, I really
have to emphasize to them that they must hover at the top to see these
menus. This is not very intuitive; it has to be figured out the hard way
or shown to you.

New users need to SEE the options available to them, not FEEL AROUND for
them.

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

Title:
  Menus are hidden by default

Status in Ayatana Design:
  New
Status in Unity:
  Confirmed
Status in Unity 2D:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-2d” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.04, Ubuntu 11.10, Ubuntu 12.04

  1. Log in to Unity, and try to connect to a server: File  Connect to 
Server.
  2. Launch Firefox, and try to select an item from the Bookmarks menu.

  What happens:

  1. The File menu, and the rest of Nautilus's menus, are hidden by default.
  - Unless you mouse over it, the menu bar is blank.
  - When you mouse over it, the menus appear.

  2. The Bookmarks menu, and the rest of Firefox's menus, are hidden by 
default.
  - Unless you mouse over it, the menu bar contains only the text Firefox Web 
Browser, which isn't useful at all (especially, but not only, since the real 
name of the application -- Mozilla Firefox -- is already present in the 
window title bar).
  - When you mouse over it, the menus appear, partly but not completely 
replacing the previous text: Firefox W File Edit View….

  What should happen: Menus should be visible by default, so that you
  can know that they exist without scrubbing the screen, and so that you
  can see where a menu is each time you aim for it.

  The current behavior has led some people (including, this week, one of
  my design colleagues) to conclude that Ubuntu applications don't have
  menus when they do. For example
  http://www.techrepublic.com/blog/opensource/gnome-shell-vs-ubuntu-
  unity-which-desktop-wins/2291: One of the most handy menu entries in
  GNOME (for me at least) is the Connect to Server entry in the Places
  menu. This allows the user to connect to nearly any type of server
  quickly and easily. The user can even connect to a Windows Share from
  here. In Unity - you won’t find that. In fact, you will be hard
  pressed to find any means to connect to a server in Ubuntu Unity.

  In bug 720424, Jono Bacon reported that when we did some developer
  tools usability testing last week and on some other occasions when I
  have had someone use Unity, I have noticed that some folks don't
  realize there is a menu there as it is not visible.

  This was confirmed by usability testing of Ubuntu 11.04, where 2 out
  of the 10 people who needed to use a menu item could not find the
  menus at all -- and of the 8 who did find them, 7 did so only when the
  window was maximized. https://lists.ubuntu.com/archives/ubuntu-
  desktop/2011-April/002970.html (Usability testing results of Ubuntu
  11.10 or 12.04 have never been published, but this part of the design
  did not change.)

  Do not confuse this bug with bug 682788, which is about adding an
  option for visibility. Adding any options would not fix this bug,
  which is about menus being hidden *by default*.

  -
  Desired change:

  Implement the 'Enhanced Menu' project for 12.10. This project will
  address the issues described in this bug and also issues described in
  the duplicates of this bus. Note the 'official' bug that tracks the
  implementation of this project is bug #682788

  The following options will be added to 'System Settings/Appearance':

  ---
  Menus
  Location: Global/Local
  Visibility: Hidden/Always displayed
  ---

  More details to follow during the 12.10 cycle... ;-)

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

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


[Dx-packages] [Bug 1205489] Re: Unity is completely translated in Saucy in Russian but shows untranslated

2013-09-02 Thread Sebastien Bacher
** Package changed: unity (Ubuntu) = unity-scope-home (Ubuntu)

** Changed in: unity-scope-home (Ubuntu)
   Importance: Undecided = High

** Changed in: unity-scope-home (Ubuntu)
   Status: Confirmed = Fix Committed

** Also affects: ubuntu-translations
   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/1205489

Title:
  Unity is completely translated in Saucy in Russian but shows
  untranslated

Status in Ubuntu Translations:
  New
Status in “unity-scope-home” package in Ubuntu:
  Fix Committed

Bug description:
  Unity is completely translated in Saucy in Russian but shows
  untranslated.

  I checked out that the files for Unity exist under 
  /usr/share/locale-langpack/ru/LC_MESSAGES/

  All of them 100% translated
  unity_firefox_extension.mo  unity-lens-photos.mo 
  unity-greeter.mounity-lens-shopping.mo 
  unity-lens-applications.mo  unity-lens-video.mo 
  unity-lens-files.mo unity.mo 
  unity-lens-friends.mo   unity_webapps.mo 
  unity-lens-music.mo 

  Also in  Language Selector (Settings) Russian is selected.

  In order to check I added screenshots with unity lenses. You can see
  that some lenses show translated, some contain untranslated strings.

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

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


[Dx-packages] [Bug 1214125] Re: unity-scope-mock stopped working after libunity r276

2013-09-02 Thread Michal Hruby
** Changed in: libunity
   Status: Fix Committed = Fix Released

** Changed in: libunity
Milestone: None = 7.1.0

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

Title:
  unity-scope-mock stopped working after libunity r276

Status in LibUnity:
  Fix Released
Status in “libunity” package in Ubuntu:
  Fix Released

Bug description:
  Sorry for filing this under libunity, but we don't have bugs for the
  mock lens/scope.

  I suspect the culprit to be r276, which changed how ScopeResult
  objects are instantiated. The scope complains as follows:

   unbound method scope_result_create() must be called with ScopeResult
  instance as first argument (got unicode instance instead)

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

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


[Dx-packages] [Bug 1063300] Re: unity-applications-daemon crashed with SIGSEGV in g_strdup()

2013-09-02 Thread Michal Hruby
** Changed in: libunity
   Status: Fix Committed = Fix Released

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

Title:
  unity-applications-daemon crashed with SIGSEGV in g_strdup()

Status in LibUnity:
  Fix Released
Status in libunity 6.0 series:
  Fix Released
Status in “libunity” package in Ubuntu:
  Fix Released
Status in “libunity” source package in Quantal:
  Fix Released

Bug description:
  [Impact]
  - possible crash of lenses in some rare cases

  [Testcase]
  - as the crash is very rare (and probably depends on timing), there's no 
clear test case for this exact issue, please make sure that lenses still work 
as expected

  [Regression potential]
  - unity crashes when it is (re-)started, or when a lens is restarted

  Original description:
  =

  Happened after every logon so far.
  ( Fresh install of Ubuntu 12.10 daily build )

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity-lens-applications 6.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: i386
  Date: Sun Oct  7 17:52:35 2012
  ExecutablePath: /usr/lib/unity-lens-applications/unity-applications-daemon
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta i386 (20121007)
  ProcCmdline: /usr/lib/unity-lens-applications/unity-applications-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb6db66b6:movdqu (%edi),%xmm1
   PC (0xb6db66b6) ok
   source (%edi) (0x0072) not located in a known VMA region (needed 
readable region)!
   destination %xmm1 ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-lens-applications
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libc.so.6
   g_strdup () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libunity.so.9
   unity_protocol_lens_service_activate_with_hints () from 
/usr/lib/i386-linux-gnu/libunity/libunity-protocol-private.so.0
   ?? () from /usr/lib/i386-linux-gnu/libunity.so.9
  Title: unity-applications-daemon crashed with SIGSEGV in g_strdup()
  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/libunity/+bug/1063300/+subscriptions

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


[Dx-packages] [Bug 1029949] Re: unity-webapps-context-daemon crashed with SIGSEGV in g_closure_invoke()

2013-09-02 Thread Michal Hruby
** Changed in: libunity
   Status: Fix Committed = Fix Released

** Changed in: libunity
Milestone: None = 7.1.0

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

Title:
  unity-webapps-context-daemon crashed with SIGSEGV in
  g_closure_invoke()

Status in LibUnity:
  Fix Released
Status in libunity 6.0 series:
  Fix Released
Status in WebApps: libunity:
  Invalid
Status in “libunity” package in Ubuntu:
  Fix Released
Status in “libunity” source package in Quantal:
  Fix Released

Bug description:
  [Impact]

  A common crash seen for example while closing Chromium from Launcher.

  [Test case]

  Run automated tests or try to reproduce the crash manually by closing
  Chromium.

  [Regression potential]

  Low, fixes a segfault from non-null terminated array.

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity-webapps-service 1.8.0-0quantal2 [origin: 
LP-PPA-webapps-preview]
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic x86_64
  ApportVersion: 2.4-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CrashDB: libunity_webapps
  Date: Fri Jul 27 19:14:29 2012
  ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-context-daemon
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcCmdline: /usr/lib/libunity-webapps/unity-webapps-context-daemon Launchpad 
launchpad.net icon://launchpad [Invalid\ UTF-8]
  SegvAnalysis:
   Segfault happened at: 0x7fbf5dd2ded6:movlpd (%rdi),%xmm1
   PC (0x7fbf5dd2ded6) ok
   source (%rdi) (0x000b) not located in a known VMA region (needed 
readable region)!
   destination %xmm1 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libunity-webapps
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  ThirdParty: True
  Title: unity-webapps-context-daemon crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to quantal on 2012-07-24 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Dx-packages] [Bug 1199961] Re: test-gtest-dbus fails and crashes when running TestScope* tests

2013-09-02 Thread Michal Hruby
** Changed in: libunity
   Status: Fix Committed = Fix Released

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

Title:
  test-gtest-dbus fails and crashes when running TestScope* tests

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

Bug description:
  Running test-gtest-dbus leads to this crash and failures
  http://pastebin.ubuntu.com/5862732/

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

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


[Dx-packages] [Bug 1160876] Re: Previews for majority of the 100 scopes don't work

2013-09-02 Thread Michal Hruby
** Changed in: libunity
   Status: Fix Committed = Fix Released

** Changed in: libunity
Milestone: None = 7.1.0

** Changed in: libunity (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Previews for majority of the 100 scopes don't work

Status in LibUnity:
  Fix Released
Status in Unity:
  Invalid
Status in “libunity” package in Ubuntu:
  Fix Released

Bug description:
  Previews for the majority of 100 scopes don't work from Home lens
  view. Right-clicking an item such as a Code coming from local
  launchpad scope gives a completely empty preview in the Dash. While
  it's expected that most of the 100 scopes don't provide a useful
  preview, we should get a generic preview instead (which is
  transparently handled by libunity now), but for some reason it's not
  happening.

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

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


[Dx-packages] [Bug 1189616] Re: libunity doesn't built against vala-0.20

2013-09-02 Thread Michal Hruby
** Changed in: libunity
   Status: New = Confirmed

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

** Changed in: libunity
   Status: Confirmed = Incomplete

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

Title:
  libunity doesn't built against vala-0.20

Status in LibUnity:
  Incomplete
Status in “libunity” package in Ubuntu:
  New
Status in “vala” package in Ubuntu:
  New

Bug description:
  libunity currently builds against vala-0.18 but that version of vala
  has been removed from Debian and will (probably) be removed from
  Saucy. libunity currently fails to build against the current default
  vala in Saucy (vala-0.20).

  Please update libunity to build against vala-0.20 and change your
  build-depends from valac-0.18 (= 0.16) to just valac (= 0.16) to
  make future transitions easier.

  libunity does build against valac-0.16 but 0.16 will be removed as
  soon as packages in Ubuntu don't need it any more.

GEN  unity.deps
GICOMP Unity-6.0.gir
  Unity-6.0.gir:100:81: warning: element annotation from state 9 is unknown, 
ignoring
  Unity-6.0.gir:3263:52: warning: element annotation from state 9 is unknown, 
ignoring
  make[4]: Leaving directory `/«PKGBUILDDIR»/src'
  make[3]: Leaving directory `/«PKGBUILDDIR»/src'
  Making all in extras
  make[3]: Entering directory `/«PKGBUILDDIR»/extras'
GEN  libunity_extras_la_vala.stamp
  make  all-am
  make[4]: Entering directory `/«PKGBUILDDIR»/extras'
CC   libunity_extras_la-unity-extra-preview-player-client.lo
CC   libunity_extras_la-unity-extra-utils.lo
CCLD libunity-extras.la
GICOMP UnityExtras-6.0.gir
  UnityExtras-6.0.gir:-1: In PreviewPlayer: error: type reference 
'ExtrasPreviewPlayerClass' not found
  make[4]: *** [UnityExtras-6.0.typelib] Error 1
  make[4]: Leaving directory `/«PKGBUILDDIR»/extras'

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libunity9 7.0.2daily13.06.06.1-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
  Date: Mon Jun 10 16:18:19 2013
  MarkForUpload: True
  SourcePackage: libunity
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (33 days ago)

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

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


[Dx-packages] [Bug 855735] Re: scope factory has improper search path if prefix is not set at configure time

2013-09-02 Thread Michal Hruby
** Changed in: libunity
   Status: Confirmed = Fix Released

** Changed in: libunity
Milestone: None = 6.14.0

** Changed in: libunity
Milestone: 6.14.0 = 7.0.0

** Changed in: unity
   Status: Confirmed = Fix Released

** Changed in: unity
Milestone: None = 7.0.1

** No longer affects: unity-2d

** No longer affects: libunity (Ubuntu)

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

Title:
  scope factory has improper search path if prefix is not set at
  configure time

Status in LibUnity:
  Fix Released
Status in Unity:
  Fix Released

Bug description:
  if one doesn't set the --prefix at configure time, the path to search
  for remote scopes gets set to NONE/share/unity/lenses/ disabling unity
  from loading remote scopes.

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

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


[Dx-packages] [Bug 620858] Re: Mouse wheel no longer works to change volume

2013-09-02 Thread Oleksandr Senkovych
This bug is happening again in upcoming 13.10 release.

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

Title:
  Mouse wheel no longer works to change volume

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

Bug description:
  Binary package hint: indicator-sound

  Since I update libindicator and indicator-sound this morning,
  scrolling over the sound indicator no longer changes the volume.

  Scrolling over the volume slider still works as expected.

  Watching DBus with dbus-monitor --session doesn't show any output at
  all while scrolling over the sound indicator.

  $ policy libindicator0
  libindicator0:
Installed: 0.3.12-0ubuntu1

  $ policy indicator-sound
  indicator-sound:
Installed: 0.4.0-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: indicator-sound 0.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-16.22-generic 2.6.35.2
  Uname: Linux 2.6.35-16-generic i686
  Architecture: i386
  Date: Thu Aug 19 22:46:26 2010
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-sound

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

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


[Dx-packages] [Bug 1051921] Re: lens-bar-keynavigation periodically writes to /tmp/wut.png

2013-09-02 Thread Treviño
** Changed in: unity/5.0
   Status: In Progress = Fix Committed

** Changed in: unity (Ubuntu Precise)
   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/1051921

Title:
  lens-bar-keynavigation periodically writes to /tmp/wut.png

Status in Unity:
  Fix Committed
Status in Unity 5.0 series:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Precise:
  Fix Committed

Bug description:
  [Impact]

   * Style::SquareButton writes a small png to /tmp/wut.png
   * If a user creates /tmp/wut.png as a symlink to some file on the system 
writeable by the owner of the unity process, then he/she can destroy that file.

  [Test Case]

   * log out
   * log in with the upgraded package
   * open the terminal application using control-alt-T, ensure the terminal is 
focused
   * invoke the HUD by pressing the Alt key and typing f (the HUD menu 
selection 'drop
 down' must appear to trigger the png file write)
   * check for presence of /tmp/wut.png

  [Regression Potential]

   * n/a

  [Other Info]

   * Marc Deslauriers from the security team said it isn't a problem on
  Ubuntu because we have symlink restrictions (in this case part of the
  Yama LSM [1]).

   * We believe, not everyone is necessarily running Yama LSM.

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

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


[Dx-packages] [Bug 1219330] Re: Dash and HUD do not accept keyboard input from ibus English input method

2013-09-02 Thread Christian Dywan
I'm using German and Japanese - I can only type Japanese in Unity on
Saucy, the same setup worked on 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/1219330

Title:
  Dash and HUD do not accept keyboard input from ibus English input
  method

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

Bug description:
  After installing ibus, the Dash's and HUD's search boxes does not
  respond to keyboard input. I can fix the issue either by switching
  ibus to the Anthy (Japanese) input method, in which case I can search
  in Japanese characters only, or by disabling ibus with im-config and
  restarting the X session. I cannot in the same session both type in
  Japanese and search the Dash in English, so this is a major problem.

  Non-Unity applications have no noticeable problem accepting English
  input from ibus.

  Using Saucy Salamander: Unity 7.1, ibus 1.5.3, and anthy 9100h.

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

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


[Dx-packages] [Bug 1217676] Re: performing action on menu incorrectly clears and reloads menu

2013-09-02 Thread Lars Uebernickel
Thanks Bill, I was able to reproduce it with that script and could also
confirm that it is a bug in unity8 caused by qmenumodel. Nick's branch
that ports the messaging indicator to unitymenumodel fixes this issue.

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

** Branch linked: lp:~nick-dedekind/unity8/unitymenumodel.messages

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

Title:
  performing action on menu incorrectly clears and reloads menu

Status in Telephony Service:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  touch image 082713
  indicator-messages 13.10.1+13.10.20130822.5-0ubuntu1

  On touch, if you delete a message from the menu or reply to a text
  message, the entire menu is cleared out (all items removed) and then
  re-added. This is not the desired behavior and is a regression. Items
  should be removed but other items in the list should not be removed
  and rea-dded.

  Steps to reproduce:
  1) make multiple incoming calls or text messages to the phone (or populate it 
programatically)
  2) swipe to delete a message or reply to a text message

  Expected Results:
  - the acted upon item should be removed from the list and all other items 
should not change

  Actual Results:
  - the acted upon items is removed but so are all the other items, then they 
are reloaded. this looks bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1217676/+subscriptions

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


[Dx-packages] [Bug 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

2013-09-02 Thread 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/1197569

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock: Plug-ins:
  Fix Committed
Status in Diodon - GTK+ Clipboard Manager:
  Triaged
Status in Scratch:
  Confirmed
Status in Totem Movie Player:
  Fix Released
Status in Unity:
  Fix Committed
Status in “activity-log-manager” package in Ubuntu:
  Fix Released
Status in “bijiben” package in Ubuntu:
  New
Status in “cairo-dock-plug-ins” package in Ubuntu:
  Triaged
Status in “diodon” package in Ubuntu:
  Fix Released
Status in “folks” package in Ubuntu:
  New
Status in “nautilus” package in Ubuntu:
  Confirmed
Status in “synapse” package in Ubuntu:
  New
Status in “totem” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-lens-applications” package in Ubuntu:
  New
Status in “unity-lens-files” package in Ubuntu:
  New
Status in “unity-lens-video” package in Ubuntu:
  New
Status in “upstart-app-launch” package in Ubuntu:
  New

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

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

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


[Dx-packages] [Bug 1219898] Re: zeitgeist_event_constructv_full declaration makes impossible to compile with -Wunused-function

2013-09-02 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=68851.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-09-02T16:03:38+00:00 Marco Trevisan (Treviño) wrote:

The declaration of zeitgeist_event_constructv_full into zeitgeist-
datamodel.h is static and this leads to a warning that makes impossible
to compile with -Wunused-function.

This seems mostly a Vala issue (maybe lead by
https://bugzilla.gnome.org/show_bug.cgi?id=620675 ?), but the library
should avoid to expose static symbols in a public header anyway.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1219898/comments/0


** Changed in: zeitgeist
   Status: Unknown = Confirmed

** Changed in: zeitgeist
   Importance: Unknown = High

** Bug watch added: GNOME Bug Tracker #620675
   https://bugzilla.gnome.org/show_bug.cgi?id=620675

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

Title:
  zeitgeist_event_constructv_full declaration makes impossible to
  compile with -Wunused-function

Status in Zeitgeist Framework:
  Confirmed
Status in “zeitgeist” package in Ubuntu:
  Confirmed

Bug description:
  The declaration of zeitgeist_event_constructv_full into zeitgeist-
  datamodel.h is static and this leads to a warning that makes
  impossible to compile with -Wunused-function.

  This seems mostly a Vala issue (maybe lead by
  https://bugzilla.gnome.org/show_bug.cgi?id=620675 ?), but the library
  should avoid to expose static symbols in a public header anyway.

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

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


[Dx-packages] [Bug 1219942] [NEW] Power indicator shows wrong time left to charge on Lenovo Ideapad Y580

2013-09-02 Thread Alexandru Bolboaca
Public bug reported:

The power indicator shows time left to charge being 5, 4, 3, 2, 1 or
Time left unknown instead of the real duration.

The time left on battery power is correctly computed. When I remove the
power, it takes a little bit until it switches from the wrong duration
to charge to the real time left on battery power, sometimes going to
sleep as a result of thinking it has little power left.

See the screenshot for the displayed value.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: indicator-power 12.10.6daily13.03.07-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic i686
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Mon Sep  2 21:11:00 2013
InstallationDate: Installed on 2013-01-09 (236 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-power
UpgradeStatus: Upgraded to raring on 2013-09-01 (1 days ago)

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


** Tags: apport-bug i386 raring

** Attachment added: Power indicator.png
   
https://bugs.launchpad.net/bugs/1219942/+attachment/3799757/+files/Power%20indicator.png

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

Title:
  Power indicator shows wrong time left to charge on Lenovo Ideapad Y580

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

Bug description:
  The power indicator shows time left to charge being 5, 4, 3, 2, 1 or
  Time left unknown instead of the real duration.

  The time left on battery power is correctly computed. When I remove
  the power, it takes a little bit until it switches from the wrong
  duration to charge to the real time left on battery power, sometimes
  going to sleep as a result of thinking it has little power left.

  See the screenshot for the displayed value.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Mon Sep  2 21:11:00 2013
  InstallationDate: Installed on 2013-01-09 (236 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to raring on 2013-09-01 (1 days ago)

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

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


[Dx-packages] [Bug 1208204] Re: indicator-sound no longer functions with xfce4-indicator-plugin

2013-09-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  indicator-sound no longer functions with xfce4-indicator-plugin

Status in Sound Menu:
  New
Status in “indicator-bluetooth” package in Ubuntu:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Triaged

Bug description:
  downgrading to the previous version, indicator-
  sound_12.10.2daily13.04.12-0ubuntu1_amd64 from Raring allows the sound
  indicator to function in Saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-sound 12.10.2+13.10.20130731-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.12-0ubuntu2
  Architecture: amd64
  Date: Sun Aug  4 12:20:02 2013
  InstallationDate: Installed on 2012-08-01 (367 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120801)
  MarkForUpload: True
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1213860] [NEW] Wrong string in the Persian translation of calendar indicator

2013-09-02 Thread Hossein Noroozpour
Oh! thank u! I think, I find it.

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

Title:
  Wrong string in the Persian translation of calendar indicator

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

Bug description:
  Look at the screenshot. Instead of displaying the current year number,
  it displays %OY.

  How to reproduce:
  - Go to Language support in the system setting
  - Change the Ubuntu interface language to Persian (fa).
  - Log out and log back in.
  - Click on the date time indicator on the top panel to open the calendar.
  - Look at the current year which should be displayed above the calendar 
table, i.e. above Mon and Sun.

  What should happen:
  - You should see there the year number, e.g. 2013, 2014, etc.

  What happens:
  - You see this string: %OY

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Aug 19 11:56:15 2013
  InstallationDate: Installed on 2013-04-22 (118 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130422)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1219942] Re: Power indicator shows wrong time left to charge on Lenovo Ideapad Y580

2013-09-02 Thread Daniel Letzeisen
Could be related:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1136227

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

Title:
  Power indicator shows wrong time left to charge on Lenovo Ideapad Y580

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

Bug description:
  The power indicator shows time left to charge being 5, 4, 3, 2, 1 or
  Time left unknown instead of the real duration.

  The time left on battery power is correctly computed. When I remove
  the power, it takes a little bit until it switches from the wrong
  duration to charge to the real time left on battery power, sometimes
  going to sleep as a result of thinking it has little power left.

  See the screenshot for the displayed value.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Mon Sep  2 21:11:00 2013
  InstallationDate: Installed on 2013-01-09 (236 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to raring on 2013-09-01 (1 days ago)

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

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


[Dx-packages] [Bug 1099847] Re: [nvidia] Launcher graphics corruption with nvidia driver

2013-09-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-304 (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/1099847

Title:
  [nvidia] Launcher graphics corruption with nvidia driver

Status in Unity:
  New
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have disper installed and often use disper -s and disper -S to
  switch between laptop screen and external screen (a shame that there's
  no native way to do it, btw).

  The screenshot shows how the Launcher showed up after a switch (look
  at the left side of the screen: that's the launcher). Hiding and
  showing it again didn't fix the issue. Switching screen back and forth
  did.

  Other times, after a switch, some windows are black and only redraw
  when you click on or move the mouse over them.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.43  Sun Aug 19 20:20:21 PDT 
2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Tue Jan 15 14:37:40 2013
  DistUpgraded: 2013-01-13 11:55:33,566 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 304.43, 3.2.0-36-generic, i686: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
   
   nvidia-current, 304.43, 3.5.0-22-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 9500M GS] [10de:0405] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15d2]
  InstallationDate: Installed on 2010-06-23 (937 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (2 days ago)
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.8.6-0ubuntu1
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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

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


[Dx-packages] [Bug 1099847] Re: [nvidia] Launcher graphics corruption with nvidia driver

2013-09-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [nvidia] Launcher graphics corruption with nvidia driver

Status in Unity:
  New
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have disper installed and often use disper -s and disper -S to
  switch between laptop screen and external screen (a shame that there's
  no native way to do it, btw).

  The screenshot shows how the Launcher showed up after a switch (look
  at the left side of the screen: that's the launcher). Hiding and
  showing it again didn't fix the issue. Switching screen back and forth
  did.

  Other times, after a switch, some windows are black and only redraw
  when you click on or move the mouse over them.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.43  Sun Aug 19 20:20:21 PDT 
2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Tue Jan 15 14:37:40 2013
  DistUpgraded: 2013-01-13 11:55:33,566 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 304.43, 3.2.0-36-generic, i686: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
   
   nvidia-current, 304.43, 3.5.0-22-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 9500M GS] [10de:0405] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15d2]
  InstallationDate: Installed on 2010-06-23 (937 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (2 days ago)
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.8.6-0ubuntu1
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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

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


[Dx-packages] [Bug 1099847] Re: [nvidia] Launcher graphics corruption with nvidia driver

2013-09-02 Thread AG Restringere
Is this somehow related to the following bug fixed in the 319.49 driver release:
http://www.nvidia.com/object/linux-display-amd64-319.49-driver

* Fixed a bug that resulted in corrupt texels when a previously empty
texture image was specified with glXBindTexImageEXT. In GNOME 3, this
caused gnome-screenshot to produce garbled window screenshots.

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

Title:
  [nvidia] Launcher graphics corruption with nvidia driver

Status in Unity:
  New
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have disper installed and often use disper -s and disper -S to
  switch between laptop screen and external screen (a shame that there's
  no native way to do it, btw).

  The screenshot shows how the Launcher showed up after a switch (look
  at the left side of the screen: that's the launcher). Hiding and
  showing it again didn't fix the issue. Switching screen back and forth
  did.

  Other times, after a switch, some windows are black and only redraw
  when you click on or move the mouse over them.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.43  Sun Aug 19 20:20:21 PDT 
2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Tue Jan 15 14:37:40 2013
  DistUpgraded: 2013-01-13 11:55:33,566 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 304.43, 3.2.0-36-generic, i686: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
   
   nvidia-current, 304.43, 3.5.0-22-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 9500M GS] [10de:0405] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15d2]
  InstallationDate: Installed on 2010-06-23 (937 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (2 days ago)
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.8.6-0ubuntu1
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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

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


[Dx-packages] [Bug 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%

2013-09-02 Thread Tim
I have the same issue as Lionel, with my wireless mouse oscillating
between reporting the correct percentage and 1%. I can confirm that the
above git branch resolves this issue.

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

Title:
  power indicator shows Logitech wireless keyboard and mouse batteries
  with 0%

Status in The Power Indicator:
  Invalid
Status in Upower:
  Incomplete
Status in “indicator-power” package in Ubuntu:
  Invalid
Status in “upower” package in Ubuntu:
  Confirmed
Status in “indicator-power” source package in Raring:
  Invalid
Status in “upower” source package in Raring:
  Won't Fix

Bug description:
  I updated by raring installation and found that the power indicator
  now shows my wireless keyboard and mouse as (missing) and with
  extremely low power. Both the keyboard and mouse work (I'm using them
  to type this bug) and the low battery light on the respective devices
  do not show low power. Even switching to brand new batteries don't
  make the indicator change state.

  I've attached a screenshot of the indicator and a screen shot of the
  power setting dialog which seems to be in conflict with the indicator.

  I've reproduced this behavior with the 3.8.0-0-generic 
  vmlinuz-3.8.0-1-generic kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily13.01.18-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Tue Jan 22 11:39:23 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-05-08 (259 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago)
  --- 
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-05-08 (259 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  Package: upower 0.9.19-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Tags:  raring running-unity
  Uname: Linux 3.8.0-1-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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


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

2013-09-02 Thread Till Kamppeter
Public bug reported:

Crashed when clicking on gear icon in upper right corner of screen (for
settings, log out, reboot, ...).

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-services 7.1.0+13.10.20130829.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
.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: Tue Sep  3 00:49:32 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
ExecutablePath: /usr/lib/unity/unity-panel-service
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2205]
InstallationDate: Installed on 2013-06-05 (89 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
MachineType: LENOVO 334729G
MarkForUpload: True
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=80d8eb01-b0c3-47cc-8dba-1ed122b2be4f ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x40601b:mov0x0(%rbp),%rdx
 PC (0x0040601b) ok
 source 0x0(%rbp) (0x0031) not located in a known VMA region (needed 
readable region)!
 destination %rdx ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_hash_table_foreach()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
dmi.bios.date: 02/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GDET92WW (1.52 )
dmi.board.asset.tag: Not Available
dmi.board.name: 334729G
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGDET92WW(1.52):bd02/05/2013:svnLENOVO:pn334729G:pvrThinkPadTwist:rvnLENOVO:rn334729G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 334729G
dmi.product.version: ThinkPad Twist
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-0ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Sun Sep  1 13:12:41 2013
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 890 
 vendor LGD
xserver.version: 2:1.14.2.901-2ubuntu4

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


** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace saucy 
third-party-packages 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/1220003

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

Status in “unity” package in Ubuntu:
  New

Bug description:
  Crashed when clicking on gear icon in upper right corner of screen
  (for settings, log out, reboot, ...).

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-services 7.1.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  .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: Tue Sep  3 00:49:32 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA 

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

2013-09-02 Thread Apport retracing service
*** This bug is a duplicate of bug 1218222 ***
https://bugs.launchpad.net/bugs/1218222

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1220038/+attachment/3800321/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1220038/+attachment/3800323/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1220038/+attachment/3800324/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1220038/+attachment/3800325/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1220038/+attachment/3800326/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1220038/+attachment/3800327/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1220038/+attachment/3800328/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

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

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

Bug description:
  indicator-printers-service crashed with signal 5 in
  g_simple_async_result_complete()

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-printers 0.1.7daily13.03.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  Date: Thu Aug 29 11:43:13 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-printers-service
  InstallationDate: Installed on 2013-08-28 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130828)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-printers-service
  ProcCwd: /home/u1310
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=ru
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  Signal: 5
  SourcePackage: indicator-printers
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libindicator3.so.7
   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-printers-service crashed with signal 5 in 
g_simple_async_result_complete()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Dx-packages] [Bug 1195874] Re: indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()

2013-09-02 Thread Ernie 07
Is it too early in the development cycle to expect to be able to execute
an installation without experiencing errors?

How can a Beta be released in a few days when I get this error at the
beginning of a USB install of the amd 64-bit desktop timestamped
2013-09-02 08:17?

1.  I could NOT get the CD creator in 13.04 to complete without throwing
an error, so I used 12.04.3 to reformat the usb and change it into a
bootable device using the iso mentioned above.

2.  Booted

3.  Selected install Ubuntu

3.  Checked the two boxes then OK

4.  Waited a short while was greeted with this message

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

Title:
  indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()

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

Bug description:
  After log in

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3+13.10.20130628-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
  CrashCounter: 1
  Date: Fri Jun 28 22:08:49 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-06-10 (18 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130609)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x7fd48ec46040 vfprintf+14352:   repnz scas 
%es:(%rdi),%al
   PC (0x7fd48ec46040) ok
   source %es:(%rdi) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %al ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
  Title: indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()
  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/indicator-datetime/+bug/1195874/+subscriptions

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


[Dx-packages] [Bug 1195874] Re: indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()

2013-09-02 Thread Ernie 07
Missed a step in the prior post, setting the timezone to usa Los Angeles

This time:

1. Booted USB

2. Set timezone

3. Selected Install Unbuntu

4. ERROR

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

Title:
  indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()

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

Bug description:
  After log in

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3+13.10.20130628-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
  CrashCounter: 1
  Date: Fri Jun 28 22:08:49 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-06-10 (18 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130609)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x7fd48ec46040 vfprintf+14352:   repnz scas 
%es:(%rdi),%al
   PC (0x7fd48ec46040) ok
   source %es:(%rdi) (0x0001) not located in a known VMA region (needed 
readable region)!
   destination %al ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
  Title: indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()
  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/indicator-datetime/+bug/1195874/+subscriptions

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