[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #17 from Michael Brown --- (In reply to Oded Arbel from comment #16) > (In reply to Michael Brown from comment #15) > > The fix I made also includes wayland copy functionality. > > So that that there now is full wayland copy/paste clipboard support in > > Eclipse for the 2023-12 release pipeline. > > In copying functionality, I don't see a different behavior with the new > build - `wl-paste -l` shows an almost identical output with the old build, > except that the new build has the type "text/plain;charset=utf-8" listed > twice. I'm guessing that now both the SWT code advertises the > Wayland-mandated type, as well as the GTK Wayland compatibility workaround. > But it works fine, so 路 LGTM. Yeah I found it necessary to also do the paste fix in eclipse to cater for the ubuntu 22.04 distributions that will be stuck in gtk v3.24.33 that is without the gtk workaround. I'm running one of those: KDE Neon on my preferred workstation I guess you are running something with a newer gtk version ? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #15 from Michael Brown --- (In reply to Oded Arbel from comment #14) > (In reply to Michael Brown from comment #12) > > However I have yet no idea yet of what updating to the latest I-Build means > > Here's how I test: > > 1. I go to https://download.eclipse.org/eclipse/downloads/index.html > 2. Under "Integration Builds" there's a list of builds, ordered by date, > descending. I pick the first (latest) that doesn't have scary red > exclamation points. ATM it is I20231109-0710, and click that. > 3. In the page that opens, under "Platform Runtime Binary", I download the > "Linux (64 bit version)", and extract it to somewhere useful on my system - > I like to maintain a bunch of Eclipse installations under ~/.local/eclipse, > so I extract the tarball there, then rename the newly created "eclipse" > folder to "eclipse-", then update the eclipse menu entry in > ~/.local/share/applications/eclipse.desktop to point to the right one). > 4. Launch the "eclipse" binary from the new installation. It would probably > not have any useful tool other than a plain text editor - which should be > enough to test copy and paste with. > > I can now verify that I20231109-0710 supports Wayland paste - I can paste > into that installation, and if I close it and open the older installation, I > cannot paste into it. > > If you want to continue working with the integration test build - you can, > just go to "Help" -> "Install new software" and install all the tools you > need into the integration build. It should also automatically update to the > new 2023-12 release when it is published. Thanks for the info: > I can now verify that I20231109-0710 supports Wayland paste - I can paste > into that installation, and if I close it and open the older installation, I > cannot paste into it. The fix I made also includes wayland copy functionality. So that that there now is full wayland copy/paste clipboard support in Eclipse for the 2023-12 release pipeline. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #13 from Michael Brown --- BTW https://github.com/eclipse-platform/eclipse.platform.swt/commits/master -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #12 from Michael Brown --- @Oded Arbel I'm told repeatedly by the main developers of swt eclipse that: "your patches were merged yesterday and there has been a successful build since then thanks to . You can just update to latest I-Build or download" However I have yet no idea yet of what updating to the latest I-Build means ...:-) https://github.com/eclipse-platform/eclipse.platform.swt/issues/868#issuecomment-1804359275 Be sure to let me know when you can confirm that the wayland clipboard fixes have arrived in the pipeline. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #10 from Michael Brown --- @Oded Arbel Thank you for your info. However I'm curious as how the merge already can be in the pipeline as the original PR was build successfully but the PR then needed to be force pushed several times and then the final PR merge build ended up in a failed state ? https://ci.eclipse.org/releng/job/eclipse.platform.swt/job/PR-863/lastBuild/console -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #7 from Michael Brown --- btw the fix: https://github.com/eclipse-platform/eclipse.platform.swt/pull/863 works with gtk 3.24.33 so no need for the gtk update -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431100] [Wayland] Copy paste from konsole to eclipse and from eclipse to konsole does not work
https://bugs.kde.org/show_bug.cgi?id=431100 --- Comment #24 from Michael Brown --- This Issue is now reloved with https://github.com/eclipse-platform/eclipse.platform.swt/pull/863 works with gtk 3.24.33 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #6 from Michael Brown --- Well I thought of attempting to do it myself and with success: https://github.com/eclipse-platform/eclipse.platform.swt/pull/863 I also managed to provide a fix for copying from Eclipse to KDE/QT apps in wayland... I expect the fixes will be released in eclipse 2023-12 Then Eclipse clipboard functionality for text/plain:utf8 will be fully functional under wayland :-) This bug report can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #3 from Michael Brown --- I just want to correct that the latest gtk version is v3.24.38 not 3.24.37 as I have written. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #2 from Michael Brown --- This bug is also a possible unresolved duplicate: https://bugs.kde.org/show_bug.cgi?id=448511 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431100] [Wayland] Copy paste from konsole to eclipse and from eclipse to konsole does not work
https://bugs.kde.org/show_bug.cgi?id=431100 --- Comment #23 from Michael Brown --- Ok sorry bad my mistake I have opened the issue here instead: https://bugs.kde.org/show_bug.cgi?id=476522 But my issue also includes the konsole app -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #1 from Michael Brown --- I would like to add some info I wrote in my first effort to document this bug: --- There seems to be some confusion in regards to the current state of being able to copy/paste from eclipse (2023-09) to: kde apps like: konsole kate kwrite and qt-creator (probably more). First I would like to link to a recent issue created in the eclipse github where this issue is already confirmed and by one of the developers: https://github.com/eclipse-platform/eclipse.platform.swt/issues/851 The current gtk-version in kde-Neon is based on Ubuntu-LTS (2022.04) and is gtk v3.24.33 (the version before any wayland clipboard patches). So I have to strongly disagree with the statements: >> *not* present in > > KDE Neon or Ubuntu LTS. in the closed thread thread: https://bugs.kde.org/show_bug.cgi?id=431100 Today on a standard kde neon setup it is not possible to copy and paste between any of the above listed kde apps in a wayland session. However as stated in the github thread I have linked to the issue is partially solved in gtk versions 3.24.34 and 3.24.36. Manually recompiling and upgrading the gtk packages in kde-neon to the newest from mantic (23.10) gives version 3.24.37. This adds the functionality of being able to copy from eclipse to the above mentioned apps. However it is still not possible to paste from these apps into eclipse. I have also tested on fedore KDE 38 and kubuntu 23.10 which also run gtk 3.24.37. Same result you can now copy From eclipse, but not paste TO eclipse. the wayland clipboard illustrates what the problem is: With all the above mentioned apps selection and right clicking copy gives the result: text/plain text/plain;charset=utf-8 and no paste functionality in eclipse. running the command: wl-paste -n -t text/plain | wl-copy -t STRING shows the result: (base) mib@neon-ws:~$ wl-paste -n -t text/plain | wl-copy -t STRING (base) mib@neon-ws:~$ wl-paste -l STRING text/plain text/plain;charset=utf-8 TEXT STRING UTF8_STRING and makes it possible to paste in eclipse. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] New: Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 Bug ID: 476522 Summary: Cannot copy from KDE Applications to Eclipse in Wayland Classification: Applications Product: kate Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: produ...@holotronic.dk Target Milestone: --- Cannot copy from KDE Applications to Eclipse in Wayland *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. have eclipse open with a selected editable source file. 2. open either konsole or kate or kwrite and select some text and right click copy 3. try to paste into the source file in eclipse. OBSERVED RESULT There is no content pasted. EXPECTED RESULT Content gets pasted SOFTWARE/OS VERSIONS Windows: ? macOS: ? Linux/KDE Plasma: Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.2.0-35-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Bug acknowledged in eclipse github: https://github.com/eclipse-platform/eclipse.platform.swt/issues/851 possible duplicate of: https://bugs.kde.org/show_bug.cgi?id=431100 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431100] [Wayland] Copy paste from konsole to eclipse and from eclipse to konsole does not work
https://bugs.kde.org/show_bug.cgi?id=431100 Michael Brown changed: What|Removed |Added Resolution|FIXED |--- CC||produ...@holotronic.dk Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444542] Discover crashes in kde neon newly updated to 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444542 --- Comment #3 from Michael Brown --- (In reply to Nate Graham from comment #1) > Can you please attach a backtrace of the crash? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports I added it as an comment ok ? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444542] Discover crashes in kde neon newly updated to 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444542 --- Comment #2 from Michael Brown --- Application: Discover (plasma-discover), signal: Segmentation fault [New LWP 8808] [New LWP 8809] [New LWP 8810] [New LWP 8811] [New LWP 8812] [New LWP 8813] [New LWP 8814] [New LWP 8815] [New LWP 8816] [New LWP 8817] [New LWP 8818] [New LWP 8819] [New LWP 8820] [New LWP 8821] [New LWP 8822] [New LWP 8823] [New LWP 8824] [New LWP 8825] [New LWP 8826] [New LWP 8827] [New LWP 8828] [New LWP 8829] [New LWP 8830] [New LWP 8831] [New LWP 8832] [New LWP 8833] [New LWP 8834] [New LWP 8835] [New LWP 8836] [New LWP 8837] [New LWP 8838] [New LWP 8839] [New LWP 8840] [New LWP 8841] [New LWP 8842] [New LWP 8843] [New LWP 8844] [New LWP 8845] [New LWP 8846] [New LWP 8847] [New LWP 8848] [New LWP 8850] [New LWP 8852] [New LWP 8853] [New LWP 8854] [New LWP 8855] [New LWP 8856] [New LWP 8857] [New LWP 8858] [New LWP 8859] [New LWP 8860] [New LWP 8861] [New LWP 8862] [New LWP 8863] [New LWP 8864] [New LWP 8865] [New LWP 8866] [New LWP 8867] [New LWP 8868] [New LWP 8871] [New LWP 8873] [New LWP 8912] [New LWP 8913] [New LWP 8915] [New LWP 8921] [New LWP 8951] [New LWP 8954] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7a69d3aaff in __GI___poll (fds=0x7ffef6a199f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f7a64c66bc0 (LWP 8807))] Thread 68 (Thread 0x7f79617fa700 (LWP 8954)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f79617f9950, clockid=, expected=0, futex_word=0x55e4ef4b25c0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f79617f9950, clockid=, mutex=0x55e4ef4b2570, cond=0x55e4ef4b2598) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55e4ef4b2598, mutex=0x55e4ef4b2570, abstime=0x7f79617f9950) at pthread_cond_wait.c:656 #3 0x7f7a6a0cf558 in QWaitConditionPrivate::wait_relative (this=0x55e4ef4b2570, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x55e4ef4b2570) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x55e4efdb98f0, mutex=mutex@entry=0x55e4ef4dda28, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f7a6a0cca61 in QThreadPoolThread::run (this=0x55e4efdb98e0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f7a6a0c945c in QThreadPrivate::start (arg=0x55e4efdb98e0) at thread/qthread_unix.cpp:329 #8 0x7f7a69463609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f7a69d47293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 67 (Thread 0x7f7961ffb700 (LWP 8951)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f7961ffa950, clockid=, expected=0, futex_word=0x55e4efedf984) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f7961ffa950, clockid=, mutex=0x55e4efedf930, cond=0x55e4efedf958) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55e4efedf958, mutex=0x55e4efedf930, abstime=0x7f7961ffa950) at pthread_cond_wait.c:656 #3 0x7f7a6a0cf558 in QWaitConditionPrivate::wait_relative (this=0x55e4efedf930, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x55e4efedf930) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x55e4eff86920, mutex=mutex@entry=0x55e4ef4dda28, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f7a6a0cca61 in QThreadPoolThread::run (this=0x55e4eff86910) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f7a6a0c945c in QThreadPrivate::start (arg=0x55e4eff86910) at thread/qthread_unix.cpp:329 #8 0x7f7a69463609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f7a69d47293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 66 (Thread 0x7f790dffb700 (LWP 8921)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f7a68aa0746 in g_cond_wait_until () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a68a23581 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a68a23ba6 in g_async_queue_timeout_pop () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a68a7d419 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7a68a7cad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f7a69463609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f7a69d47293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 65 (Thread 0x7f790f7fe700 (LWP 8915)): #0 __GI___libc_read (nbytes=16, buf=0x7f790f7fd7d0, fd=139) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=139, buf=0x7f790f7fd7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f7a68a9bb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a68a52ebe in g_main_con
[Discover] [Bug 444542] New: Discover crashes in kde neon newly updated to 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444542 Bug ID: 444542 Summary: Discover crashes in kde neon newly updated to 5.23.2 Product: Discover Version: 5.23.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: produ...@holotronic.dk CC: aleix...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. run kde neon newly updated to 5.23.2 2. open discover in any way 3. wait OBSERVED RESULT Discover crashes EXPECTED RESULT Discover stays open and can show found updates status SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 360774] New: Konsole crashes on exit of last open konsole session.
https://bugs.kde.org/show_bug.cgi?id=360774
Bug ID: 360774
Summary: Konsole crashes on exit of last open konsole session.
Product: konsole
Version: 15.08.0
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: produ...@holotronic.dk
Application: konsole (15.08.0)
Qt Version: 5.5.1
Operating System: Linux 4.3.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)
-- Information about the crash:
- What I was doing when the application crashed:
THis time around I had had a remote (ssh) debug session, to setup a dhcpd serve
for debugging some armhf kernel 4.4.4-rt (ipv4 dhcp client not working)network
issues.
- Unusual behavior I noticed:
systemctl status shows this: (prior to reboot)
mib@debian9-ws:~$ systemctl status
● debian9-ws
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Sun 2016-03-20 11:12:09 CET; 2h 54min ago
CGroup: /
├─857 /sbin/cgmanager -m name=systemd
├─init.scope
│ └─1 /sbin/init quietc
├─system.slice
│ ├─avahi-daemon.service
│ │ ├─884 avahi-daemon: running [debian9-ws.local
│ │ └─893 avahi-daemon: chroot helpe
│ ├─dbus.service
│ │ └─888 /usr/bin/dbus-daemon --system --address=systemd: --nofork
--nopidfile --systemd-activation
│ ├─ModemManager.service
│ │ └─885 /usr/sbin/ModemManager
│ ├─cron.service
│ │ └─855 /usr/sbin/cron -f
│ ├─exim4.service
│ │ └─1228 /usr/sbin/exim4 -bd -q30m
│ ├─apache2.service
│ │ ├─1257 /usr/sbin/apache2 -k start
│ │ ├─4437 /usr/sbin/apache2 -k start
│ │ └─4438 /usr/sbin/apache2 -k start
│ ├─accounts-daemon.service
│ │ └─883 /usr/lib/accountsservice/accounts-daemon
│ ├─atd.service
│ │ └─880 /usr/sbin/atd -f
│ ├─systemd-journald.service
│ │ └─318 /lib/systemd/systemd-journald
│ ├─isc-dhcp-server.service
│ │ └─7165 /usr/sbin/dhcpd -4 -q -cf /etc/dhcp/dhcpd.conf enp9s0
│ ├─runit.service
│ │ ├─859 runsvdir -P /etc/service log:
│ │ ├─871 runsv git-daemon
│ │ ├─874 svlogd -tt /var/log/git-daemon
│ │ └─875 /usr/lib/git-core/git-daemon --verbose --reuseaddr
--base-path=/var/lib /var/lib/git
│ ├─udisks2.service
│ │ └─1514 /usr/lib/udisks2/udisksd --no-debug
│ ├─systemd-resolved.service
│ │ └─931 /lib/systemd/systemd-resolved
│ ├─upower.service
│ │ └─1438 /usr/lib/upower/upowerd
│ ├─systemd-timesyncd.service
│ │ └─778 /lib/systemd/systemd-timesyncd
│ ├─packagekit.service
│ │ └─4175 /usr/lib/packagekit/packagekitd
│ ├─ssh.service
│ │ └─924 /usr/sbin/sshd -D
│ ├─systemd-logind.service
│ │ └─882 /lib/systemd/systemd-logind
│ ├─systemd-networkd.service
│ │ └─7071 /lib/systemd/systemd-networkd
│ ├─system-getty.slice
│ │ └─getty@tty1.service
│ │ └─942 /sbin/agetty --noclear tty1 linux
│ ├─systemd-udevd.service
│ │ └─325 /lib/systemd/systemd-udevd
│ ├─polkitd.service
│ │ └─908 /usr/lib/policykit-1/polkitd --no-debug
│ ├─sddm.service
│ │ ├─ 916 /usr/bin/sddm
│ │ └─1070 /usr/lib/xorg/Xorg -nolisten tcp -auth
/var/run/sddm/{0038e1fc-aebe-4a15-a692-fcc52dba99d3} -
│ ├─rsyslog.service
│ │ └─858 /usr/sbin/rsyslogd -n
│ ├─bluetooth.service
│ │ └─1322 /usr/lib/bluetooth/bluetoothd
│ └─rtkit-daemon.service
│ └─1535 /usr/lib/rtkit/rtkit-daemon
└─user.slice
└─user-1000.slice
├─session-1.scope
│ ├─1335 /usr/lib/x86_64-linux-gnu/sddm/sddm-helper --socket
/tmp/sddm-auth7bc1269c-b9f8-4b7c-8996-0
│ ├─1341 /bin/sh /usr/bin/startkde
│ ├─1373 /usr/bin/dbus-launch --exit-with-session --sh-syntax
│ ├─1374 /usr/bin/dbus-daemon --fork --print-pid 5
--print-address 15 --session
│ ├─1380 /usr/bin/ssh-agent /usr/bin/startkde
│ ├─1414
[kdevelop] [Bug 358296] Kdevelop crashes when trying to scp a file by rightclick --> run external script
https://bugs.kde.org/show_bug.cgi?id=358296 --- Comment #3 from Michael Brown <produ...@holotronic.dk> --- Sorry for the delay.. I have not updated in the meanwhile. Yes I can confirm closing all editor tabs and rightl-click --> External_scripts--> triggers a crash immediately.. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358296] New: Kdevelop crashes when trying to scp a file by rightclick --> run external script
https://bugs.kde.org/show_bug.cgi?id=358296 Bug ID: 358296 Summary: Kdevelop crashes when trying to scp a file by rightclick --> run external script Product: kdevelop Version: 4.7.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: produ...@holotronic.dk Application: kdevelop (4.7.1) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I'm running mostly kde5 plasma desktop with sddm manager login. Had to install MATE desktop to get desktop to run. This Problem seemed to appear after having run Caja filemananger (Gnome app ?). Running Ghex has also given som major display problems and display flickering at shutdown / reboot. Before latest updates sddm display manager has high probability of crashing trying to combine a workflow with kdevelop, dolphin (rightclick compress), konqueror(rightclick kdiff3) and caja(right click Rabbitvcs)...hmmm... The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff1bcb3c940 (LWP 2110))] Thread 12 (Thread 0x7ff19f15f700 (LWP 2111)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ff1b6de7d2a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7ff1b6de7d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7ff1b56fb284 in start_thread (arg=0x7ff19f15f700) at pthread_create.c:333 #4 0x7ff1b922574d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7ff11da1f700 (LWP 2112)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7ff1b98d7394 in QWaitConditionPrivate::wait (time=1000, this=0x3b525c0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=this@entry=0x3b52e78, mutex=mutex@entry=0x3b52e80, time=time@entry=1000) at thread/qwaitcondition_unix.cpp:158 #3 0x7ff1b81e4f16 in KDevelop::DUChainPrivate::CleanupThread::run (this=0x3b52e60) at /build/kdevplatform-Y8NEm6/kdevplatform-1.7.1/language/duchain/duchain.cpp:283 #4 0x7ff1b98d6e4c in QThreadPrivate::start (arg=0x3b52e60) at thread/qthread_unix.cpp:352 #5 0x7ff1b56fb284 in start_thread (arg=0x7ff11da1f700) at pthread_create.c:333 #6 0x7ff1b922574d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7ff10f465700 (LWP 2113)): #0 0x7ff1b921887d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7ff1b30ad510 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff1b3069cb4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff1b306a170 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff1b306a2dc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff1b9a173a6 in QEventDispatcherGlib::processEvents (this=0x7ff1080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x7ff1b99e52e1 in QEventLoop::processEvents (this=this@entry=0x7ff10f464c90, flags=...) at kernel/qeventloop.cpp:149 #7 0x7ff1b99e5655 in QEventLoop::exec (this=this@entry=0x7ff10f464c90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7ff1b98d4559 in QThread::exec (this=) at thread/qthread.cpp:538 #9 0x7ff1b98d6e4c in QThreadPrivate::start (arg=0x43bd458) at thread/qthread_unix.cpp:352 #10 0x7ff1b56fb284 in start_thread (arg=0x7ff10f465700) at pthread_create.c:333 #11 0x7ff1b922574d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7ff1068f6700 (LWP 2120)): #0 0x7ff1b921c86d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7ff1b306a1cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff1b306a2dc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff1b9a173a6 in QEventDispatcherGlib::processEvents (this=0x7ff0fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x7ff1b99e52e1 in QEventLoop::processEvents (this=this@entry=0x7ff1068f5c90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7ff1b99e5655 in QEventLoop::exec (this=this@entry=0x7ff1068f5c90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7ff1b98d4559 in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7ff1b98d6e4c in QThreadPrivate::start (arg=0x4600c80) at thread/qthread_unix.cpp:352 #8 0x7ff1b56fb284 in start_thread (arg=0x7ff1068f6700) at pthread_create.c:333 #9
[kdevelop] [Bug 358296] Kdevelop crashes when trying to scp a file by rightclick --> run external script
https://bugs.kde.org/show_bug.cgi?id=358296 --- Comment #1 from Michael Brown <produ...@holotronic.dk> --- Well after my second reboot things worked normally again. As a side note I was logged in to the same external unit via minicom usb serial konsole terminal + ssh -X login in different tab. Logging in in same fashion does not retrigger the bug. However I'm sure some problems will reappear once I start caja for github access... or need ghex. -- You are receiving this mail because: You are watching all bug changes.
