[Dx-packages] [Bug 1520667] Re: Try to load images from the icon theme

2015-11-27 Thread Lars Uebernickel
** Branch linked: lp:~larsu/notify-osd/1520667

** Changed in: notify-osd (Ubuntu)
   Status: New => In Progress

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

Title:
  Try to load images from the icon theme

Status in notify-osd package in Ubuntu:
  In Progress

Bug description:
  Using xenial, rhythmbox song playing notifications don't have an
  image, that seems to be a regression from
  https://code.launchpad.net/~larsu/notify-osd/spam-a-bit-
  less/+merge/274382

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1520667/+subscriptions

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


[Dx-packages] [Bug 1303796] Re: Display scaling is not applied runtime

2015-11-03 Thread Lars Uebernickel
Attached a branch that fixes the issue I mentioned in comment #3

** Branch linked: lp:~larsu/notify-osd/lp1303796

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

Title:
  Display scaling is not applied runtime

Status in notify-osd package in Ubuntu:
  Triaged

Bug description:
  I changed my scaling to a value and back to 1, I think notify-osd got
  triggered at that time, and all subsequent notifications were scaled
  incorrectly.

  It looks like notify-osd doesn't update the scaling value runtime.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 13:59:10 2014
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic 
root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash 
quiet vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.0-4ubuntu1
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
   xserver-xorg-video-ati   1:7.3.0-1ubuntu3
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1303796/+subscriptions

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


[Dx-packages] [Bug 1303796] Re: Display scaling is not applied runtime

2015-11-02 Thread Lars Uebernickel
Seb just told me that this doesn't happen anymore when changing scale
factor, but when changing font size in a11y settings.

** Changed in: notify-osd (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Display scaling is not applied runtime

Status in notify-osd package in Ubuntu:
  Triaged

Bug description:
  I changed my scaling to a value and back to 1, I think notify-osd got
  triggered at that time, and all subsequent notifications were scaled
  incorrectly.

  It looks like notify-osd doesn't update the scaling value runtime.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 13:59:10 2014
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic 
root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash 
quiet vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.0-4ubuntu1
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
   xserver-xorg-video-ati   1:7.3.0-1ubuntu3
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1303796/+subscriptions

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


[Dx-packages] [Bug 1303796] Re: Display scaling is not applied runtime

2015-11-02 Thread Lars Uebernickel
I can't reproduce this on wily anymore, even when changing the device
scale back and forth multiple times.

Michał, is this still a problem for you? If so, how can I reproduce it?

** Changed in: notify-osd (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: notify-osd (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

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

Title:
  Display scaling is not applied runtime

Status in notify-osd package in Ubuntu:
  Incomplete

Bug description:
  I changed my scaling to a value and back to 1, I think notify-osd got
  triggered at that time, and all subsequent notifications were scaled
  incorrectly.

  It looks like notify-osd doesn't update the scaling value runtime.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 13:59:10 2014
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic 
root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash 
quiet vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.0-4ubuntu1
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
   xserver-xorg-video-ati   1:7.3.0-1ubuntu3
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1303796/+subscriptions

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


[Dx-packages] [Bug 1488344] Re: dbus rejected send messages

2015-10-30 Thread Lars Uebernickel
Indeed, accountsservice sends a reply even when the client talking to it
doesn't want one. The dbus daemon doesn't remember messages that have
NO_REPLY_EXPECTED set, so the replies from accountsservice look like
unsolicited messages to it and it denies them.

Gnome bug #755421 argues that this should be fixed in gdbus, and I
agree. gdbus automatically sets NO_REPLY_EXPECTED when no callback is
given, so it makes sense that it also handles the server side by
discarding replies for such messages. I've attached a patch upstream.

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

** Also affects: glib via
   https://bugzilla.gnome.org/show_bug.cgi?id=755421
   Importance: Unknown
   Status: Unknown

** Changed in: accountsservice (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: New => Triaged

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

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

Title:
  dbus rejected send messages

Status in GLib:
  Unknown
Status in accountsservice package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Seeing these log entries in the syslog

  Aug 24 18:26:36 M1 dbus[783]: [system] Rejected send message, 9 matched
  rules; type="method_return", sender=":1.5" (uid=0 pid=733
  comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)"
  member="(unset)" error name="(unset)" requested_reply="0"
  destination=":1.59" (uid=1000 pid=4326
  comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")

  Hope the attached info helps locating the issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Tue Aug 25 18:30:51 2015
  InstallationDate: Installed on 2014-10-31 (298 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1473269] Re: Wily login screen shows an all black notification bubble

2015-10-12 Thread Lars Uebernickel
** Changed in: gtk+3.0 (Ubuntu)
   Status: In Progress => Opinion

** Changed in: notify-osd (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: notify-osd (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

** Branch linked: lp:~larsu/notify-osd/lp1473269

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

Title:
  Wily login screen shows an all black notification bubble

Status in gtk+3.0 package in Ubuntu:
  Opinion
Status in notify-osd package in Ubuntu:
  In Progress

Bug description:
  Wily login screen shows an all black notification bubble. No idea what
  it says, obviously.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1473269/+subscriptions

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


[Dx-packages] [Bug 1480387] Re: Clicking a date to go back or forward a month causes repeated jumps between two dates

2015-10-01 Thread Lars Uebernickel
** Package changed: indicator-datetime (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

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

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=755941
   Importance: Unknown
   Status: Unknown

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

Title:
  Clicking a date to go back or forward a month causes repeated jumps
  between two dates

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
  or trusty. It happened for me in the most recent wily iso.

  Open the indicator, click one of the greyed dates at the start or end
  of the month (sometimes requires more than one go). The active date
  starts to repeatedly jump between this date and another one. I ran
  with G_MESSAGES_DEBUG=all and when it's happening this is spammed (I
  clicked a date in 2015-05).

  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 31 17:09:43 2015
  InstallationDate: Installed on 2012-10-07 (1026 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2013-05-07 (815 days ago)

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

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


[Dx-packages] [Bug 1482181] Re: Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging

2015-09-26 Thread Lars Uebernickel
Problem figured out by Trevinho and didrocks on irc: unity only emits
AcceleratorActivated() for the first id returned by GrabAccelerator()
and doesn't watch the unique name of the grabbing process. Thus, when
something other than unity-settings-daemon grabs the key before it, or
u-s-d crashes, those keys it grabbed at the very beginning can never be
regrabbed.

After a couple of rounds of testing and some code review, I can't make
unity-settings-daemon subscribe to the same accelerator twice and thus
getting into that situation itself. Feel free to reassign it to u-s-d
once unity is fixed but this problem still persists.

** Changed in: unity-settings-daemon (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly
  after logging

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  I've installed 15.10 and I can't open a terminal using ctrl-alt-t or
  use any other media keys. All system shorcuts as well don't work.

  Note that this started at least in 14.10.

  Restarting Unity "fixes" it (or logging out/logging back), so it seems
  a race between Unity and settings daemon at startup.

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

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


[Dx-packages] [Bug 1495173] Re: compiz crashed with SIGSEGV in g_bit_lock()

2015-09-17 Thread Lars Uebernickel
This is not a bug in glib. UploadBlacklist() loops through a list of
strings with

  for (auto item : blacklist_)
// do something with item.c_str()

which makes a copy of each string in every iteration. This means that
item.c_str() is not valid anymore after the loop finishes.
g_settings_set_strv() then rightly complains about invalid utf8  from
whatever is lying around at those memory addresses then.

The attached branch fixes this by using a const reference in the loop.

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

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

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

** Branch linked: lp:~larsu/unity/lp1495173

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

Title:
  compiz crashed with SIGSEGV in g_bit_lock()

Status in glib2.0 package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Error occurred while trying to unlock from launcher disk volume icon using 
context menu.
  The error can be reproduced.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150910.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sun Sep 13 01:10:59 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2015-09-13 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f33bc884338 :lock bts 
%r12d,(%rbx)
   PC (0x7f33bc884338) ok
   source "%r12d" ok
   destination "(%rbx)" (0x0020) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   g_bit_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_serialiser_needed_size () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_bit_lock()
  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/glib2.0/+bug/1495173/+subscriptions

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

  tedg 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=
  om26er 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

  tedg 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 1436211] Re: Remove GTK3 from phone images

2015-08-22 Thread Lars Uebernickel
litimezonemap contains gtk3 widgets that are used in unity7's system
settings. Can we make unity-system-settings not depend on it?

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

Title:
  Remove GTK3 from phone images

Status in Canonical System Image:
  In Progress
Status in address-book-service package in Ubuntu:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  In Progress
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-touch-meta package in Ubuntu:
  Invalid
Status in unity-asset-pool package in Ubuntu:
  Confirmed
Status in evolution-data-server package in Debian:
  New

Bug description:
  This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone
  images to save some space.

  ===TODO===

  -- address-book-service --

  address-book-service depends on evolution-data-server, which depends
  on GTK3. evolution-data-server further depends on libgweather-3-6 and
  libgcr-ui-3-1 which both directly depend on GTK3 too.

  Would it be possible to work with libfolks-eds25 and other libraries
  alone? Or would it be possible to modify evolution-data-server
  building to not depend on GTK3 since we're not using the toolkit
  anyway?

  -- themes (unity-asset-pool, adwaita-icon-theme...) --

  humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on
  adwaita-icon-theme. adwaita-icon-theme directly depends on GTK3.

  -- ubuntu-system-settings --

  ubuntu-system-settings depends on libtimezonemap1 which directly
  depends on GTK3. Maybe the library could be made not to depend on
  GTK3?

  ===DONE===
  -- gnome-control-center-signon --
  Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be 
possible to refactor it so that it would not depend on GTK3 bringing it on the 
images?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436211/+subscriptions

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


[Dx-packages] [Bug 1320634] Re: The blacklisted-media-players key doesn't work

2015-08-22 Thread Lars Uebernickel
Indeed, the blacklisted-media-players settings key hasn't been honored
for a couple of ubuntu releases.

The idea is that applications have UI to disable integration into the
sound menu. For example in VLC, you can disable it in Preferences (look
for DBus control interface). It might make sense to disable it by
default for this app.

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

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

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

Title:
  The blacklisted-media-players key doesn't work

Status in indicator-sound package in Ubuntu:
  Triaged

Bug description:
  I only want Audacious show in the sound menu. So I removed vlc from the 
interested-media-players to the  blacklisted-media-players via dconf. So 
far everything works as supposed, but when I start vlc it adds itself to the 
interested-media-players and apears in the sound menu and stays there after 
vlc is closed
  At this point vlc is still in theblacklisted-media-players. that should 
override the interested-media-players tag, but doesn't.

  screen: http://i.imgur.com/dOXGL0W.png

  I've also tested this with Rhythmbox; same problem.

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

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


[Dx-packages] [Bug 1473029] Re: notification (image update, gmail, calls) displayed twice

2015-07-16 Thread Lars Uebernickel
Thanks for reporting this. When it happens again, could you please paste
the output of

  gdbus call --session --dest com.canonical.indicator.messages --object-
path /com/canonical/indicator/messages/phone --method
org.gtk.Menus.Start [0,1]

This is to find out whether the service thinks there are two messages
(due to a bug or because something has posted two messages) or unity
falsely shows two messages when there's actually only one.

Also, please attach ~/.cache/upstart/indicator-messages.log.

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

Title:
  notification (image update, gmail, calls) displayed twice

Status in Canonical System Image:
  New
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34

  Sometimes notifications are displayed twice in the indicator. It
  happens randomly with all kind of notifications (image update, gmail,
  calls) Push client logs shows a single notification. There is nothing
  specific to reproduce, sometimes it happens, sometimes it doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473029/+subscriptions

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


[Dx-packages] [Bug 1462346] Re: Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at zoom levels bigger than 100% in Nautilus

2015-07-06 Thread Lars Uebernickel
** Changed in: humanity-icon-theme (Ubuntu)
   Status: New = In Progress

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

Title:
  Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at
  zoom levels bigger than 100% in Nautilus

Status in humanity-icon-theme package in Ubuntu:
  In Progress

Bug description:
  Hello,

  the icon size of the  folder-drag-accept/gnome-fs-directory-accept
  icon in Nautilus is too small when a zoom level bigger than 100% in
  the icon view is used. This can be reproduced the following way:

  - Start Nautilus (or Nemo)
  - Open a directory that contains at least one subdirectory plus at least one 
file (or a second subdirectory)
  - Switch to icon view, set a zoom level bigger than 100%
  - Try to move a file/directory into another directory
  - When the mouse moves over the target directory, it's icon will switch to 
the folder-drag-accept/gnome-fs-directory-accept icon, but in a version that is 
no larger than 48x48, even if the zoom level (and thus the icon size) is set 
greater. I have attached a screenshot that illustrates the problem.

  With the Adwaita icon theme the problem does not happen, the icon
  seems to get the correct size at all zoom levels.

  Currently the Humanity icon theme contains (as symlink) a svg file of
  the responsible folder-drag-accept/gnome-fs-directory-accept icon in
  the directories Humanity/status/24 and Humanity/48. The dirs for
  bigger icons (e.g. 128) do not contain that icons, so I assumed it may
  be a quick fix to symlink them to also to those dirs. But that caused
  just other problems - now the icons had always the 128x128 size
  regardless of zoom level and was often too big instead of too small!

  A way to fix this seems to be to place png files of the icons in all
  of the Humanity/status/[icon size]-directories, each png scaled to the
  appropriate size. That is a bit more hassle but seems to work for the
  Adwaita theme.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: humanity-icon-theme 0.6.8
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun  5 10:53:39 2015
  InstallationDate: Installed on 2015-04-16 (49 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415)
  PackageArchitecture: all
  SourcePackage: humanity-icon-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1462346/+subscriptions

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


[Dx-packages] [Bug 1462346] Re: Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at zoom levels bigger than 100% in Nautilus

2015-06-29 Thread Lars Uebernickel
** Changed in: humanity-icon-theme (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

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

Title:
  Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at
  zoom levels bigger than 100% in Nautilus

Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  Hello,

  the icon size of the  folder-drag-accept/gnome-fs-directory-accept
  icon in Nautilus is too small when a zoom level bigger than 100% in
  the icon view is used. This can be reproduced the following way:

  - Start Nautilus (or Nemo)
  - Open a directory that contains at least one subdirectory plus at least one 
file (or a second subdirectory)
  - Switch to icon view, set a zoom level bigger than 100%
  - Try to move a file/directory into another directory
  - When the mouse moves over the target directory, it's icon will switch to 
the folder-drag-accept/gnome-fs-directory-accept icon, but in a version that is 
no larger than 48x48, even if the zoom level (and thus the icon size) is set 
greater. I have attached a screenshot that illustrates the problem.

  With the Adwaita icon theme the problem does not happen, the icon
  seems to get the correct size at all zoom levels.

  Currently the Humanity icon theme contains (as symlink) a svg file of
  the responsible folder-drag-accept/gnome-fs-directory-accept icon in
  the directories Humanity/status/24 and Humanity/48. The dirs for
  bigger icons (e.g. 128) do not contain that icons, so I assumed it may
  be a quick fix to symlink them to also to those dirs. But that caused
  just other problems - now the icons had always the 128x128 size
  regardless of zoom level and was often too big instead of too small!

  A way to fix this seems to be to place png files of the icons in all
  of the Humanity/status/[icon size]-directories, each png scaled to the
  appropriate size. That is a bit more hassle but seems to work for the
  Adwaita theme.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: humanity-icon-theme 0.6.8
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun  5 10:53:39 2015
  InstallationDate: Installed on 2015-04-16 (49 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415)
  PackageArchitecture: all
  SourcePackage: humanity-icon-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1462346/+subscriptions

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


[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

2015-06-05 Thread Lars Uebernickel
This patch is a backport of the upstream patch to 3.14

** Patch added: 0001-Add-a-traditional-menubar.patch
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1447224/+attachment/4410401/+files/0001-Add-a-traditional-menubar.patch

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

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Confirmed
Status in totem source package in Vivid:
  Confirmed
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

2015-05-27 Thread Lars Uebernickel
Totem's menu xml has placeholders for subtitles and languages, which are
populated dynamically based on the video that is loaded.

The traditional menubar, the gear menu, and the fullscreen gear menu all
share the same placeholder ids and Totem inserts the dynamic submenu in
only one of them. I've worked around this issue in [1] by not populating
the gear menu and fullscreen gear menu at all. I think we can take this
for now.

We're thinking about how to fix this properly in gtk as well.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=749695

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

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

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Confirmed
Status in totem source package in Vivid:
  Confirmed
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1427286] Re: g_variant_unref warning displayed when calling back after a missed call

2015-03-02 Thread Lars Uebernickel
This is an issue in telephony-service: it calls g_variant_unref() on a
variant that it doesn't own a reference to [1].

g_variant_new_strv() returns a floating reference which is consumed by
the call to messaging_menu_message_add_action(). Another bug in that
code is g_variant_unref() might be called with a NULL variant when the
condition in line 212 is false. Both of those things will be fixed when
removing the unref call.

[1] http://bazaar.launchpad.net/~phablet-team/telephony-
service/trunk/view/head:/indicator/messagingmenu.cpp#L239

** Package changed: indicator-messages (Ubuntu) = telephony-service
(Ubuntu)

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

Title:
  g_variant_unref warning displayed when calling back after a missed
  call

Status in telephony-service package in Ubuntu:
  New

Bug description:
  On ubuntu touch rtm 248, those warning are displayed when selecting
  the call back action in the messaging menu, following a missed call

  g_variant_unref: assertion 'value-ref_count  0' failed

  backtrace of a warning

  #0  g_log (log_domain=0xb6598a70 GLib, 
  log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
  format=0xb65a17d4 %s: assertion '%s' failed)
  at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1075
  #1  0xb656ad62 in g_return_if_fail_warning (log_domain=optimized out, 
  pretty_function=optimized out, expression=optimized out)
  at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088
  #2  0xb6516664 in action_free (data=0xb3000e70) at messaging-menu-message.c:76
  #3  0xb657aae8 in g_slist_foreach (list=optimized out, list@entry=0xf72490, 
  func=0xb6516621 action_free, user_data=user_data@entry=0x0)
  at /build/buildd/glib2.0-2.41.5/./glib/gslist.c:877
  #4  0xb657aafa in g_slist_free_full (list=0xf72490, free_func=optimized out)
  at /build/buildd/glib2.0-2.41.5/./glib/gslist.c:172
  #5  0xb651672c in messaging_menu_message_finalize (object=0xb2603b50)
  at messaging-menu-message.c:101
  #6  0xb66139f8 in g_object_unref (_object=0xb2603b50)
  at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:3170
  #7  0xb65596a0 in g_hash_table_remove_internal (hash_table=0xf70608, 
  key=0xfbb4c0, notify=1) at 
/build/buildd/glib2.0-2.41.5/./glib/ghash.c:1300
  #8  0xb651518e in messaging_menu_app_remove_message_internal (app=0xf70640, 
  message_id=0xfbb4c0 caller_number_replaced) at 
messaging-menu-app.c:510
  #9  0xb6515348 in messaging_menu_app_activate_message 
(app_interface=0xf3ba70, 
  invocation=0xf70678, message_id=0xfbb4c0 caller_number_replaced, 
  action_id=0xf92460 callBack, params=0xf777c8, user_data=0xf70640)
  at messaging-menu-app.c:593
  #10 0xb5cda948 in ffi_call_VFP () from 
/usr/lib/arm-linux-gnueabihf/libffi.so.6
  #11 0xb5cdafc0 in ffi_call () from /usr/lib/arm-linux-gnueabihf/libffi.so.6
  #12 0xb6610b6c in g_cclosure_marshal_generic (closure=optimized out, 
  return_gvalue=optimized out, n_param_values=5, 
  param_values=optimized out, invocation_hint=0xbedc4070, 
marshal_data=0x0)
  at /build/buildd/glib2.0-2.41.5/./gobject/gclosure.c:1448
  #13 0xb66105b4 in g_closure_invoke (closure=0xf726d8, 
return_value=0xbedc4050, 
  n_param_values=5, param_values=0xf9dbc0, invocation_hint=0xbedc4070)
  at /build/buildd/glib2.0-2.41.5/./gobject/gclosure.c:768
  #14 0xb661d0aa in signal_emit_unlocked_R (node=node@entry=0xf62da0, 
  detail=detail@entry=0, instance=instance@entry=0xf3ba70, 
  emission_return=emission_return@entry=0xbedc4160, 
  instance_and_params=instance_and_params@entry=0xf9dbc0)
  at /build/buildd/glib2.0-2.41.5/./gobject/gsignal.c:3553
  #15 0xb6622a30 in g_signal_emitv (instance_and_params=0xf9dbc0, 
  signal_id=optimized out, detail=0, return_value=0xbedc4160)
  at /build/buildd/glib2.0-2.41.5/./gobject/gsignal.c:3048
  #16 0xb651aac4 in _indicator_messages_application_skeleton_handle_method_call 
