madscientist/msjnc

msjnc doesn't start

Opened this issue · 7 comments

datr commented

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:

my $window = Gtk2::Window->new('toplevel');

And exits. Any ideas as to what might be happening?

datr commented

Running

./msjnc --fg

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.

/home/dean/.juniper_networks/network_connect/ncsvc: unrecognized option '-U'
usage: /home/dean/.juniper_networks/network_connect/ncsvc -h host -u user -p passwd -r realm -f cert_file [-L log_level] [-g]
       /home/dean/.juniper_networks/network_connect/ncsvc -v
       /home/dean/.juniper_networks/network_connect/ncsvc -K

    log_level : 0 : Log Critical messages only
                1 : Log Critital and Error messages
                2 : Log Critital, Error and Warning messages
                3 : Log Critital, Error, Warning and Info messages(default)
                4 : Log All Verbose messages
                5 : Log All messages
    -v : Print version information and quit
    -g : Zip and upload logs to host
    -K : Kill all running ncsvc services

/home/dean/.juniper_networks/network_connect/ncsvc -v                                                                                                           
Juniper Network Connect Server for Linux.
Version         : 1.2
Release Version : 6.0-0-Build12507
Build Date/time : Dec 27 2007 17:32:48 
Copyright 2002-2007 Juniper Networks

Removing line 850 seemed to fix the problem.

$pf->{url}  and push @cmd, ('-U', $pf->{url});

Same here. Ubuntu 13.04, msjnc doesn't seem do do anything but msjnc --fg works fine
(I didn't run into the second problem that you mention though)

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.

WARNING **: Unable to create Ubuntu Menu Proxy: Timeout was reached at /usr/bin/msjnc line 967.
at /usr/bin/msjnc line 967
        main::window_passwd('Enter password', 'Enter your password or PIN+SeurID') called at /usr/bin/msjnc line 1113
        main::window_dis_connect('Gtk2::Button=HASH(0x2127c10)') called at /usr/bin/msjnc line 2168
        eval {...} called at /usr/bin/msjnc line 2168

--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...