[Touch-packages] [Bug 1712701] Re: Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

2017-08-23 Thread Simon Steinbeiß
** Bug watch added: Debian Bug tracker #872687
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872687

** Also affects: gtk+3.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872687
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1712701

Title:
  Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  This bug affects gtk3 >= 3.22.18.1.

  How to reproduce:
  
  In Xfce, try to open the xfce4-powermanager-plugin and click the 
brightness-slider.
  When dragging the slider, the parent window disappears (loses focus) and the 
slider value is not changed.

  This is a regression within Gtk+ which was introduced in
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

  garnacho has provided a patch in the upstream bugreport but so far it
  has not been merged.

  Note that this bug has already been reported in Arch and Debian.

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

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


[Touch-packages] [Bug 1712701] [NEW] Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

2017-08-23 Thread Simon Steinbeiß
Public bug reported:

This bug affects gtk3 >= 3.22.18.1.

How to reproduce:

In Xfce, try to open the xfce4-powermanager-plugin and click the 
brightness-slider.
When dragging the slider, the parent window disappears (loses focus) and the 
slider value is not changed.

This is a regression within Gtk+ which was introduced in
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

garnacho has provided a patch in the upstream bugreport but so far it
has not been merged.

Note that this bug has already been reported in Arch and Debian.

** Affects: gtk
 Importance: Unknown
 Status: Unknown

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gtk+3.0 (Debian)
 Importance: Unknown
 Status: Unknown

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

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

** Description changed:

  This bug affects gtk3 >= 3.22.18.1.
  
  How to reproduce:
  
  In Xfce, try to open the xfce4-powermanager-plugin and click the 
brightness-slider.
  When dragging the slider, the parent window disappears (loses focus) and the 
slider value is not changed.
  
  This is a regression within Gtk+ which was introduced in
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530
  
  garnacho has provided a patch in the upstream bugreport but so far it
  has not been merged.
+ 
+ Note that this bug has already been reported in Arch and Debian.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1712701

Title:
  Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  This bug affects gtk3 >= 3.22.18.1.

  How to reproduce:
  
  In Xfce, try to open the xfce4-powermanager-plugin and click the 
brightness-slider.
  When dragging the slider, the parent window disappears (loses focus) and the 
slider value is not changed.

  This is a regression within Gtk+ which was introduced in
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

  garnacho has provided a patch in the upstream bugreport but so far it
  has not been merged.

  Note that this bug has already been reported in Arch and Debian.

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

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


[Touch-packages] [Bug 1623768] Re: Adapt to new Totem icon name

2016-09-15 Thread Simon Steinbeiß
Thanks, I've added the symlinks and pushed them to xubuntu-artwork.

** Changed in: xubuntu-artwork (Ubuntu)
   Status: New => Fix Committed

** Changed in: xubuntu-artwork (Ubuntu)
 Assignee: (unassigned) => Simon Steinbeiß (ochosi)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to humanity-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1623768

Title:
  Adapt to new Totem icon name

Status in humanity-icon-theme package in Ubuntu:
  New
Status in lubuntu-artwork package in Ubuntu:
  New
Status in ubuntukylin-theme package in Ubuntu:
  New
Status in xubuntu-artwork package in Ubuntu:
  Fix Committed

Bug description:
  Totem has changed its icon name for easier integration with flatpak

  -Icon=totem
  +Icon=org.gnome.Totem

  If your icon theme will be used in Ubuntu 16.04 LTS also, then I
  recommend making a symlink from the totem icon to the new
  org.gnome.Totem icon. Alternatively, you could drop the icon and let
  users use the high resolution icons shipped by Totem itself.

  See also bug 1618138 which lists some other app icon name changes but
  those icons aren't shipped in all themes.

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

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


[Touch-packages] [Bug 1576576] Re: Update to 3.20 needs work and coordination

2016-05-02 Thread Simon Steinbeiß
Not that this is really avoidable - more a question of time and effort -
but the Gtk3.20 update will most likely result in the need for a rewrite
of the default Xubuntu Gtk+ theme (Greybird), but as its codebase is
comparable to that of the light-themes those would be hit by the same
fate.

Naturally we can all switch to new and different themes, which already
support 3.20. However this is something that shouldn't go unmentioned
and unplanned.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1576576

Title:
  Update to 3.20 needs work and coordination

Status in Mozilla Firefox:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  The current upstream stable/Debian version is 3.20 but that includes quite 
some changes in the css handling which means we are going to need to update/fix 
the unity themes and make sure you main application look fine before landing.
  The transition needs to be prepared in a staging ppa before being considered, 
help is welcome since it's likely the desktop team is not going to have lot of 
cycles to work on that.

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

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


[Touch-packages] [Bug 1448834] Re: mouse battery not shown after upgrade

2015-05-07 Thread Simon Steinbeiß
** Package changed: xfce4-power-manager (Ubuntu) = upower (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1448834

Title:
  mouse battery not shown after upgrade

Status in gnome-power-manager package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the
  battery level in my wireless logitech mouse.  However after upgrading
  to 15.04 the mouse battery status is not shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xfce4-power-manager 1.4.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Apr 26 19:49:19 2015
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-power-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)

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

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


[Touch-packages] [Bug 1441975] Re: have not shadows

2015-04-09 Thread Simon Steinbeiß
With compiz drawing all the shadows in Unity, there is no comprehensive CSD 
theming in Ambiance/Radiance.
The easy fix is to add something like this commit to the light-themes:
https://github.com/shimmerproject/Greybird/commit/b9f9b0826195ad115b56724326aa0d3e91063dd4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1441975

Title:
  have not shadows

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  nautilus and desktop have not shadows on context menus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  9 08:54:22 2015
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2015-03-05 (34 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2015-03-05T22:46:49.143864

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

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


[Touch-packages] [Bug 1403633] Re: strange characters in battery name

2014-12-19 Thread Simon Steinbeiß
As exposed by the terminal output in comment #5, the problem is in
upower, not in xfce4-power-manager.

** Package changed: xfce4-power-manager (Ubuntu) = upower (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1403633

Title:
  strange characters in battery name

Status in upower package in Ubuntu:
  New

Bug description:
  The name of the battery has characters not rendered properly.  See the
  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xfce4-power-manager 1.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Dec 17 22:01:02 2014
  InstallationDate: Installed on 2014-12-17 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20141217)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1379287] Re: Blank Volume notification displayed at startup and when scrolling the indicator.

2014-10-09 Thread Simon Steinbeiß
Potentially fixed in trunk: https://code.launchpad.net/~ted/indicator-
sound/revert-notifications/+merge/237664

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1379287

Title:
  Blank Volume notification displayed at startup and when scrolling
  the indicator.

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

Bug description:
  As of the latest indicator-sound package in Utopic, there is a blank Volume 
notification that is displayed:
  1) at system startup.
  2) when scrolling the indicator (along with the normal volume indicator).

  Please see the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20141007-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume': 
(true, '', [1.0]), 'scroll': (true, 'i', []), 
'play-playlist.gmusicbrowser.desktop': (true, 's', []), 
'gmusicbrowser.desktop': (true, '', [{'running': false, 'state': 
'Paused'}]), 'desktop-settings': (true, '', []), 'volume': (true, 'i', 
[0.67987060546875]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (67%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': true}]), 'previous.gmusicbrowser.desktop': (true, 
'', []), 'play.gmusicbrowser.desktop': (true, '', ['Paused'])},)
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct  9 06:57:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-09 (60 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140809)
  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/1379287/+subscriptions

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


[Touch-packages] [Bug 1374379] Re: lightdm's session-cleanup-script get's called on unlock

2014-09-26 Thread Simon Steinbeiß
As you mentioned, it should actually be LightDM doing this, light-locker
doesn't do anything special when unlocking a session.

Maybe Robert has got an idea what's up with that.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1374379

Title:
  lightdm's session-cleanup-script get's called on unlock

Status in “light-locker” package in Ubuntu:
  New
Status in “lightdm” package in Ubuntu:
  New

Bug description:
  When I unlock the screen after it has been locked by light locker the
  session-cleanup-script of lightdm get's called. I used to use the
  session-cleanup-script to umount some volumes on logout. I don't want
  to umount the volumes on lock or unlock.

  Maybe this is related to lightdm's #1249515 and might actually be a
  bug in lightdm!?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.4.0-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: XFCE
  Date: Fri Sep 26 12:02:17 2014
  InstallationDate: Installed on 2014-08-09 (47 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140723)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1374379/+subscriptions

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


[Touch-packages] [Bug 1330037] Re: [FFe] upower 0.99.1 transition

2014-09-15 Thread Simon Steinbeiß
As Xubuntu Project Lead and following my Xubuntu Release Team collegues,
I would like to strongly object to this FFe. It really is extremely late
in the cycle for something quite untested to land that affects so many
desktops.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1330037

Title:
  [FFe] upower 0.99.1 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “cinnamon-control-center” package in Ubuntu:
  New
Status in “cinnamon-session” package in Ubuntu:
  New