(
  connection=0xb3006048, sender=0xb26055b8 :1.52, 
  object_path=0xb2605c48 
/com/canonical/indicator/messages/telephony_service_call_desktop, 
  interface_name=0xb26052a8 com.canonical.indicator.messages.application, 
  method_name=0xb26055e8 ActivateMessage, parameters=0xf8a508, 
  invocation=0xf70678, user_data=0xf3ba70)
  at indicator-messages-application.c:1917
  #17 0xb66f0fa4 in g_dbus_interface_method_dispatch_helper (
  invocation=0xf70678, 
  method_call_func=0xb651a8a1 
_indicator_messages_application_skeleton_handle_method_call, 
interface=0xf3ba70)
  at /build/buildd/glib2.0-2.41.5/./gio/gdbusinterfaceskeleton.c:609
  #18 skeleton_intercept_handle_method_call (connection=optimized out, 
  sender=optimized out, object_path=optimized out, 
  interface_name=optimized out, method_name=0xb26055e8 ActivateMessage, 
  parameters=0xf8a508, 

[Dx-packages] [Bug 1421919] Re: clock is missing ~10% of the time

2015-02-27 Thread Lars Uebernickel
indicator-datetime-service seems to do the right thing when it loses its
name (exit the process). Maybe it gets stuck in a deadlock and doesn't
respond to D-Bus calls anymore?

Can someone please attach a backtrace of the running process when this
happens again?

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

Title:
  clock is missing ~10% of the time

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This bug is maybe related to Bug #1239710, as in comment #34 mentioned
  I created a new bug report.

  After start of my pc the clock in the notification area is missing sometimes. 
When you kill the indicator-datetime the clock is displaying again:
  sudo pkill -9 indicator-date

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: wl tbs6982fe tbs6680fe tbs6923fe tbs6985se tbs6928se 
tbs6982se tbs6991fe tbs6618fe tbs6983fe tbs6922fe tbs6928fe tbs6991se tbs6290fe
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 14 10:26:41 2015
  InstallationDate: Installed on 2014-03-30 (320 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140329)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1416810] Re: indicator-messages should depent (or recommend) libmessaging-menu0

2015-02-24 Thread Lars Uebernickel
 They could use DBus directly if they wanted.

No, the D-Bus interface is not part of the public API.

 [...] the messaging menu never appears in the panel, unless
libmessaging-menu0 gets installed, although applications using it are
installed [...]

It doesn't appear until an application registers itself. (If that
doesn't happen for some reason, please file a bug.)

** Changed in: indicator-messages (Ubuntu)
   Status: Opinion = Won't Fix

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

Title:
  indicator-messages should depent (or recommend) libmessaging-menu0

Status in indicator-messages package in Ubuntu:
  Won't Fix

Bug description:
  indicator-messages does not work without libmessaging-menu0, hence
  there should be some sort of dependency.

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

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


[Dx-packages] [Bug 1416810] Re: indicator-messages should depent (or recommend) libmessaging-menu0

2015-02-24 Thread Lars Uebernickel
Seems to me like Thunderbird's messaging menu integration is optional.
Please file a bug against it to make it depend on libmessaging-menu.

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

Title:
  indicator-messages should depent (or recommend) libmessaging-menu0

Status in indicator-messages package in Ubuntu:
  Won't Fix

Bug description:
  indicator-messages does not work without libmessaging-menu0, hence
  there should be some sort of dependency.

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

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


[Dx-packages] [Bug 1344990] Re: Volume control jumps back and forth

2015-01-23 Thread Lars Uebernickel
** Branch linked: lp:~larsu/ido/fix-volume-slider

** Project changed: indicator-sound = ido

** Changed in: ido
   Status: New = Fix Committed

** Changed in: ido
 Assignee: (unassigned) = Lars Uebernickel (larsu)

** Package changed: indicator-sound (Ubuntu) = ido (Ubuntu)

** Changed in: ido (Ubuntu)
 Assignee: Ted Gould (ted) = Lars Uebernickel (larsu)

** Changed in: ido (Ubuntu)
   Status: Triaged = Invalid

** Changed in: ido (Ubuntu)
   Status: Invalid = Fix Released

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

Title:
  Volume control jumps back and forth

Status in Indicator Display Objects:
  Fix Committed
Status in Unity:
  Invalid
Status in ido package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1) Listen to music via Audacious
  2) Open volume control from Unity's panel
  3) Try to change the volume

  What happens:

  - The volume control doesn't follow mouse properly and jumps back and
  forth

  What should happen:

  - The obvious thing

  I believe this is regression as didn't notice anything weird in 13.10
  with exactly same setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Jul 19 19:51:32 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1332858] Re: Speaker icon should change to indicate that sound is muted

2014-11-23 Thread Lars Uebernickel
It already does this.

Please provide more information on when this doesn't work for you. Is
the Mute menu item in the sound menu checked when sound is on mute,
but the icon in the panel shows that volume is above 0? How about the
Mute checkbox in System Settings  Sound?

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

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

Title:
  Speaker icon should change to indicate that sound is muted

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

Bug description:
  The speaker icon on the menu bar should change to indicate that the
  sound is muted.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: armhf
  Date: Sat Jun 21 11:25:24 2014
  InstallationDate: Installed on 2014-06-19 (2 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140619.1)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1386255] Re: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars

