chris_uk[m] | I have a couple if crash files | 06:33 |
---|---|---|
guiverc | chris_uk[m], you should be able to submit then with `ubuntu-bug /var/crash/[name of crashfile].crash` | 06:34 |
chris_uk[m] | in beta 21.10 var/crash named _usr_ bin_ autojack.120. crash and _ usr_ bin_ autojack.1000. crash | 06:35 |
chris_uk[m] | Thanks | 06:36 |
chris_uk[m] | Will do. | 06:36 |
chris_uk[m] | Experiencing some problem sending the crash files. Getting message in Aport ' The Application Studio Controls has closed unexpectedly.' | 07:06 |
chris_uk[m] | And in Konsole message: 'QStandardPaths: XDG_RUNTIME_ DUR not set, defaulting to ' /tmp/runtime-root' | 07:06 |
chris_uk[m] | Have sent error message via Aport | 07:06 |
chris_uk[m] | Should be RUNTIME_ DIR | 07:07 |
frank_ | Good Morning! | 08:03 |
frank_ | May I ask, if there is a documentation regarding the compiling of Ardour6 on ubuntustudio? | 08:05 |
OvenWerks | frank_: There is none | 15:02 |
OvenWerks | frank_: I am assuming you are using a git pull from github? | 15:02 |
OvenWerks | frank_: if you look at: https://nightly.ardour.org/i/A_Linux_x86_64/build_log.txt | 15:03 |
OvenWerks | you can see the ./waf configure line used. | 15:04 |
OvenWerks | when you run that line, it will most likely fail because of missing deps. Most likely you will just need the *-dev package of those libs. Keep adding them until configure passes all the way through | 15:05 |
OvenWerks | then ./waf will build | 15:06 |
OvenWerks | frank_: please note this will not give you a build that waf install will put in the same place as a pre built binary from ardour.org or ubuntu | 15:10 |
OvenWerks | frank_: also please note that the current github version of Ardour is not useable. | 15:10 |
OvenWerks | waf install will put things in /usr/local/ | 15:11 |
OvenWerks | If you want to build for testing only, it is best to run ardour from the build directory. | 15:12 |
OvenWerks | run from */ardour/gtk2_ardour/ardev | 15:13 |
OvenWerks | Or for debugging, remove the --optimize from your configure line to build a debug version and run */ardour/gtk2_ardour/ardbg | 15:16 |
OvenWerks | frank_: if any of this does not make sense to you, I would sugest using either the Ardour version from the ubuntu repositories or downloading the version(s) from ardour.org | 15:17 |
OvenWerks | chris_uk[m]: before you worry about this problem in studio-controls make sure you have the latest version 2.2.6, the older version has a known problem. | 15:19 |
chris_uk[m] | OvenWerks @OvenWerks:libera.chat I do have Studio Controls 2.2.6. | 15:45 |
OvenWerks | chris_uk[m]: if you run autojack from a terminal do you have the output? | 15:47 |
rgh | anyone knows where/when snd-seq-dummy is loaded ? | 16:22 |
rgh | I'm on 21.10 (cause I borked a 21.04 install .. I'm special) | 16:22 |
OvenWerks | rgh: are you missing it, or want it not to load? | 16:23 |
rgh | I don | 16:23 |
rgh | s/don/want it not to load/ | 16:23 |
OvenWerks | I would expect it gets loaded when midi devices are around... but then midi stuff is there even with no midi device... so I would guess at boot. | 16:24 |
OvenWerks | if you want it not to load, blacklist it. | 16:24 |
OvenWerks | I do not know if there are other seq modules that depend on that or not | 16:25 |
OvenWerks | modprobe -r will fail if another module depends on it | 16:26 |
rgh | gotcha | 16:28 |
chris_uk[m] | OvenWerks @OvenWerks:libera.chat I get this output: | 16:36 |
chris_uk[m] | fozzy@fozzy-systemproductname:~$ autojack|pastebinit Can't open ALSA playback device 'hw:NVidia,0,0'. Can't open ALSA capture device 'hw:NVidia,0,0'. | 16:36 |
OvenWerks | I would not think that would cause a crash... at least not of autojack. I would think that is likely zita-a2j | 16:38 |
chris_uk[m] | I use a Focusrite 6i6 2nd gen | 16:40 |
OvenWerks | It seems normal, zita-a2j (or jackdbus) will find that your monitor does not have a capture device and in zita-a2j just not run or in jackdbus' case run as output only. | 16:40 |
OvenWerks | ok so master is usb | 16:41 |
chris_uk[m] | Studio Controls is working OK in this beta. | 16:41 |
chris_uk[m] | I can' t see any problems in general. | 16:42 |
OvenWerks | if you open studio-controls, and look at the Extra Devices tab, select your nvidia device. The capture port count will probably be 100. | 16:42 |
OvenWerks | if you set it to 0 that error message should go away | 16:43 |
chris_uk[m] | Yes, master is the Focusrite. | 16:43 |
OvenWerks | (easiest way is to hit All twice. | 16:43 |
OvenWerks | So the problem above (crash report) is gone now? | 16:44 |
OvenWerks | chris_uk[m]: there was a problem (about two days ago) with version 2.2.5 that caused a crash in autojack. The crash report may be a left over from that | 16:46 |
chris_uk[m] | I haven' t got the Nvidia drivers in use yet. | 16:46 |
chris_uk[m] | Just tried to lower the capture port count to 0 and I got a crash notification. The + and - bi | 16:46 |
OvenWerks | Interesting | 16:47 |
chris_uk[m] | box is now greyed out so can' t lower it. | 16:47 |
OvenWerks | it can't go lower than 0 | 16:47 |
chris_uk[m] | It is still on 99 | 16:48 |
chris_uk[m] | But greyed out | 16:48 |
OvenWerks | So with a crash report does that mean you can't close the gui? (close button in the lower right) | 16:48 |
chris_uk[m] | Yes, it closes the whole studio controls. | 16:49 |
OvenWerks | so on restart, is that button available again? | 16:50 |
OvenWerks | Maybe run studio-controls from a terminal might give some more info | 16:50 |
chris_uk[m] | Yes, it is available | 16:51 |
OvenWerks | If you click the All beside it should turn to off, then click that and the number should go to 0 | 16:52 |
* OvenWerks needs to make that show off if the number is not 0 | 16:52 | |
chris_uk[m] | Yes, it goes 0 | 16:53 |
OvenWerks | apply should make that permanent | 16:54 |
chris_uk[m] | Ok | 16:54 |
OvenWerks | you may wish the playback to be 0 as well if you don't ever use that output. | 16:54 |
OvenWerks | I can't get the +/- arrows to crash here | 16:55 |
chris_uk[m] | Ok. Done | 16:55 |
OvenWerks | So I am not sure what happened in your case | 16:55 |
OvenWerks | it is hard to know which way to default things for first time use | 16:56 |
chris_uk[m] | Do you want the terminal output? | 16:56 |
OvenWerks | are there errors? | 16:56 |
OvenWerks | I am looking for traceback lines | 16:56 |
chris_uk[m] | TypeError. | 16:57 |
OvenWerks | Yeah I would like that then | 16:57 |
OvenWerks | it is probably the last traceback line. It should have a line number | 16:58 |
chris_uk[m] | Traceback (most recent call last): File "/usr/bin/studio-controls", line 1039, in xdev_changed | 17:01 |
chris_uk[m] | Here is more | 17:03 |
chris_uk[m] | Traceback (most recent call last): File "/usr/bin/studio-controls", line 1039, in xdev_changed sub_db['rate'] = int(self.xdev_rate_drop.get_active_id()) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' | 17:03 |
OvenWerks | interesting so the sample rate in the dropdown is not set. | 17:05 |
OvenWerks | actually.... why would we save that at all? | 17:05 |
OvenWerks | Oh we don't. | 17:06 |
chris_uk[m] | Sample rate greyed out in Extra devices | 17:08 |
chris_uk[m] | And is empty (not set) | 17:09 |
OvenWerks | Yes, that makes sense... it is (or seems to be) the same problem we just fixed in autojack. | 17:11 |
OvenWerks | There are no rates found in the codec#0 file... | 17:13 |
OvenWerks | well actually, this being hdmi, they would be in an excluded part of the file | 17:13 |
OvenWerks | Eickmeyer: ^^^ | 17:14 |
OvenWerks | chris_uk[m]: thank you for testing | 17:14 |
chris_uk[m] | Ok | 17:14 |
OvenWerks | is it possible to run ubuntu-bug studio-controls | 17:15 |
OvenWerks | and add in the above traceback? | 17:15 |
Eickmeyer[m] | Final Freeze is in effect. | 17:15 |
OvenWerks | (in the description) | 17:15 |
OvenWerks | Eickmeyer: ok | 17:16 |
OvenWerks | I will fix anyway. can backports be activated for 21.10 now? | 17:16 |
chris_uk[m] | So no need for Ubuntu-bug? | 17:18 |
Eickmeyer[m] | <OvenWerks> "I will fix anyway. can backports..." <- We *might* be able to sneak it into the release if a good case is made. | 17:21 |
Eickmeyer[m] | chris_uk[m]: It's still needed. | 17:22 |
chris_uk[m] | Ok | 17:53 |
chris_uk[m] | Suitable summary description for bug? | 18:00 |
OvenWerks | studio-controls hangs? | 18:03 |
OvenWerks | studio-controls hangs on apply? | 18:03 |
chris_uk[m] | Ok | 18:03 |
OvenWerks | command line out is: and the stuff above. | 18:04 |
chris_uk[m] | Done | 18:06 |
OvenWerks | What is the bug number? | 18:07 |
chris_uk[m] | Just logged out. | 18:09 |
OvenWerks | ok, I will wait it should show up in my mailbox soon | 18:09 |
chris_uk[m] | I will log back in | 18:09 |
chris_uk[m] | Where do I login? | 18:10 |
OvenWerks | https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1946572 | 18:14 |
ubottu | Launchpad bug 1946572 in studio-controls (Ubuntu) "Studio controls hangs on Apply" [Undecided, New] | 18:14 |
OvenWerks | chris_uk[m]: it is ok, I found it. | 18:16 |
chris_uk[m] | Thanks Ubottu. | 18:17 |
OvenWerks | chris_uk[m]: if you wish, you can download https://raw.githubusercontent.com/ovenwerks/studio-controls/master/usr/bin/studio-controls | 18:19 |
OvenWerks | and run this from the commandline to see if this fixes things | 18:19 |
OvenWerks | I guess you would need to cp it into /usr/bin for it to work right | 18:20 |
OvenWerks | If we are getting too difficult for you, I guess testing can wait... unless Eickmeyer can duplicate this | 18:21 |
chris_uk[m] | It is too difficult. | 18:24 |
OvenWerks | no problem | 18:24 |
OvenWerks | most people are not comfortable with a lot of commandline things | 18:24 |
chris_uk[m] | Does ubuntu-bug command automatically collect the contents of the terminal? | 18:28 |
OvenWerks | no, | 18:28 |
OvenWerks | The only place that happened was because you added it | 18:29 |
chris_uk[m] | Di you have what you need? | 18:29 |
OvenWerks | if the crash icon shows up and you send a bug from there then it does. | 18:29 |
OvenWerks | Yes there is already a fix uploaded. When it gets to the package state I don't know. | 18:30 |
chris_uk[m] | Right. | 18:30 |
OvenWerks | I can't really test it here because my system doesn't show that bug. | 18:31 |
Eickmeyer | chris_uk[m]: Is there any chance I can get you to update the bug description with a description of the behavior? | 23:24 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!