[Dx-packages] [Bug 1318321] Re: "the cache has no package" error when wine update is available

2015-08-24 Thread Hartwig Kolbe
But, "sudo apt-get upgrade" works for me. It installs updates for wine, and the 
error goes away.
Seems the updater does not like wine.

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

Title:
  "the cache has no package" error when wine update is available

Status in Pipelight:
  New
Status in Wine "Compholio" Edition:
  Triaged
Status in indicator-applet package in Ubuntu:
  Confirmed
Status in wine1.6 package in Ubuntu:
  Confirmed

Bug description:
  (Note: This also affects the regular Wine package, see below)

  Hello,

  On Ubuntu 14.04 x64, each time there is an update for wine-compholio
  available, but not installed yet, update-manager has the following
  error in system indicator :

  class 'KeyError' The cache has no package named wine-compholio-i386

  Installing the updates removes the error message.

  I attach a screenshot of the whole message.

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

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


[Dx-packages] [Bug 1386111] Re: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04

2015-08-24 Thread Scott Howard
*** This bug is a duplicate of bug 1380702 ***
https://bugs.launchpad.net/bugs/1380702

Thanks everyone! This has been triaged and is in progress, see bug
#1380702. I'm marking this as a duplicate of that one so we can merge
the conversation over there. Please respond with future comments at bug
#1380702

** This bug has been marked a duplicate of bug 1380702
   No keyboards shortcuts in QT apps

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

Title:
  Keyboard shortcuts not working on Ubuntu 14.10 and 15.04

Status in Unity:
  New
Status in eclipse package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in qtbase package in Ubuntu:
  Confirmed
Status in texmaker package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Keyboard shortcuts do not work. E.g. F1 for quick compile, Strg+F for
  searching

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: texmaker 4.3-1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 27 11:01:56 2014
  InstallationDate: Installed on 2014-04-18 (191 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: texmaker
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago)

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

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


[Dx-packages] [Bug 627195]

2015-08-24 Thread Fdo-bugs
So... this has been sitting in my inbox for a *long* time, sorry.

I think a better approach would be to suggest clients make direct use of
the desktop entry spec, rather than duplicating the methods here. We
already have a property to direct clients to the desktop file for the
media player, so they can check that desktop file for whether it can be
activated, and call the org.freedesktop.Application Activate() method.

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

Title:
  Window management - Apps raised from indicators sometimes dont have
  the focus

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Messaging Menu:
  Fix Released
Status in Messaging Menu 13.04 series:
  Fix Released
Status in The Sound Menu:
  Fix Released
Status in The Sound Menu 13.04 series:
  Fix Released
Status in DBus Menu:
  Triaged
Status in MPRIS:
  Confirmed
Status in Ubuntu One Client:
  Fix Committed
Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in empathy package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in libdbusmenu package in Ubuntu:
  Confirmed
Status in tomboy package in Ubuntu:
  Confirmed
Status in ubuntuone-client package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 11.10 beta
  compiz 1:0.9.5.94+bzr2803-0ubuntu5
  unity 4.16.0-0ubuntu1

  1. open banshee, start a song in it and minimize
  2. open another application lets say gnome-terminal
  3. click on the sound menu and select banshee

  What happens
  banshee icon in the launcher wiggles and banshee main window is not shown

  What should happen
  banshee main window should come to focus

  This is a long standing bug which Ted Gould thinks should be fixed at
  window manager's level.

  Some other observations=
  The problem wont happen
  1. if every other app is minimized or
  2. Banshee is the only opened app or
  3. after opening gnome-terminal, banshee window is closed so that it hides to 
the SoundMenu and opened again

  =Comment from Ted Gould=
   tedg, Hi! any thoughts on the long standing bug 627195 ? Its been 
there before unity so I guess we can conclude unity not to be responsible

   om26er, My thought is that window managers should $%#$ get
  fixed... though I haven't convinced smspillaz of it yet.

  =The good rule=
  3v1n0: Indicators should present the application windows by passing to them 
the timestamp of the menu item activation event.

  Unfortunately for indicator-sound, this is not trival as it sounds, since it 
