=== d is now known as Guest77600 [04:35] hola [04:36] <`Fibz> hiya [09:35] hello [09:35] does anyone know if ubuntu studio have the same screen-goes-off-and-cant-turn-back-on-when-closing-the-lid problem as xubuntu? [09:44] s/have/has/ [11:40] How do I get Ubuntu Studio 14.04 to recognize my 1024x768 screen? It tells me that the display is 640x480. [11:43] I don't have any opportunity to get the 1024x768 resolution. [11:44] Btw, I'm using Ubuntu Studio on Virtual Box of Ubuntu 14.04 [13:03] hi [14:02] ciao === marco is now known as Guest92920 [15:13] Stupid question, I know - but how do I dual boot Ubuntu Studio alongside an already installed Ubuntu? [17:12] Hello [17:12] running 64bit, most of my stuff is working great [17:41] strangely, both jackd and jackdbus are running in this install. In my 32bit install, only "jackdbus auto" was present. [17:42] also, my actual sound card isn't showing up in pavucontrol if it's used by jack :( [17:56] fortunately i kept my 32bit install files, so if any 32bit libs are missing for stuff, i can use them...seems to be working perfectly :D === [TFB]Sakrecoer is now known as sakrecoer [18:12] does anyone have any idea why my (physical) sound card isn't showing up in pavucontrol? [18:12] it shows up in alsamixer [18:13] (onboard sound card for now) [19:52] delt: you should not have both jackd and jackdbus running. What that means is that jackdbus is running but not on and jackd has been turned on by some application wanting to talk to jack and not finding it. Killall -9 jackd and then qjackctl or jack_control can start jackdbus working and pulse will be able to find jack and send sound through it's card. [19:53] Or if you don't turn jackdbus on, pulse should at least see the sound device and be able to use it [19:53] OvenWerk1: yeah, i'm trying to figure out where jackd is being started from.. [19:54] Any app that uses jack as it sound backend will start it if there is no jack running. [19:54] but jackd does not play with dbus well and so can't work with pulse [19:54] on my 32bit install it worked with just jackdbus...? [19:54] same on 64bit [19:54] yes it did, using the jack sink plugin for pulse [19:57] anyway, it's working fine now, except the actual hardware sound card isn't visible in pavucontrol. [19:57] alsa or pulse programs are outputting to the jack sink which i can see in qjackctl [19:58] and i can see those apps listed in pavucontrol's playback tab, with the meters moving [20:00] in qjackctl i have "enable D-bus interface" ticked on [20:00] As soon as jack stops the alsa device will show up in pavucontrol. [20:01] wasn't this way on my other install... i could still adjust the volume on it [20:02] yeah if i kill jack, it appears in pavucontrol [20:02] but even when jack is using it, i can adjust the volume of the hardware in, say, alsamixer [20:05] i'd just like it to also appear in pavucontrol =) [20:13] even when only jackdbus is running and not jackd, i still can't see the sound card in pavucontrol [20:13] jack apps are working fine, and there's no jackd process [20:14] .... missing mixer module perhaps? [20:43] hmm... now there's a 5-10 second delay when i press alt+f2 before the "run program" box appears [20:43] I am not the one to ask about that part, qasmixer is my choice [20:43] oops I was talking about alsa still [20:44] I have all the alsa devices turned off in pulse. [20:45] I have not found pulse deals with levels in a way I like anyway. [20:45] I have qjackctl set to load on login with jackdbus running and use that for all my sound. [21:33] heh, i uninstalled some unity/ubuntu packages, and the problem solved itself :D [21:46] oh..duh, that's because of the order in which the processes were started :/ [21:50] actually when the pavucontrol window pops up i can see my sound card for a split second then it disappears