2014-11-14 Thread Lars Uebernickel
** Changed in: overlay-scrollbar (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: overlay-scrollbar (Ubuntu)
 Assignee: Lars Uebernickel (larsu) = Sebastien Bacher (seb128)

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

Title:
  devhelp and many other apps crash with SIGSEGV in g_closure_invoke()
  due to overlay-scrollbars

Status in Overlay Scrollbar:
  New
Status in Ubuntu GNOME:
  New
Status in “overlay-scrollbar” package in Ubuntu:
  In Progress

Bug description:
  With the gnome3-team/gnome3-staging PPA enabled all Gtk+ applications
  segfault when I do stuff like

  - Press the Menu key
  - Press the Save button in gedit's headerbar
  - Press the hamburger menu button in devhelp's headerbar (the stack trace 
attached to this bug)
  - Press the Add button in gtimelog
  - Try to open any of the regular menus in gtimelog

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: devhelp 3.14.0-1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
  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: GNOME
  Date: Mon Oct 27 17:15:30 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/devhelp
  InstallationDate: Installed on 2012-07-25 (824 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcCmdline: devhelp
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: devhelp
  StacktraceTop:
   ?? ()
   g_closure_invoke (closure=0x11e4ce0, return_value=0x0, n_param_values=2, 
param_values=0x7fffd6ed0920, invocation_hint=0x7fffd6ed08c0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x11e50b0, detail=detail@entry=0, 
instance=instance@entry=0x182a510, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd6ed0920) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3483
   g_signal_emit_valist (instance=optimized out, signal_id=optimized out, 
detail=optimized out, var_args=var_args@entry=0x7fffd6ed0ab0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3309
   g_signal_emit (instance=instance@entry=0x182a510, signal_id=optimized out, 
detail=detail@entry=0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3365
  Title: devhelp crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago)
  UserGroups: adm cdrom dip docker libvirtd lp lpadmin plugdev sambashare 
shared sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1386255/+subscriptions

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


[Dx-packages] [Bug 1389725] Re: g_app_info warning on start (utouch)

2014-11-07 Thread Lars Uebernickel
** Changed in: indicator-messages (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  g_app_info warning on start (utouch)

Status in “indicator-messages” package in Ubuntu:
  In Progress

Bug description:
  Using rtm 143, indicator-messages displays warnings on start

  backtrace of one of those

  #0  g_log (log_domain=0xb6f87914 GLib-GIO, 
  log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
  format=0xb6e247d4 %s: assertion '%s' failed)
  at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1075
  #1  0xb6dedd62 in g_return_if_fail_warning (log_domain=optimized out, 
  pretty_function=optimized out, expression=optimized out)
  at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088
  #2  0xb6ef610c in g_app_info_equal (appinfo1=0x4e088, appinfo2=0x0)
  at /build/buildd/glib2.0-2.41.5/./gio/gappinfo.c:132
  #3  0x000170d2 in g_app_info_is_default_for_uri_scheme (
  uri_scheme=0x1d63c mailto, info=0x4e088) at im-desktop-menu.c:87
  #4  im_desktop_menu_app_added (applist=optimized out, 
  app_id=0x50b80 telephony-service-call, app_info=0x4e088, 
  user_data=0x3fe40) at im-desktop-menu.c:176
  #5  0x000173ee in im_desktop_menu_constructed (object=0x3fe40)
  at im-desktop-menu.c:380
  #6  0xb6e96fae in g_object_new_internal (class=class@entry=0x0, 
  params=params@entry=0xbefff354, n_params=n_params@entry=1)
  at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1814
  #7  0xb6e98650 in g_object_new_valist (object_type=object_type@entry=346680, 
  first_property_name=first_property_name@entry=0x1d054 application-list, 
  var_args=..., var_args@entry=...)
  at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034
  #8  0xb6e987ec in g_object_new (object_type=346680, 
  first_property_name=0x1d054 application-list)
  at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617
  #9  0x00017510 in im_desktop_menu_new (applist=optimized out)
  at im-desktop-menu.c:427
  #10 0x00014d16 in main (argc=optimized out, argv=optimized out)
  at messages-service.c:277

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

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


[Dx-packages] [Bug 1386584] Re: SIGSEGV when notification contains |

2014-11-05 Thread Lars Uebernickel
** Project changed: unity = indicator-messages

** Package changed: unity (Ubuntu) = indicator-messages (Ubuntu)

** Changed in: indicator-messages
   Status: Confirmed = In Progress

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

Title:
  SIGSEGV when notification contains |

Status in The Messaging Menu:
  In Progress
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  When a notification on the messages menu contains the | character (in
  my case a nickname in xchat), the process unity-panel-service crashes
  with:

  ngl@BEATRIX:~/Scrivania/database$ /usr/lib/unity/unity-panel-service

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP
  (accel_group)' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP
  (accel_group)' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP
  (accel_group)' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP
  (accel_group)' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP
  (accel_group)' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP
  (accel_group)' failed

  
  (unity-panel-service:11336): Gtk-CRITICAL **: 
gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed

  (unity-panel-service:11336): Gtk-CRITICAL **:
  gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed

  (unity-panel-service:11336): Gtk-CRITICAL **: gtk_print_action_and_target: 
assertion 'strchr (action_name, '|') == NULL' failed
  Segmentation fault (core dumped)

  
  ngl@BEATRIX:~/Scrivania/database$ lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  ngl@BEATRIX:~/Scrivania/database$ apt-cache policy unity-services
  unity-services:
Installed: 7.3.1+14.10.20141016-0ubuntu1
Candidate: 7.3.1+14.10.20141016-0ubuntu1
Version table:
   *** 7.3.1+14.10.20141016-0ubuntu1 0
  500 http://it.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Dx-packages] [Bug 1381871] Re: [wizard] volume notification showing up during wizard (with volume as 0)

2014-10-16 Thread Lars Uebernickel
** Branch linked: lp:~larsu/indicator-sound/lp1381871

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

Title:
  [wizard] volume notification showing up during wizard (with volume as
  0)

Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid

Bug description:
  The volume notification shows up at the 'lock security' page on the
  wizard, showing volume as 0.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 109
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-16 04:39:16
  version version: 109
  version ubuntu: 20141016
  version device: 20141014-acf0142
  version custom: 1413412663

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

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


[Dx-packages] [Bug 1381871] Re: [wizard] volume notification showing up during wizard (with volume as 0)

2014-10-16 Thread Lars Uebernickel
** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  [wizard] volume notification showing up during wizard (with volume as
  0)

Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid

Bug description:
  The volume notification shows up at the 'lock security' page on the
  wizard, showing volume as 0.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 109
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-16 04:39:16
  version version: 109
  version ubuntu: 20141016
  version device: 20141014-acf0142
  version custom: 1413412663

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

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


[Dx-packages] [Bug 1381069] Re: We should hide the player controls in the sound indicator until the music player is fixed to work with them

2014-10-14 Thread Lars Uebernickel
** Changed in: indicator-sound (Ubuntu)
   Status: New = In Progress

** Changed in: indicator-sound (Ubuntu)
 Assignee: Thomas Strehl (strehl-t) = Lars Uebernickel (larsu)

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

Title:
  We should hide the player controls in the sound indicator until the
  music player is fixed to work with them

Status in “indicator-sound” package in Ubuntu:
  In Progress

Bug description:
  see these two bugs:
  https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232

  Essentially, the music player does not work with the sound menu, and
  the fix is involved. Until the default experience works, I suggest
  that we do not show these controls.

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

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


[Dx-packages] [Bug 1378821] Re: today/yesterday label on sms and calls is incorrect

2014-10-13 Thread Lars Uebernickel
** Changed in: indicator-messages (Ubuntu)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

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

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

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

Title:
  today/yesterday label on sms and calls is incorrect

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

Bug description:
  rtm image on krillin, build 88

  I'm in timzone UTC -4
  If I have a missed call or sms that shows up in the indicator, it will 
sometimes incorrect be displayed as Yesterday time even though it happened 
today. This happens if the missed call is anytime after 8pm local time.

  I believe it's because the determination for that label is using UTC
  time rather than converting to the local timezone. It should be
  changed to use local time zone.

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

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


[Dx-packages] [Bug 1372061] Re: SMS notification: time format not translatable

2014-10-13 Thread Lars Uebernickel
** No longer affects: indicator-messages (Ubuntu)

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

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

Title:
  SMS notification: time format not translatable

Status in Ubuntu Translations:
  Triaged
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  See the attached screenshot. The time for the notification seems to be
  hardcoded to hh:mm - mm, d. This works well for the US, but it's not
  a format that is used in all other countries. In Spain, for example,
  the date would rather be d mm.

  The time format needs to be marked for translation.

  Not sure from which project the notifications come from, for some
  reason I seem to remember they were moved to u-s-s, but if it's the
  wrong project/package, please reassign. Thanks!

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

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


[Dx-packages] [Bug 1378462] Re: cannot reply to second notification

2014-10-10 Thread Lars Uebernickel
indicator-messages doesn't supply the state of whether or not a message
item is expanded or not.

** Changed in: unity8 (Ubuntu)
   Status: Opinion = Triaged

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

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

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

Title:
  cannot reply to second notification

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  build 88, rtm on krillin

  - unlock the phone
  - make sure messaging-app is not running
  - send two sms messages to the phone
  - once they appear, open the messaging-menu
  - reply to the first message by clicking the message which makes it expand to 
reveal the send field
  - this works
  - attempt to reply to the second message by clicking the message to make it 
expand

  Expected results:
  the item should expand and allow you to send a message

  Actual results:
  the item cannot be expanded and you can't reply

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

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


[Dx-packages] [Bug 1369737] Re: Send button does not enable until you press spacebar

2014-10-10 Thread Lars Uebernickel
This is not an issue in indicator-messages. Action parameters (the reply
string is the parameter in this case) cannot have insensitive states.

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

** Changed in: unity8 (Ubuntu)
 Assignee: Lars Uebernickel (larsu) = Nick Dedekind (nick-dedekind)

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

Title:
  Send button does not enable until you press spacebar

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  krillin build 40, rtm image

  - make sure word prediction/preditive text is turned on (this is now the 
default)
  - receive a text message on your phone
  - pull down messaging indicator
  - click on the message
  - type Hello in the entry field

  Expected result:
  - the send button should become active as soon as you start typing

  Actual result:
  - send button stays disabled until you press the spacebar

  The send button should not wait until the word is committed before
  becoming active, but instead should listen for any change and enable
  the button accordingly. The messaging app does this correctly.

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

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


