Bug 189722

Summary:	klipper crashes after doing action
Product:	[Unmaintained] klipper	Reporter:	brian_whittaker
Component:	general	Assignee:	Esben Mose Hansen <kde>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	brian_whittaker, cfeck, dimsuz, vitaliyy
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Details of klipper crash inside

Description brian_whittaker 2009-04-15 16:15:52 UTC

Version:           kdebase-workspace-4.2.1-7.fc10.i386 (using KDE 4.2.1)
OS:                Linux
Installed from:    Fedora RPMs

I run Windows in a vmware virtual machine (using vmplayer 4.5.2 and VMware tools in the Windows client) on my FC10 box and I have 2 actions in klipper which run firefox (one for URLs and one for bug numbers).  Copying to clipboard in the vmware client is reflected to the X clipboard and klipper sees it.  If I copy a URL or bug number klipper offers the firefox actions and if I select the action it is done - but then sometimes, apparently randomly, klipper dies.

This may possibly be a duplicate of bug 188253 or bug 165726, but it seems to only happen when the clipboard entry comes from my vmplayer client, not from any other window.  It may well be a problem in the interaction of vmplayer with X (which is a bit unusual in other respects) leading to something happening which klipper would not usually expect.

Regrettably no backtrace - sometimes I get a popup reporting a segv but no usable backtrace (perhaps Fedora built without debug).

Comment 1 Vitaliy Yermolenko 2009-05-28 10:32:13 UTC

/usr/bin/klipper from kdebase-workspace-4.1.2-14.fc10.x86_64 crashes for me from time to time (it might be 2-5 times occasionally per working day) as well on Fedora 10 (2.6.27.5-117.fc10.x86_64) - see klipper.kcrash as attachment below.

Comment 2 Vitaliy Yermolenko 2009-05-28 10:33:16 UTC

Created attachment 34070 [details]
Details of klipper crash inside

Comment 3 brian_whittaker 2009-05-28 11:27:09 UTC

Since reporting this bug I have turned disabled actions (automatic actions that is) and switched to invoking actions as required with ctrl-alt-R, and klipper hasn't crashed since.  Looks like that's an effective workaround, and may also be a clue as to what the underlying problem is.

Comment 4 Christoph Feck 2013-09-12 21:42:13 UTC

This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)

Comment 5 Andrew Crouthamel 2018-09-24 02:17:36 UTC

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!

Comment 6 Andrew Crouthamel 2018-10-27 03:55:41 UTC

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!