Status in “cinnamon-settings-daemon” package in Ubuntu:
  New
Status in “gnome-applets” package in Ubuntu:
  In Progress
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-shell” package in Ubuntu:
  In Progress
Status in “gnome-shell-pomodoro” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Fix Released
Status in “mate-applets” package in Ubuntu:
  Fix Released
Status in “mate-power-manager” package in Ubuntu:
  Fix Released
Status in “mate-session-manager” package in Ubuntu:
  Fix Released
Status in “mutter” package in Ubuntu:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  Fix Released
Status in “tracker” package in Ubuntu:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  In Progress
Status in “xfce4-power-manager” package in Ubuntu:
  Fix Committed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “xfce4-settings” package in Ubuntu:
  In Progress
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “xfce4-weather-plugin” package in Ubuntu:
  Invalid
Status in “wmbattery” package in Debian:
  Fix Released

Bug description:
  upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops
  the suspend/hibernate functions, as logind now does that. All major
  DEs have support for this,so nearly everything just needs a rebuild.
  This bug tracks the transition.

  A transition is required as some features were removed and the SONAME
  was changed

  All packages (and build logs) are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  sugar will probably need removing. If a package only needs a rebuild,
  mark it fix commited, if something else is needed, in progress.

  cairo-dock-plug-ins: needs rebuilding
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release.
  gnome-power-manager: Fixed in newest upstream release. Merge from debian
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend broken with upstart, no rebuilds needed
  cinnamon: Rebuild
  mate: all mate packages need rebuilding
  python-dbusmock: needs rebuild
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  telepathy-mission-control-5: Debian has dropped upower support, so it's done
  wmbattery: needs rebuild
  xfce4-power-manager: Needs rebuilding
  xfce4-session: Fixed already, since we switched to logind
  xfce4-settings: Needs rebuild
  xfce4-systemload-plugin: needs rebuild

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+subscriptions

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


[Touch-packages] [Bug 1359249] Re: Launching PAVUControl works from Xubuntu, but not from Xfce

2014-08-20 Thread Simon Steinbeiß
Yup, that is the case. So far, only Xubuntu and Ubuntu Studio are taken into 
account.
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-sound/trunk.14.04/view/head:/src/service.vala#L209

I guess the reason the Xfce session isn't there is because nobody
complained about it before.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1359249

Title:
  Launching PAVUControl works from Xubuntu, but not from Xfce

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

Bug description:
  In Xubuntu 14.04 when clicking the sound indicator and choosing Sound
  Settings Pavucontrol is launched, but it does not get launched in the
  same scenario when the session Xfce is launched instead, with the
  same settings. In fact I installed the xfce4 package on top of
  Xubuntu's and launched it. Both xsession files list the same thing to
  start it, so is indicator only choosing to work on whitelisted
  sessions?

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

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


[Touch-packages] [Bug 1347272]

2014-07-28 Thread Simon Steinbeiß
Applied to git master.

commit 791f02416560f5ac75250a9a67f4e2a3d0ac6f7c
Author: Eric Koegel eric.koe...@gmail.com
Date:   Mon Jul 28 09:03:30 2014 +0300

Fork before gtk/dbus init (bug #11045)

https://mail.xfce.org/pipermail/xfce4-dev/2014-May/030715.html
has the rational for the change.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1347272

Title:
  Several XFCE applications appear irresponsible after communicating
  with a daemon

Status in pixbuf library for gtk+:
  New
Status in One Hundred Papercuts:
  Triaged
Status in System policy:
  Confirmed
Status in Thunar file manager:
  Confirmed
Status in xfce4-appfinder:
  Confirmed
Status in Xfce4 Power Manager:
  Confirmed
Status in xfce4-settings:
  Fix Released
Status in Volume management daemon for XFCE 4:
  Invalid
Status in Volume management daemon for Xfce:
  Confirmed
Status in “gdk-pixbuf” package in Ubuntu:
  Triaged
Status in “policykit-1” package in Ubuntu:
  Triaged
Status in “thunar” package in Ubuntu:
  Triaged
Status in “xfce4-appfinder” package in Ubuntu:
  Triaged
Status in “xfce4-power-manager” package in Ubuntu:
  Triaged
Status in “xfce4-settings” package in Ubuntu:
  Triaged
Status in “xfce4-volumed” package in Ubuntu:
  Triaged

Bug description:
  Several programs in Xfce have a daemon mode call gtk_init() before
  fork()ing.

  This is unsafe, and when it goes wrong this will typically manifest as
  the daemon hanging shortly after forking, and appearing to simply do
  nothing at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions

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