Bug 22449 - quassel-client crashes when a URL in a message is clicked
Summary: quassel-client crashes when a URL in a message is clicked
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-24 17:50 CET by Barry Jackson
Modified: 2021-03-18 00:40 CET (History)
1 user (show)

See Also:
Source RPM: quassel-0.12.4-4.mga6..src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Barry Jackson 2018-01-24 17:50:23 CET 
Description of problem: As summary.

There is no way to kill the remaining broken GUI window other than CTRL/ALT/ESC and click it's header.

Version-Release number of selected component (if applicable):
quassel-client-0.12.4-4.mga6.x86_64

Maybe this needs a rebuild for mga7 ?

How reproducible:


Steps to Reproduce:
1.
2.
3.
Barry Jackson 2018-01-24 17:51:52 CET

Source RPM: quassel-client-0.12.4-4.mga6.x86_64 => quassel-0.12.4-4.mga6..src.rpm

Comment 1 Marja Van Waes 2018-01-25 09:31:22 CET 
Assigning to the registered maintainer.

Assignee: bugsquad => geiger.david68210
CC: (none) => marja11

Comment 2 Barry Jackson 2018-01-25 09:44:01 CET 
The same version in Mga6 is working without problems talking to the same version quassel-core running on a Mga6 server.

In both cases Firefox is default browser at the currently updated versions for Mga6 and Cauldron.
Comment 3 Barry Jackson 2018-02-27 13:40:23 CET 
The crash is happening more often now and not only when clicking a link.
Increasing severity.

I will try to get a backtrace but last time I tried the debuginfo-install script was broken making it very difficult.

Severity: normal => major

Comment 4 Barry Jackson 2021-03-18 00:40:23 CET 
Closing as I have not seen this issue in some time. Probably fixed in an update at some point.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.