[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-12-21 Thread Ross Gammon
@adaucyjr: It looks like the same bug has been reported in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899147

It looks like they have decided NOT to do a Stable Release Update there,
due to the risk of regressions.

** Bug watch added: Debian Bug tracker #899147
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899147

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-12-21 Thread Ross Gammon
Bug fixes are normally uploaded to the development release so that users
will get the fix when updating to the next release. As in this case, the
bug also exists in the still supported stable releases (Xenial and
Trusty), it is necessary to follow the Stable Release Update (SRU)
process in order to fix the problem in those releases.

The process is explained here:
https://wiki.ubuntu.com/StableReleaseUpdates

This process involves updating the bug report description and make sure it 
contains the following types of information:
- An explanation and justification for backporting the fix to the stable 
release.
- A [Test Case] section with detailed instructions how to reproduce the bug.
- A [Regression Potential] section with a discussion about potential regressions

Then two patches that fix the problem are required, one for Xenial, and
one for Trusty. The process will then ensure that there will be no
serious regressions for users of the Stable releases.

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1746310] Re: Drop fonts-symbola from platform?

2018-02-07 Thread Ross Gammon
Without checking, I don't think Ubuntu Studio have any objections.

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1746310/+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 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-11-09 Thread Ross Gammon
** Changed in: ubuntustudio-meta (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  Fix Committed
Status in lubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-08-23 Thread Ross Gammon
Just an update for my upgrade. I can't remember exactly what happened
now. But I think that I looked into the emacs issue, and then did
something like "apt-get --fix-broken" or "apt-get --fix-missing". And
once the emacs problem was fixed, I could "apt-get upgrade" & "dist-
upgrade" to continue the upgrade, and the upgrade completed fine.

Sorry about the vagueness, but I thought I would report back that it is
no longer a problem for me.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Triaged
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-08-11 Thread Ross Gammon
Affects me too. To answer Brian's question in #15, "sudo dpkg
--configure -a" did not show (or do) anything for me, instead there was
only a message that emacs24 is left unconfigured. I will check for a bug
for that in a tick.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Triaged
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1570749] Re: Upgrade to 11.7 from May 2016

2017-01-03 Thread Ross Gammon
Yakkety and Xenial have already been released. Packages do not get
updated after release. Specific critcal bugs can be fixed through the
Stable Release Updates (SRU) process.

However, in the case of libav, this package was removed from Ubuntu
after the vivid release, in favour of ffmpeg. Perhaps you can use that
library instead?

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

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

Title:
  Upgrade to 11.7 from May 2016

Status in libav package in Ubuntu:
  Invalid

Bug description:
  Please, upgrade to 11.6 from February 2016, see https://libav.org/ and
  https://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v11.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1570749/+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 455694] Re: FFE: Provide some policykit privileges by default on desktops

2016-09-01 Thread Ross Gammon
policykit-desktop-privileges is seeded in Ubuntu Studio (probably for a
while now). It is pulled in by desktop-common, which is pulled on by the
Ubuntu Studio desktop seed.

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  FFE: Provide some policykit privileges by default on desktops

Status in netbook-meta package in Ubuntu:
  Fix Released
Status in policykit-desktop-privileges package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in netbook-meta source package in Lucid:
  Fix Released
Status in policykit-desktop-privileges source package in Lucid:
  Fix Released
Status in ubuntu-meta source package in Lucid:
  Fix Released
Status in ubuntustudio-meta source package in Lucid:
  Won't Fix

Bug description:
  Please see comment 16 for details of the FFE.

  
  Binary package hint: gnome-applets

  This is a regression from Jaunty. It doesn't provide an option for
  saving the authentication information and requires to enter the
  password every time a different option is selected.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Oct 19 20:55:20 2009
  DistroRelease: Ubuntu 9.10
  Package: gnome-applets 2.28.0-0ubuntu1
  ProcEnviron:
   LC_TIME=de_DE.UTF-8
   LANGUAGE=en_US.UTF-8
   PATH=(cususername, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: gnome-applets
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netbook-meta/+bug/455694/+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 1546328] Re: Systray option does not work.

2016-04-03 Thread Ross Gammon
Whoops. The new ticket upstream:
https://sourceforge.net/p/qjackctl/tickets/27/

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-04-03 Thread Ross Gammon
OK - that re-factoring (Single/unique application instance control
adapted to Qt5/X11) was listed in the release notes to 0.4.1.

I am not sure that allowing more than one Qjackctl instance is a good
idea. Some audio applications require JACK to be running, and other
start it themselves. This may cause users to get in a real tangle. But I
will leave that to my more experience Ubuntu Studio team members to
confirm.