[Dx-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful

2014-10-10 Thread Lars Uebernickel
** Changed in: indicator-messages (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  [Indicators] replace the text Empty! with something more useful

Status in Transfer Indicator:
  Invalid
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “indicator-transfer” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  when clearing the menu on this indicator (and others), the text
  Empty! is displayed. Can we please remove that and put something
  more useful there. It looks bad. Need advise from design..

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

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


[Dx-packages] [Bug 1378463] Re: notifications are very hard to read when indicators open

2014-10-10 Thread Lars Uebernickel
Notifications are handled in unity8, which also knows when the indicator
menu is opened. It could suppress or differently color the bubbles in
that case.

The messaging menu itself never sends notifications.

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

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

Title:
  notifications are very hard to read when indicators open

Status in Ubuntu UX bugs:
  New
Status in “unity-notifications” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  The background color of notifications and the indicator panel is the
  same, making it extremely hard to differentiate a notification from a
  menu item.

  Steps to reproduce:
  - ulock phone
  - send an sms to the phone
  - wait until it arrives and pull down the messageing menu
  - while the menu is pulled down, send another sms to the phone

  Notice when it arrives it looks like another menu item, very hard to
  distinguish that it's a notification

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

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


[Dx-packages] [Bug 1378469] Re: messaging-menu should be closed after sending last message

2014-10-10 Thread Lars Uebernickel
** Package changed: indicator-messages (Ubuntu) = unity8 (Ubuntu)

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

Title:
  messaging-menu should be closed after sending last message

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  if you open the messaging-menu and reply to items in there, it should
  be closed automatically after replying to the last item.

  To reproduce:
  - send an sms to the phone
  - open the messaging-menu
  - reply to the message

  Expected results:
  - the menu should close

  Actual results:
  - a blank messaging-menu stays open, forcing user to close it

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

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


[Dx-packages] [Bug 1378811] Re: If a SIM slot with no signal is selected as the default SIM then replying via the indicator fails silently

2014-10-10 Thread Lars Uebernickel
Reassigning to the components that actually send the message.

** Package changed: indicator-messages (Ubuntu) = messaging-app
(Ubuntu)

** Also affects: telepathy-ofono (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/1378811

Title:
  If a SIM slot with no signal is selected as the default SIM then
  replying via the indicator fails silently

Status in “messaging-app” package in Ubuntu:
  New
Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  Prerquisites:

  The 'For messages use' option in System Settings Cellular panel should
  be set to a slot that contains a SIM card with no signal

  Steps to reproduce:

  1. Send a message to the SUT (with the messaging-app closed)
  2. Wait for the snap notification to disappear
  3. Open the messaging indicator and press anywhere on the message (except on 
the message icon which will open the messaging app)
  4. Enter your reply in the text field that appears (keeping in mind that 
there may be a bug that stops the Send button from being enabled if the 
keyboard is in the middle of autocorrecting a word)
  5.) Hit the send button when it is enabled

  Expected result:

  I'm either informed that sending failed because the SIM had no signal,
  or better, offered the option to rectify this by choosing a SIM for
  that action.

  Actual result:

  The message disappears from the menu, the same as if it was
  successfully sent, but it was not successfully sent (as it was not
  received on the other end).

  Note that if the 'For messages use' option is set to nothing, or 'Ask
  me each time' then the user will be prompted to choose a SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140925-0ubuntu1 [origin: unknown]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: armhf
  Date: Wed Oct  8 12:49:00 2014
  InstallationDate: Installed on 2014-10-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141008-030204)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1378811/+subscriptions

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


[Dx-packages] [Bug 1378048] Re: Forward button does not work

2014-10-06 Thread Lars Uebernickel
Unlikely to be a bug in the sound menu, as that works with all other
players.

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

** Also affects: media-hub (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Forward button does not work

Status in “indicator-sound” package in Ubuntu:
  Incomplete
Status in “media-hub” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

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

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


[Dx-packages] [Bug 1378103] Re: Indicator does not display message and there is no notification when screen is locked and message is in messaging app

2014-10-06 Thread Lars Uebernickel
Unlikely to be a bug in the messaging indicator itself. The messaging
app displays notifications and adds an entry into the messaging menu. If
you can't see notifications either, it's probably a bug in the app.

** Package changed: indicator-messages (Ubuntu) = messaging-app
(Ubuntu)

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

Title:
  Indicator does not display message and there is no notification when
  screen is locked and message is in messaging app

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Steps:
  I used skype for this to make it easy to repro

  0. Set your phone by opening the messaging app to a thread for a conversation 
that you are not about to test then use the power button to blank the screen
  1. Open skype you on your desktop
  2. Use skype to send a text to your phone
  3. Wait a few seconds for the alert
  4. Click on the notification to open it as a conversation in the messaging app
  5. use the power button to blank your screen again
  6. use skype to send another text

  Result:
  The alert sounds plays, and the screen turns on, but there is no notification 
and the message is not in the messaging menu. If you unlock the phone you see 
the message in the conversation.

  Expected:
  The notification shows and the message is in the indicator.

  This is krillin, r84

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1378103/+subscriptions

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


[Dx-packages] [Bug 1374517] Re: Back Forward buttons don't rewind or fast-forward, respectively, the track for however long they are pushed

2014-10-01 Thread Lars Uebernickel
Good point. I didn't implement it yet because it's hard to get right
with MPRIS (the D-Bus protocol we use to talk to media players). Players
do provide a Seek() method, but no way to put them into a seeking state.
That means, it would continue playing while the previous or next button
is pressed and then jump to the new position after the button is
released.

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

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

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

Title:
  Back  Forward buttons don't rewind or fast-forward, respectively, the
  track for however long they are pushed

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

Bug description:
  According to specifications
  https://wiki.ubuntu.com/Sound#Playback_item:

   - If a track is currently playing, the Back button should rewind the track 
for however long it is pushed.
   - If a track is currently playing, the Forward button should fast-forward 
the track for however long it is pushed.

  That doesn't happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 17:44:39 2014
  InstallationDate: Installed on 2014-06-07 (111 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.indicator.sound.desktop: 
2014-06-07T15:18:04.803967

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

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


[Dx-packages] [Bug 1374249] Re: Scrolling works erratically when sound center balance is off-center

2014-10-01 Thread Lars Uebernickel
Indeed, good catch. The sound menu always manipulated the left channel.

I've attached a branch fixes most of the problem by making it handle
channels in the same way that system settings does. Changing the volume
to 0 still resets the balance to center, though (same as in system
settings).

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

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

** Changed in: unity-control-center (Ubuntu)
   Status: New = Triaged

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

** Changed in: unity-control-center (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

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

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = Critical

** Changed in: unity-control-center (Ubuntu)
   Importance: Critical = Medium

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

Title:
  Scrolling works erratically when sound center balance is off-center

Status in “indicator-sound” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  When the center balance is adjusted to the right, scrolling on the
  volume icon in the panel produces erratic results. The same thing
  happens when trying to adjust the volume in the sound menu. The volume
  buttons still function correctly though.

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

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


[Dx-packages] [Bug 1369468] Re: no warning when volume increased to maximum and headphones plugged

2014-10-01 Thread Lars Uebernickel
** Changed in: indicator-sound (Ubuntu)
   Status: New = Triaged

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

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

Title:
  no warning when volume increased to maximum and headphones plugged

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

Bug description:
  Android gives the user a warning if they attempt to raise the volume
  to 100% when headphones are plugged.

  This is a sensible precaution both to save the user from tinnitus and
  to avoid any potential legal repercussions.

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

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


[Dx-packages] [Bug 1347713] Re: cannot launch sound settings from indicator-sound applet panel

2014-10-01 Thread Lars Uebernickel
*** This bug is a duplicate of bug 1359248 ***
https://bugs.launchpad.net/bugs/1359248

** This bug has been marked a duplicate of bug 1359248
   Sound settings no longer works with Gnome Control Center Sound in Xfce

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

Title:
  cannot launch sound settings from indicator-sound applet panel

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

Bug description:
  XUBUNTU  14.04 full updated.

  1) lsb_release -rd : 
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) sudo apt-cache policy indicator-sound
  [sudo] password for $USER: 
  indicator-sound:
Installed: 12.10.2+14.04.20140401-0ubuntu1
Candidate: 12.10.2+14.04.20140401-0ubuntu1
Version table:
   *** 12.10.2+14.04.20140401-0ubuntu1 0
  500 http://es.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) launch pulse audio volumen control
  4) nothing. I captured the 
log(/home/$USER/.cache/upstart/indicator-sound.log):


  ** (process:1854): WARNING **: service.vala:222: unable to launch
  sound settings: Failed to execute child process gnome-control-center
  (No such file or directory)

  ** (process:1854): WARNING **: volume-control.vala:487: unable to sync
  volume to AccountsService:
  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface
  'com.ubuntu.AccountsService.Sound'

  ** (process:1854): WARNING **: volume-control.vala:487: unable to sync
  volume to AccountsService:
  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface
  'com.ubuntu.AccountsService.Sound'

  ** (process:1854): WARNING **: volume-control.vala:487: unable to sync
  volume to AccountsService:
  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface
  'com.ubuntu.AccountsService.Sound'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute': 
(true, '', [false]), 'phone-settings': (true, '', []), 
'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': (true, '', 
[0.2196044921875]), 'scroll': (true, 'i', []), 
'play-playlist.gmusicbrowser.desktop': (true, 's', []), 
'gmusicbrowser.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'desktop-settings': (true, '', []), 'previous.vlc.desktop': 
(true, '', []), 'vlc.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'volume': (true, 'i', [0.46710526315789475]), 
'play-playlist.vlc.desktop': (true, 's', []), 'root': (true, '', [{'title': 
'Sound', 'accessible-desc': 'Volume (46%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': true}]), 'previous.gmusicbrowser.desktop': (true, 
'', []), 'play.gmusicbrowser.desktop': (true, '', ['Paused']), 
'play.vlc.desktop': (true, '', ['Paused'])},)
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul 23 15:47:23 2014
  InstallationDate: Installed on 2014-05-31 (52 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1343681] Re: VLC media player uses ugly motif theme when opened through sound indicator

2014-10-01 Thread Lars Uebernickel
I can't reproduce this in 14.10. Is it still a problem for you? If it
is, please also add VLC as affected.

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

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

Title:
  VLC media player uses ugly motif theme when opened through sound
  indicator

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

Bug description:
  Ubuntu Trusty 14.04

  Steps to reproduce:
  1. Install vlc
  2. Run it once  close
  3. Go into sound indicator and click on the play in mpris indicator for vlc
  4. Vlc opens with some motif / gtk 1.0 theme

  I didn't have time to test, but possibly affects other players like
  Clementine and Amarok, which use QT.

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

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


[Dx-packages] [Bug 1317828] Re: sound indicator disappeared after updates

2014-10-01 Thread Lars Uebernickel
** Changed in: indicator-sound (Ubuntu)
   Status: New = Invalid

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

Title:
  sound indicator disappeared after updates

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

Bug description:
  indicator-sound is missing all over sudden,
  tried to reinstall, no luck there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute': 
(true, '', [false]), 'phone-settings': (true, '', []), 'mic-volume': (true, 
'', [0.123504638671875]), 'scroll': (true, 'i', []), 'vlc.desktop': (true, 
'', [{'running': false, 'state': 'Paused'}]), 'play.clementine.desktop': 
(true, '', ['Paused']), 'previous.vlc.desktop': (true, '', []), 
'desktop-settings': (true, '', []), 'play-playlist.vlc.desktop': (true, 's', 
[]), 'clementine.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'play-playlist.clementine.desktop': (true, 's', []), 'volume': 
(true, 'i', [0.3541107177734375]), 'next.clementine.desktop': (true, '', []), 
'previous.clementine.desktop': (true, '', []), 'root': (true, '', [{'title': 
'Sound', 'accessible-desc': 'Volume (35%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': false}]), 'play.vlc.desktop': (true, '', 
['Paused'])},)
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  9 11:52:11 2014
  InstallationDate: Installed on 2014-04-17 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful

2014-09-12 Thread Lars Uebernickel
 Third, some code in the indicator system itself is inserting the word
Empty! into empty indicator menus and should not

Indeed, unity8 is putting that in while the menu has not been loaded
yet:

  http://bazaar.launchpad.net/~unity-
team/unity8/trunk/view/head:/qml/Panel/Indicators/DefaultIndicatorPage.qml#L200

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

Title:
  [Indicators] replace the text Empty! with something more useful

Status in Transfer Indicator:
  Invalid
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-messages” package in Ubuntu:
  Confirmed
Status in “indicator-transfer” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  when clearing the menu on this indicator (and others), the text
  Empty! is displayed. Can we please remove that and put something
  more useful there. It looks bad. Need advise from design..

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

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


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

2014-09-08 Thread Lars Uebernickel
** Branch linked: lp:~larsu/indicator-datetime/dont-escape-unicode-chars

** Changed in: indicator-datetime
   Status: New = In Progress

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

Title:
  Some translations are not loaded

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

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

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

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


[Dx-packages] [Bug 1358436] Re: Indicator sound missing from unity panel

2014-08-19 Thread Lars Uebernickel
I'm not sure what the bug is here. The setting controls whether the
sound menu is shown or not. If it is set to false, it is not visible. It
can be controlled from the sound panel in System Settings.

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

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

Title:
  Indicator sound missing from unity panel

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

Bug description:
  Indicator sound is missing from the panel. Restarting the panel
  service doesn't bring it up. Neither does a reboot.

  The menu reappeared only after toggling the dconf setting:

  gsettings set com.canonical.indicator.sound visible false
  gsettings set com.canonical.indicator.sound visible true

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 14:31:05 2014
  InstallationDate: Installed on 2013-12-19 (242 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218)
  SourcePackage: indicator-sound
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (101 days ago)
  upstart.indicator-sound.log:
   (process:7458): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
   
   ** (process:12518): CRITICAL **: volume_control_set_volume_internal: 
assertion '_tmp1_ == PA_CONTEXT_READY' failed

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

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


[Dx-packages] [Bug 1329289] Re: Messaging indicator sometimes fails to send a reply

2014-07-26 Thread Lars Uebernickel
I've seen similar issues recently. I'm pretty sure that this is not an
issue in the service, but in the UI layer in unity8.

** Also affects: unity8
   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/1329289

Title:
  Messaging indicator sometimes fails to send a reply

Status in The Unity 8 shell:
  New
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Open the messaging app
  2. Send a message to your own phone
  3. Close the messaging app
  4. Hit the power button
  5. Drag down the indicator
  6. Reply to the message
  7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead 
saves it.

  See attached screenshot  note the greyed send button

  WORKAROUND:
  Remove all messages from the indicator and use the messaging app once to 
reply, you will then be good till your indicator locks up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Thu Jun 12 12:01:29 2014
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140612)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1331460] Re: vlc sound-menu entry broken 14.04

2014-06-23 Thread Lars Uebernickel
 @Lars even mine is `false` it does work perfectly. So it should be
some thing else.

What do you mean by work perfectly? Does the sound menu display the
VLC menu item as senstive and when you click it, VLC's main window is
raised? If so, that would be a bug in the sound menu, because it
shouldn't allow that when 'CanRaise' is false.

Can you give more detail on how to reproduce this state? I always get an
insensitive menu item, no matter whether VLC is playing something or
not.

Please note that starting VLC from the sound menu when it is not running
works fine, as does controlling playback through the menu.

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

Title:
  vlc sound-menu entry broken 14.04

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

Bug description:
  I can observe some weird behaviour (see also 
http://askubuntu.com/questions/481713/vlc-sound-menu-integration-broken-14-04 )
  where the sound-menu entry is insensitive to anything, only when vlc is 
running; when closing vlc one can use the entry to open it again, but as soon 
as it is running the entry becomes insensitive (which means, that the 
back/forward/play buttons do not work) again; 

  Moreover the multimedia-keys do not work for vlc.

  All other players spotify, gmusicbrowser, gnome-mplayer work
  flawlessly...

  I'm Running ubuntu 14.04 and vlc 2.1.4

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

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


[Dx-packages] [Bug 1331460] Re: vlc sound-menu entry broken 14.04

2014-06-18 Thread Lars Uebernickel
Thanks for reporting this bug.

The sound menu shows vlc as inactive because vlc reports that it cannot
raise its main window:

$ gdbus call --session --dest org.mpris.MediaPlayer2.vlc  --object-path 
/org/mpris/MediaPlayer2
  --method org.freedesktop.DBus.Properties.Get 'org.mpris.MediaPlayer2' 
'CanRaise'
(false,)

Also, the sound menu doesn't handle multimedia keys. That's up to the
application.

** Package changed: indicator-sound (Ubuntu) = vlc (Ubuntu)

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

Title:
  vlc sound-menu entry broken 14.04

Status in “vlc” package in Ubuntu:
  New

Bug description:
  I can observe some weird behaviour (see also 
http://askubuntu.com/questions/481713/vlc-sound-menu-integration-broken-14-04 )
  where the sound-menu entry is insensitive to anything, only when vlc is 
running; when closing vlc one can use the entry to open it again, but as soon 
as it is running the entry becomes insensitive (which means, that the 
back/forward/play buttons do not work) again; 

  Moreover the multimedia-keys do not work for vlc.

  All other players spotify, gmusicbrowser, gnome-mplayer work
  flawlessly...

  I'm Running ubuntu 14.04 and vlc 2.1.4

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

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


[Dx-packages] [Bug 1330390] Re: Some messages sent from the indicator never appear in the message-app

2014-06-16 Thread Lars Uebernickel
This is probably a bug in the messaging app. The message is sent, so the
messaging menu definitely communicated it back to the app.

** Package changed: indicator-messages (Ubuntu) = telephony-service
(Ubuntu)

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

Title:
  Some messages sent from the indicator never appear in the message-app

Status in “telephony-service” package in Ubuntu:
  New

Bug description:
  Sometimes, when I answer a message directly from the indicator panel,
  the message *is* sent, but is never visible in the message-app, even
  after restarting.

  I'm sadly at the moment unable to reproduce this bug for sure, but it
  occurs to me very often so I prefer to file an issue yet, in case
  others can help or in case in ring a bell to someone.

  I'm on #79, on a Nexus 4 (I've two phones, and I've seen this on
  both).

  I will post again if I have a clearer STR.

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

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


[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app

2014-06-11 Thread Lars Uebernickel
 I disagree. The x-canonical-snap-decisions-timeout is intentionally used in
 favour of the Freedesktop timeout feature, to indicate very clearly, that is
 is only applicable to snap-decisions notifications.

I think that's unnecessary for the same reason I thought introducing hints for
snap decision actions was unnecessary. It's unlikely that developers have a
problem understanding that the timeout only applies to a specific kind of
notification. They already need to know about the different kinds of
notifications and what they can do with them.

Adding additional hints only increases the complexity of the API and makes it
harder to switch between different kinds of notifications.

 Using the regular parameter of the Notify() method - and only applying it
 snap-decisioin notifications - would be misleading, because the intention of
 that timeout parameter is to be affecting all kinds of notifications.

We already go against the intention of that parameter by ignoring it
completely. In fact, we go against the freedesktop specification, which states
that notification servers need to honor this parameter.

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

Title:
  snap decision timeout needs to be determined by the requesting app

Status in Network Menu:
  Fix Released
Status in Telephony Service:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity:
  Invalid
Status in Server and client library for desktop notifications in Unity:
  Confirmed
Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-notifications” package in Ubuntu:
  Fix Released

Bug description:
  Problem:
  If user receives an SMS/call, snap decision for incoming SMS/call stays on 
screen for always only 60sec. and then disappears from screen (by default). 
There was no interaction from user. 

  Possible solution:
  The snap decision should stay on screen for the amount of time the app asks 
it to, being always app dependant. 
  A 60sec. time-out is too short due to use cases where an action from user is 
mandatory. 

  Use case example: A class 1/2 SMS arrives after user triggered a USSD
  command from dialer. These type of SMS always requires a response from
  user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is
  too short because it can be missed and these type of SMS is NOT saved
  into the usual messages thread.

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

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


[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app

2014-06-11 Thread Lars Uebernickel
 It's unlikely that developers have a problem understanding that the
 timeout only applies to a specific kind of notification.
 Being explicit rather than implicit avoids misunderstanding and
 possible false-positive bug-reports due to that.

I agree with that sentiment, but think it's the wrong trade-off with
regards to simplicity. We already have precedence for snap decisions
behaving differently when using the standard API (for example, snap
decisions must have at least one action and they're the only
notification type that can be cancelled). Did we see many bug reports
from confused developers for that?

 Adding additional hints only increases the complexity of the API and
 makes it harder to switch between different kinds of notifications.
 By design every introduced notification-type serves a very
 specific purpose, that differs in behaviour, visuals and interaction.
 Thus switching between different notification-types is not a common
 thing to do for a developer, unless UX-requirements change later on.

UX requirements change all the time. Also, just because it's not common
doesn't mean we need to make it difficult.

I'll stop arguing about this though if you feel strongly about it. I
don't think we'll be using this API for much longer anyway.

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

Title:
  snap decision timeout needs to be determined by the requesting app

Status in Network Menu:
  Fix Released
Status in Telephony Service:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity:
  Invalid
Status in Server and client library for desktop notifications in Unity:
  Confirmed
Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-notifications” package in Ubuntu:
  Fix Released

Bug description:
  Problem:
  If user receives an SMS/call, snap decision for incoming SMS/call stays on 
screen for always only 60sec. and then disappears from screen (by default). 
There was no interaction from user. 

  Possible solution:
  The snap decision should stay on screen for the amount of time the app asks 
it to, being always app dependant. 
  A 60sec. time-out is too short due to use cases where an action from user is 
mandatory. 

  Use case example: A class 1/2 SMS arrives after user triggered a USSD
  command from dialer. These type of SMS always requires a response from
  user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is
  too short because it can be missed and these type of SMS is NOT saved
  into the usual messages thread.

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

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


[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app

2014-06-05 Thread Lars Uebernickel
Reopening, because adding the x-canonical-snap-decisions-timeout hint
was a bad idea. The notification spec already has a timeout parameter on
org.freedesktop.Notifications.Notify(). We can just use that one for
snap decisions and ignore it for all other notification types.

I've attached branches for unity-notifications and indicator-network.

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

** Changed in: indicator-network (Ubuntu)
   Status: Fix Released = Confirmed

** Branch linked: lp:~larsu/unity-notifications/revert-timeout

** Branch linked: lp:~larsu/indicator-network/use-standard-timeout

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

Title:
  snap decision timeout needs to be determined by the requesting app

Status in Network Menu:
  Fix Released
Status in Telephony Service:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity:
  Invalid
Status in Server and client library for desktop notifications in Unity:
  Confirmed
Status in “indicator-network” package in Ubuntu:
  Confirmed
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-notifications” package in Ubuntu:
  Fix Released

Bug description:
  Problem:
  If user receives an SMS/call, snap decision for incoming SMS/call stays on 
screen for always only 60sec. and then disappears from screen (by default). 
There was no interaction from user. 

  Possible solution:
  The snap decision should stay on screen for the amount of time the app asks 
it to, being always app dependant. 
  A 60sec. time-out is too short due to use cases where an action from user is 
mandatory. 

  Use case example: A class 1/2 SMS arrives after user triggered a USSD
  command from dialer. These type of SMS always requires a response from
  user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is
  too short because it can be missed and these type of SMS is NOT saved
  into the usual messages thread.

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

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


[Dx-packages] [Bug 1323992] Re: Logout doesn't call com.canonical.Unity.Session.RequestLogout

2014-05-29 Thread Lars Uebernickel
** Changed in: indicator-session (Ubuntu)
   Importance: High = Critical

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

Title:
  Logout doesn't call com.canonical.Unity.Session.RequestLogout

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

Bug description:
  Hi,

  I've tried with by branch lp:~paulliu/unity8/logout with Unity-Mir session.
  When manually using qdbus, I can successfully kill unity8 process.
  But when click logout in indicator-session, I found it didn't call 
com.canonical.Unity.Session.RequestLogout
  Here's the dbus-monitor --session log http://paste.ubuntu.com/7534797/

  Please check it.

  Many Thanks,
  Paul

  --
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - 
About Ubuntu

  Distributor ID:   Ubuntu
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10
  Codename: utopic

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  indicator-session:
Installed: 12.10.5+14.04.20140410-0ubuntu1
Candidate: 12.10.5+14.04.20140410-0ubuntu1
Version table:
   *** 12.10.5+14.04.20140410-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages
  500 http://tw.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  unity8 process killed

  4) What happened instead

  nothing happened.

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

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


[Dx-packages] [Bug 1315384] Re: python-indicate not showing up in message indicator

2014-05-28 Thread Lars Uebernickel
libmessaging-menu doesn't depend on gtk. It shouldn't matter which gtk
version you use as long as glib is up to date.

I agree that the package should be removed.

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

Title:
  python-indicate not showing up in message indicator

Status in Libindicate:
  Confirmed
Status in “libindicate” package in Ubuntu:
  Confirmed

Bug description:
  Install python-indicate and libindicate-doc. Run:

  python /usr/share/doc/libindicate/examples/im-client.py

  An entry should appear in message indicator, but does not. That worked
  in 12.04 but is broken in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-indicate 12.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 15:22:27 2014
  InstallationDate: Installed on 2014-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: libindicate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1319983] Re: notify-osd loses pending bubble if append occurs when bubble is not yet visible

2014-05-16 Thread Lars Uebernickel
** Changed in: notify-osd (Ubuntu)
   Status: New = In Progress

** Changed in: notify-osd (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

** Branch linked: lp:~larsu/notify-osd/lp1319983

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

Title:
  notify-osd loses pending bubble if append occurs when bubble is not
  yet visible

Status in “notify-osd” package in Ubuntu:
  In Progress
Status in “notify-osd” source package in Trusty:
  New

Bug description:
  [Impact]
  When a notification specifiying x-canonical-append:true is recieved and 
merges with a bubble the bubble will be lost if the bubble is not yet visible.  
We will also update times incorrectly on any synchronous bubble.

  [Test Case]
  Running the attached scripts (play.py and play2.py) show the issue: bubbles 
after the first one aren't shown, because they specify x-canonical-append. The 
attached branch fixes that.

  [Regression Potential]
  The patch only touches code that is concerned with updating an existing 
notification. This is currently broken anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1319983/+subscriptions

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


[Dx-packages] [Bug 1304434] Re: indicator-printers not working on Ubuntu 14.04

2014-05-15 Thread Lars Uebernickel
Sorry about that bug. I wonder how it even got through unnoticed.

** Branch linked: lp:~larsu/indicator-printers/lp1304434

** Project changed: unity = indicator-printers

** Changed in: indicator-printers
   Status: New = In Progress

** Changed in: indicator-printers
 Assignee: (unassigned) = Lars Uebernickel (larsu)

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

Title:
  indicator-printers not working on Ubuntu 14.04

Status in Print Indicator:
  In Progress
Status in “indicator-printers” package in Ubuntu:
  Confirmed

Bug description:
  even after lates updates still no printer notifications in the panel .
  I checked and the package indicator-printers is correctly installed
  and the printer prints without problems. But, there is no notification
  icons on unity panel. I had no problems at all with 13.10 instead

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

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


[Dx-packages] [Bug 1304434] Re: indicator-printers not working on Ubuntu 14.04

2014-05-15 Thread Lars Uebernickel
** Description changed:

- even after lates updates still no printer notifications in the panel . I
- checked and the package indicator-printers is correctly installed and
- the printer prints without problems. But, there is no notification icons
- on unity panel. I had no problems at all with 13.10 instead
+ [Impact]
+ The panel should have a print indicator as long as there are any print jobs 
queued or processed. Currently, this indicator never appears, even though 
printing works fine.
+ 
+ This is because the service that listens to CUPS fails to register its
+ D-Bus name (as of revision 68), which results in the panel component not
+ finding the service. The attached branch fixes this by making the
+ service register the name the panel expects.
+ 
+ [Test Case]
+ Print a document from any application and check whether the print indicator 
appears while it is printing.
+ 
+ [Regression Potential]
+ Almost none. The print indicator is not working at all right now, and the fix 
only touches that indicator.
+ 
+ [Original Description]
+ even after lates updates still no printer notifications in the panel . I 
checked and the package indicator-printers is correctly installed and the 
printer prints without problems. But, there is no notification icons on unity 
panel. I had no problems at all with 13.10 instead

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

Title:
  indicator-printers not working on Ubuntu 14.04

Status in Print Indicator:
  In Progress
Status in “indicator-printers” package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  The panel should have a print indicator as long as there are any print jobs 
queued or processed. Currently, this indicator never appears, even though 
printing works fine.

  This is because the service that listens to CUPS fails to register its
  D-Bus name (as of revision 68), which results in the panel component
  not finding the service. The attached branch fixes this by making the
  service register the name the panel expects.

  [Test Case]
  Print a document from any application and check whether the print indicator 
appears while it is printing.

  [Regression Potential]
  Almost none. The print indicator is not working at all right now, and the fix 
only touches that indicator.

  [Original Description]
  even after lates updates still no printer notifications in the panel . I 
checked and the package indicator-printers is correctly installed and the 
printer prints without problems. But, there is no notification icons on unity 
panel. I had no problems at all with 13.10 instead

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

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


[Dx-packages] [Bug 1315384] Re: python-indicate not showing up in message indictor

2014-05-08 Thread Lars Uebernickel
libmessaging-menu already comes with python bindings through gobject-
introspection. Unfortunately the online documentation seems to have been
taken down. The libmessaging-menu-dev package contains the C
documentation (viewable with devhelp), which maps 1:1 to the python API.

Here's a simple example:

from gi.repository import GLib, Gio, MessagingMenu

mmapp = MessagingMenu.App(desktop_id='my-app.desktop')

# make the application appear in the messaging menu. The name and icon are 
taken from the desktop file above
mmapp.register()

def source_activated(mmapp, source_id):
  print('source {} activated'.format(source_id))

# do something when the user clicks on a source. The source will be removed 
automatically
mmapp.connect('activate-source', source_activated)

# add a 'source' (a menu item below the application's name) with the name 
'Inbox' and a count of 7
icon = Gio.ThemedIcon.new_with_default_fallbacks('my-source-icon')
mmapp.append_source_with_count('inbox', icon, 'Inbox', 7)

# this is not necessary for gtk applications, which start a mainloop in 
gtk_main()
GLib.MainLoop().run()

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

Title:
  python-indicate not showing up in message indictor

Status in Libindicate:
  Confirmed
Status in “libindicate” package in Ubuntu:
  Confirmed

Bug description:
  Install python-indicate and libindicate-doc. Run:

  python /usr/share/doc/libindicate/examples/im-client.py

  An entry should appear in message indicator, but does not. That worked
  in 12.04 but is broken in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-indicate 12.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 15:22:27 2014
  InstallationDate: Installed on 2014-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: libindicate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1315384] Re: python-indicate not showing up in message indictor

2014-05-07 Thread Lars Uebernickel
libindicate has been deprecated in favor of libmessaging-menu in Quantal
(12.10), becasue we couldn't use libindicate on the phone. Porting to
libmessaging-menu is fairly simple. Let me know if you need any
pointers.

Note that this might change again when we switch to Unity8, which will
most likely have a Qt/QML API as part of the SDK. Sorry about that.

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

Title:
  python-indicate not showing up in message indictor

Status in Libindicate:
  Confirmed
Status in “libindicate” package in Ubuntu:
  Confirmed

Bug description:
  Install python-indicate and libindicate-doc. Run:

  python /usr/share/doc/libindicate/examples/im-client.py

  An entry should appear in message indicator, but does not. That worked
  in 12.04 but is broken in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-indicate 12.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 15:22:27 2014
  InstallationDate: Installed on 2014-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: libindicate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1316613] Re: com.canonical.desktop.interface scrollbar-mode corrupts gtk3 apps in non-Unity desktops

2014-05-06 Thread Lars Uebernickel
No, it is not just a theme problem, but it can be fixed by setting
backgrounds for various widgets in the theme. We did that for ubuntu-
themes last cycle.

These theme fixes aren't necessary with gtk 3.12 (or without overlay-
scrollbars).

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