needs a change to the MPRIS dbus specification.
  See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 
for more informations.

  For what concerns libappindicator based indicators (such as the one used by 
tomboy), since it's not currently possible in libdbusmenu to pass the event 
during activation (so that clients will be able to get the proper timestamp 
using gtk_get_current_event_time), there are two "hackish" ways:
  1. Use the server time to present a window:
     https://bugzilla.gnome.org/show_bug.cgi?id=688830
  2. Get the event timestamp from the dbus-menu linked to the gtk-menus:
     http://paste.ubuntu.com/5701235/
  3. Qt applications workaround: http://is.gd/WnW9eN

  Window managers will obey to it.

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

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


[Dx-packages] [Bug 627195]

2015-08-24 Thread Lars Uebernickel
Created attachment 88321
Add org.mpris.MediaPlayer2.Activate

Alex, the desktop entry spec recently gained support for
org.freedesktop.Application, which has a method Activate() that takes a
platform data. I think it makes sense to reuse this terminology and the
platform-data convention.

The attached patch deprecates Raise() and CanRaise in favor of
Activate() and CanActivate.

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

Title:
  Window management - Apps raised from indicators sometimes dont have
  the focus

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Messaging Menu:
  Fix Released
Status in Messaging Menu 13.04 series:
  Fix Released
Status in The Sound Menu:
  Fix Released
Status in The Sound Menu 13.04 series:
  Fix Released
Status in DBus Menu:
  Triaged
Status in MPRIS:
  Confirmed
Status in Ubuntu One Client:
  Fix Committed
Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in empathy package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in libdbusmenu package in Ubuntu:
  Confirmed
Status in tomboy package in Ubuntu:
  Confirmed
Status in ubuntuone-client package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 11.10 beta
  compiz 1:0.9.5.94+bzr2803-0ubuntu5
  unity 4.16.0-0ubuntu1

  1. open banshee, start a song in it and minimize
  2. open another application lets say gnome-terminal
  3. click on the sound menu and select banshee

  What happens
  banshee icon in the launcher wiggles and banshee main window is not shown

  What should happen
  banshee main window should come to focus

  This is a long standing bug which Ted Gould thinks should be fixed at
  window manager's level.

  Some other observations=
  The problem wont happen
  1. if every other app is minimized or
  2. Banshee is the only opened app or
  3. after opening gnome-terminal, banshee window is closed so that it hides to 
the SoundMenu and opened again

  =Comment from Ted Gould=
   tedg, Hi! any thoughts on the long standing bug 627195 ? Its been 
there before unity so I guess we can conclude unity not to be responsible

   om26er, My thought is that window managers should $%#$ get
  fixed... though I haven't convinced smspillaz of it yet.

  =The good rule=
  3v1n0: Indicators should present the application windows by passing to them 
the timestamp of the menu item activation event.

  Unfortunately for indicator-sound, this is not trival as it sounds, since it 
needs a change to the MPRIS dbus specification.
  See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 
for more informations.

  For what concerns libappindicator based indicators (such as the one used by 
tomboy), since it's not currently possible in libdbusmenu to pass the event 
during activation (so that clients will be able to get the proper timestamp 
using gtk_get_current_event_time), there are two "hackish" ways:
  1. Use the server time to present a window:
     https://bugzilla.gnome.org/show_bug.cgi?id=688830
  2. Get the event timestamp from the dbus-menu linked to the gtk-menus:
     http://paste.ubuntu.com/5701235/
  3. Qt applications workaround: http://is.gd/WnW9eN

  Window managers will obey to it.

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

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


[Dx-packages] [Bug 627195]

2015-08-24 Thread Fdo-bugs
Not convinced that following GApplication's slightly esoteric form is
helpful.  The name's fine, but the way it encodes/decodes the timestamp
is kinda weird.

We'll probably need a CanRaiseWithTimestamp property or some such to let
clients know whether this is implemented.  Or a HasRaiseWithTimestamp,
which can be used in combination with CanRaise.

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

Title:
  Window management - Apps raised from indicators sometimes dont have
  the focus

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Messaging Menu:
  Fix Released
