I recently found that I wasn't hearing my usual notification sound, although I hadn't changed any configuration settings. I had a command configured to run too, but that wasn't running either (although I have confirmed it's working correctly) When I open the "Configure Notifications" panel, it seems to work but when I click "OK" the window just freezes and I have to kill Konversation. I thought this might be something to do with a corrupted configuration file, so I experimented by quitting Konversation, removing ~/.kde/share/config/konversationrc and ~/.kde/share/config/konversation.notifyrc and restarting, but I still see the same behaviour. I don't see the panel freeze behaviour on any other configuration panels, and neither do I see it if I click "Cancel" on the notifications configuration panel. This has severely disrupted my workflow - I'd love to find a fix or workaround for this! Reproducible: Always Steps to Reproduce: a) lack of notifications: 1. Start Konversation 2. Get someone to mention my nickname b) panel freeze: 1. Start Konversation 2. Click on Settings->Configure Notificatons->OK Actual Results: a) I hear no notification sounds and my notification command is not run. b) the panel cannot be closed and I cannot continue with IRC conversations (although it still redraws and I can drag the window and panel around, maximise them, etc). After clicking "OK", neither "Cancel" or the window close button work. Expected Results: I should hear my usual notification sound file:///usr/share/sounds/KDE-Im-Nudge.ogg. The panel should disappear.
For the record, here's the output of running "apt-cache showpkg konversation" on my machine: Package: konversation Versions: 1.5~rc1+git20130415-0ubuntu1 (/var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_raring_universe_binary-amd64_Packages) (/var/lib/dpkg/status) Description Language: File: /var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_raring_universe_binary-amd64_Packages MD5: 529965a53c80f878568781c6a205d5f5 Description Language: en File: /var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_raring_universe_i18n_Translation-en MD5: 529965a53c80f878568781c6a205d5f5 Reverse Depends: konversation:i386,konversation kubuntu-full,konversation konversation-dbg,konversation 1.5~rc1+git20130415-0ubuntu1 konversation-data,konversation 1.3~beta1-2 konversation-data,konversation 1.3~beta1-2 konversation-data,konversation 1.5~rc1+git20130415-0ubuntu1 Dependencies: 1.5~rc1+git20130415-0ubuntu1 - kde-runtime (0 (null)) kdepim-runtime (0 (null)) libc6 (2 2.14) libkabc4 (2 4:4.4.3) libkde3support4 (2 4:4.4.3) libkdecore5 (2 4:4.5.85) libkdeui5 (2 4:4.7.0) libkemoticons4 (2 4:4.4.95) libkidletime4 (2 4:4.4.95) libkio5 (2 4:4.5.85) libknotifyconfig4 (2 4:4.4.3) libkparts4 (2 4:4.4.3) libphonon4 (2 4:4.2.0) libqca2 (2 2.0.2) libqt4-dbus (2 4:4.7) libqt4-network (2 4:4.7) libqt4-qt3support (2 4:4.7) libqt4-xml (2 4:4.7) libqtcore4 (2 4:4.8.0) libqtgui4 (2 4:4.8.0) libsolid4 (2 4:4.4.3) libstdc++6 (2 4.1.1) phonon (0 (null)) konversation-data (5 1.5~rc1+git20130415-0ubuntu1) konversation:i386 (0 (null)) Provides: 1.5~rc1+git20130415-0ubuntu1 - irc Reverse Provides:
Unfortunately this is a standard dialog provided by KDE's libraries, and we haven't received any similar reports nor are we able to reproduce the problem, so we're a bit stuck for now. It's possible upgrading to a newer KDE version might help you, otherwise this would probably require debugging acrobatics locally on your system (i.e. use gdb to find out what it's getting stuck on). What version of kdelibs do you have installed?
Thanks for the reply - I feared as much, but thought I should report the problem anyway. As it happens, I managed to fix the problem by uninstalling and reinstalling Konversation, and rebooting (I'm still using the same configuration files). Perhaps a bit flipped in the binary or something because it works fine now. (I now wish I'd checksummed the old binary to check that hypothesis).
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!