View Single Post
Old 07-23-2018, 09:27 AM   #32
shosty
Human being with feelings
 
Join Date: Aug 2015
Posts: 144
Default

Quote:
Originally Posted by clepsydrae View Post
It's just a kernel message saying that while reassociating your wireless with an access point (of MAC address a8:f5:ac:bf:04:d9) it received a response. It's typical for there to be periodic log messages about wireless communication; I'd guess it was a red herring unless you see the lines pop up every time exactly when reaper hangs. Sometimes network or video card drivers do cause weird issues.

It would surprise me if reaper tries to open a net port and doesn't have a very fast timeout on that operation in the event that the network is not reachable. I think there would be myriad bug reports of this if that was the case.

You're running reaper from the command line, I assume, to make sure to catch any output it produces?

Sounds like you're using JACK, so I would open the qjackctl "Messages" window and watch that as reaper starts.

You've tried a brand new ~/.reaper directory?

You can "journalctl -f" in a terminal as reaper starts, if you're not already. (If that doesn't work do "tail -f /var/log/syslog".)
I was only running it from a terminal to capture the output, I don't normally.

Messages doesn't show anything particularly interesting that I can see:

Code:
Mon Jul 23 17:22:44 2018: Starting jack server...
Mon Jul 23 17:22:44 2018: JACK server starting in realtime mode with priority 10
Mon Jul 23 17:22:44 2018: self-connect-mode is "Don't restrict self connect requests"
Mon Jul 23 17:22:44 2018: Acquired audio card Audio0
Mon Jul 23 17:22:44 2018: creating alsa driver ... hw:0|hw:0|2048|2|44100|0|0|nomon|swmeter|-|32bit
Mon Jul 23 17:22:44 2018: Using ALSA driver HDA-Intel running on card 0 - HDA Intel PCH at 0xd9430000 irq 34
Mon Jul 23 17:22:44 2018: configuring for 44100Hz, period = 2048 frames (46.4 ms), buffer = 2 periods
Mon Jul 23 17:22:44 2018: ALSA: final selected sample format for capture: 32bit integer little-endian
Mon Jul 23 17:22:44 2018: ALSA: use 2 periods for capture
Mon Jul 23 17:22:44 2018: ALSA: final selected sample format for playback: 32bit integer little-endian
Mon Jul 23 17:22:44 2018: ALSA: use 2 periods for playback
17:22:44.254 D-BUS: JACK server was started (org.jackaudio.service aka jackdbus).
Mon Jul 23 17:22:44 2018: graph reorder: new port 'system:capture_1'
Mon Jul 23 17:22:44 2018: New client 'system' with PID 0
Mon Jul 23 17:22:44 2018: graph reorder: new port 'system:capture_2'
Mon Jul 23 17:22:44 2018: graph reorder: new port 'system:playback_1'
Mon Jul 23 17:22:44 2018: graph reorder: new port 'system:playback_2'
Mon Jul 23 17:22:44 2018: New client 'PulseAudio JACK Sink' with PID 1726
Mon Jul 23 17:22:44 2018: port 'PulseAudio JACK Sink:front-left' created
Mon Jul 23 17:22:44 2018: port 'PulseAudio JACK Sink:front-right' created
Mon Jul 23 17:22:44 2018: Connecting 'PulseAudio JACK Sink:front-left' to 'system:playback_1'
Mon Jul 23 17:22:44 2018: Connecting 'PulseAudio JACK Sink:front-right' to 'system:playback_2'
Mon Jul 23 17:22:44 2018: New client 'PulseAudio JACK Source' with PID 1726
Mon Jul 23 17:22:44 2018: port 'PulseAudio JACK Source:front-left' created
Mon Jul 23 17:22:44 2018: port 'PulseAudio JACK Source:front-right' created
Mon Jul 23 17:22:44 2018: Connecting 'system:capture_1' to 'PulseAudio JACK Source:front-left'
Mon Jul 23 17:22:44 2018: Connecting 'system:capture_2' to 'PulseAudio JACK Source:front-right'
Mon Jul 23 17:22:45 2018: New client 'REAPER' with PID 1357
17:22:45.378 JACK connection change.
17:22:45.379 Statistics reset.
17:22:45.415 Client activated.
17:22:45.416 Patchbay deactivated.
17:22:45.474 JACK connection graph change.
17:22:45.672 JACK connection change.
Mon Jul 23 17:22:45 2018: New client 'qjackctl' with PID 1825
Mon Jul 23 17:22:45 2018: port 'REAPER:MIDI Input 1' created
Mon Jul 23 17:22:45 2018: port 'REAPER:MIDI Input 2' created
Mon Jul 23 17:22:45 2018: port 'REAPER:MIDI Input 3' created
Mon Jul 23 17:22:45 2018: port 'REAPER:out1' created
Mon Jul 23 17:22:45 2018: port 'REAPER:out2' created
Mon Jul 23 17:22:45 2018: port 'REAPER:in1' created
Mon Jul 23 17:22:45 2018: port 'REAPER:in2' created
Mon Jul 23 17:22:45 2018: Connecting 'REAPER:out1' to 'system:playback_1'
Mon Jul 23 17:22:45 2018: Connecting 'REAPER:out2' to 'system:playback_2'
Mon Jul 23 17:22:45 2018: Connecting 'system:capture_1' to 'REAPER:in1'
Mon Jul 23 17:22:45 2018: Connecting 'system:capture_2' to 'REAPER:in2'
When I killed the process and started again it started so wasn't able to check your last suggestion, I will try to next time though, as well as a new reaper directory.
shosty is offline   Reply With Quote