MuttonChop segfaults if config file is incomplete.

Bug #1161975 reported by timttmy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MuttonChop
Fix Released
Undecided
Unassigned

Bug Description

After upgrading MuttonChop from an older version to a current version the programme would segfault and leave no clue to why it was doing so.
It turns out it is because the port that the MuttonChop server runs on needs to be specified in the muttonchop.conf file even if you are using the assumed default port 2876.
It would be a good idea to either inform the user of the fault or actually default to a known port.

jezra (jezra)
Changed in muttonchop:
status: New → Fix Committed
jezra (jezra)
Changed in muttonchop:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.