As a quick and temporary fix, I think the patch to build with QT4 would
be the best. All of the above 3 issues are solved, and the QT4 libraries
are required anyway for other often used audio applications (e.g.
ffado).

I have created a new ticket upstream about the freeze with Dmitry's
suggestions. Hopefully we will get a better fix from upstream for the
next release.

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-04-03 Thread Ross Gammon
Thanks Dmitry for spending so much time on this.

I had been meaning to create a separate bug for the freezing behaviour,
and to try and get some debug output from X to send upstream to
Qjackctl. But I had been busy, and it looks like you have found the
issue anyway.

Not knowing the X11 API nor QT myself, do you think it would be easy to
patch Qjackctl to use the QT5 functions instead (at least in this one
place)?

I can forward your analysis upstream on a new bug, but we only have a
few weeks and they may not respond quickly enough.

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-22 Thread Ross Gammon
Disabling the system tray completely seems a bit of a backwards step.

Like you, I am no QT expert. Although it is on my to-do list to learn.
So if anyone can help identify what makes Ubuntu Studio freeze if
Qjackctl was minimised before upgrade, it would be appreciated.

Otherwise, uploading the debdiff version where Qjackctl is compiled with
QT4 seems the best option for users. It works out of the box with no
issues for the users, or funny visual stuff, and the QT4 libraries will
still be available and installed for other applications anyway.

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-20 Thread Ross Gammon
@ Len:

Thanks for testing that. I didn't think to try leaving minimised first.

I have to admit that uploading the version that builds with QT4 is my
current favourite. It is a whole lot neater and has zero problems for
the user as far as I can tell.

But if we are forced to upload the QT5 version, then we would have to
advise users to manually edit their conf file to set StartMinimised to
false.

That would be a real pain. Unfortunately, I don't really know where to
start looking for what actually causes that lock up.

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-19 Thread Ross Gammon
A new debdiff with appmenu-qt5 demoted to "recommends".

If appmenu-qt5 disappears from the archive, Qjackctl is still useable
for people that minimise to the system tray (via the drop down indicator
menu), but the icon shown in the tray is a red cross instead of
reflecting the "stopped"/"started" status of Qjackctl.

** Patch added: "systray_qjackctl_recommends_0.4.1-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1546328/+attachment/4604238/+files/systray_qjackctl_recommends_0.4.1-1ubuntu2.debdiff

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-19 Thread Ross Gammon
@ Dmitry. I was just reading the discussion in Ubuntu-devel and
wondering what to do. Without appmenu-qt5, the menu works from the
systray, but the icon is not animated. It just shows a red cross all the
time, which is misleading for the user.

So I guess we could just recommend it, and then it will be pulled in as
long as it is there. We can then try and work with upstream to get a
better forward looking fix for xenial + 1.

I would prefer that appmenu-qt5 is still around in xenial, because as
Len says, Qjackctl is a critical part of Ubuntu Studio, and we would
prefer a slick user experience.

@ Len. Have you had a chance to test the latest version in our testing
ppa? I noticed a second menu appearing underneath the "indicator" one,
which eventually goes away. It wasn't really that noticeable on my VM,
but it was running at less than half-screen size,

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-18 Thread Ross Gammon
I now upload a new debdiff which rather than dropping back to build with
QT4, instead cherry-picks some upstream commits to get the systray menu
working, and depend upon appmenu-qt5 to get the systray icon showing.

The changes can be tested by upgrading to the verision uploaded to the Ubuntu 
Studio Testing ppa:
https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/dev-testing

The only difference in that version being the changelog version (~ppa3).

** Patch added: "systray_qjackctl_0.4.1-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1546328/+attachment/4603770/+files/systray_qjackctl_0.4.1-1ubuntu2.debdiff

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-08 Thread Ross Gammon
Thanks Dmitry. That really helps make it clear. I have updated the
upstream bug with the analysis.

So it appears we have a choice:
1. Go with the original proposal (patch attached) and build qjackctl with QT4 
for Xenial
2. Cherry pick two of the upstream commits and try and get it working that way

I will look at (2) in the next few days.

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-02 Thread Ross Gammon
Thanks Dmitry.

I can confirm that we have been testing with up-to-date Xenial boxes
with the latest QT5.

I just installed appmenu-QT5 and it makes things slightly better in that
the icon in the tray is dynamic, but the menu that drops down from it is
empty.

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

Title:
  Systray option does not work.

Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-03-02 Thread Ross Gammon
** Attachment added: "Qjackctl with QT5 and appmenu-qt5 installed"
   
https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1546328/+attachment/4586886/+files/VirtualBox_UbuntuStudioXenial1604_02_03_2016_19_40_05.png

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

Title:
  Systray option does not work.

Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1546328/+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 1546328] Re: Systray option does not work.

