This is what I get when attempting to open one more console with mocp http://dpaste.de/WHhsO/ (this text will be erased in a month. Please copy this text somehow to fit in this thread or add or tags)
Please send mocmaint 'mocp_client_log' from the failing client and the last 100 lines of 'mocp_server_log' (both gzipped). You will have to run 'mocp' with the '-D' option to get these.
The '-D' option shouldn't make a difference but I wouldn't have thought to try debugging this problem without it.
I tried without '-D' but still couldn't reproduce it. I suspect it more likely that it has to do with the particular file selected or being played at the time.
Are you able to trigger the assertion without '-D' then repeat the exact same sequence with it?
> I suspect it more likely that it has to do with the particular file selected or being played at the time.
Probably so. I have executed mocp -D again after noticing I had two displays already, so I loaded a directory, tried to open another display, and after I failed I started mocp -D and the wanted bug did occur.
GenghisKhan
Sat, 2012-10-20 23:08
Permalink
I use Salix OS
I installed MOC 2.5.0-beta1 with the SLKBUILD from http://salixos.org/forum/viewtopic.php?p=26606#p26606
jcf
Sun, 2012-10-21 01:23
Permalink
Gathering Evidence
Please send mocmaint 'mocp_client_log' from the failing client and the last 100 lines of 'mocp_server_log' (both gzipped). You will have to run 'mocp' with the '-D' option to get these.
GenghisKhan
Sun, 2012-10-21 06:34
Permalink
mocp -D behaves differently
Using mocp -D does allow me to use several displays. I think my logs are useless.
mocp_client_log http://rghost.net/41061506
mocp_server_log http://rghost.net/41061509
jcf
Sun, 2012-10-21 07:52
Permalink
Interesting!
The '-D' option shouldn't make a difference but I wouldn't have thought to try debugging this problem without it.
I tried without '-D' but still couldn't reproduce it. I suspect it more likely that it has to do with the particular file selected or being played at the time.
Are you able to trigger the assertion without '-D' then repeat the exact same sequence with it?
GenghisKhan
Mon, 2012-10-22 18:31
Permalink
I did it
> I suspect it more likely that it has to do with the particular file selected or being played at the time.
Probably so. I have executed mocp -D again after noticing I had two displays already, so I loaded a directory, tried to open another display, and after I failed I started mocp -D and the wanted bug did occur.
I have sent you an Email.
jcf
Sun, 2013-09-08 04:30
Permalink
FIXED
I have today committed r2552 to SVN which fixes this problem.
Many thanks to "GenghisKahn" for sticking with this problem throughout many debugging tests.