I was trying to compose a new mail message. The composer window opened, and I tried to drag and drop an image from a message I had received previously (in the message display subpanel of the main KMail window) to the composer window, so that the received image (in the message display subpanel) is used as an attachment (or in the HTML text) of the new message. Not even sure if it's actually possible, just thought it was the quickest way to do it. As soon as I try to drag the image out of the message display window, I get thrown back to KDE's login screen - no error messages, no crash report, as if the PC just finished booting. When I log back in, I think the PIM server (sorry, not sure) is crashed, because kmail opens but displays no messages or folders in its window. Performing a normal restart brings everything back to normal. Using KMail 4.13.2 on OpenSUSE 13.1, 64-bit version. Let me know how if can help with debugging somehow Reproducible: Always Steps to Reproduce: 1. In KMail, choose a message with an image in-line (not as an attachment) and have it displayed in the message subpanel. 2. Open composer to create a new mail message 3. Drag image from old message to the composer window (to use as an attachment) Actual Results: Crash all the way back to KDE login screen Expected Results: Image should become an attachment (or be inserted in-line) in the new message in composer.
backtrace please .
Can you please indicate how I can provide a backtrace? As I said, when the crash occurs I get thrown back to the session login screen - no "KMail has unexpectedly crashed" message or whatever. I think there is a way to run kmail and log everything that happens? Can you please guide me through it because I am not too familiar with debugging KDE apps?
I tried to run kmail using gdb (as indicated in the debugging tutorials of KDE), but the log I obtained was not really usefull (as I need to install a bucketload of debugging symbols). However, I did get the following errors at the console when trying to reproduce the bug: X Error: BadLength (poly request too large or internal Xlib length error) 16 Major opcode: 18 (X_ChangeProperty) Resource id: 0x17f X Error: BadLength (poly request too large or internal Xlib length error) 16 Major opcode: 44 (X_QueryKeymap) Resource id: 0x17f From what I gather, these errors cause X.org to fail, hence my being thrown back at the login prompt. If there is any interest in pursuing this I can install the necessary packages to obtain more information. If not, I will leave things be as I can live with it and without the extra debug packages (according to the log there must be at least 50 of them missing).
without backtrace I can't debug it. So yes debug package can be usefull
need info
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!