Title:
  com.canonical.desktop.interface scrollbar-mode corrupts gtk3 apps in
  non-Unity desktops

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

Bug description:
  This setting needs to be 'normal' for non-Unity desktops (i.e. Gnome-
  Shell, Cinnamon) or else background color corruption occurs in certain
  widgets (I suspect maybe the GtkScrolledWindow widgets?)

  See pictures here:

  https://github.com/linuxmint/Cinnamon/issues/2771

  Nothing immediately jumps out at me in the quilt patches, but I will
  investigate further and see if I can troubleshoot this as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1316613/+subscriptions

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


[Dx-packages] [Bug 1312968] Re: Open an App from Indicator doesn't work correctly

2014-05-02 Thread Lars Uebernickel
The sound menu start the applications through GLib's
g_app_info_launch(). Maybe clementine can't handle being started from a
different environment?

There's another bug in that clementine doesn't show its main window when
starting it from the sound menu (or the launcher) for the first time.

** Package changed: indicator-sound (Ubuntu) = clementine (Ubuntu)

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

Title:
  Open an App from Indicator doesn't work correctly

Status in “clementine” package in Ubuntu:
  Confirmed

Bug description:
  When I open clementine from the dash the theme and the icons of my gtk theme 
work. But when I open clementine from the sound menu the gtk theme is broken.
  Ubuntu 14.04
  indicator-sound 12.10.2+14.04.20140401-0ubuntu1

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

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


[Dx-packages] [Bug 1312097] Re: in Ubuntu14.04, the indicator don't work corretly

2014-04-24 Thread Lars Uebernickel
What do you mean by the sound go in the other way? Scrolling up is
supposed to increase the volume and scrolling down decrease it. Is it
the other way around for you?

Do you mean scrolling over the sound menu title in the panel or
scrolling on the volume slider in the sound menu itself?

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

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

Title:
  in Ubuntu14.04,  the indicator don't work corretly

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

Bug description:
  Problem:  in Ubuntu 14.04 the indicator-sound don't work corretly,
  for example i can't adjust sound with scrolling because the sound go
  in the other way (mouse don't have any problem, this is a problem of
  indicator!)

  My Solution i had install Saucy Salamander indicator sound, and this
  work corretly!

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

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


[Dx-packages] [Bug 1080076] Re: Music titles in SoundMenu too small

2014-04-23 Thread Lars Uebernickel
** Description changed:

- When looking at the currently running track in SoundMenu (clementine
- music player), the space for the title of the track and album are too
- small, because the album art is directly next to it. Both titles are
- truncated and thus almost unreadable, when longer than about 10
- characters.
+ [Impact]
+ The artist/title/album labels in the sound menu are often hard to read 
because they get ellipsized fairly quickly (i.e., for relatively short labels). 
Also, the menu is visually unbalanced in languages with longer strings (making 
the menu wider), because the playback controls are hardcoded with a ~100px left 
margin.
+ 
+ The fix for this bug makes the font size a bit smaller, according to the
+ design spec for the sound menu. It also makes sure that labels with a
+ width of about 25 characters are always shown in full, independent of
+ the font size. The playback controls are centered.
+ 
+ [Test Case]
+ Play a song in Rhythmbox that has an track name (or artist or album name) 
that is longer than about 20 characters. Open the sound menu and see that the 
long label is ellpsized.
+ 
+ [Regression Potential]
+ If the fix to this bug is faulty, it might lead to weird menu sizes (too 
small or too large). The playback controls used hard-coded coordinates for 
drawing and hit detection. Rendering or selection bugs might occur.
+ 
+ 
+ [Original Description]
+ When looking at the currently running track in SoundMenu (clementine music 
player), the space for the title of the track and album are too small, because 
the album art is directly next to it. Both titles are truncated and thus almost 
unreadable, when longer than about 10 characters.
  
  Is it possible to put the album artwork in a different column? Or make
  the SoundMenu wider?

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

Title:
  Music titles in SoundMenu too small

Status in elementary OS:
  Invalid
Status in Indicator Display Objects:
  In Progress
Status in “ido” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  The artist/title/album labels in the sound menu are often hard to read 
because they get ellipsized fairly quickly (i.e., for relatively short labels). 
Also, the menu is visually unbalanced in languages with longer strings (making 
the menu wider), because the playback controls are hardcoded with a ~100px left 
margin.

  The fix for this bug makes the font size a bit smaller, according to
  the design spec for the sound menu. It also makes sure that labels
  with a width of about 25 characters are always shown in full,
  independent of the font size. The playback controls are centered.

  [Test Case]
  Play a song in Rhythmbox that has an track name (or artist or album name) 
that is longer than about 20 characters. Open the sound menu and see that the 
long label is ellpsized.

  [Regression Potential]
  If the fix to this bug is faulty, it might lead to weird menu sizes (too 
small or too large). The playback controls used hard-coded coordinates for 
drawing and hit detection. Rendering or selection bugs might occur.

  
  [Original Description]
  When looking at the currently running track in SoundMenu (clementine music 
player), the space for the title of the track and album are too small, because 
the album art is directly next to it. Both titles are truncated and thus almost 
unreadable, when longer than about 10 characters.

  Is it possible to put the album artwork in a different column? Or make
  the SoundMenu wider?

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

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


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

2014-04-23 Thread Lars Uebernickel
It's unlikely that this is a bug in the messaging menu. Even if it were
restarting, it would request all currently pending messages from the
applications again. Reassigning.

** Package changed: indicator-messages (Ubuntu) = telephony-service
(Ubuntu)

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

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

Status in “telephony-service” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  PREREQUISITE:
  2 phones

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

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

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

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

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


[Dx-packages] [Bug 1310490] Re: indicator-messages is hidden on 14.04 LTS

2014-04-21 Thread Lars Uebernickel
Hey, thanks for reporting this issue. The messaging menu hides itself
when no applications are using it. The output of

  gsettings get com.canonical.indicator.messages applications

shows a list of applications that have registered to appear in the menu.
Do Thunderbird and gmail-notifier appear in that list?

Also, is indicator-messages-service running?

