[Touch-packages] [Bug 1899349] [NEW] Jack_control in jackd2 1.9.14 will not accept char parameters

2020-10-11 Thread Len Ovens
Public bug reported: trying to set self-connect-mode (for example): $ jack_control eps self-connect-mode e gives: --- engine param set "self-connect-mode" -> "e" Traceback (most recent call last): File "/usr/bin/jack_control", line 400, in main() File "/usr/bin/jack_control", line 283,

[Touch-packages] [Bug 1899298] [NEW] dbus.Byte does not accept single character strings

2020-10-10 Thread Len Ovens
Public bug reported: Using dbus.Byte to create a Byte value for dbus errors out with: return dbus.Byte(value); TypeError: Expected a bytes or str of length 1, or an int in the range 0-255 even with a one character string like 'e' or 'a'. This is likely because python2 strings were char and

[Touch-packages] [Bug 1899298] Re: dbus.Byte does not accept single character strings

2020-10-10 Thread Len Ovens
This is specific to this package in ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-python in Ubuntu. https://bugs.launchpad.net/bugs/1899298 Title: dbus.Byte does not accept single character strings

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2018-08-05 Thread Len Ovens
Gui no longer run su ** Changed in: ubuntustudio-controls (Ubuntu) Status: New => Fix Released ** Changed in: ubuntustudio-controls (Ubuntu) Assignee: (unassigned) => Len Ovens (len-ovenwerks) -- You received this bug notification because you are a member of Ubuntu Touch

Re: [Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-10-21 Thread Len Ovens
e need to be addressed if new users are to keep using Ubuntu longer than a quick try. -- Len Ovens www.ovenwerks.net -- 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/1713313

[Touch-packages] [Bug 1646245] [NEW] /etc/init.d/ondemand keeps /etc/init.d/cpufrequtils from working

2016-11-30 Thread Len Ovens
Public bug reported: dpkg -S /etc/init.d/ondemand says initscripts. /etc/init.d/cpufrequtils already sets the cpu governor and has the option that a user can set system governor in /etc/default/. ondemand over rides this and even worse does it 60 seconds late so that the user can not even set the

[Touch-packages] [Bug 1567993] Re: alsa-utils does not store and restore alsa settings on boot reboot

2016-04-15 Thread Len Ovens
Fix confirmed here too. Thank you. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1567993 Title:

[Touch-packages] [Bug 1567993] Re: alsa-utils does not store and restore alsa settings on boot reboot

2016-04-13 Thread Len Ovens
>> "Do either of you have a /var/lib/alsa/asound.state file?" Not here. The directory exists, but no file inside. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1567993

[Touch-packages] [Bug 1567993] Re: alsa-utils does not store and restore alsa settings on boot reboot

2016-04-13 Thread Len Ovens
synaptic says I have alsa-utils (1.1.0-0ubuntu4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1567993 Title: alsa-utils does not store and restore alsa settings on

[Touch-packages] [Bug 1567993] Re: alsa-utils does not store and restore alsa settings on boot reboot

2016-04-13 Thread Len Ovens
I confirm that it still doesn't work for me either. I did try manually creating /run/alsa/ but that did not work either. The directory seems to vanish on reboot... perhaps because /run is created at boot. That would indicate that alsa-utils needs to create this directory at each boot. ** Changed

[Touch-packages] [Bug 1567993] Re: alsa-utils does not store and restore alsa settings on boot reboot

2016-04-08 Thread Len Ovens
in /var/log/syslog I find systemd-udevd[400]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. Hmm, nothing to do with run levels perhaps. The directory /run/alsa does not exist. Normally /etc/init.d/alsa-utils would create this directory at run time. My

[Touch-packages] [Bug 1567993] Re: alsa-utils does not store and restore alsa settings on boot reboot

2016-04-08 Thread Len Ovens
On further checking, I find alsa-utils is not in rc2.d either, but in rcS.d, expected to run before final run level. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.

[Touch-packages] [Bug 1567993] [NEW] alsa-utils does not store and restore alsa settings on boot reboot

2016-04-08 Thread Len Ovens
Public bug reported: The standard run level seems to have changed from run level 2 to run level 5 in 16.04. /etc/init.d/alsa-utils does not have a symlink in rc5.d and so does not run and store and restore alsa settings on shutdown/boot. Most internal audio interfaces are set to some reasonable

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-07 Thread Len Ovens
I meant to add would be possible (advisable) to change the qjackctl.desktop file to use: export XDG_CURRENT_DESKTOP=Unity; qjackctl as the executable line as a temporary work around? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-07 Thread Len Ovens
@Dmitry, I still require: export XDG_CURRENT_DESKTOP=Unity To make the icon show. Is this being fixed in other places? Also: the new version has changed the name of one of the settings that needs to be set by default for thing s to work ootb. see Bug #1567589 -- You received this bug

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-06 Thread Len Ovens
Rui has announced a new version of qjackctl on LAA, LAD,LAU mailing lists. One of the updates/changes is to remove Start minimized to system tray as an option. There are some other fixes for indicator menu, but they say they are kde based, so I do not know if they will also work for xfce. I am no

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-03 Thread Len Ovens
@Dmitry, @Ross: I do remember qjackctl from before only allowing singltons :) one could close qjackctl to the systray and start it again from the menu with the result of two qjackctls. That while annoying, is not a real problem provided the user is using jackdbus as it is ok to have more than one

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-02 Thread Len Ovens
@Dmitry, Sorry for not being clearer. "> - Setting "Start minimized to system tray" makes desktop unusable. Mouse moves, but no input is possible. One has to use c/a/f1 to a vterm in order to kill qjackctl to make the desktop usable again. " After setting "Start minimized to system tray", exit

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-01 Thread Len Ovens
@Dmitry, doing: $ export XDG_CURRENT_DESKTOP=Unity $ qjackctl Does make the icon behave as expected. Good. However, the rest of the problems still exist: - The qjackctl menu does not work, instead an empty drop-down appears. (for the reasons you already mentioned) - Setting "Start minimized

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-03-20 Thread Len Ovens
Hmm, maybe for now just set ./configure --enable-system-tray=no or --disable-system-tray Honestly, I use the system tray settings with qjackctl all the time. I just don't have the screen real estate to deal with it. Screen 1 has the editor window and meter bridge and screen 2 has the mixer panel

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-03-20 Thread Len Ovens
Ross: "we would have to advise users to manually edit their conf file to set StartMinimised to false." They may not be able to. A not uncommon use of qjackctl is to have it set to start with session in order to run jack at that time. So the user upgrades, reboots and finds they can't do

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-03-19 Thread Len Ovens
Note: The problem is starting qjackctl when "Start minimized to tray" has already select on a previous run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu.

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-03-19 Thread Len Ovens
Reboot did get me a nice icon, but running qjackctl with "Start minimized to tray" still locks all screen input. It is interesting that with "Enable system tray icon" selected it is fine, I can start and stop with no problems. It is the Start minimized to tray option that causes trouble. Perhaps

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-03-19 Thread Len Ovens
Ross: Downloaded and installed qjackctl_0.4.1-1ubuntu2~ppa3_i386.deb from https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/dev- testing/+packages Setup->misc->Enable system tray icon seems to work Minus the icon... stop and then start works ok too. Setup->misc->Start minimized to system

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-03-18 Thread Len Ovens
If not having a package breaks an app that package would be a depend by definition... or am I missing something? This small application, Qjackctl, is a major part of Ubuntustudio as the app that allows the user to control jackd/jackdbus from a gui. With out proper systray operation the user may