-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
msjnc doesn't start #10
Comments
Running
Seems to work fine though, I was able to get it running for the most part. I did run into another issue though. msjnc tried to pass a -U parameter to ncsvc. My version of ncsvc doesn't support this parameter and so immediately exited.
Removing line 850 seemed to fix the problem.
|
Same here. Ubuntu 13.04, msjnc doesn't seem do do anything but msjnc --fg works fine |
Yup, same problem here - Ubuntu 13.04 only works when using --fg. I have not yet been able to figure out why, but I did run it in an xterm with perl -d and got the following error after the Gtk->init call forked off.
|
--fg works. No subsequent issues though, what could be a plausible fix? |
Without the --fg option, msjnc runs in the background (which profile is used?). In addition, the Ubuntu launcher created by msjnc in ~/.local/share/applications/ms-jnc.desktop does not apply the --fg option. Users may think the launcher doesn't work. |
Yep, --fg works fine. I just edited my ~/.local/share/application/ms-jnc.desktop file and add the --fg option to the Exec line. Works like a champ. |
Yup - same here: Upgraded from kubuntu 12.x to (gnome) ubuntu 14.x and MS-JNC just stopped working. Much hair pulling before I found this thread, which saved my bacon! Adding the [--fg] option on the command line works like a charm, and [deanproxy]'s advice to put it into the [ms-jnc.desktop] file makes it all sweetness and cream. Now, I just wonder why this is a problem in the first place? I doubt it's something super particular to the Mad Scientist's work - but I don't have so much time to investigate. I have money to earn... |
Just tried the script on a fresh build of Ubuntu 13.04. The script exits without an error code but nothing else seems to happen.
I'm afraid I don't know much perl but adding in some extra logging it seems to get to line 1657:
And exits. Any ideas as to what might be happening?
The text was updated successfully, but these errors were encountered: