Install/Setup bug

[cmaughan]

Aside from a boot error after a clean install of the app, the first thing I notice is that the dialog showing the error is just a couple of lines high and I can't resize it; making it very difficult to read the error:

I did Ctrl+A, CTRL+C to copy it to notepad:
Complains about a missing 'U' drive, which I obviously don't have...

Sonic Pi Boot Error Report

System Information

• Sonic Pi version: 3.1.0
• OS: Windows 10

GUI Log

C:\Users\cmaughan\.sonic-pi\log\gui.log

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] -    port: 4558 [OK]
[GUI] - Server OSC listen port 4557
[GUI] -    port: 4557 [OK]
[GUI] - Server incoming OSC cues port 4559
[GUI] -    port: 4559 [OK]
[GUI] - Scsynth port 4556
[GUI] -    port: 4556 [OK]
[GUI] - Server OSC out port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Scsynth send port 4556
[GUI] - Erlang router port 4560
[GUI] -    port: 4560 [OK]
[GUI] - OSC MIDI out port 4561
[GUI] -    port: 4561 [OK]
[GUI] - OSC MIDI in port 4562
[GUI] -    port: 4562 [OK]
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 21928
[GUI] - waiting for Sonic Pi Server to boot...
..
[GUI] - Sonic Pi Server failed to start with this error message: 
      > Server Exception:
 No such file or directory @ rb_sysopen - U:/.sonic-pi/log//osc_cues.log
 ["C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `open'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:106:in `block (2 levels) in included'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'"]
[GUI] - UDP OSC Server no longer listening
..........................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...

Server Errors

C:\Users\cmaughan\.sonic-pi\log\server-errors.log

Unable to create U:/.sonic-pi due to permissions errors
Unable to create U:/.sonic-pi/store/default/ due to permissions errors
Unable to create U:/.sonic-pi/log/ due to permissions errors
Unable to create U:/.sonic-pi/store/default/cached_samples due to permissions errors
Unable to open log file U:/.sonic-pi/log//debug.log
Unable to open process log file U:/.sonic-pi/log//processes.log

Server Output

C:\Users\cmaughan\.sonic-pi\log\server-output.log

Sonic Pi server booting...
Using protocol: udp
Detecting port numbers...
Send port: 4558
Listen port: 4557
  - OK
Scsynth port: 4556
  - OK
Scsynth send port: 4556
  - OK
OSC cues port: 4559
  - OK
Erlang port: 4560
  - OK
OSC MIDI out port: 4561
  - OK
OSC MIDI in port: 4562
  - OK
Failed to start server: No such file or directory @ rb_sysopen - U:/.sonic-pi/log//osc_cues.log
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `open'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:106:in `block (2 levels) in included'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'
Server is exiting.
Shutting down GUI...
Goodbye :-)

Scsynth Output

C:\Users\cmaughan\.sonic-pi\log\scsynth.log

Process Log

C:\Users\cmaughan\.sonic-pi\log\processes.log

[ethancrawford]

Hi @cmaughan - by "obviously don't have...", I assume you have neither a physical hard drive or a network drive connected to your computer with that name?

[cmaughan]

Yes, no U drive. Just C:/

[ethancrawford]

If you have Ruby installed on your computer in its own right, (instead of just through Sonic Pi,), I'm not sure how immediately helpful it will be, but we can do a few small things that might shed some light on the issue, if you're able:

1. Open a command prompt (ie, run cmd) and in it, run the interactive Ruby interpreter by typing irb and pressing [Enter]
2. Type the following few things in the window once irb has started (pressing [Enter] after each) and see what they spit out:

• Dir.home
• ENV['SONIC_PI_HOME']

(I'm guessing that Dir.home might say something like "U:" maybe?)
Also, that environment variable SONIC_PI_HOME can be set to an arbitrary folder that you desire for Sonic Pi to have act as it's area for storing config details/log files/etc. Perhaps using this would be a suitable work around? you could set it to C:\Users\cmaughan specifically, or something else entirely.

As to why it's failing to detect the default home folder, not sure really.

[cmaughan]

Thanks for the feedback, I just found the problem and solved it thanks to a post on stackoverflow. The issue was that I have a local environment variable:
HOMEDRIVE=U:
It turns out that this is related to my machine being setup on a corporate domain, which creates the U drive for some kind of user data, but it doesn't really exist (I don't understand why):
https://superuser.com/questions/255776/overriding-homedrive-and-homepath-as-a-windows-7-user

The above post told me to do this, which sorted it out - I just did it in a command prompt before launching sonic pi:
net use U: \localhost\C$\Users\cmaughan

[ethancrawford]

Note my comment above that you can also start Sonic Pi with its own 'home drive' environment variable too, if that is preferred 🙂

[cmaughan]

Thanks, I missed that bit, great :)
Next problem is that the UI isn't so hot on a high DPI display ;) But I can live with that.

[ethancrawford]

Maybe it'll end up on the to-do list... It would definitely be nice to support them 🙂

[ethancrawford]

@cmaughan - Is there anything still unaddressed in this issue?

[cmaughan]

I think the DPI issues are largely sorted at this point.
The Home drive is likely still a problem that catches users out and stops them using Sonic Pi (IMHO, a special setting isn't enough if the user doesn't know why the app won't start). It needs a repro and fix I think.