Project

General

Profile

Bug #1354

Immediate crash on windows with v0.12.2

Added by Yoshi8765 over 5 years ago. Updated about 5 years ago.

Status:
New
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
Start date:
05/09/2015
Due date:
% Done:

0%

Estimated time:
Version:
0.11-pre
OS:
Windows

Description

I just used the exe installer to upgrade quassel from v0.11.0 to 0.12.2. I simply let the installer do its business. It chose to uninstall v0.11.0 first then install v0.12.2 in the same directory. I am installing minimal (no quasselclient or core).

With this new version, every time it starts up, it crashes immediately. I have no idea how to deal with this.

History

#1 Updated by Monzta over 5 years ago

I experience the same. In 0.12 i can't write messages. 0.10 and all other version won't start. 0.11 was fine before, but does not start anymore if i install it new.

#2 Updated by JessAveryJA over 5 years ago

I am also having this problem. I just updated to 0.12.2 from 0.10.0 and it crashes on start.

#3 Updated by Shoop about 5 years ago

Can confirm bug. Also affects quassel core it seems, but not quassel client, which will sit and do nothing happily

Happens everytime. Back to .11 for now

Heres the log from Windows event viewer

Log Name: Application
Source: Application Error
Date: 7/11/2015 5:58:38 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DeadBolt
Description:
Faulting application name: quassel.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x100ec341
Faulting process id: 0x1b08
Faulting application start time: 0x01d0bc24a72db153
Faulting application path: C:\Program Files (x86)\Quassel\quassel.exe
Faulting module path: unknown
Report Id: fb9f0785-2817-11e5-ab04-ecf4bb46444d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-07-11T21:58:38.000000000Z" />
<EventRecordID>114488</EventRecordID>
<Channel>Application</Channel>
<Computer>DeadBolt</Computer>
<Security />
</System>
<EventData>
<Data>quassel.exe</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>100ec341</Data>
<Data>1b08</Data>
<Data>01d0bc24a72db153</Data>
<Data>C:\Program Files (x86)\Quassel\quassel.exe</Data>
<Data>unknown</Data>
<Data>fb9f0785-2817-11e5-ab04-ecf4bb46444d</Data>
</EventData>
</Event>

#4 Updated by circiter about 5 years ago

I'd like to add, that in my case (no auto-connect) the application crashes on connect. It starts fine, until I choose a network and try to connect. I get to "Found your hostname." I'm sure it's the same bug.

#5 Updated by slikts about 5 years ago

Is there some better way to debug this crash? I haven't been able to find any information on how to submit a proper bug report, like if there's a way to get a crash log. The 0.12 version for Windows should probably be unpublished or at least a notice added that there's a known issue and a link to 0.11. I ended up editing the download URL to get the 0.11 version that actually works.

#6 Updated by rdes321@gmail.com about 5 years ago

The crash happens after identify with NickServ. If you turn off auto identify, you can connect, but it still crashes when you try to identify manually.

Also available in: Atom PDF