Status in Messaging Menu 13.04 series:
  Fix Released
Status in The Sound Menu:
  Fix Released
Status in The Sound Menu 13.04 series:
  Fix Released
Status in DBus Menu:
  Triaged
Status in MPRIS:
  Confirmed
Status in Ubuntu One Client:
  Fix Committed
Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in empathy package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in libdbusmenu package in Ubuntu:
  Confirmed
Status in tomboy package in Ubuntu:
  Confirmed
Status in ubuntuone-client package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 11.10 beta
  compiz 1:0.9.5.94+bzr2803-0ubuntu5
  unity 4.16.0-0ubuntu1

  1. open banshee, start a song in it and minimize
  2. open another application lets say gnome-terminal
  3. click on the sound menu and select banshee

  What happens
  banshee icon in the launcher wiggles and banshee main window is not shown

  What should happen
  banshee main window should come to focus

  This is a long standing bug which Ted Gould thinks should be fixed at
  window manager's level.

  Some other observations=
  The problem wont happen
  1. if every other app is minimized or
  2. Banshee is the only opened app or
  3. after opening gnome-terminal, banshee window is closed so that it hides to 
the SoundMenu and opened again

  =Comment from Ted Gould=
   tedg, Hi! any thoughts on the long standing bug 627195 ? Its been 
there before unity so I guess we can conclude unity not to be responsible

   om26er, My thought is that window managers should $%#$ get
  fixed... though I haven't convinced smspillaz of it yet.

  =The good rule=
  3v1n0: Indicators should present the application windows by passing to them 
the timestamp of the menu item activation event.

  Unfortunately for indicator-sound, this is not trival as it sounds, since it 
needs a change to the MPRIS dbus specification.
  See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 
for more informations.

  For what concerns libappindicator based indicators (such as the one used by 
tomboy), since it's not currently possible in libdbusmenu to pass the event 
during activation (so that clients will be able to get the proper timestamp 
using gtk_get_current_event_time), there are two "hackish" ways:
  1. Use the server time to present a window:
     https://bugzilla.gnome.org/show_bug.cgi?id=688830
  2. Get the event timestamp from the dbus-menu linked to the gtk-menus:
     http://paste.ubuntu.com/5701235/
  3. Qt applications workaround: http://is.gd/WnW9eN

  Window managers will obey to it.

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

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


[Dx-packages] [Bug 627195]

2015-08-24 Thread Lars Uebernickel
Instead of only passing a timestamp, this could be the same platform
data that GApplication uses in its Activate method (of type "asv").
This would make passing these kinds of things more uniform and easier to
handle for toolkits, as well as being extensible.

Maybe we could even call it Activate ;)

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

Title:
  Window management - Apps raised from indicators sometimes dont have
  the focus

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Messaging Menu:
  Fix Released
Status in Messaging Menu 13.04 series:
  Fix Released
Status in The Sound Menu:
  Fix Released
Status in The Sound Menu 13.04 series:
  Fix Released
Status in DBus Menu:
  Triaged
Status in MPRIS:
  Confirmed
Status in Ubuntu One Client:
  Fix Committed
Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in empathy package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in libdbusmenu package in Ubuntu:
  Confirmed
Status in tomboy package in Ubuntu:
  Confirmed
Status in ubuntuone-client package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 11.10 beta
  compiz 1:0.9.5.94+bzr2803-0ubuntu5
  unity 4.16.0-0ubuntu1

  1. open banshee, start a song in it and minimize
  2. open another application lets say gnome-terminal
  3. click on the sound menu and select banshee

  What happens
  banshee icon in the launcher wiggles and banshee main window is not shown

  What should happen
  banshee main window should come to focus

  This is a long standing bug which Ted Gould thinks should be fixed at
  window manager's level.

  Some other observations=
  The problem wont happen
  1. if every other app is minimized or
  2. Banshee is the only opened app or
  3. after opening gnome-terminal, banshee window is closed so that it hides to 
the SoundMenu and opened again

  =Comment from Ted Gould=
   tedg, Hi! any thoughts on the long standing bug 627195 ? Its been 