** Changed in: indicator-messages (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/1310490

Title:
  indicator-messages is hidden on 14.04 LTS

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

Bug description:
  I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've
  noticed, that the mail icon is hidden. I've reinstalled the package:
  `sudo apt-get install --reinstall indicator-messages` - it was
  successful, but didn't change anything. Tried to install thunderbird,
  but nothing changed.

  If I want to run it manually ($ indicator-messages or with Alt+F2) the
  command not found...

  I know, that it is hidden, because I'm using GMail Notifier, which
  displays itself, and it works.

  Package info:
  indicator-messages:
Installed: 13.10.1+14.04.20140410-0ubuntu1
Candidate: 13.10.1+14.04.20140410-0ubuntu1
Version table:
   *** 13.10.1+14.04.20140410-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Please fix this issue!

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

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


[Dx-packages] [Bug 1310490] Re: indicator-messages is hidden on 14.04 LTS

2014-04-21 Thread Lars Uebernickel
The gmail-notifier doesn't register to use the messaging menu, then.
Reassigning this bug to that project.

** Package changed: indicator-messages (Ubuntu) = gm-notify (Ubuntu)

** Changed in: gm-notify (Ubuntu)
   Status: Incomplete = 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/1310490

Title:
  indicator-messages is hidden on 14.04 LTS

Status in “gm-notify” package in Ubuntu:
  New

Bug description:
  I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've
  noticed, that the mail icon is hidden. I've reinstalled the package:
  `sudo apt-get install --reinstall indicator-messages` - it was
  successful, but didn't change anything. Tried to install thunderbird,
  but nothing changed.

  If I want to run it manually ($ indicator-messages or with Alt+F2) the
  command not found...

  I know, that it is hidden, because I'm using GMail Notifier, which
  displays itself, and it works.

  Package info:
  indicator-messages:
Installed: 13.10.1+14.04.20140410-0ubuntu1
Candidate: 13.10.1+14.04.20140410-0ubuntu1
Version table:
   *** 13.10.1+14.04.20140410-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Please fix this issue!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gm-notify/+bug/1310490/+subscriptions

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


[Dx-packages] [Bug 1302930] Re: Every message gets new list item on empathy indicator

2014-04-15 Thread Lars Uebernickel
** Branch linked: lp:~larsu/telepathy-indicator/lp1302930

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

** Changed in: indicator-messages (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

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

Title:
  Every message gets new list item on empathy indicator

Status in “indicator-messages” package in Ubuntu:
  In Progress

Bug description:
  In messaging indicator i see every message as a separate item, even
  with same person. So i have many notifications with same persons. Also
  opening empathy doesn't remove item from list. Only clicking on
  indicator element.

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

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


[Dx-packages] [Bug 1307441] Re: The conversation window by Empathy is blank...

2014-04-14 Thread Lars Uebernickel
*** This bug is a duplicate of bug 1195276 ***
https://bugs.launchpad.net/bugs/1195276

Hey Joshua. Thanks for taking the time to report this bug. I'm marking
it as a duplicate because it has already been reported as bug #1195276.

** This bug has been marked a duplicate of bug 1195276
   Chat messages are not displayed

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

Title:
  The conversation window by Empathy is blank...

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

Bug description:
  Hello, when someone send me a message indicator-messages notices me
  the message but when I open it from indicator-menù the conversation
  windows is empty. If I open Empathy and choose to open the user
  convertation the window shows me the unseen messages and everything
  works fine. I hope all of you understood what I mean...

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

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


[Dx-packages] [Bug 1252026] Re: Message indicator and Empathy showing different status

2014-04-11 Thread Lars Uebernickel
This seems to be a bug in empathy. telepathy-indicator (the component
providing messaging menu integration with empathy) correctly requests
TP_CONNECTION_PRESENCE_TYPE_HIDDEN when I choose invisible from the
messaging menu.

** Package changed: indicator-messages (Ubuntu) = empathy (Ubuntu)

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

Title:
  Message indicator and Empathy showing different status

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Maybe related to #1103438. The following behaviour occurs:

  -if I select Invisible from Messaging Menu, Empathy actually changes to 
Busy.
  -if I select Invisible in Empathy it activates Busy in Empathy instead. 
Messaging Menu however also shows Busy when this happens.

  The behaviour is not always consistent, it depends on the exact order
  the status is selected.

  Description:  Ubuntu 13.10
  Release:  13.10
  empathy 3.8.4-1ubuntu2
  indicator-messages 13.10.1+13.10.20131011-0ubuntu1

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

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


[Dx-packages] [Bug 1259564] Re: GPG_AGENT_INFO not being passed to thunderbird

2014-04-11 Thread Lars Uebernickel
indicator-messages was ported to upstart recently, which should make
sure that it is started with the right environment.

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

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

Title:
  GPG_AGENT_INFO not being passed to thunderbird

Status in “indicator-messages” package in Ubuntu:
  Fix Released

Bug description:
  On Trusty, if I launch thunderbird from the terminal or from the Dash,
  then thunderbird is able to use enigmail. If I launch via indicator-
  messages, it is not.

  Steps to reproduce:
  1. adjust /usr/lib/thunderbird/thunderbird.sh to have:
  echo TEST: $GPG_AGENT_INFO  /tmp/tbird.gpg

  2. Launch from a terminal:
  $ rm -f /tmp/tbird.gpg ; thunderbird
  $ cat /tmp/tbird.gpg # separate terminal
  TEST: /run/user/1000/keyring-bzAKyI/gpg:0:1
  (It worked!)

  3. Launch from the Dash:
  $ rm -f /tmp/tbird.gpg
  launch from Dash
  $ cat /tmp/tbird.gpg # separate terminal
  TEST: /run/user/1000/keyring-bzAKyI/gpg:0:1
  (It worked!)

  4. Launch from indicator-messages:
  $ rm -f /tmp/tbird.gpg
  select Thunderbird Mail from indicator-messages
  $ cat /tmp/tbird.gpg # separate terminal
  TEST:
  (It did not work)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-messages 13.10.1+14.04.20131125-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 10 07:59:07 2013
  InstallationDate: Installed on 2011-06-28 (895 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110425.2)
  SourcePackage: indicator-messages
  UpgradeStatus: Upgraded to trusty on 2013-11-04 (35 days ago)

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

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


[Dx-packages] [Bug 1260728] Re: Indicators should send timestamps, not pre-formatted strings

2014-04-11 Thread Lars Uebernickel
indicator-messages uses time stamps for all times.

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

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

Title:
  Indicators should send timestamps, not pre-formatted strings

Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Triaged
Status in “indicator-messages” package in Ubuntu:
  Invalid

Bug description:
  Some indicators send pre-formatted strings, when they should be
  sending unix timestamps, to be formatted by the UI according to locale
  / timezone / user preferences.

  See https://wiki.ubuntu.com/TimeAndDate for the design spec.

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

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


[Dx-packages] [Bug 1185565] Re: Indicators should have Upstart jobs

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-messages (Ubuntu)
   Status: New = Fix Released

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

Title:
  Indicators should have Upstart jobs

Status in Application Indicators:
  Fix Committed
Status in The Date and Time Indicator:
  Fix Released
Status in Indicator Location:
  Fix Committed
Status in Network Menu:
  Fix Released
Status in The Power Indicator:
  Fix Released
Status in The Session Menu:
  Fix Released
Status in Sound Menu:
  Fix Released
Status in The Sync Menu:
  Fix Committed
Status in Libindicator:
  Confirmed
Status in Unity:
  Fix Released
Status in “indicator-application” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-sync” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “unity-greeter” package in Ubuntu:
  Fix Released

Bug description:
  Indicators should move over to using the upstart jobs to get better
  logging and management of their processes.

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

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


[Dx-packages] [Bug 1216833] Re: sorting is wrong with the converged indicator codebase

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-messages
   Status: In Progress = Fix Released

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

Title:
  sorting is wrong with the converged indicator codebase

Status in The Messaging Menu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released

Bug description:
  The design (https://wiki.ubuntu.com/MessagingMenu#Presentation) states
  that the default chat and email clients should be first, the new
  codebase has sources alphabetically sorted though

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

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


[Dx-packages] [Bug 764389] Re: if on a different workspace, clicking on an indicator applet like evolution mail does not switch workspace

2014-04-11 Thread Lars Uebernickel
*** This bug is a duplicate of bug 1047809 ***
https://bugs.launchpad.net/bugs/1047809

** This bug is no longer a duplicate of bug 882277
   When clicking an item from the messaging menu, it doesn't changes virtual 
desktop
** This bug has been marked a duplicate of bug 1047809
   Needs to set timestamps, so applications don't open in background

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

Title:
  if on a different workspace, clicking on an indicator applet like
  evolution mail does not switch workspace

Status in Ayatana Design:
  New
Status in The Messaging Menu:
  Incomplete
Status in Unity:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  if on a different workspace, clicking on an indicator applet like
  evolution mail does not switch workspace

  scenario:

  you are working on workspace 2 and evolution mail is open in workspace
  1. A new mail arrives and the indicator turns blue. You click on the
  blue envelope and you see that you've got a mail!. So you click on the
  unread mail count of the evolution indicator applet, but you are not
  taken to the evolution mail interface as you are working on a
  different workspace.

  This functionality is avalable in the gnome 2.30 and ubuntu 10.10.

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

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


[Dx-packages] [Bug 1225063] Re: cannot remove/uninstall online/offline indicator

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-messages
   Status: In Progress = Fix Released

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

Title:
  cannot remove/uninstall online/offline indicator

Status in The Messaging Menu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released

Bug description:
  I'd like to remove and uninstall the package which provides this:
  http://i.imgur.com/6zcx7Jq.png

  Since there is no About/settings, I don't know which app this is.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-services 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Sep 13 19:06:04 2013
  InstallationDate: Installed on 2013-09-09 (3 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130909)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1088029] Re: turn off the notifications in accordance to the messaging menu status

2014-04-11 Thread Lars Uebernickel
This has nothing to do with the messaging menu, as that doesn't actually
show the popups.

** No longer affects: indicator-messages

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

Title:
  turn off the notifications in accordance to the messaging menu status

Status in Ayatana Design:
  New
Status in “notify-osd” package in Ubuntu:
  Incomplete

Bug description:
  The messaging menu status (online/away/busy/offline) should not be
  restricted to instant messaging. Switching it to busy should turn
  off the new mail notifications, especially the popup and the sound.

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

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


[Dx-packages] [Bug 1245495] Re: Rhythmbox controls and track info broken

2014-04-11 Thread Lars Uebernickel
zomtir, thanks for looking into this. However, we can't make this
dependent on the proxy being available, as we want to allow starting
recently-used players from the sound menu as well.

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

Title:
  Rhythmbox controls and track info broken

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

Bug description:
  A Rhythmbox section appears in the indicator menu as it should but
  there are several glitches:

  When RB isn't running  click on the icon in the indicator  RB starts as 
expected  :-)
  When RB is running  click on the icon in the indicator  RB icon wiggles in 
launcher but window doesn't come to focus  :-(

  Track info and album art appears in notifications, but is never shown
  in the sound menu.

  Regardless of whether RB is running:
  Sound menu track controls (prev, play/pause, next) do nothing.
  The play/pause button has a dotted orange ring, which turns to an orange 
square on mouseover (see screenshots).

  Ubuntu 13.10 64-bit
  unity: 7.1.2+13.10.20131014.1-0ubuntu1
  indicator-sound: 12.10.2+13.10.20131011-0ubuntu1
  rhythmbox: 2.99.1-0ubuntu1

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

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


[Dx-packages] [Bug 1297078] Re: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service:11:g_str_hash:g_hash_table_lookup_node:g_hash_table_lookup:media_player_list_greeter_iterator_real_nex

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Confirmed = Fix Released

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

Title:
  /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-
  
service:11:g_str_hash:g_hash_table_lookup_node:g_hash_table_lookup:media_player_list_greeter_iterator_real_next_value:indicator_sound_service_update_preferred_players

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-sound.  This problem was most recently seen with
  version 12.10.2+14.04.20140324-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9dbe66d2829b8e3ffdaf0c61c37d0777f031ce1c
  contains more details.

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

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


[Dx-packages] [Bug 652978] Re: Notify-OSD should be suppressed when using the sound menu

2014-04-11 Thread Lars Uebernickel
This issue cannot be solved in the sound menu. It is up to the
applications to issue notification bubbles based on how the track was
changed. Similarly for notify-osd: it doesn't have enough information to
decide whether to show the bubble (namely, where the track-changed event
was originally from).

I think apps should never show a notification in response to a manual
track change, unless the track was changed using the media keys.

** Changed in: indicator-sound (Ubuntu)
   Status: Triaged = Invalid

** Changed in: indicator-sound
   Status: Triaged = Invalid

** Changed in: notify-osd (Ubuntu)
   Status: Triaged = Invalid

-- 
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, dx-packages
https://bugs.launchpad.net/bugs/652978

Title:
  Notify-OSD should be suppressed when using the sound menu

Status in Ayatana Design:
  Fix Committed
Status in Sound Menu:
  Invalid
Status in “indicator-sound” package in Ubuntu:
  Invalid
Status in “notify-osd” package in Ubuntu:
  Invalid

Bug description:
  When using the sound menu, the user is immediately visually notified
  about switching of tracks by the menu itself.

  +

  When notifying using Notify-OSD, it covers some parts of sound menu
  itself. I think Notify-OSD should not be shown when switching tracks
  using the sound-menu and MAY BE whenever switching manually.

  Example video:
  http://dl.dropbox.com/u/275756/out.ogv

  
  PS:
  U1 was not working, so dropbox. :)
  and yes, I did spend like 10 minutes thinking which songs I should show in 
the video. :P

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

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


[Dx-packages] [Bug 733285] Re: Focus indication on playback controls is misleading

2014-04-11 Thread Lars Uebernickel
** Changed in: ido
   Status: In Progress = Fix Released

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

Title:
  Focus indication on playback controls is misleading

Status in Indicator Display Objects:
  Fix Released
Status in “ido” package in Ubuntu:
  Fix Released

Bug description:
  indicator-sound 0.6.2-0ubuntu1, Ubuntu 11.04
  indicator-sound 12.10.2+13.10.20131011-0ubuntu1, Ubuntu 13.10

  1. Open the sound menu.
  2. Hover over, or use arrow keys to navigate to, the Back/Rewind button.

  What happens: The Play button is highlighted.
  https://launchpadlibrarian.net/71790474/out-2.ogv

  What should happen: The Back/Rewind button is highlighted.

  The same problem happens with the Next/Forward button.

  https://wiki.ubuntu.com/Sound#playback-item: The Space key should
  visibly activate whichever button is highlighted. However,
  highlighting the Back or Forward button with a keyboard should not be
  possible; instead, the Left and Right keys should immediately activate
  Back and Forward respectively whenever any of the three are
  highlighted.

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

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


[Dx-packages] [Bug 1297818] Re: indicator-sound keyboard navigation issues

2014-04-11 Thread Lars Uebernickel
** Changed in: ido
   Status: In Progress = Fix Released

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

Title:
  indicator-sound keyboard navigation issues

Status in Indicator Display Objects:
  Fix Released
Status in “ido” package in Ubuntu:
  Fix Released

Bug description:
  Using current trusty with
  https://code.launchpad.net/~larsu/ido/lp733285/+merge/212691 (though
  the issue is probably not new to those changes)

  - get totem added to indicator-sound (use it with the mpris plugin enabled)
  - open the indicator
  - go to the line of totem controls with the keyboard

  - the play button is selected

  - use left/right keys

  - the back/forward buttons get selected, there is no way to go back
  on the play one

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

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


[Dx-packages] [Bug 1306499] Re: Sound indicator is laggy #287 on mako

2014-04-11 Thread Lars Uebernickel
This is a UI issue. We're using the same indicator-sound on unity7 and
have no such issues.

** Package changed: indicator-sound (Ubuntu) = unity8 (Ubuntu)

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

Title:
  Sound indicator is laggy #287 on mako

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Open sound indicator
  Try and swipe the volume up and down
  Try and increase/decrease volume with the hardware vol+  vol- keys
  Note that the slider takes a long time to update, and sometimes leaps 
backwards and forwards despite you only holding one button down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: armhf
  Date: Fri Apr 11 10:39:43 2014
  InstallationDate: Installed on 2014-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140411)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1024705] Re: Sound menu doesn't support absolute icon paths of desktop files

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Fix Committed = Fix Released

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

Title:
  Sound menu doesn't support absolute icon paths of desktop files

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

Bug description:
  Hi! I used MenuLibre to change gmusicbrowser's ugly default icon for a
  higher resolution one. All icons were successfully changes, included
  the alt+tab icon, but its icon in SoundMenu indicator was gone after
  the change. See attached screenshot.

  I'm using Ubuntu 12.04 with Unity 5.12.0.

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

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


[Dx-packages] [Bug 711345] Re: Unify sound message menus registration process

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Triaged = Won't Fix

** Changed in: indicator-messages
   Status: Triaged = Won't Fix

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

Title:
  Unify sound  message menus registration process

Status in The Messaging Menu:
  Won't Fix
Status in Sound Menu:
  Won't Fix
Status in LibUnity:
  Triaged
Status in Unity:
  Triaged
Status in Unity 2D:
  Triaged
Status in “libunity” package in Ubuntu:
  Triaged

Bug description:
  I would like to propose the unification of the application registration 
process.
  AFAIK, at the moment there is a following situation with the registration 
process:
  1. Sound Menu. Every application registers itself after the first start 
(providing desktop-file location through the dbus). The only preregistered 
application is banshee.
  2. Messages menu. Every application registers itself, placing file with 
desktop-file location into the /usr/share/indicators/messages/applications/ 
folder (or user folder). Default launcher list (evolution, empathy and gwibber) 
is hardcoded, rather than stored in gconf scheme, as indicator-sound does.

  In fact, I see no united way to deal with all that stuff. I suppose, that 
