Project

General

Profile

Bug #1332

Quassel crash on saving new server

Added by ThePsionic over 10 years ago. Updated over 7 years ago.

Status:
New
Priority:
Urgent
Assignee:
-
Category:
Usability
Target version:
-
Start date:
01/13/2015
Due date:
% Done:

0%

Estimated time:
Version:
0.10.0
OS:
Windows

Description

When I try to save a new server, Quassel crashes. This happens whether I do or do not enter a server password, whether or not I use the default port, and whether or not I use SSL. This has been tested on both Quassel 0.10.0 and Quassel 0.11.0 on Windows 64-bits.

History

#1 Updated by ThePsionic over 10 years ago

Note that this happens on clean installs, nothing has been changed. Only Quassel itself has been installed, not Core or Client (a.k.a. minimal install). As far as I am aware, no crash logs are generated.

#2 Updated by ThePsionic over 10 years ago

Adding servers does work when one has already been configured by the setup wizard.

#3 Updated by digitalcircuit over 7 years ago

I can confirm this still happens in Quassel 0.13-git-master (unreleased).

  1. Compile monolithic and/or client and core
  2. Run in fresh directory, e.g.
    --configdir="$(mktemp -d)"
  3. Cancel setup wizard
  4. Go to File → Networks → Configure Networks
  5. Add a network
  6. Crash

Talking with justJanne on IRC, it also happens if you delete an identity in use. Core doesn't crash, but client/monolithic do.

The client needs to handle missing identities better; warning and/or offering to set up a new identity if one's missing/been deleted from a network.

Also available in: Atom PDF