I am using a new install of Opensuse 15.1, updated. QSSTV version 9.4.4.
When I start QSSTV for one user, it started up. For another, it does not. When I start it from a terminal i get the following error:
** (qsstv:28320): WARNING **: Couldn’t register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In my previous 15.1 install QSSTV started using the same home directory.
EDIT:
After several minutes, a window frame appears. After several more, some content appears, but window controls don’t work. It you shade the title bar, the window contents is replace by whatever you were just viewing.
Although I haven’t used this app,
There are some basic things I generally configure for this type of app.
You don’t describe how you launch this app (automatically like a service? Manually?) and you don’t say whether you’re running the second User simultaneously with the first user, or reboot before logging in as a new User or if you simply logout from the first User or login as the second User, and if either of the two Users is logging in remotely or interactively at the machine.
The reason why how each User logs in and launches the app can be an issue if both are using the same (default?) app settings, I’ve generally found that each User typically needs to be configured with unique network settings and sometimes serial settings.
If the app was launched by one person with a particular configuration, unless the app is thoroughly killed it may still be using resources that a second User might want to use if both use the same configuration, causing contention and “no response” for the second User.
It has a main menu entry, but I have been launching it from a terminal for both users to see messages or errors.
I log in as one user, then log out and log in as the other user.
I did sopy the supposed config file from the user that works, and put it in my Home directory. I no longer get the accessibility bus message, but the program launch remains.
The initial splash screen does appear, startup messages appear, and then everything almost stops. After a few minutes, the program window frame appears, after a few more minutes, the main program window appears, but nothing is accessible.
I am fairly certain this has something to do with my user settings somewhere. And, if I remove the config folder, the accessibility error returns.
Am speculating that although you may be logging out and changing the User on one end, that is not being communicated to the other end which still thinks that it’s communicating to the first User.
If both machines do a complete reboot before connecting the first time,
Do you see an error (I’m guessing not).
Then, I’m guessing that you’re seeing your problem after one end logs out, logs back in as another User and tries to connect using different credentials.
I have copied the “config” file from the user for which QSSTV works. Now I when start QSSTV I now longer get the error, but the program still doesn’t fully start.
I issue killall QSSTV twice. The second time says there is no such process. I log in to the other user, start QSSTV and it starts fine. Exit QSSTV. Kill QSSTV. Log out. Log in to the first user, QSSTV won’t start.
After I copied the config file from a user that works to my Home, there aren’t any errors generated in the terminal when I start the program. I just takes about .3% of cpu time, and never becomes usable.
A new wrinkle…
If I have WSJT_X running, and start QSSTV, they will conflict, and QSSTV seems to win. I get an error dialog from WSJT-X and then the QSSTV window becomes active and I am able to change configuration settings. There’s also another error dialog from QSSTV.
As soon as I can reliably reproduce the QSSTV error I will post it.
Also, I don’t think QSSTV is detecting all of the sound cards.
I was able to get QSSTV to start up again by having it conflict with WSJT-X. I then changed the radio settings to use my 8900 and the SignaLink connected to it. It will monitor and transmit, shut down and restart. So … there is a configuration issue with the 991a. If the configuration is incorrect, QSSTV hangs.
I may put a serial card in the computer and connect with that to see if that helps.
I may also connect my IC-718 and see if I can transmit/receive SSTV with it using a SignaLink. I can always change frequencies manually.
And MAYBE there is a 991a forum floating around that can help.
Hi
I would suggest contacting the maintainer of the repository you acquired the QSSTV package from as I’m assuming they have hardware to test on(?). If you look at the changelog, should see an email address
The other option is to fire up a live USB of say Leap 15.2 or Tumbleweed and install the QSSTV package and see if it’s working in the later release, Leap 15.1 will be EoL this month…
I was able to create a new user and QSSTV would startup there. I think the problem in my user account is it had been set up for my IC-718 and then I changed settings for my 991a, and the program would hang. I think I have been able to demonstrate to myself that the problem is the radio configuration, That is why I need to find the true configuration file. If I muck things up, I can then delete the config file and start over without going through the conflict with another program routine.
I will be expanding my search by looking for info on that config file, and settings for the radio.