2016-02-29 Thread Ross Gammon
The Ubuntu changes to qtbase-opensource-src 5.5.1 do seem to include backports 
from the 5.6 branch which may be System Tray related:
https://launchpadlibrarian.net/243321175/qtbase-opensource-src_5.5.1+dfsg-14ubuntu1_5.5.1+dfsg-14ubuntu2.diff.gz

But I am not sure. I will add a task to see if someone more experienced
in QT5 can help find the right eventual fix.

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Systray option does not work.

Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1546328/+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 1355136] Re: Add recommends printer-driver-brlaser package in -desktop installations

2015-11-19 Thread Ross Gammon
I can see in Xenial that ubuntustudio-desktop now recommends printer-
driver-brlaser.

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Add recommends printer-driver-brlaser package in -desktop
  installations

Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-gnome-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  For Brother DCP-7030 and Brother DCP-7065DN the printer-driver-brlaser
  package needs to be installed which is available since utopic. Would
  be nice if this was installed by default as recommends in -desktop
  installations for automatic configuraton in system-config-printer like
  other printer-driver packages.

  This would close LP: #1351238

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1355136/+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 1509632] Re: libav dev and extra package are not co-installable

2015-10-25 Thread Ross Gammon
** Package changed: libav (Ubuntu) => ffmpeg (Ubuntu)

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

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

Title:
  libav dev and extra package are not co-installable

Status in ffmpeg package in Ubuntu:
  Fix Released

Bug description:
  once again libavcodec-dev depends on libavcodec-ffmpeg56 but does not allow 
libavcodec-ffmpeg-extra56 which is a dependency from UbuntuStudo-audio
  (it should have a OR dependency)

  that result in the situation where you can either develop or hear
  sound but not both

  the bug does happen before and again but it seems it does happen again
  with each Ubuntu release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1509632/+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 1509632] Re: libav dev and extra package are not co-installable

2015-10-24 Thread Ross Gammon
I assume from your information that you just upgraded to the latest
Ubuntu Studio release (15.10). Can you confirm?

It would be easier if you used ubuntu-bug to report bugs as it automatically 
attaches all this information (versions etc.) to the bug:
https://wiki.ubuntu.com/ReportingBugs

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

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

Title:
  libav dev and extra package are not co-installable

Status in libav package in Ubuntu:
  Incomplete

Bug description:
  once again libavcodec-dev depends on libavcodec-ffmpeg56 but does not allow 
libavcodec-ffmpeg-extra56 which is a dependency from UbuntuStudo-audio
  (it should have a OR dependency)

  that result in the situation where you can either develop or hear
  sound but not both

  the bug does happen before and again but it seems it does happen again
  with each Ubuntu release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1509632/+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 1509632] Re: libav dev and extra package are not co-installable

2015-10-24 Thread Ross Gammon
If my assumption is correct, the bug should be reported against the
ffmpeg source package (which has replaced libav in Debian & Ubuntu
Wily).

It appears that in the next version of ffmpeg (7:2.8.1), 
libavcodec-ffmpeg-extra56 & libavcodec-ffmpeg56 become alternative dependencies 
as you suggest. Wily should probably be patched the same:
https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/commit/?id=c8f3616a25097bf4f02c703f31e0b38b29d1da2f

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

Title:
  libav dev and extra package are not co-installable

Status in libav package in Ubuntu:
  Incomplete

Bug description:
  once again libavcodec-dev depends on libavcodec-ffmpeg56 but does not allow 
libavcodec-ffmpeg-extra56 which is a dependency from UbuntuStudo-audio
  (it should have a OR dependency)

  that result in the situation where you can either develop or hear
  sound but not both

  the bug does happen before and again but it seems it does happen again
  with each Ubuntu release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1509632/+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 1426942] Re: Kubuntu Vivid - unable to display Gujarati Text

2015-03-01 Thread Ross Gammon
** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New = Confirmed

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

Title:
  Kubuntu Vivid - unable to display Gujarati Text

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Applications built with qt5/KDE Framework 5 on Kubuntu Vivid Beta 1
  can no longer render Gujarati script. This is probably due to

  https://bugreports.qt.io/browse/QTBUG-44568

  My Platform:
  Kubuntu Vivid Beta 1

  Packages affected: Any package built with Qt5 5.4 (e.g. konsole, Muon
  Package Manager etc)

  Expected:
  Render Gujarati script correctly (as was the case in Kubuntu versions prior 
to 15.04)

  Actual Results:
  Gujarati glyphs are displayed as squares

  
  The above Qt bug is scheduled to be fixed in Qt 5.5. If Kubuntu Vivid is 
going to ship with Qt 5.4, will it be possible to include a patched Qt5.4 to 
resolve this specific bug?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1426942/+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