Bug 324195

Summary: Klipper crashed on clicking its icon in systray, after unsuccessful copy & paste operation.
Product: [Unmaintained] klipper Reporter: Keren Sky <keren_sky>
Component: generalAssignee: Esben Mose Hansen <kde>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: drkonqi, triaged
Priority: NOR    
Version First Reported In: 0.9.7   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Keren Sky 2013-08-28 23:59:43 UTC 
Application: klipper (0.9.7)
KDE Platform Version: 4.10.5
Qt Version: 4.8.4
Operating System: Linux 3.10-9.dmz.1-liquorix-amd64 x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:
I wanted to copy and paste text over ssh, into kate.
I opened the wanted file in "ee" and clicked "Select All" in konsole's  edit menu.
I clicked copy in konsole's edit menu, switched to kate. 
I pasted. the pasted text was wrong; it was some other text i had copied & pasted correctly some time before.
I clicked the klipper icon in the systray, to see what was in its menu. Nothing happened immediatly.
Eventually the crash dialog appeared, w/ 3 stars filled.

-- Backtrace:
Application: Klipper (klipper), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fb876e08037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#6  0x00007fb876e0b698 in __GI_abort () at abort.c:90
#7  0x00007fb8744d0b85 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007fb8744cecf6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fb8744ced23 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fb8744cef96 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fb875598884 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007fb87559dcf6 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007fb8771c9d32 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_klipper.so
#14 0x00007fb876df2ea5 in __libc_start_main (main=0x4006d0, argc=1, ubp_av=0x7fffb4140928, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb4140918) at libc-start.c:260
#15 0x0000000000400701 in _start ()

Possible duplicates by query: bug 323830, bug 323692, bug 323586, bug 323544, bug 322782.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-08-30 06:04:28 UTC 
Unfortunately, the backtrace doesn't contain much helpful information due to uncaught exception (not your fault). 

If the crash is reproducible, please follow the guide[1] and try to run klipper under gdb to get a better backtrace.  Note you need to specified to '--nofork' argument. 

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 2 Andrew Crouthamel 2018-09-24 02:24:48 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 3 Andrew Crouthamel 2018-10-27 04:15:27 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!