there before unity so I guess we can conclude unity not to be responsible

   om26er, My thought is that window managers should $%#$ get
  fixed... though I haven't convinced smspillaz of it yet.

  =The good rule=
  3v1n0: Indicators should present the application windows by passing to them 
the timestamp of the menu item activation event.

  Unfortunately for indicator-sound, this is not trival as it sounds, since it 
needs a change to the MPRIS dbus specification.
  See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 
for more informations.

  For what concerns libappindicator based indicators (such as the one used by 
tomboy), since it's not currently possible in libdbusmenu to pass the event 
during activation (so that clients will be able to get the proper timestamp 
using gtk_get_current_event_time), there are two "hackish" ways:
  1. Use the server time to present a window:
     https://bugzilla.gnome.org/show_bug.cgi?id=688830
  2. Get the event timestamp from the dbus-menu linked to the gtk-menus:
     http://paste.ubuntu.com/5701235/
  3. Qt applications workaround: http://is.gd/WnW9eN

  Window managers will obey to it.

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

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


[Dx-packages] [Bug 1462841] Re: window spread causes system logout

2015-08-24 Thread Nickey
I have the same issue. Would only like to add:

- Changing settings in Unity Tweak Tool has the same effect (unwanted
logout). This is not restricted to 'Window spread', i.e. happens when
changing other settings, too (I tried 'Hotcorners' and 'Window
snapping')

- My Window Spread had worked OK for more than a year now. The problem
started to happen when I did this:

1. Disable window spread
2. Enable window spread

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

Title:
  window spread causes system logout

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

Bug description:
  Expect to happen: 
  -window spread upon  w
  - no intempestive logout when tweaking window spread with the unity-tweak-tool

  What happened instead:
  -After installing unity tweak, turning ON the window spread caused a system 
logout when I clicked on any icon with multiple windows open.
  -A logout also happens if hot corners is enabled with the action set to 
window spread, and the mouse pointer directed to the preset hot corner.
  -A logout also happened when i press -w but in an unpredictable manner 
( w sometimes have the desired effect without logout)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-tweak-tool 0.0.6ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun  8 09:49:51 2015
  InstallationDate: Installed on 2013-08-29 (647 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: unity-tweak-tool
  UpgradeStatus: Upgraded to trusty on 2015-04-20 (48 days ago)

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

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


[Dx-packages] [Bug 1486445] Re: Lots of zeitgeist errors

2015-08-24 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/1486445

Title:
  Lots of zeitgeist errors

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt"
 was not found, exec: google-chrome-stable, mime_type: application/pkix-cert
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" 
was not found, exec: google-chrome-stable, mime_type: 
application/x-extension-html
  ...
  Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop
  Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 
2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop]
  ...
  Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop

  Any clues how to fix all that?

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

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


[Dx-packages] [Bug 1403744] Re: when I input something in Dash, Dash panel forced termination

2015-08-24 Thread jiaowen520li
This bug still exists in UK15.10-0823-Daily-i386.

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

Title:
  when I input something in Dash, Dash panel forced termination

Status in Ubuntu Kylin:
  New
Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  when I input words (english not chinese) in Dash, Dash panel close .
  re-input some words, it is happen.

  chinese description:
  在Dash中输入任何单词,Dash界面就会消失,回到桌面,如果输入错误,删掉几个字符,也会出现此问题

  OS:Ubuntu Kylin alpha1  i386

  machine: dell -Vostro-3900

  
  - new 
---

  when I input words in Dash, Dash panel forced termination:
  Input English - When the Dash first opens,input function normal; switch to 
other page in Dash at the moment,input words will lead to Dash panel forced 
termination.Since then, Open Dash to re-input some words,Dash panel exits 
immediately.
  Input Chinese - Dash panel exits immediately.

  Configuration:
  PC: HP-Pavilion-Sleekbook-15-PC
  OS: UK15.04-0408-Daily-i386

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

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


[Dx-packages] [Bug 1488080] Re: Should not use generic contact avatar

2015-08-24 Thread Sebastien Bacher
Thanks but that's not how things work, the icon is coming from the
client code adding the entry. The contact one is e.g used by telephony-
service. Can you provide steps to get an entry which is not from a
person with a buddy icon? That service would be where the bug is

** Package changed: indicator-messages (Ubuntu) => unity8 (Ubuntu)

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

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

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

Title:
  Should not use generic contact avatar

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I'm not sure I'm filing the bug against the right package.

  The persistent notifications on vivid (phone) show a generic
  human/contact icon, if no avatar was specified. However, that image
  may not match all contexts in terms of who/what posted the
  notification (it may be a server monitoring system, for instance, so
  clearly not a person).

  current build number: 24
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-07-22 14:36:08
  version version: 24
  version ubuntu: 20150713
  version device: 20150529-8e13c5f
  version custom: 20150709-814-29-21-vivid

  ---

  Feedback from Patricia Davila (design):

  Yes, I agree, a generic contact icon does not add value or give any
  info to the user in the context of a notification. As I mentioned, if
  the avatar is not present, the notification artwork should display the
  originating application's icon by default, rather than an generic
  placeholder or 'nothing' at worst.

  Please see the following spec for more information on layout and
  behaviour of notifications in the notification centre:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.xl5q9x18f0qi

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

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


[Dx-packages] [Bug 1488080] [NEW] Should not use generic contact avatar

2015-08-24 Thread Michał Karnicki
Public bug reported:

I'm not sure I'm filing the bug against the right package.

The persistent notifications on vivid (phone) show a generic
human/contact icon, if no avatar was specified. However, that image may
not match all contexts in terms of who/what posted the notification (it
may be a server monitoring system, for instance, so clearly not a
person).

current build number: 24
device name: krillin
channel: ubuntu-touch/stable/bq-aquaris.en
last update: 2015-07-22 14:36:08
version version: 24
version ubuntu: 20150713
version device: 20150529-8e13c5f
version custom: 20150709-814-29-21-vivid

---

Feedback from Patricia Davila (design):

Yes, I agree, a generic contact icon does not add value or give any info
to the user in the context of a notification. As I mentioned, if the
avatar is not present, the notification artwork should display the
originating application's icon by default, rather than an generic
placeholder or 'nothing' at worst.

Please see the following spec for more information on layout and
behaviour of notifications in the notification centre:
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.xl5q9x18f0qi

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

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

Title:
  Should not use generic contact avatar

Status in indicator-messages package in Ubuntu:
  New

Bug description:
  I'm not sure I'm filing the bug against the right package.

  The persistent notifications on vivid (phone) show a generic
  human/contact icon, if no avatar was specified. However, that image
  may not match all contexts in terms of who/what posted the
  notification (it may be a server monitoring system, for instance, so
  clearly not a person).

  current build number: 24
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-07-22 14:36:08
  version version: 24
  version ubuntu: 20150713
  version device: 20150529-8e13c5f
  version custom: 20150709-814-29-21-vivid

  ---

  Feedback from Patricia Davila (design):

  Yes, I agree, a generic contact icon does not add value or give any
  info to the user in the context of a notification. As I mentioned, if
  the avatar is not present, the notification artwork should display the
  originating application's icon by default, rather than an generic
  placeholder or 'nothing' at worst.

  Please see the following spec for more information on layout and
  behaviour of notifications in the notification centre:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.xl5q9x18f0qi

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

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


[Dx-packages] [Bug 1488072] [NEW] Headset loud warning issues when the screen is blank

2015-08-24 Thread Dave Morley
Public bug reported:

STEPS:
This is a behavioural bug and may require input from design.

1. Install the latest rc-proposed image
2. Plug in a wired headset
3. Play some music
4. Tap on cancel the the volume is dropped below the acceptable level
5. Blank the screen
6. Tap the volume up button

EXPECTED:
I expect something to tell me I need to wake the phone to accept the policy so 
the volume raises above the 50% level

ACTUAL:
The popup appear but gives no indication that it is there so you have no idea 
why the volume isn't increasing.

POSSIBLE SOLUTIONS:
1. An audible ping so you know that this volume up is doing something different
2. Wake the screen so the information is visible, only issue here is that the 
cancel or accept button might be pressed so then there is no idea why it didn't 
work
3. Flash the led like you do for messages to get the users attention.

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


** Tags: qa-manual-testing

** Tags added: qa-manual-testing

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

Title:
  Headset loud warning issues when the screen is blank

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  STEPS:
  This is a behavioural bug and may require input from design.

  1. Install the latest rc-proposed image
  2. Plug in a wired headset
  3. Play some music
  4. Tap on cancel the the volume is dropped below the acceptable level
  5. Blank the screen
  6. Tap the volume up button

  EXPECTED:
  I expect something to tell me I need to wake the phone to accept the policy 
so the volume raises above the 50% level

  ACTUAL:
  The popup appear but gives no indication that it is there so you have no idea 
why the volume isn't increasing.

  POSSIBLE SOLUTIONS:
  1. An audible ping so you know that this volume up is doing something 
different
  2. Wake the screen so the information is visible, only issue here is that the 
cancel or accept button might be pressed so then there is no idea why it didn't 
work
  3. Flash the led like you do for messages to get the users attention.

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

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


[Dx-packages] [Bug 1488007] Re: Bluetooth doesn't find hc-05 devices

2015-08-24 Thread Birger
** Attachment added: "GUI.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1488007/+attachment/4451576/+files/GUI.png

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

Title:
  Bluetooth doesn't find hc-05 devices

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  This bug affects the GUI of the bluetooth-indicator on my fully
  updated ubuntu phone.

  The hc-05 is the most common bluetooth device in electronics. I use it
  together with an arduino microprocessor. The bluetooth indicator
  doesn't find the device and so it cannot pair. With my ubuntu laptop
  and my android device everything works fine.

  However the device can be found via the hcitool -scan command in the
  terminal on the ubuntu phone. It can also be paired via bluez-simple-
  agent hci0 xx:xx:xx:xx:xx:xx So basically bluetooth works but
  unfortunately not the simple way.

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

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


[Dx-packages] [Bug 1488007] Re: Bluetooth doesn't find hc-05 devices

2015-08-24 Thread Birger
** Attachment added: "Terminal.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1488007/+attachment/4451575/+files/Terminal.png

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

Title:
  Bluetooth doesn't find hc-05 devices

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  This bug affects the GUI of the bluetooth-indicator on my fully
  updated ubuntu phone.

  The hc-05 is the most common bluetooth device in electronics. I use it
  together with an arduino microprocessor. The bluetooth indicator
  doesn't find the device and so it cannot pair. With my ubuntu laptop
  and my android device everything works fine.

  However the device can be found via the hcitool -scan command in the
  terminal on the ubuntu phone. It can also be paired via bluez-simple-
  agent hci0 xx:xx:xx:xx:xx:xx So basically bluetooth works but
  unfortunately not the simple way.

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

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


[Dx-packages] [Bug 1488007] [NEW] Bluetooth doesn't find hc-05 devices

2015-08-24 Thread Birger
Public bug reported:

This bug affects the GUI of the bluetooth-indicator on my fully updated
ubuntu phone.

The hc-05 is the most common bluetooth device in electronics. I use it
together with an arduino microprocessor. The bluetooth indicator doesn't
find the device and so it cannot pair. With my ubuntu laptop and my
android device everything works fine.

However the device can be found via the hcitool -scan command in the
terminal on the ubuntu phone. It can also be paired via bluez-simple-
agent hci0 xx:xx:xx:xx:xx:xx So basically bluetooth works but
unfortunately not the simple way.

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


** Tags: arduino bluetooth hc-05

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

Title:
  Bluetooth doesn't find hc-05 devices

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  This bug affects the GUI of the bluetooth-indicator on my fully
  updated ubuntu phone.

  The hc-05 is the most common bluetooth device in electronics. I use it
  together with an arduino microprocessor. The bluetooth indicator
  doesn't find the device and so it cannot pair. With my ubuntu laptop
  and my android device everything works fine.

  However the device can be found via the hcitool -scan command in the
  terminal on the ubuntu phone. It can also be paired via bluez-simple-
  agent hci0 xx:xx:xx:xx:xx:xx So basically bluetooth works but
  unfortunately not the simple way.

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

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