Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Suddenly pop-up when copy files to USB flash. But copying continue successfully. Version-Release number of selected component: copyq-2.7.0-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/copyq eval -- ' if (monitoring()) {updateTitle()}' crash_function: QCoreApplication::notifyInternal2 executable: /usr/bin/copyq global_pid: 29819 kernel: 4.4.8-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1015 #1 QCoreApplication::sendEvent at kernel/qcoreapplication.h:227 #2 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1650 #3 QCoreApplication::sendPostedEvents at kernel/qcoreapplication.cpp:1508 #4 postEventSourceDispatch at kernel/qeventdispatcher_glib.cpp:270 #8 g_main_context_iteration at gmain.c:3901 #9 QEventDispatcherGlib::processEvents at kernel/qeventdispatcher_glib.cpp:417 #10 QEventLoop::exec at kernel/qeventloop.cpp:204 #11 QThread::exec at thread/qthread.cpp:503 #12 QThreadPrivate::start at thread/qthread_unix.cpp:340
Created attachment 1157494 [details] File: backtrace
Created attachment 1157495 [details] File: cgroup
Created attachment 1157496 [details] File: core_backtrace
Created attachment 1157497 [details] File: dso_list
Created attachment 1157498 [details] File: environ
Created attachment 1157499 [details] File: limits
Created attachment 1157500 [details] File: maps
Created attachment 1157501 [details] File: mountinfo
Created attachment 1157502 [details] File: namespaces
Created attachment 1157503 [details] File: open_fds
Created attachment 1157504 [details] File: proc_pid_status
Created attachment 1157505 [details] File: var_log_messages
Created attachment 1157506 [details] File: exploitable
Thanks for the report. Can you reproduce or is this a one time thing? How exactly were you copying files to the usb? Drag and drop? Ctrl C, Ctrl V? command line? Are you using Plasma, LXQt, Gnome, others? Once I receive this information I will try to reproduce. If reproducible will send upstream. Thanks!
Now I unable to reproduce it. May be it rare condition. Drag&Drop or Ctrl-C, Ctrl-V But now i tried both ways from different mounted FS. No CopyQ crashes. GNOME Shell 3.18.5 GNOME nautilus 3.18.5 CopyQ Clipboard Manager v2.7.0 I look at mountinfo It involve Live Win8.1 USB drive with two partitions. This time strugle to make it bootable and use different ways to built, so it hard to reproduce.
Similar problem has been detected: I copied a bitly link and it crashed. http://bit.ly/1UgZsog reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/copyq eval -- ' if (monitoring()) {updateFirst()}' crash_function: QCoreApplication::notifyInternal2 executable: /usr/bin/copyq global_pid: 11851 kernel: 4.5.6-200.fc23.x86_64 package: copyq-2.7.0-1.fc23 reason: copyq killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
FYI a commit has been pushed upstream to assuage this issue. https://github.com/hluk/CopyQ/issues/520
Saw that, will process shortly: rhbz=1347965
*** Bug 1351650 has been marked as a duplicate of this bug. ***
Any idea if following bug is a duplicate? https://bugzilla.redhat.com/show_bug.cgi?id=1359528
(In reply to Sudhir Khanger from comment #20) > Any idea if following bug is a duplicate? > > https://bugzilla.redhat.com/show_bug.cgi?id=1359528 Shouldn't be. The patch referenced in c#17 was tagged for 2.7.1.