indicator interaction API should be similar in most cases, however in this case 
they are absolutely different.
  First, messages-applications have no dbus-method to register themselves. Yep, 
that's not fatal, it only makes maintainers should care about indicator 
creation.
  And second, sound-applications are unable to preregister themselves during 
the installation. Yep, this is conflicts with SoundMenu spec, but really why 
it's stated in spec? And why it's different from Messages policy? The main 
problem are applications who don't provide any GUI and are not intended to be 
started as usual applications, but as something like user-session daemons. In 
fact I can name only one such application :) — my mpd-sound-menu, in most cases 
user wants it to be started with his session to display MPD status.

  Your suggestions?

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

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


[Dx-packages] [Bug 1091142] Re: Volume scrolling inconsistent

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound (Ubuntu)
   Status: Fix Committed = Fix Released

** Changed in: indicator-sound
   Status: Fix Committed = Fix Released

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

Title:
  Volume scrolling inconsistent

Status in Sound Menu:
  Fix Released
Status in Unity:
  Invalid
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  When adjusting the volume with the scroll wheel there are two
  scenario's which are inconsistent with eachother:

  Scenario 1:
  1. Click on the speaker icon in the top right corner
  2. Keep hovering over the speaker icon
  3. Scroll to adjust the volume. The volume is adjusted in small steps.

  Sceanrio 2:
  1. Click on the speaker icon in the top right corner
  2. Move the cursor down and hover over the volume slider.
  3. Scroll to adjust the volume. The volume is adjusted in large steps.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Dec 17 10:41:09 2012
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 987920] Re: Back Forward buttons in Sound Indicator menu should be highlighted

2014-04-11 Thread Lars Uebernickel
*** This bug is a duplicate of bug 733285 ***
https://bugs.launchpad.net/bugs/733285

This was recently fixed. See bug #733285.

** This bug has been marked a duplicate of bug 733285
   Focus indication on playback controls is misleading

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

Title:
  Back  Forward buttons in Sound Indicator menu should be highlighted

Status in Ayatana Design:
  Fix Released
Status in Sound Menu:
  Triaged
Status in “indicator-sound” package in Ubuntu:
  Triaged

Bug description:
  The Forward  Back buttons in the Sound Indicator menu should be
  highlighted when the mouse pointer is focused on either one of them.
  Only the Play button is highlighted even when the pointer is moving
  away from it in a horizontal direction.

  Ubuntu 11.10 64bit
  indicator-sound 0.7.9-0ubuntu2.1
  ---
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Package: indicator-sound 0.8.5.0-0ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Tags:  precise running-unity
  Uname: Linux 3.2.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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


[Dx-packages] [Bug 947401] Re: indicator-sound-service crashed with SIGABRT in __assert_fail_base()

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Incomplete = Invalid

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

Title:
  indicator-sound-service crashed with SIGABRT in __assert_fail_base()

Status in Sound Menu:
  Invalid
Status in “indicator-sound” package in Ubuntu:
  Expired

Bug description:
  running veetle Plugin 0.9.17 in FIrefox

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: indicator-sound 0.8.3.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  Date: Mon Mar  5 20:28:44 2012
  ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
  ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
  Signal: 6
  SourcePackage: indicator-sound
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
   __pthread_mutex_lock_full () from /lib/x86_64-linux-gnu/libpthread.so.0
  Title: indicator-sound-service crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-04 (0 days ago)
  UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers

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

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


[Dx-packages] [Bug 946509] Re: indicator-sound-service crashed with SIGABRT in raise()

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Incomplete = Invalid

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

Title:
  indicator-sound-service crashed with SIGABRT in raise()

Status in Sound Menu:
  Invalid
Status in “indicator-sound” package in Ubuntu:
  Invalid

Bug description:
  First boot trying 64 bit 12.04 from thumb drive.  I got the crash 
notification, but the sound indicator is still in the top panel and it still 
works.
  This is the beta downloaded on 03-04-2012.  
  Your instructions:
  We also need:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System - About Ubuntu

  Do not work.

  Entering the first command in terminal returs nothing and there is no way to 
do System  About Ubuntu in Unity.
   I looked all through the System setting, but there is no About Ubuntu 
anywhere.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: indicator-sound 0.8.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  ApportVersion: 1.93-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.305
  Date: Sun Mar  4 17:34:18 2012
  ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
  LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: indicator-sound
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: indicator-sound-service crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Dx-packages] [Bug 841338] Re: unity-panel-service crashed with SIGSEGV

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Incomplete = Invalid

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

Title:
  unity-panel-service crashed with SIGSEGV

Status in Sound Menu:
  Invalid
Status in “indicator-sound” package in Ubuntu:
  Expired

Bug description:
  The unity panel crashed and reappeared a few seconds with the
  protruding edges of the items at right of panel.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: unity-services 4.12.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Sun Sep  4 17:33:11 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current-updates, 280.13, 3.0.0-9-generic, x86_64: installed
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0446]
   nVidia Corporation Device [10de:0df5] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0446]
  MachineType: Dell Inc. Dell System XPS 15Z
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic 
root=UUID=11bc44a2-684a-4707-ac24-e515e1417acf ro persistent splash quiet 
pcie_aspm=force acpi=noirq i915.semaphores=1 vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f77a57b636b:callq  0x7f77a57aff80 
gtk_widget_get_type
   PC (0x7f77a57b636b) ok
   source 0x7f77a57aff80 (0x7f77a57aff80) ok
   destination (%rsp) (0x7fff1a861000) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
  Title: unity-panel-service crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 05/09/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 060G42
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd05/09/2011:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS 15Z
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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


[Dx-packages] [Bug 1005149] Re: When connect Webcam the indicator mute.

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Incomplete = Invalid

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

Title:
  When connect Webcam the indicator mute.

Status in Sound Menu:
  Invalid
Status in “indicator-sound” package in Ubuntu:
  Expired

Bug description:
  Two cases:

  A) With the webcam connected from the beginning of the PC when loaded
  ubuntu and sound and sound-indicator are off, both in the login screen
  with the desktop. If you also look at the sound settings, vemosque all
  options are out. After a few seconds or minutes, the sound returns but
  the indicator still show the silencing or freezing. If we go back into
  the configuration, now everything is correct. But the sound-indicator
  continues to display an incorrect status.

  B) With Ubuntu already loaded sound and sound-indicator function
  properly. Now connect the webcam, in some cases occur as in the case
  A) and in others only a slight cut perceive sound but everything is
  displayed either at the time.

  Thank you for great OS and GNU/Linux community! :)

  6 years of ubuntu and count! ;)

  David Gámiz Jiménez

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

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


[Dx-packages] [Bug 1206534] Re: Max volume icon on volume slider is incorrect.

2014-04-11 Thread Lars Uebernickel
** Changed in: indicator-sound
   Status: Fix Committed = Fix Released

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

Title:
  Max volume icon on volume slider is incorrect.

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

Bug description:
  max-icon setting on volume control is set to 'audio-volume-low-high-panel'.
  Should be 'audio-volume-high-panel'

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

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


[Dx-packages] [Bug 1077252] Re: Empathy shows up as running even though it is stopped

2014-04-10 Thread Lars Uebernickel
This should be fixed with lp:~larsu/indicator-messages/listen-to-app-
stopped-running.

** Branch linked: lp:~larsu/indicator-messages/listen-to-app-stopped-
running

** Changed in: indicator-messages (Ubuntu)
   Status: New = In Progress

** Changed in: indicator-messages (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

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

Title:
  Empathy shows up as running even though it is stopped

Status in “indicator-messages” package in Ubuntu:
  In Progress

Bug description:
  Empathy is shown as running even when it is not. I can start Empathy
  and quit it, and still it is shown as running in the Messaging Menu.

  Steps to reproduce:
  - Open the Messaging Menu without running Empathy

  Expected result:
  - Empathy is shown as not running

  Actual result:
  - Empathy is shown as running

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: indicator-messages 12.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sat Nov 10 00:35:08 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-10-11 (29 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-messages
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (21 days ago)

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

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


[Dx-packages] [Bug 1077626] Re: Top bar problem with status

2014-04-10 Thread Lars Uebernickel
This seems to be a bug in empathy. telepathy-indicator (the component
providing messaging menu integration with empathy) correctly requests
TP_CONNECTION_PRESENCE_TYPE_HIDDEN when I choose invisible from the
messaging menu.

** Package changed: indicator-messages (Ubuntu) = empathy (Ubuntu)

** Changed in: empathy (Ubuntu)
   Status: New = Triaged

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

Title:
  Top bar problem with status

Status in “empathy” package in Ubuntu:
  Triaged

Bug description:
  When I select (invisible) in the top bar, empathy changes the status
  to (busy).

  ProblemType: Bug
  DistroRelease: elementary OS 0.2
  Package: elementary-desktop 1.284-0~355~precise1 [origin: 
LP-PPA-elementary-os-daily]
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Uname: Linux 3.2.0-32-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu14+elementary3~precise1
  Architecture: i386
  CasperVersion: 1.315+elementary2~precise1
  CrashDB: elementary_meta
  Date: Sun Nov 11 12:52:02 2012
  LiveMediaBuild: elementary OS 0.2 Luna - Build i386 LIVE Binary 
20121101-16:54
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: elementary-meta
  SuspiciousXErrors:
   
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1254196] Re: apps behavior

2014-04-10 Thread Lars Uebernickel
*** This bug is a duplicate of bug 1261058 ***
https://bugs.launchpad.net/bugs/1261058

Thanks for reporting this. It's the same issue as bug #1261058.

** This bug has been marked a duplicate of bug 1261058
   Selecting incoming message does not raise corresponding chat window to the 
foreground

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

Title:
  apps behavior

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

Bug description:
  Hello,

  I am reporting a annoying behavior of indicator-messages.

  rbarbosa@rene-Inspiron-14z:~$ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  rbarbosa@rene-Inspiron-14z:~$ apt-cache policy indicator-messages
  indicator-messages:
    Instalado: 13.10.1+13.10.20131011-0ubuntu1
    Candidato: 13.10.1+13.10.20131011-0ubuntu1
    Tabela de versão:
   *** 13.10.1+13.10.20131011-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  rbarbosa@rene-Inspiron-14z:~$ apt-cache policy pidgin
  pidgin:
    Instalado: 1:2.10.7-0ubuntu4.1
    Candidato: 1:2.10.7-0ubuntu4.1
    Tabela de versão:
   *** 1:2.10.7-0ubuntu4.1 0
  500 http://br.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  What i expect to happen: If i receive notifications about Pidgin or
  Xchat messages with these apps not minimized when i click on the sub-
  menu disponible in indicator-messages these apps should receive the
  focus and go to screen foreground.

  What is happening: With these apps not minimized and in screen
  background or another workspace i just receive a wiggle on Unity
  launcher and they are not going to screen foreground when i click in
  the sub-menus created.

  The wrong behavior is not happening when these apps are minimized.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-messages 13.10.1+13.10.20131011-0ubuntu1 [modified: 
usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service]
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov 22 19:07:40 2013
  InstallationDate: Installed on 2013-11-21 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1103438] Re: Online Status in indicator does not reflect empathy's online status

2014-04-10 Thread Lars Uebernickel
Thanks for reporting this.

** Package changed: indicator-messages (Ubuntu) = telepathy-indicator
(Ubuntu)

** Package changed: telepathy-indicator (Ubuntu) = telepathy-indicator

** Changed in: telepathy-indicator
   Status: Confirmed = In Progress

** Changed in: telepathy-indicator
 Assignee: (unassigned) = Lars Uebernickel (larsu)

** Branch linked: lp:~larsu/telepathy-indicator/lp1103438

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

Title:
  Online Status in indicator does not reflect empathy's online status

Status in Telepathy Indicator Service:
  In Progress

Bug description:
  The messaging menu does not reflect the right online status of empathy. 
Empathy is online, but the messaging menu shows offline (screenshot attached). 
Maybe it is a duplicate of bug 1057385?
  If there is anything else needed, just ask for it.

  Description:  Ubuntu 12.10
  Release:  12.10

  indicator-messages:
Installed: 12.10.4-0ubuntu1
Candidate: 12.10.4-0ubuntu1
Version table:
   *** 12.10.4-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected: messaging menu shows the same status as empathy does

  Happened: messaging menu shows offline while empathy shows online (and is 
online)
  --- 
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  InstallationDate: Installed on 2013-01-07 (15 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  NonfreeKernelModules: fglrx wl
  Package: indicator-messages 12.10.4-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-22-generic x86_64
  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/telepathy-indicator/+bug/1103438/+subscriptions

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


[Dx-packages] [Bug 1301463] Re: Send button when responding to texts is grayed out and non-functional

2014-04-10 Thread Lars Uebernickel
** Package changed: indicator-messages (Ubuntu) = unity8 (Ubuntu)

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

Title:
  Send button when responding to texts is grayed out and non-functional

Status in “unity8” package in Ubuntu:
  New

Bug description:
  If I get a text, the message indicator is blue. If I click a message
  from within the indicator, I am presented with a text field and a send
  button. I can type into the text field, but the button is grayed out.
  If I click it, then the text field, etc goes away, but the message
  isn't sent and it isn't added to the thread in the messaging app. If I
  click the message again in the messaging indicator, it shows the text
  field with the message, but the button is still grayed out and won't
  send.

  This is on mako with latest promoted (r250)

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

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


  1   2   3   >