Bug 355579 - Konversation crash if audio-notify is enabled
Summary: Konversation crash if audio-notify is enabled
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.6
Platform: Ubuntu Linux
: NOR grave
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-19 10:26 UTC by Samuel Suther
Modified: 2020-11-24 23:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Suther 2015-11-19 10:26:50 UTC
If someone call my nickname in a IRC-Chat, and following isset in Konversation-Settings:
Configure Notifications ⇒ Play Sound (checked) ⇒ Nickname called

Konversation crash

Reproducible: Always




konversation
QCoreApplication::arguments: Please instantiate the QApplication object first
XSync seems available and ready
XSync Inited
Supported, init completed
Created alarm 27262977
codecForName: ucnv_open failed ISO-8859-16 U_FILE_ACCESS_ERROR
codecForName: ucnv_open failed ISO-8859-16 U_FILE_ACCESS_ERROR
kf5.kiconthemes: "Theme tree: (Breeze)"
0x3050e40 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x24aeb80) ): Attempt to set a screen on a child window.
0x304a310 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x24aeb80) ): Attempt to set a screen on a child window.
0x302d530 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x24aeb80) ): Attempt to set a screen on a child window.
0x305eb30 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x24aeb80) ): Attempt to set a screen on a child window.
Speicherzugriffsfehler (Speicherabzug geschrieben)
Comment 1 Justin Zobel 2020-11-21 06:55:44 UTC
Thanks for the report, Samuel. I've just tested this with konversation 1.7.7 and I can't replicate the issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 2 Samuel Suther 2020-11-24 15:39:48 UTC
Nope, don't use it for a long time now. Ticket is sooooooooo old. 
Please only close it!