| Summary: | Konversation crashes when saving changes made to identity | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | JR <zorael> |
| Component: | general | Assignee: | Konversation Developers <konversation-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | hein |
| Priority: | NOR | Keywords: | triaged |
| Version: | 1.3.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
konversationrc
kcrash gathered upon connection crash |
||
|
Description
JR
2011-06-09 17:31:06 UTC
Addendum; This happens when I try to connect to the server as well, rendering the program currently nonfunctional. I can attach that kcrash if need be, or file a new bug if you wish it. This is pretty funky, because it's crashing in generated rather than hand-created code, and it's the first such crash report I'm aware of. Considering 1.3.1 has been out in the wild for quite some time, and this is happening in a frequently-used part of the UI, I'd expect there to be (many) more crash reports if it was an easy-to-reproduce problem. Needless to say I also can't reproduce it. So we might be in for a chase. Right now I'd like you to do two things: a) Please attach your Konversation settings file. That's $KDEHOME/share/config/konversationrc, where $KDEHOME is $HOME/.kde or $HOME/.kde4 depending on what your distro has chosen to use. PLEASE NOTE that this file may contain IRC network services (e.g. nickserv), server and channel passwords and perhaps other passwords (say as part of the Quick Button or command alias configs) depending on whether you've configured any in Konversation. You should remove these passwords before attaching the settings file here using your favorite text editor. If you're not comfortable attaching your settings here for privacy reasons, please consider mailing it to me at hein@kde.org. If you do so it may be circulated privately among Konversation developers. b) Yes, please do attach the other crash backtrace you mentioned in the addendum here. Created attachment 62159 [details]
konversationrc
Apologies for the wait. I'm attaching my konversationrc file, and then the other kcrash I get from attempting to connect.
Created attachment 62160 [details]
kcrash gathered upon connection crash
(In reply to comment #4) > Created attachment 62160 [details] > kcrash gathered upon connection crash This backtrace looks like a very different crash: Application: Konversation (konversation), signal: Segmentation fault [KCrash Handler] #6 Server::getViewContainer (this=<value optimized out>) at ../../src/irc/server.cpp:3567 #7 0x000000000049cc58 in Server::Server (this=0x2505550, parent=<value optimized out>, settings=...) at ../../src/irc/server.cpp:116 #8 0x0000000000479322 in ConnectionManager::connectTo (this=0x1d16140, flag=<value optimized out>, settings=...) at ../../src/connectionmanager.cpp:149 #9 0x00000000004795b4 in ConnectionManager::connectTo (this=0x1d16140, flag=Konversation::PromptToReuseConnection, serverGroupId=<value optimized out>) at ../../src/connectionmanager.cpp:94 #10 0x000000000047c8ae in ConnectionManager::qt_metacall (this=0x1d16140, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0x7fff3ce10a10) at ./connectionmanager.moc:140 Is this reproducible with Konversation 1.4 or 1.5 RC1? Then we would need a newer backtrace. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |