[plasmashell] [Bug 372967] New: plasma 5.8.4
https://bugs.kde.org/show_bug.cgi?id=372967 Bug ID: 372967 Summary: plasma 5.8.4 Product: plasmashell Version: 5.8.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: petrov.rainki...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-47-generic x86_64 Distribution: Ubuntu Xenial Xerus -- Information about the crash: - What I was doing when the application crashed: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f13f65fd8c0 (LWP 1302))] Thread 10 (Thread 0x7f1325b40700 (LWP 1531)): #0 0x7f13ecb4fac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f13ecb0b35e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13ecb0b4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13f183623b in QEventDispatcherGlib::processEvents (this=0x7f1328c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f13f17e0cea in QEventLoop::exec (this=this@entry=0x7f1325b3fcc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f13f1605fb4 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f133015b587 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f13f160ab98 in QThreadPrivate::start (arg=0x48f9590) at thread/qthread_unix.cpp:344 #8 0x7f13f06ee70a in start_thread (arg=0x7f1325b40700) at pthread_create.c:333 #9 0x7f13f0f1782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f133928b700 (LWP 1462)): #0 0x7f13ecb4fae4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f13ecb0adc9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13ecb0b340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13ecb0b4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f13f183623b in QEventDispatcherGlib::processEvents (this=0x7f132c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f13f17e0cea in QEventLoop::exec (this=this@entry=0x7f133928ad00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f13f1605fb4 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f13f160ab98 in QThreadPrivate::start (arg=0x2194050) at thread/qthread_unix.cpp:344 #8 0x7f13f06ee70a in start_thread (arg=0x7f133928b700) at pthread_create.c:333 #9 0x7f13f0f1782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f1339a8c700 (LWP 1461)): #0 0x7f13ecb0af3a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f13ecb0b400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13ecb0b4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13f183623b in QEventDispatcherGlib::processEvents (this=0x7f13340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f13f17e0cea in QEventLoop::exec (this=this@entry=0x7f1339a8bce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f13f1605fb4 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f1339edf985 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #7 0x7f13f160ab98 in QThreadPrivate::start (arg=0x45131f0) at thread/qthread_unix.cpp:344 #8 0x7f13f06ee70a in start_thread (arg=0x7f1339a8c700) at pthread_create.c:333 #9 0x7f13f0f1782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f1341ac7700 (LWP 1448)): #0 0x7f13ecb0ac2b in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f13ecb0b340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13ecb0b4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13f183623b in QEventDispatcherGlib::processEvents (this=0x7f133c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f13f17e0cea in QEventLoop::exec (this=this@entry=0x7f1341ac6c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f13f1605fb4 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f13f480aaa6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f13f160ab98 in QThreadPrivate::start (arg=0x267c4c0) at thread/qthread_unix.cpp:344 #8 0x7f13f06ee70a in start_thread (arg=0x7f1341ac7700) at pthread_create.c:333 #9 0x7f13f0f1782d in clone () at ../sysdeps/unix/sysv/
[systemsettings] [Bug 449811] New: Mouse acceleration reset after mouse unplug/plug operation
https://bugs.kde.org/show_bug.cgi?id=449811 Bug ID: 449811 Summary: Mouse acceleration reset after mouse unplug/plug operation Product: systemsettings Version: 5.24.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: fio2...@gmail.com Target Milestone: --- SUMMARY *** 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. Set mouse acceleration to flat profile and set pointer speed () to second position 2. Unplug and plug mouse OBSERVED RESULT Acceleration restored to top acceleration value (scroll not changed) EXPECTED RESULT Acceleration restored to previously set value SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0-r1 Qt Version: 5.15.2 ADDITIONAL INFORMATION Did not happen in 5.23.5 or any previous versions dmesg: [Feb 8 16:38] usb 1-5: USB disconnect, device number 71 [ +0.03] usb 1-5.1: USB disconnect, device number 72 [ +0.045449] usb 1-5.3: USB disconnect, device number 73 [Feb 8 16:48] usb 1-5: new high-speed USB device number 74 using xhci_hcd [ +0.145063] usb 1-5: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.44 [ +0.03] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ +0.01] usb 1-5: Product: 4-Port USB 2.0 Hub [ +0.02] usb 1-5: Manufacturer: Generic [ +0.045768] hub 1-5:1.0: USB hub found [ +0.001602] hub 1-5:1.0: 4 ports detected [ +0.350575] usb 1-5.1: new full-speed USB device number 75 using xhci_hcd [ +4.194090] usb 1-5.1: New USB device found, idVendor=1b1c, idProduct=1b13, bcdDevice= 3.08 [ +0.04] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.01] usb 1-5.1: Product: Corsair K70 RGB Gaming Keyboard [ +0.01] usb 1-5.1: Manufacturer: Corsair [ +0.01] usb 1-5.1: SerialNumber: 1400701EAE3D8C8153AA2CE2F5001941 [ +0.952370] input: Corsair Corsair K70 RGB Gaming Keyboard Keyboard as /devices/pci:00/:00:01.2/:20:00.0/:21:08.0/:2a:00.1/usb1/1-5/1-5.1/1-5.1:1.0/0003:1B1C:1B13.006D/input/input191 [ +0.052717] input: Corsair Corsair K70 RGB Gaming Keyboard as /devices/pci:00/:00:01.2/:20:00.0/:21:08.0/:2a:00.1/usb1/1-5/1-5.1/1-5.1:1.0/0003:1B1C:1B13.006D/input/input192 [ +0.44] input: Corsair Corsair K70 RGB Gaming Keyboard as /devices/pci:00/:00:01.2/:20:00.0/:21:08.0/:2a:00.1/usb1/1-5/1-5.1/1-5.1:1.0/0003:1B1C:1B13.006D/input/input193 [ +0.59] hid-generic 0003:1B1C:1B13.006D: input,hiddev1,hidraw1: USB HID v1.11 Keyboard [Corsair Corsair K70 RGB Gaming Keyboard ] on usb-:2a:00.1-5.1/input0 [ +0.626940] hid-generic 0003:1B1C:1B13.006E: hiddev2,hidraw2: USB HID v1.11 Device [Corsair Corsair K70 RGB Gaming Keyboard ] on usb-:2a:00.1-5.1/input1 [ +0.029148] elogind-daemon[3407]: Watching system buttons on /dev/input/event12 (Corsair Corsair K70 RGB Gaming Keyboard Keyboard) [ +0.048755] usb 1-5.3: new full-speed USB device number 76 using xhci_hcd [ +0.107821] usb 1-5.3: New USB device found, idVendor=2ea8, idProduct=2203, bcdDevice= 1.02 [ +0.03] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ +0.01] usb 1-5.3: Product: Xtrfy M4 [ +0.01] usb 1-5.3: Manufacturer: Wings Tech [ +0.105111] input: Wings Tech Xtrfy M4 as /devices/pci:00/:00:01.2/:20:00.0/:21:08.0/:2a:00.1/usb1/1-5/1-5.3/1-5.3:1.0/0003:2EA8:2203.006F/input/input194 [ +0.69] hid-generic 0003:2EA8:2203.006F: input,hidraw3: USB HID v1.11 Mouse [Wings Tech Xtrfy M4] on usb-:2a:00.1-5.3/input0 [ +0.004111] input: Wings Tech Xtrfy M4 Keyboard as /devices/pci:00/:00:01.2/:20:00.0/:21:08.0/:2a:00.1/usb1/1-5/1-5.3/1-5.3:1.1/0003:2EA8:2203.0070/input/input195 [ +0.052003] hid-generic 0003:2EA8:2203.0070: input,hiddev3,hidraw4: USB HID v1.11 Keyboard [Wings Tech Xtrfy M4] on usb-:2a:00.1-5.3/input1 [ +0.038171] elogind-daemon[3407]: Watching system buttons on /dev/input/event16 (Wings Tech Xtrfy M4 Keyboard) [Feb 8 17:23] usb 1-5: USB disconnect, device number 74 [ +0.03] usb 1-5.1: USB disconnect, device number 75 [ +0.058468] usb 1-5.3: USB disconnect, device number 76 [Feb 8 18:14] usb 1-5: new high-speed USB device number 77 using xhci_hcd [ +0.145271] usb 1-5: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.44 [ +0.03] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ +0.01] usb 1-5: Product: 4-Port USB 2.0 Hub [ +0.01] usb 1-5: Manufacturer: Generic [ +0.041518] hub 1-5:1.0: USB hub found [ +0.001601] hub
[systemsettings] [Bug 449811] Mouse acceleration reset after mouse unplug/plug operation
https://bugs.kde.org/show_bug.cgi?id=449811 --- Comment #4 from Ivan --- It is a wired mouse: Xtrfy M4 RGB It does not seem like it has internal memory. However, it has a switch to change pooling rate, a button to change DPI, and a button to change light color. In dmesg it is shown as a keyboard. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 467477] New: kup-purger doesn't work
https://bugs.kde.org/show_bug.cgi?id=467477 Bug ID: 467477 Summary: kup-purger doesn't work Classification: Applications Product: kup Version: 0.9.1 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: simon.pers...@mykolab.com Reporter: gulpega...@gmail.com Target Milestone: --- When I try to open "Prune or backups" or "Show files" from the notification bar, nothing happens. If I try to open kup-purger from the command line still nothing happens, kup-filedigger opens instead. Linux/KDE Plasma: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459452] New: Latte dock crashed when closing file manager
https://bugs.kde.org/show_bug.cgi?id=459452 Bug ID: 459452 Summary: Latte dock crashed when closing file manager Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: xenogea...@mail.ru Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.9-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Latte crashed while an internet browser was open. Froze the file manager The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7fc1228e4684 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /lib64/libQt5Quick.so.5 #5 0x7fc12291343f in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /lib64/libQt5Quick.so.5 #6 0x7fc1228fbc05 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /lib64/libQt5Quick.so.5 #7 0x7fc122900df5 in QSGBatchRenderer::Renderer::renderBatches() () at /lib64/libQt5Quick.so.5 #8 0x7fc122901866 in QSGBatchRenderer::Renderer::render() () at /lib64/libQt5Quick.so.5 #9 0x7fc1228e9104 in QSGRenderer::renderScene(QSGBindable const&) () at /lib64/libQt5Quick.so.5 #10 0x7fc122955a22 in QSGOpenGLLayer::grab() () at /lib64/libQt5Quick.so.5 #11 0x7fc122956025 in QSGOpenGLLayer::updateTexture() () at /lib64/libQt5Quick.so.5 #12 0x7fc122ac2236 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /lib64/libQt5Quick.so.5 #13 0x7fc1228e9874 in QSGRenderer::preprocess() () at /lib64/libQt5Quick.so.5 #14 0x7fc1228e90cb in QSGRenderer::renderScene(QSGBindable const&) () at /lib64/libQt5Quick.so.5 #15 0x7fc1228e95a3 in QSGRenderer::renderScene(unsigned int) () at /lib64/libQt5Quick.so.5 #16 0x7fc12294db05 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /lib64/libQt5Quick.so.5 #17 0x7fc1229bc3e9 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /lib64/libQt5Quick.so.5 #18 0x7fc12295bbc3 in QSGRenderThread::syncAndRender(QImage*) () at /lib64/libQt5Quick.so.5 #19 0x7fc12295c89b in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #20 0x7fc120859487 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #21 0x7fc1202e7e2d in start_thread () at /lib64/libc.so.6 #22 0x7fc12036d1b0 in clone3 () at /lib64/libc.so.6 Thread 6 (Thread 0x7fc0f59d8640 (LWP 2674) "KCupsConnection"): #1 0x7ffce3b819ac in clock_gettime () #2 0x7fc1203334ad in clock_gettime@GLIBC_2.2.5 () at /lib64/libc.so.6 #3 0x7fc11ee6d458 in g_main_context_check () at /lib64/libglib-2.0.so.0 #4 0x7fc11eec213a in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #5 0x7fc11ee6a940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #6 0x7fc120a69f66 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fc120a17c6a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x7fc12085818a in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x7fc0d6abf50b in KCupsConnection::run() () at /lib64/libkcupslib.so #10 0x7fc120859487 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #11 0x7fc1202e7e2d in start_thread () at /lib64/libc.so.6 #12 0x7fc12036d1b0 in clone3 () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc0f61d9640 (LWP 2650) "latte-dock"): #1 0x7fc11c587000 in usbmuxd_listen_inotify () at /lib64/libusbmuxd-2.0.so.6 #2 0x7fc11c587c8b in device_monitor () at /lib64/libusbmuxd-2.0.so.6 #3 0x7fc1202e7e2d in start_thread () at /lib64/libc.so.6 #4 0x7fc12036d1b0 in clone3 () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc10c87f640 (LWP 2495) "QQmlThread"): #1 0x7fc120a69e5e in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7fc11ee6d475 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fc11eec213a in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #4 0x7fc11ee6a940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fc120a69f66 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fc120a17c6a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fc12085818a in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fc1225b3c59 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7fc120859487 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fc12
[plasma-wayland-protocols] [Bug 470180] New: Screens go black after manual suspend
https://bugs.kde.org/show_bug.cgi?id=470180 Bug ID: 470180 Summary: Screens go black after manual suspend Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gome...@hotmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 159212 --> https://bugs.kde.org/attachment.cgi?id=159212&action=edit Screenshot - screen configuration SUMMARY When returning from "suspend", the monitors do not turn on or return with low resolution (640x480). Wayland does not allow changing resolution (attachment). I have two HP V206hz monitors that have a maximum resolution of 1600x900x60hz and are connected to a Radeon RX 6600 via cable (displayport > DVI). 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. Manually suspend the computer. 2. Wait for the suspension process to finish (front panel LED flashes). 3. Press any key to wake up the computer. OBSERVED RESULT Screens go black after manual suspend. One of the screens returns with 640x480 resolution after returning from automatic suspend (when automatic splint shutdown is not active). If the screen turns off automatically (before automatic suspend) the monitor video returns with adequate resolution (1600x900) EXPECTED RESULT Screens turn on after computer resumes from sleep. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OS: Kubuntu 22.04.2 LTS x86_64 Kernel: 5.19.0-42-generic KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION To view any content, you must force restart with the power button or remove and reinsert the monitor cable. I installed the amd package for the gpu but the problem remained. https://www.amd.com/en/support/graphics/amd-radeon-6000-series/amd-radeon-6600-series/amd-radeon-rx-6600 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470180] Screens go black after manual suspend
https://bugs.kde.org/show_bug.cgi?id=470180 --- Comment #2 from Ivan --- Thanks for the clarification. Those who found this page, here is the link of the issue on the Ubuntu bug hub. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2020709 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470180] Screens go black after manual suspend
https://bugs.kde.org/show_bug.cgi?id=470180 Ivan changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] New: When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 Bug ID: 470411 Summary: When turning on/restarting/suspending one of the screens acquires low resolution. Classification: Plasma Product: kwin Version: 5.27.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: gome...@hotmail.com Target Milestone: --- Created attachment 159319 --> https://bugs.kde.org/attachment.cgi?id=159319&action=edit low resolution on 2º screen SUMMARY When turning on/restarting/suspending one of the screens returns with low resolution (640x480). This behavior is random (it doesn't always happen). I have two HP V206hz monitors that have a maximum resolution of 1600x900x60hz and are connected to a Radeon RX 6600 via cable (displayport > DVI). Wayland does not allow resolution change (attachment). 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 Search bugs on google https://forums.gentoo.org/viewtopic-p-8782847.html?sid=709763f992be9f655473ea850ef7b784 The dmesg and xorg.0.log files https://pastebin.com/u/anarcochip/1/znbvbyhU STEPS TO REPRODUCE 1. Turn on, restart, or suspend your computer. 2. Power on, restart, or wait for the hibernation process to complete (front panel LED flashes). 3. Wait for the login screen or press any key to wake up the computer. OBSERVED RESULT One of the screens returns with a resolution of 640x480. In some moments the screen with low resolution changes the color scale to 16bits (I suppose), in these moments, sometimes the screen changes and goes black, but it remains "on" (the monitor's led does not blink). This behavior is random (doesn't always happen) and happens randomly on both monitors, sometimes the 1st sometimes the 2nd. Sometimes restarting resolves the issue. EXPECTED RESULT Both screens turn on with resolution set to 1600x900x60hz. SOFTWARE/OS VERSIONS Windows: This behavior is not observed on win11 system macOS: Not tested Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I noticed that kwin related issues were not answered on Ubuntu's bugs.launchpad.net so I decided to move to Kubuntu-23.04 which wants to support multi-screem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #1 from Ivan --- Created attachment 159335 --> https://bugs.kde.org/attachment.cgi?id=159335&action=edit K-23.04-Xorg.0.log-after-crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #2 from Ivan --- Created attachment 159336 --> https://bugs.kde.org/attachment.cgi?id=159336&action=edit K-23.04-dmesg-after-crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #3 from Ivan --- Created attachment 159337 --> https://bugs.kde.org/attachment.cgi?id=159337&action=edit printscreen-after-crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #4 from Ivan --- Hello everybody! Is it possible to set the resolution manually? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 469433] New: Baloo error
https://bugs.kde.org/show_bug.cgi?id=469433 Bug ID: 469433 Summary: Baloo error Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.105.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: i...@taipang.com Target Milestone: --- Application: baloo_file_extractor (5.105.0) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.1.27-1-lts x86_64 Windowing System: X11 Distribution: Artix Linux DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: help help help help help help help help help help help help help help help help The crash can be reproduced every time. -- Backtrace: Application: Служба извлечения информации для поиска в подсистеме Baloo (baloo_file_extractor), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #5 0x7fee21ca0983 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #6 0x7fee21c51ea8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7fee21c3b53d in __GI_abort () at abort.c:79 #8 0x7fee2276691e in ?? () from /usr/lib/liblmdb.so #9 0x7fee22764c2a in ?? () from /usr/lib/liblmdb.so #10 0x7fee22772646 in ?? () from /usr/lib/liblmdb.so #11 0x7fee22769d53 in ?? () from /usr/lib/liblmdb.so #12 0x7fee2276b987 in ?? () from /usr/lib/liblmdb.so #13 0x7fee2276fc8d in mdb_cursor_del () from /usr/lib/liblmdb.so #14 0x7fee22771485 in ?? () from /usr/lib/liblmdb.so #15 0x7fee23174df7 in Baloo::DocumentIdDB::del(unsigned long long) () from /usr/lib/libKF5BalooEngine.so.5 #16 0x7fee23183c5f in Baloo::Transaction::removePhaseOne(unsigned long long) () from /usr/lib/libKF5BalooEngine.so.5 #17 0x55d700ee80ee in ?? () #18 0x55d700ee91e6 in ?? () #19 0x7fee224c06a7 in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7fee224b0e76 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #21 0x7fee2248d268 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #22 0x7fee224d77d3 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #23 0x7fee224d7dca in ?? () from /usr/lib/libQt5Core.so.5 #24 0x7fee2110f53b in g_main_dispatch (context=0x7fee18000ee0) at ../glib/glib/gmain.c:3460 #25 g_main_context_dispatch (context=0x7fee18000ee0) at ../glib/glib/gmain.c:4200 #26 0x7fee2116c219 in g_main_context_iterate.constprop.0 (context=0x7fee18000ee0, block=1, dispatch=1, self=) at ../glib/glib/gmain.c:4276 #27 0x7fee2110e1a2 in g_main_context_iteration (context=0x7fee18000ee0, may_block=1) at ../glib/glib/gmain.c:4343 #28 0x7fee224d7f8c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #29 0x7fee224858ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #30 0x7fee22490539 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #31 0x55d700eded99 in ?? () #32 0x7fee21c3c790 in __libc_start_call_main (main=main@entry=0x55d700ede050, argc=argc@entry=1, argv=argv@entry=0x7ffe5e4c84a8) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x7fee21c3c84a in __libc_start_main_impl (main=0x55d700ede050, argc=1, argv=0x7ffe5e4c84a8, init=, fini=, rtld_fini=, stack_end=0x7ffe5e4c8498) at ../csu/libc-start.c:360 #34 0x55d700edeec5 in ?? () [Inferior 1 (process 3039) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469442] New: Discover crushed when i open `.flatpakref` file. I has installed flatpak backend for Discover.
https://bugs.kde.org/show_bug.cgi?id=469442 Bug ID: 469442 Summary: Discover crushed when i open `.flatpakref` file. I has installed flatpak backend for Discover. Classification: Applications Product: Discover Version: 5.24.7 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: ivan0pe...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- Created attachment 158748 --> https://bugs.kde.org/attachment.cgi?id=158748&action=edit File that i tried to load with Discover SUMMARY Discover crushed when I open `.flatpakref` file. I have installed flatpak backend for Discover. STEPS TO REPRODUCE 1. Try to open `org.chromium.Chromium.flatpakref` 2. In the Portal dialog choose `Discover` OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 1.15.3 ADDITIONAL INFORMATION I downloaded that file from `https://flathub.org/apps/org.chromium.Chromium` Backtrace: `A useful backtrace could not be generated` Signal: Segmentation fault (11) When I tried 10 minutes later, Discover crushed while installing from the same file. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469442] Discover crushed when I open `.flatpakref` file. I have installed flatpak backend for Discover.
https://bugs.kde.org/show_bug.cgi?id=469442 Ivan changed: What|Removed |Added Summary|Discover crushed when i |Discover crushed when I |open `.flatpakref` file. I |open `.flatpakref` file. I |has installed flatpak |have installed flatpak |backend for Discover. |backend for Discover. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469861] New: Audio is delayed after rendering and the delay is growing to the end of the video after using video speed 1000x in the video fragments
https://bugs.kde.org/show_bug.cgi?id=469861 Bug ID: 469861 Summary: Audio is delayed after rendering and the delay is growing to the end of the video after using video speed 1000x in the video fragments Classification: Applications Product: kdenlive Version: 23.04.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: platonov.ivan.vitaliev...@gmail.com Target Milestone: --- I made a video with several video fragments at 1000x speed. Rendered with MP4 - mainstream (H264/AAC). After rendering, I found that the audio started to delay from some point for a couple of seconds, and the beginning of the normal speed fragment cuts audio right after speeded fragment. STEPS TO REPRODUCE 1. Add video fragments 2. Make several of them in the middle with 1000x speed 3. Render to MP4 - mainstream (H264/AAC) SOFTWARE/OS VERSIONS Windows: 10 KDE Frameworks Version 5.105.0 Qt Version 5.15.9 (built against 5.15.9) MLT Version 7.15.0 Open source multimedia framework. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469861] Audio is delayed after rendering and the delay is growing to the end of the video after using video speed 1000x in the video fragments
https://bugs.kde.org/show_bug.cgi?id=469861 Ivan changed: What|Removed |Added CC||platonov.ivan.vitalievich@g ||mail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469861] Audio is delayed after rendering and the delay is growing to the end of the video after using video speed 1000x in the video fragments
https://bugs.kde.org/show_bug.cgi?id=469861 --- Comment #1 from Ivan --- Rendered the same project once again with previous versions 23.04.0a without any issues. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469861] Audio is delayed after rendering and the delay is growing to the end of the video after using video speed 1000x in the video fragments
https://bugs.kde.org/show_bug.cgi?id=469861 --- Comment #2 from Ivan --- Created attachment 159012 --> https://bugs.kde.org/attachment.cgi?id=159012&action=edit Tracks layout -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 ivan changed: What|Removed |Added Platform|openSUSE|Neon Version|6.0.1 |6.1.1 --- Comment #4 from ivan --- Unfortunately the issue is still there on Neon running the latest 6.1.1. Single display connected via DP to an AMD Radeon 5700XT. When unlocking after a display sleep and/or display power off/on, the desktop context manu and the trash widget menu keep appearing in a floating window in the center of the screen (if the desktop or the trash are not focused). Can't find any weird logs anywhere either... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 --- Comment #5 from ivan --- Created attachment 171247 --> https://bugs.kde.org/attachment.cgi?id=171247&action=edit Demonstration on Neon / Plasma 6.1.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 --- Comment #6 from ivan --- Updated to 6.1.2 and the trash widget contextual menu now appears in the right place even if it's not focused. Unfortunately the desktop one still appears in the center of the screen as a window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 ivan changed: What|Removed |Added Version|6.1.1 |6.1.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 489711] New: Offering to switch profile to the proxy quality
https://bugs.kde.org/show_bug.cgi?id=489711 Bug ID: 489711 Summary: Offering to switch profile to the proxy quality Classification: Applications Product: kdenlive Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: platonov.ivan.vitaliev...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Import 1080p video 2. Do not press any button until the proxy file is created 3. Cancel the offer to transcode the original file as it has a variable bitrate 4. See the popup offering to switch the project profile to the proxy resolution OBSERVED RESULT You might have SD video quality on the end if you are not paying attention to the messages. EXPECTED RESULT It was ok in previous versions. Not sure which one was that. SOFTWARE/OS VERSIONS Linux/KDE: Calculate Linux CLD KDE Frameworks Version 5.116.0 Qt Version 5.15.14 (built against 5.15.14) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 489711] Offering to switch profile to the proxy quality
https://bugs.kde.org/show_bug.cgi?id=489711 Ivan changed: What|Removed |Added CC||platonov.ivan.vitalievich@g ||mail.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 482296] New: The Energy Saver information screen is not stable. Constantly rattles with great frequency.
https://bugs.kde.org/show_bug.cgi?id=482296 Bug ID: 482296 Summary: The Energy Saver information screen is not stable. Constantly rattles with great frequency. Classification: Applications Product: kinfocenter Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ivan.chernousov.1...@gmail.com CC: sit...@kde.org Target Milestone: --- Created attachment 166348 --> https://bugs.kde.org/attachment.cgi?id=166348&action=edit Recording the Energy Saving-System Information window. SUMMARY: The Energy Saver information screen is not stable. Constantly rattles with great frequency. Video from the screen is attached. EXPECTED RESULT Fix bug. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 Ivan changed: What|Removed |Added CC||knezivan...@gmail.com --- Comment #6 from Ivan --- (In reply to Felix Ernst from comment #4) > I am not sure "being conservative" works here. When a completely blind > person sits in front of Konsole and tries to go to the menu F10 is their > only option AFAIK. Take that away and they can't even open the help menu > AFAIK. > > That's why I suggested that Konsole should only give up control of the F10 > key when the current terminal application uses it. This way the general > accessibility of Konsole doesn't have to suffer just because some terminal > applications also want to use F10. I disagree. F10 is often used in terminal applications. People are used to Ctrl+C and Ctrl+V and other common shortcuts, but that's not how it works in Konsole. The same should be applied to F10 and F11. I'm pretty much blind and when I'm using terminal apps like I'm used to instead of getting F10 action from my application I'm getting some useless menu. In my opinion this is serious bug -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #8 from Ivan --- > Of course any change we ever make (even if it is during a major transition > from Qt 5 to Qt 6 like this) will go against previously expected behaviour. > I don't really see though in what way what you are saying disagrees with me. > I do agree with your point that it is unwanted when a terminal program's F10 > shortcut doesn't work because it was stolen by Konsole. But this doesn't > change the argument I made which was: "When a completely blind person sits > in front of Konsole and tries to go to the menu F10 is their only option > AFAIK. Take that away and they can't even open the help menu AFAIK." I disagree that conservative approach is not a way to go. Terminal is very special application and it should be excluded from a "normal" behaviour. IMHO F10 to open a menu is a stupid idea in the first place in the same way as F11 for full screen etc. It may work well in a browser, but not in all applications. And when it comes to terminal - it's not just an app, it's a container for running apps. I don't think that terminal should be aware what keys are used in a terminal app and to decide when to open the menu or to pass. I have lots of scripts I created that utilise all F keys. And I always loved Konsole. Suddenly I'm in a big trouble. Not to mention popular apps like mc, htop etc. IMHO getting rid of this "feature" is a way to go, or at least adding something like shift+F10, like they did for copy-paste (ctrl+shift+c). I wouldn't be surprised if someone wants to use ctrl+c in terminal for copy :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481735] New: program crashes when trying to open an image with parameter luminosity in metadata
https://bugs.kde.org/show_bug.cgi?id=481735 Bug ID: 481735 Summary: program crashes when trying to open an image with parameter luminosity in metadata Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: korti...@gmail.com Target Milestone: --- Created attachment 166045 --> https://bugs.kde.org/attachment.cgi?id=166045&action=edit In the attached files is an example of an image with metadata that is causing the crash SUMMARY If the image metadata has a parameter with more characters after zero (3.909536743164), a crash occurs. And what is worse, after that it is impossible to load the program, and have to demolish the whole database, so that it does not contain this number. STEPS TO REPRODUCE 1. Download the attached file 2. Try to read it in the program or enter it into the database 3. See the result OBSERVED RESULT crash EXPECTED RESULT no crashes program and database didn't crash SOFTWARE/OS VERSIONS Windows: Windows 11 Pro 23H2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 ivan changed: What|Removed |Added Version|6.0.3 |6.0.4 --- Comment #12 from ivan --- Issue is still present in 6.0.4 on Kde Neon running on amd cpu and gpu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 ivan changed: What|Removed |Added CC||v...@ircsystem.net --- Comment #2 from ivan --- On Wayland the same thing happens when waking from sleep and/or locking and unlocking the session. Every right click on desktop or on panels when the focus is on another application will result in the contextual menu to appear in the middle of the screen. If the desktop or panel is focused via left click first, then the menu will appear correctly under the mouse, but the situation doesn't heal if the focus is given back to an application. A plasmashell restart fixes it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 ivan changed: What|Removed |Added CC||v...@ircsystem.net --- Comment #10 from ivan --- Using Neon and Wayland, can confirm this issue. I'm on a desktop workstation with a single DP monitor and as soon as it gets powered off by either power saving rules or a suspend action, when the monitor turns on, the right client context menu on desktop gets rendered in a window at the center of the screen if another window is in focus. A plasmashell restart fixes it temporarly, until the screen goes off again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453206] Paste option in context menu does not work in details mode
https://bugs.kde.org/show_bug.cgi?id=453206 Ivan changed: What|Removed |Added CC||gulpega...@gmail.com --- Comment #1 from Ivan --- I confirm the regression reported by Efe Ciftci. The problem started with the first release of KDE Gear 22.04 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453206] Paste option in context menu does not work in details mode
https://bugs.kde.org/show_bug.cgi?id=453206 --- Comment #2 from Ivan --- The problem has been solved by last plasma update provided by neon packages on 4 May 2022 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453206] Paste option in context menu does not work in details mode
https://bugs.kde.org/show_bug.cgi?id=453206 --- Comment #4 from Ivan --- I'm sorry you're right, I probably did a quick test and put the mouse pointer on a line relative to a folder which as you indicated offers the paste command. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
https://bugs.kde.org/show_bug.cgi?id=456348 Ivan changed: What|Removed |Added CC||idem...@protonmail.com --- Comment #2 from Ivan --- Same problem. Krusader don't browse archives after last update. Only infinity rotating circle. Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.13.0-51-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458349] New: Removable devices are remembered by /dev/sdX paths, which with a larger number of devices change.
https://bugs.kde.org/show_bug.cgi?id=458349 Bug ID: 458349 Summary: Removable devices are remembered by /dev/sdX paths, which with a larger number of devices change. Product: systemsettings Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_deviceautomounter Assignee: tdfisc...@kde.org Reporter: sadileki...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- This behavior is quite problematic when using multiple drives. For example I've got a single large drive I like to always have ready and mounted. I then get into trouble if my remembered drive was on /dev/sda, is absent, and then I try to insert a sdcard. The sdcard is quickly mounted as if it was the large drive (since it occupies the /dev/sda path), worse, sometimes I really prefer to mount them manually as read only when data recovering. I would wish for a way to maybe just simply have the option to supply a custom device path. Then I could just copy paste the /dev/disk/by-uuid/* corresponding path. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 442048] New: KolourPaint critical installation error
https://bugs.kde.org/show_bug.cgi?id=442048 Bug ID: 442048 Summary: KolourPaint critical installation error Product: kolourpaint Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: choiva...@gmail.com Target Milestone: --- Hi, I'm a loyal Linux user. I am writing to report a known bug after installing KolourPaint version 21.08.0 from the software center. After installing the desktop commands are canceled and when restarting the Pc it is left on a black screen with a check mark, having to reinstall the operating system completely. I hope I can contribute to solving the problem and at your disposal with any questions. My operating system is Solus Mate 4.3 64 bits kernel 5.13.1. Regards Ivan. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453206] Paste option in context menu does not work in details mode
https://bugs.kde.org/show_bug.cgi?id=453206 --- Comment #7 from Ivan --- The problem is no longer present in plasma 5.25.3, kde frameworks 5.69.0, Qt Version 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424138] Report with tags does not show split transactions with tags.
https://bugs.kde.org/show_bug.cgi?id=424138 Ivan changed: What|Removed |Added CC||ivanperezdoming...@gmail.co ||m --- Comment #4 from Ivan --- I can confirm that this bug is present in KMM 5.1.1 (build ba2c445) which, as of the time of this writing, I think is the last stable version. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424138] Report with tags does not show split transactions with tags.
https://bugs.kde.org/show_bug.cgi?id=424138 --- Comment #5 from Ivan --- In case it's useful, I'm seeing this bug on Ubuntu 18.04 with the stable AppImage. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 308267] Home view, net total of preferred accounts doesn't include stocks
https://bugs.kde.org/show_bug.cgi?id=308267 Ivan changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- CC||ivanperezdoming...@gmail.co ||m --- Comment #4 from Ivan --- I can add information to this bug, and I'd like to reopen. In KMM 5.1.1 AppImage on Linux (Ubuntu 18.04 64 bit), the preferred account section shows three columns: Account, Current Balance, and To Minimum Balance/Maximum Credit. The column Current Balance does not take brokerage/stock accounts into account when calculating the total. So, it shows the account balance correctly for each individual account, but then the total is not the sum of that column. I have tried this with two accounts only, a checking account and an investing account with shares. The sum matches the checking account and the investing account is ignored. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 308267] Home view, net total of preferred accounts doesn't include stocks
https://bugs.kde.org/show_bug.cgi?id=308267 --- Comment #6 from Ivan --- Created attachment 135495 --> https://bugs.kde.org/attachment.cgi?id=135495&action=edit Minimal example to reproduce bug 308267 Attached a minimal example to reproduce the bug. I can also provide a screenshot if that helps. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 308267] Home view, net total of preferred accounts doesn't include stocks
https://bugs.kde.org/show_bug.cgi?id=308267 --- Comment #7 from Ivan --- Created attachment 135496 --> https://bugs.kde.org/attachment.cgi?id=135496&action=edit Screenshot of bug Screenshot demonstrating bug -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 308267] Home view, net total of preferred accounts doesn't include stocks
https://bugs.kde.org/show_bug.cgi?id=308267 --- Comment #8 from Ivan --- I am attaching a KMM file with two accounts, which should help reproduce the bug, and a screenshot of what I see (and did not expect to see). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 308267] Home view, net total of preferred accounts doesn't include stocks
https://bugs.kde.org/show_bug.cgi?id=308267 --- Comment #9 from Ivan --- (Apologies for the multiple messages. I did not realize the bug tracker was sending messages for each attachment individually.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428468] icon-only task manager crash when move icons position on Wayland
https://bugs.kde.org/show_bug.cgi?id=428468 --- Comment #18 from Ivan --- I confirm that the problem is NOT present in Plasma 5.21 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438974] New: Image is distorted when the console window is resized
https://bugs.kde.org/show_bug.cgi?id=438974 Bug ID: 438974 Summary: Image is distorted when the console window is resized Product: konsole Version: 21.04.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: ivan.kryuko...@gmail.com Target Milestone: --- Created attachment 139559 --> https://bugs.kde.org/attachment.cgi?id=139559&action=edit This is screenshot bug SUMMARY STEPS TO REPRODUCE 1. Install Oh My Zsh with powerlevel10k theme. 2. When I resize the window, this effect is created. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: Plasma 5.22.1 KDE Frameworks Version: KDE 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420590] System Settings Crashin
https://bugs.kde.org/show_bug.cgi?id=420590 --- Comment #3 from Ivan --- When I click for second time in any section. Recent log: KDE Version: 5.19.5 Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.11-1-MANJARO x86_64 Windowing system: X11 Distribution: Manjaro Linux Application: Configurações do sistema (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f61af46b137 in ?? () from /usr/lib/libQt5Quick.so.5 #6 0x7f61af46b179 in ?? () from /usr/lib/libQt5Quick.so.5 #7 0x7f61af5ea103 in ?? () from /usr/lib/libQt5Quick.so.5 #8 0x7f61ab210c9a in ?? () from /usr/lib/libQt5XcbQpa.so.5 #9 0x7f61ab212f24 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #10 0x7f61ab214661 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #11 0x7f61af47d60d in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #12 0x7f61af47d6f5 in QQuickItemPrivate::setVisible(bool) () from /usr/lib/libQt5Quick.so.5 #13 0x7f61a00697d1 in ?? () from /usr/lib/qt/qml/org/kde/kirigami.2/libkirigamiplugin.so #14 0x7f61a006add8 in ?? () from /usr/lib/qt/qml/org/kde/kirigami.2/libkirigamiplugin.so #15 0x7f61af478185 in QQuickItemPrivate::itemChange(QQuickItem::ItemChange, QQuickItem::ItemChangeData const&) () from /usr/lib/libQt5Quick.so.5 #16 0x7f61af47f044 in QQuickItemPrivate::removeChild(QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #17 0x7f61af480ef3 in QQuickItem::setParentItem(QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #18 0x7f61af481497 in QQuickItem::~QQuickItem() () from /usr/lib/libQt5Quick.so.5 #19 0x7f618d704037 in ?? () from /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #20 0x7f61af7a47b9 in KDeclarative::QmlObject::~QmlObject() () from /usr/lib/libKF5Declarative.so.5 #21 0x7f61af7a504a in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /usr/lib/libKF5Declarative.so.5 #22 0x7f61b15b261c in KQuickAddons::ConfigModule::~ConfigModule() () from /usr/lib/libKF5QuickAddons.so.5 #23 0x7f6170e663b3 in ?? () from /usr/lib/qt/plugins/kcms/kcm_lookandfeel.so #24 0x7f61b16b2263 in ?? () from /usr/lib/libKF5KCMUtils.so.5 #25 0x7f61b16b2289 in ?? () from /usr/lib/libKF5KCMUtils.so.5 #26 0x7f61b16b86f4 in KCModuleProxy::deleteClient() () from /usr/lib/libKF5KCMUtils.so.5 #27 0x7f61b16b8869 in KCModuleProxy::~KCModuleProxy() () from /usr/lib/libKF5KCMUtils.so.5 #28 0x7f61b16b892a in KCModuleProxy::~KCModuleProxy() () from /usr/lib/libKF5KCMUtils.so.5 #29 0x7f61b004b36e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #30 0x7f61b0bab04e in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #31 0x7f61b0bab3ca in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #32 0x7f61b004b36e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #33 0x7f61b0bab04e in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #34 0x7f61b0d0882a in QScrollArea::~QScrollArea() () from /usr/lib/libQt5Widgets.so.5 #35 0x7f61b1400118 in KPageWidgetItem::~KPageWidgetItem() () from /usr/lib/libKF5WidgetsAddons.so.5 #36 0x7f61b1400216 in ?? () from /usr/lib/libKF5WidgetsAddons.so.5 #37 0x7f61b1401574 in KPageWidgetModel::removePage(KPageWidgetItem*) () from /usr/lib/libKF5WidgetsAddons.so.5 #38 0x7f61b16f19f6 in ModuleView::closeModules() () from /usr/lib/libsystemsettingsview.so.3 #39 0x7f61a319f29c in ?? () from /usr/lib/qt/plugins/systemsettings_sidebar_mode.so #40 0x7f61a319d82e in ?? () from /usr/lib/qt/plugins/systemsettings_sidebar_mode.so #41 0x7f61a319dd53 in ?? () from /usr/lib/qt/plugins/systemsettings_sidebar_mode.so #42 0x7f61af08c50e in ?? () from /usr/lib/libQt5Qml.so.5 #43 0x7f61aef7203f in ?? () from /usr/lib/libQt5Qml.so.5 #44 0x7f61aef73eda in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /usr/lib/libQt5Qml.so.5 #45 0x7f61aef8fad7 in ?? () from /usr/lib/libQt5Qml.so.5 #46 0x7f61aef9262f in ?? () from /usr/lib/libQt5Qml.so.5 #47 0x7f61aef2ccce in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #48 0x7f61af0a98d6 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #49 0x7f61af05b5cd in QQmlBoundSignalExpression::evaluate(void**) () from /usr/lib/libQt5Qml.so.5 #50 0x7f61af05bab1 in ?? () from /usr/lib/libQt5Qml.so.5 #51 0x7f61af08bfad in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #52 0x7f61b0057bb5 in ?? () from /usr/lib/libQt5Core.so.5 #53 0x7f61aa420712 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () from /usr/lib/libQt5QuickTemplates2.so.5 #54 0x7f61aa43dff1 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5QuickTemplates2.
[Breeze] [Bug 428092] New: Ugly color title background in system tray when Breeze Dark is selected
https://bugs.kde.org/show_bug.cgi?id=428092 Bug ID: 428092 Summary: Ugly color title background in system tray when Breeze Dark is selected Product: Breeze Version: 5.20.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: gulpega...@gmail.com Target Milestone: --- Created attachment 132627 --> https://bugs.kde.org/attachment.cgi?id=132627&action=edit Clipboard widget SUMMARY Ugly color title background in system tray when Breeze Dark is selected STEPS TO REPRODUCE 1. Select "Breeze Dark" in Plasma Stlyle. 2. Left click on every widget in system tray (es. clipboard, audio volume). OBSERVED RESULT The widget title and his background color are too similar. EXPECTED RESULT Better color contrast SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.20 (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428447] icon-only task manager application launch animation missing on Wayland
https://bugs.kde.org/show_bug.cgi?id=428447 Ivan changed: What|Removed |Added CC||gulpega...@gmail.com --- Comment #4 from Ivan --- I confirm the issue reported by Pawel. No animation on the task manager icons and no bouncing/blinking mouse pointer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428468] New: icon-only task manager crash when move icons position on Wayland
https://bugs.kde.org/show_bug.cgi?id=428468 Bug ID: 428468 Summary: icon-only task manager crash when move icons position on Wayland Product: plasmashell Version: 5.20.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: gulpega...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In the icon-only task manager, when I try to change a position of a pinned icon (dragging it by mouse), plasma crashes. It happens only in Wayland. STEPS TO REPRODUCE 1. Drag an icon on the icon-only task manager to change its position OBSERVED RESULT Plasma crashes and a new login is required EXPECTED RESULT Icon change its position in the task manager SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.20 (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428468] icon-only task manager crash when move icons position on Wayland
https://bugs.kde.org/show_bug.cgi?id=428468 --- Comment #2 from Ivan --- This is not possible (or maybe i'm not able) just because plasma crashes immediately and the user is logged out -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366454] Right Alt does not change ketboard language layout back to English, both Win keys do not change layout at all
https://bugs.kde.org/show_bug.cgi?id=366454 --- Comment #2 from Ivan --- (In reply to Justin Zobel from comment #1) > Thanks for the report Ivan. I've just tested this on systemsettings 5.20.2 > and I can't replicate the issue. I was able to toggle between layouts with > right alt. > > Can you please test and confirm if this issue is still occurring or if this > bug report can be marked as resolved. I'm setting status to "needsinfo" > pending your response, please change back to "reported" or "resolved" when > you respond, thanks. Thanks for testing. It's been a while since this bug disappeared, however long enough for me to forget about the report. I've tested key combinations on systemsettings 5.20.3 and everything was working too. Lets close this ticket and thank you again for your efforts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473058] New: Plasma shell crashes after deleting new default panel and closing "panel removed" notification
https://bugs.kde.org/show_bug.cgi?id=473058 Bug ID: 473058 Summary: Plasma shell crashes after deleting new default panel and closing "panel removed" notification Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ivan@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Created new default panel, edited the panel and then deleted it. After closing the "panel removed" notification by clicking on the red "x" button plasma suddenly crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1198 (plasmashell) UID: 1000 (ivan) GID: 1000 (ivan) Signal: 11 (SEGV) Timestamp: Sun 2023-08-06 00:33:46 CEST (1min 10s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ivan) Boot ID: 6949b5c50f2944ba9b898954483c1eec Machine ID: f9a42193b6db47fb9d2cae67364f9a30 Hostname: minipc Storage: /var/lib/systemd/coredump/core.plasmashell.1000.6949b5c50f2944ba9b898954483c1eec.1198.169127482600.zst (present) Size on Disk: 29.6M Message: Process 1198 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64 Stack trace of thread 1198: #0 0x7f3efdeaec24 pthread_sigmask (libc.so.6 + 0x8fc24) #1 0x7f3efde5b1b9 sigprocmask (libc.so.6 + 0x3c1b9) #2 0x7f3f004f1e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f3f004f2b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f3efde5afd0 n/a (libc.so.6 + 0x3bfd0) #5 0x7f3effa77c86 _ZN5QtQml18qmlExecuteDeferredEP7QObject (libQt5Qml.so.5 + 0x277c86) #6 0x7f3efff49059 _ZN16QQuickTransition7prepareER5QListI17QQuickStateActionERS0_I12QQmlPropertyEP23QQuickTransitionManagerP7QObject (libQt5Quick.so.5 + 0x149059) #7 0x7f3efff3e997 _ZN23QQuickTransitionManager10transitionERK5QListI17QQuickStateActionEP16QQuickTransitionP7QObject (libQt5Quick.so.5 + 0x13e997) #8 0x7f3efe2dd50d _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd50d) #9 0x7f3eff162fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #10 0x7f3efe2b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #11 0x7f3efe308c31 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x308c31) #12 0x7f3efe3094c4 n/a (libQt5Core.so.5 + 0x3094c4) #13 0x7f3efcd017a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #14 0x7f3efcd01a38 n/a (libglib-2.0.so.0 + 0x54a38) #15 0x7f3efcd01acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #16 0x7f3efe309836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #17 0x7f3efe2b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #18 0x7f3efe2b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #19 0x55c346242dc3 n/a (plasmashell + 0x26dc3) #20 0x7f3efde461ca n/a (libc.so.6 + 0x271ca) #21 0x7f3efde46285 __libc_start_main (libc.so.6 + 0x27285) #22 0x55c346242ee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 1215: #0 0x7f3efdea4da6 n/a (libc.so.6 + 0x85da6) #1 0x7f3efdea7468 pthread_cond_wait (libc.so.6 + 0x88468) #2 0x7f3efe0d1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b) #3 0x7f3eff72fc7f n/a (libQt5WaylandClient.so.5 + 0x7ac7f)
[plasmashell] [Bug 476633] Plasma crash due to lack of memory
https://bugs.kde.org/show_bug.cgi?id=476633 --- Comment #2 from Ivan --- Created attachment 163249 --> https://bugs.kde.org/attachment.cgi?id=163249&action=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 i was just browsing with firefox, then plasma suddenly crashed (maybe due to lack of ram, because around 2.6 gib and 712 mib of swap were used out of 4 gib and 1 gb) -- Backtrace (Reduced): #5 0x7f13e5966c86 in QtQml::qmlExecuteDeferred(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f13e5d76059 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f13e5d6b997 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f13e431650d in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f13e4fdffae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476633] Plasma crash due to lack of memory
https://bugs.kde.org/show_bug.cgi?id=476633 Ivan changed: What|Removed |Added CC||oivan2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #6 from Ivan --- (In reply to Nate Graham from comment #5) > Yes, in System Settings > Display and Monitor Hi thanks, I change the setting in System Settings > Display & Monitor but it changes randomly... so how can I change it so it doesn't change after any event (reboot, sleep etc)? Any config file that I can edit, any parameters, ...? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 111663] Add a "clean recent project list" button on the "open recent project" submenu
https://bugs.kde.org/show_bug.cgi?id=111663 Ivan changed: What|Removed |Added CC||ivantrufa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 461113] New: Recent list file can not update if it's full
https://bugs.kde.org/show_bug.cgi?id=461113 Bug ID: 461113 Summary: Recent list file can not update if it's full Classification: Applications Product: Haruna Version: 0.9.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: ivantrufa...@gmail.com Target Milestone: --- SUMMARY *** 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. Use haruna 0.9.3 2. Make some entries in recent files 3. Try to 'clear the list' 4.It's cleared but if you close and open haruna again, the previous entries are still there OBSERVED RESULT Recent files list doesn't update if it's full EXPECTED RESULT Recent files list updates normally and have recently played files there SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0-1 Qt Version: 5.15.6 ADDITIONAL INFORMATION Open last file and video position is working, I downgraded to 0.9.0 version of Haruna and recent files worked properly -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423994] New: Accounts from a template are not being created
https://bugs.kde.org/show_bug.cgi?id=423994 Bug ID: 423994 Summary: Accounts from a template are not being created Product: kmymoney Version: git (master) Platform: MS Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ivan.zinkev...@gmail.com Target Milestone: --- SUMMARY I'm trying to create a default set of accounts, but I don't see any when I created a new file. STEPS TO REPRODUCE 1. Start "New file" wizard 2. Select currency "USD" 3. Select "Base - detail" 4. Open "Accounts" tab 5. There are no accounts from the template. OBSERVED RESULT EXPECTED RESULT Accounts from the template are added. SOFTWARE/OS VERSIONS Windows: 10 (available in About System) KDE Plasma Version: The windows windowing system KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423994] Accounts from a template are not being created
https://bugs.kde.org/show_bug.cgi?id=423994 --- Comment #2 from Ivan --- (In reply to Jack from comment #1) > Templates don't create accounts, they create categories. The terminology > can easily be confusing, because internally, categories are a special type > of account. I don't believe there are any cases where initial setup creates > any accounts for you, other than the setup wizard asking if you want to set > up an initial checking account. Yes, thank you for the answer. The terminology is confusing. I just thought that this is something similar to GnuCash. I think, we can close the bug now :) -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 462110] New: Weird ghost key while creating shortcut
https://bugs.kde.org/show_bug.cgi?id=462110 Bug ID: 462110 Summary: Weird ghost key while creating shortcut Classification: Applications Product: Haruna Version: 0.9.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: ivantrufa...@gmail.com Target Milestone: --- SUMMARY While trying to make a custom shortcut, while pressing function key(for example Alt or Ctrl) "," symbol is displayed before it. After attempt of assigning own shortcut the shortcut won't work(nothing will happen instead of expected action) *** 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. Go to shortcuts 2. Try to edit any of them and put firstly the function key OBSERVED RESULT Before function key there is ",", which probably means that there is some ghost keystroke before the function key, and the shortcut won't work as intended. EXPECTED RESULT Expected not to see ghost keystroke and expected my shortcut to work SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.17.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491707] Mouse input globally lost after clicking on System tray gtk3-application icon
https://bugs.kde.org/show_bug.cgi?id=491707 --- Comment #8 from Ivan --- Graphic Platform: X11 KDE Plasma Version: 6.1.4 --> 6.1.5 KDE Frameworks Version: 6.4.0 --> 6.5.0 Qt Version: 6.7.2 Nothing has changed, the bug is still reproducible. Some another affected applications for tests: gajim, quodlibet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491707] Mouse input globally lost after clicking on System tray gtk3-application icon
https://bugs.kde.org/show_bug.cgi?id=491707 --- Comment #9 from Ivan --- > Notably, I cannot reproduce the issue with the systray icon for > Syncthing-gtk, which is also GTK3 Arch Linux. Syncthing-gtk behaves exactly the same as the others described above. Remark: I use X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491707] Mouse input globally lost after clicking on System tray gtk3-application icon
https://bugs.kde.org/show_bug.cgi?id=491707 --- Comment #3 from Ivan --- (In reply to Nate Graham from comment #1) > So if you remove the "Ignore global shortcuts: Force, Yes" window rule, it > stops happening? Yes, the bug only happens when this option is enabled. I use feature "Ignore global shortcuts" when working with virtual machines and with far2l file manager. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491707] Mouse input globally lost after clicking on System tray gtk3-application icon
https://bugs.kde.org/show_bug.cgi?id=491707 Ivan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491707] Mouse input globally lost after clicking on System tray gtk3-application icon
https://bugs.kde.org/show_bug.cgi?id=491707
Ivan changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #5 from Ivan ---
(In reply to David Edmundson from comment #4)
> Do you know if this is a recent regression at all?
It's hard to say, since I started using "Ignore global shortcuts" feature when
it turned out that after update Plasma to 6.1 the built-in far2l feature
("Exclusively handle hotkeys that include Ctrl/Alt/Win") does not work
anymore. I think I've been seeing this bug for about a month or a month and a
half at least.
(In reply to David Edmundson from comment #4)
> When in this state, does killing kglobalaccel6 release the mouse.
Do you mean "kglobalacceld"? There is no "kglobalaccel6" on my machines.
No, killing this process has no effect.
Exiting the application with the "Ignore global shortcuts" feature activated
also has no effect.
Everything returns to normal only after closing (or killing) the
gtk3-application which icon we clicked.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 491707] Mouse input globally lost after clicking on System tray gtk3-application icon
https://bugs.kde.org/show_bug.cgi?id=491707 --- Comment #6 from Ivan --- The problem is reproducible on neon-testing-20240820-0254.iso and neon-unstable-20240826-0356.iso. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450691] Draw Box-effect corrupted by changing Preview Resolution
https://bugs.kde.org/show_bug.cgi?id=450691 Ivan <3847b8fe-a74d-4b44-a19e-3b68d5e31...@anonaddy.me> changed: What|Removed |Added CC||3847b8fe-a74d-4b44-a19e-3b6 ||8d5e31...@anonaddy.me Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Ivan <3847b8fe-a74d-4b44-a19e-3b68d5e31...@anonaddy.me> --- I can confirm this, sadly still happening in 24.08.0, after creating dozens of boxes that highlight different text in different images... That is a horrible, infuriating bug, let me be honest. I usually edit my videos in a lower preview resolution so everything is snappier, and once I wanted to preview the whole thing... yeah, all boxes where messed up, not only in size, but position too. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 489276] Compressor/Expander: MLT: "[filter avfilter.compand ] Cannot set sink channel counts"
https://bugs.kde.org/show_bug.cgi?id=489276 Ivan <3847b8fe-a74d-4b44-a19e-3b68d5e31...@anonaddy.me> changed: What|Removed |Added CC||3847b8fe-a74d-4b44-a19e-3b6 ||8d5e31...@anonaddy.me Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Ivan <3847b8fe-a74d-4b44-a19e-3b68d5e31...@anonaddy.me> --- In my case I found out when trying to use `Deeser` or `Crystalizer` effects on an audio track; so it is not only happening with `Compressor/Expander`; seems to happen to many audio effects. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 --- Comment #7 from ivan --- (In reply to ivan from comment #6) > Updated to 6.1.2 and the trash widget contextual menu now appears in the > right place even if it's not focused. Unfortunately the desktop one still > appears in the center of the screen as a window. Errata. Trash widget context menu still appears as a window in the middle of the screen :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489530] Shut Down and Reboot from application launcher freezes on X11
https://bugs.kde.org/show_bug.cgi?id=489530 Ivan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME CC||van.a.griba...@gmail.com --- Comment #4 from Ivan --- Got same stuff after upgrading 6.0.5 -> 6.1.1. ArchLinux. X11. Killing plasma-fallback after trying to shutdown makes system to shutdown Removing ~/.config/ksmserverrc removed the issue After rebooting file was created again. before: [$Version] update_info=ksmserver_update_loginMode_value.upd:ksmserver_update_loginMode_value_default_enum [General] loginMode=restoreSavedSession [LegacySession: saved at previous logout] clientMachine1=localhost command1=org.gnome.Nautilus count=1 [Session: saved at previous logout] clientId1=10146d7e3df00017202576790009590005 count=1 discardCommand1[$e]=rm,$HOME/.config/session/yakuake_10146d7e3df00017202576790009590005_1720257737_185315 program1=/usr/bin/yakuake restartCommand1=/usr/bin/yakuake,-session,10146d7e3df00017202576790009590005_1720257737_185315 restartStyleHint1=0 userId1=ivan after: [General] loginMode=emptySession [LegacySession: saved at previous logout] count=0 [Session: saved at previous logout] clientId1=10146d7e3df00017202590790009480005 count=1 discardCommand1[$e]=rm,$HOME/.config/session/yakuake_10146d7e3df00017202590790009480005_1720259120_929681 program1=/usr/bin/yakuake restartCommand1=/usr/bin/yakuake,-session,10146d7e3df00017202590790009480005_1720259120_929681 restartStyleHint1=0 userId1=ivan -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 491014] New: Cant edit touchpad settings
https://bugs.kde.org/show_bug.cgi?id=491014 Bug ID: 491014 Summary: Cant edit touchpad settings Classification: Applications Product: systemsettings Version: 6.1.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: ivanmaisky...@gmail.com CC: natalie_clar...@yahoo.de Target Milestone: --- Created attachment 172116 --> https://bugs.kde.org/attachment.cgi?id=172116&action=edit Screenshot of bug SUMMARY I can't edit touchpadsettings STEPS TO REPRODUCE 1. Just open menu in settings "Мышь и сенсорная панель -> Сенсорная панель" OBSERVED RESULT Nothing EXPECTED RESULT Touchpad settings SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.2-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION sudo reboot doesn't help -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491707] New: Mouse input globally lost after clicking on System tray gtk3-application icon
https://bugs.kde.org/show_bug.cgi?id=491707 Bug ID: 491707 Summary: Mouse input globally lost after clicking on System tray gtk3-application icon Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: spne...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Install and run any gtk3 application which displays its icon in the System tray, e.g.: VeraCrypt, Psensor, Deluge-gtk. 2. Run any other application with "Ignore global shortcuts: Force, Yes" window settings. 3. Click on the gtk3 application icon in the System tray. OBSERVED RESULT The system stops responding to mouse input globally until the gtk3 application is closed. EXPECTED RESULT The gtk3 application acts according to the programmed action of clicking on the System tray icon, such as showing or hiding its window. SOFTWARE/OS VERSIONS Linux: Arch Linux Kernel: archlinux 6.10.4-arch2-1 #1 SMP PREEMPT_DYNAMIC Sun, 11 Aug 2024 16:19:06 + x86_64 GNU/Linux Graphic Platform: X11 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Tested also on OpenSuse Tumbleweed with the same result. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414920] Plasma crashes in RunnerModel::matchesChanged() while searching [no dupes from 5.19 or later]
https://bugs.kde.org/show_bug.cgi?id=414920 --- Comment #29 from Ivan --- I guess, people disabled this functionality or eve deleted kde and this is the reason why you don't have any reports anymore 😅 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399584] Support macOS Mojave (10.14)
https://bugs.kde.org/show_bug.cgi?id=399584 Ivan changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #13 from Ivan --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409017] New: It is not possible to view/remove the packages installed via the kde store.
https://bugs.kde.org/show_bug.cgi?id=409017 Bug ID: 409017 Summary: It is not possible to view/remove the packages installed via the kde store. Product: plasmashell Version: 5.16.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gulpega...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 121067 --> https://bugs.kde.org/attachment.cgi?id=121067&action=edit Windows decoration add-on installer, show plasma widgets (Redshift Control) and not the downloaded and installed windows decorations SUMMARY It is not possible to view the packages installed via the kde store. STEPS TO REPRODUCE 1. Open any configuration tool that includes download from the store by add-on installer (icons, window decorations, colors, ecc) 2. Download a new item (es. new icons pack) 3. Apply new item 4. Open the add-on installer again 5. Select "Installed" radio button OBSERVED RESULT No presence of previously installed packages EXPECTED RESULT List of installed packages and possibility to remove them SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION If a plasma widget is installed (es. Redshift control), it appears in every "Installed" sections of every add-on installer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409017] It is not possible to view/remove the packages installed via Add-On installer
https://bugs.kde.org/show_bug.cgi?id=409017 Ivan changed: What|Removed |Added Summary|It is not possible to |It is not possible to |view/remove the packages|view/remove the packages |installed via the kde |installed via Add-On |store. |installer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409017] It is not possible to view/remove the packages installed via Add-On installer
https://bugs.kde.org/show_bug.cgi?id=409017 Ivan changed: What|Removed |Added Version|5.16.1 |5.16.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409017] It is not possible to view/remove the packages installed via Add-On installer
https://bugs.kde.org/show_bug.cgi?id=409017 Ivan changed: What|Removed |Added Version|5.16.2 |5.16.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409017] It is not possible to view/remove the packages installed via Add-On installer
https://bugs.kde.org/show_bug.cgi?id=409017 Ivan changed: What|Removed |Added Version|5.16.3 |5.16.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404796] New: plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=404796 Bug ID: 404796 Summary: plasma crash right after login Product: plasmashell Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dron...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.1) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.19.25-1-lts x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: mostly nothing, except starting virt-viewer fresh ArchLinux x64 kde/plasma 5.15.1 The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3c87812680 (LWP 961))] Thread 23 (Thread 0x7f3c24ff9700 (LWP 1162)): #0 0x7f3c8bc6bafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3c8cb6cc4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3c8cb6cd3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3c723b1469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f3c723b5339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f3c723b052d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f3c723b3389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f3c8cb6696c in () at /usr/lib/libQt5Core.so.5 #8 0x7f3c8bc65a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f3c8c850b23 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f3c257fa700 (LWP 1161)): #0 0x7f3c8bc6bafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3c8cb6cc4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3c8cb6cd3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3c723b1469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f3c723b5339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f3c723b052d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f3c723b3389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f3c8cb6696c in () at /usr/lib/libQt5Core.so.5 #8 0x7f3c8bc65a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f3c8c850b23 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f3c25ffb700 (LWP 1160)): #0 0x7f3c8bc6bafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3c8cb6cc4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3c8cb6cd3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3c723b1469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f3c723b5339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f3c723b052d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f3c723b3389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f3c8cb6696c in () at /usr/lib/libQt5Core.so.5 #8 0x7f3c8bc65a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f3c8c850b23 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f3c267fc700 (LWP 1159)): #0 0x7f3c8bc6bafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3c8cb6cc4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3c8cb6cd3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3c723b1469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f3c723b5339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f3c723b052d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f3c723b5392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f3c723b052d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f3c723b3389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5Thread
[frameworks-kpackage] [Bug 409017] It is not possible to view/remove the packages installed via Add-On installer
https://bugs.kde.org/show_bug.cgi?id=409017 Ivan changed: What|Removed |Added Product|plasmashell |frameworks-kpackage Assignee|k...@davidedmundson.co.uk|notm...@gmail.com Version|5.16.4 |5.60.0 Component|general |default Target Milestone|1.0 |--- -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405904] New: The saved version of the image is not linked to the original.
https://bugs.kde.org/show_bug.cgi?id=405904 Bug ID: 405904 Summary: The saved version of the image is not linked to the original. Product: digikam Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Versioning Assignee: digikam-bugs-n...@kde.org Reporter: lebede...@gmail.com Target Milestone: --- Created attachment 119060 --> https://bugs.kde.org/attachment.cgi?id=119060&action=edit Photo image from GT-I9100 Samsung Galaxy S2 SUMMARY There is an image from samsung phone in the digiKam collection. STEPS TO REPRODUCE 1. Edit image 2. Save. OBSERVED RESULT SEE that the original file and version are just different images. But the version has a suffix _v1 and a history of changes in the verisoning panel. EXPECTED RESULT The original image and versions are linked in the right panel. SOFTWARE/OS VERSIONS Ubuntu 18.04LTS ADDITIONAL INFORMATION This effect is observed by me only on images received on the Samsung Galaxy phones (galaxy s2, s7egge, s8plus). The rest of the images work well. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405904] The saved version of the image is not linked to the original.
https://bugs.kde.org/show_bug.cgi?id=405904 --- Comment #2 from Ivan --- I tried version 5.9 and 6.0, all the same. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405904] The saved version of the image is not linked to the original.
https://bugs.kde.org/show_bug.cgi?id=405904 --- Comment #6 from Ivan --- I tried 6.1.0, all the same. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420590] System Settings Crashin
https://bugs.kde.org/show_bug.cgi?id=420590 Ivan changed: What|Removed |Added CC||ivanvalentimsan...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420590] System Settings Crashin
https://bugs.kde.org/show_bug.cgi?id=420590 --- Comment #1 from Ivan --- Created attachment 128058 --> https://bugs.kde.org/attachment.cgi?id=128058&action=edit New crash information added by DrKonqi systemsettings5 (5.18.4) using Qt 5.14.2 After clicking on any other section the application closes. -- Backtrace (Reduced): #6 0x in () #7 0x7f4114a68fa7 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f4114a69019 in () at /usr/lib/libQt5Quick.so.5 #9 0x7f4114c2fa93 in () at /usr/lib/libQt5Quick.so.5 #10 0x7f41105bf47a in () at /usr/lib/libQt5XcbQpa.so.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 409017] It is not possible to view/remove the packages installed via Add-On installer
https://bugs.kde.org/show_bug.cgi?id=409017 Ivan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Ivan --- Solved on Plasma version 5.17.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397063] New: kwin crashed
https://bugs.kde.org/show_bug.cgi?id=397063 Bug ID: 397063 Summary: kwin crashed Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ivan9...@protonmail.com Target Milestone: --- Application: kwin_x11 (5.13.4) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-29-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: kwin crashed when using display windows with active screen borders The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e5930b940 (LWP 1319))] Thread 6 (Thread 0x7f5e24a05700 (LWP 3457)): #0 0x7f5e58d18811 in __GI_ppoll (fds=0x7f5e180009e8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5e5607a5ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5e50a08195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f5e55eba727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5e51d6b6ba in start_thread (arg=0x7f5e24a05700) at pthread_create.c:333 #8 0x7f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f5e279d9700 (LWP 1449)): #0 0x7f5e58d18811 in __GI_ppoll (fds=0x7f5e2b38, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5e5607a5ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5e50a08195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f5e55eba727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5e51d6b6ba in start_thread (arg=0x7f5e279d9700) at pthread_create.c:333 #8 0x7f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f5e1700 (LWP 1386)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5e54fffde4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f5e54fffe29 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f5e51d6b6ba in start_thread (arg=0x7f5e1700) at pthread_create.c:333 #4 0x7f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f5e34f51700 (LWP 1375)): #0 0x7f5e58d18811 in __GI_ppoll (fds=0x7f5e2c000ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5e5607a5ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5e50a08195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f5e55eba727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5e51d6b6ba in start_thread (arg=0x7f5e34f51700) at pthread_create.c:333 #8 0x7f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f5e3767a700 (LWP 1359)): #0 0x7f5e58d18811 in __GI_ppoll (fds=0x7f5e3000bc68, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5e5607a5ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5e4f915f35 in ?? () fro
[Discover] [Bug 397246] New: Crash of discover
https://bugs.kde.org/show_bug.cgi?id=397246 Bug ID: 397246 Summary: Crash of discover Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: ivan9...@protonmail.com Target Milestone: --- Application: plasma-discover (5.13.4) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-29-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: I was typing the name of the program in the search engine, and it closed suddenly. I only had the firefox and dolphin browser The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f14b63258c0 (LWP 10868))] Thread 7 (Thread 0x7f146fdf3700 (LWP 10881)): #0 0x7f14ac21f407 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f14ac221cea in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14ac222330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14ac22249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f14b22030bb in QEventDispatcherGlib::processEvents (this=0x7f14680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f146fdf2cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f14b1fdf5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f14b1fea727 in QThreadPrivate::start (arg=0x16e7460) at thread/qthread_unix.cpp:367 #8 0x7f14ae0876ba in start_thread (arg=0x7f146fdf3700) at pthread_create.c:333 #9 0x7f14b15ee41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f147da15700 (LWP 10877)): #0 0x7f14ac266a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f14ac3d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14ac22249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14b22030bb in QEventDispatcherGlib::processEvents (this=0x7f1478c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f147da14cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f14b1fdf5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f14b1fea727 in QThreadPrivate::start (arg=0x2b98e80) at thread/qthread_unix.cpp:367 #7 0x7f14ae0876ba in start_thread (arg=0x7f147da15700) at pthread_create.c:333 #8 0x7f14b15ee41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f147f810700 (LWP 10874)): #0 0x7f14ac266a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f14ac221bf9 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14ac222307 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14ac22249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f14b22030bb in QEventDispatcherGlib::processEvents (this=0x7f14780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f147f80fcf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f14b1fdf5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f14b1fea727 in QThreadPrivate::start (arg=0x1a3fad0) at thread/qthread_unix.cpp:367 #8 0x7f14ae0876ba in start_thread (arg=0x7f147f810700) at pthread_create.c:333 #9 0x7f14b15ee41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f148948b700 (LWP 10873)): #0 0x7f14ac266a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f14ac221929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14acbb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14ac22249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f14b22030bb in QEventDispatcherGlib::processEvents (this=0x7f14840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f148948ac80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f14b1fdf5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f14b542cf86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f14b1fea727 in QThreadPrivate::start (arg=0x19a43f0) at thread/qthread_unix.cpp:367 #9 0x7f14ae0876ba in start_thread (arg=0x
[plasma-browser-integration] [Bug 392188] New: Mouseover on chrome tab sometimes crashes the KDE
https://bugs.kde.org/show_bug.cgi?id=392188 Bug ID: 392188 Summary: Mouseover on chrome tab sometimes crashes the KDE Product: plasma-browser-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: ivan.zalo...@gmail.com Target Milestone: --- I don't know the reason but, sometimes KDE Plasma will crash when I do a mouseover on chrome tab (in the tab menu at top). After crash I sometimes get SDDM screen and sometimes it stays black screens with few white squares on top left -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 392188] Mouseover on chrome tab sometimes crashes the KDE
https://bugs.kde.org/show_bug.cgi?id=392188 --- Comment #2 from Ivan --- Yes I am on wayland, I also have same installation on laptop but it never happened. Maybe it is because of a gpu driver? I have RX 580 gpu -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 392188] Mouseover on chrome tab sometimes crashes the KDE
https://bugs.kde.org/show_bug.cgi?id=392188 --- Comment #3 from Ivan --- Oops, I don't have this extension installed. I didn't know where to report -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 392188] Mouseover on chrome tab sometimes crashes the KDE
https://bugs.kde.org/show_bug.cgi?id=392188 --- Comment #4 from Ivan --- it happens on firefox too -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392188] Mouseover on chrome tab sometimes crashes the KDE
https://bugs.kde.org/show_bug.cgi?id=392188 --- Comment #5 from Ivan --- Here is error log from journalctl crash happened at aroudn 17:46 https://pastebin.com/Yp9Y1rAx -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376165] New: Splash screen doesn't hide when i click other window.
https://bugs.kde.org/show_bug.cgi?id=376165 Bug ID: 376165 Summary: Splash screen doesn't hide when i click other window. Product: krita Version: 3.1.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: ivanx...@openmailbox.org Target Milestone: --- Hi, i have this problem with Krita in Windows, when krita starts it shows a splash screen that covers a part of my monitor, so normally i click any other window to hide the splash screen so i can still use my computer when krita is loading, thats with other software like photoshop, in Krita the splash doesn't hide and i have to wait that Krita starts completely. Its really uncomfortable. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 402923] New: Segmentation fault in Kexi
https://bugs.kde.org/show_bug.cgi?id=402923 Bug ID: 402923 Summary: Segmentation fault in Kexi Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bogushiva...@gmail.com Target Milestone: --- Application: kexi-3 (3.1.0 ()) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.20.0-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Double click (to design form in my case) leads to segmentation fault in Kexi The crash can be reproduced every time. -- Backtrace: Application: Kexi (kexi-3), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5272a38400 (LWP 3210))] Thread 5 (Thread 0x7f524daf2700 (LWP 3217)): #0 0x7f52793d5afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f527949ecd1 in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:864 #2 0x7f527949ecd1 in std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7f5250b09f54 in () at /usr/lib/libQt5WebKit.so.5 #4 0x7f5250b0a079 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7f52794a5063 in std::execute_native_thread_routine(void*) (__p=0x55a8f4fd07a0) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:80 #6 0x7f52793cfa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f527b328b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f52635ae700 (LWP 3215)): #0 0x7f52793d5afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f52637ffc24 in () at /usr/lib/dri/i965_dri.so #2 0x7f52637ff948 in () at /usr/lib/dri/i965_dri.so #3 0x7f52793cfa9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f527b328b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f526b599700 (LWP 3213)): #0 0x7f527b3197a4 in read () at /usr/lib/libc.so.6 #1 0x7f5278952971 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f52789a30b0 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f52789a44e6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f52789a462e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f527b6c15c4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f527b66a58c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f527b4ae5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f5277ca8ba6 in () at /usr/lib/libQt5DBus.so.5 #9 0x7f527b4af9cc in () at /usr/lib/libQt5Core.so.5 #10 0x7f52793cfa9d in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f527b328b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f5271619700 (LWP 3212)): #0 0x7f527b31dc21 in poll () at /usr/lib/libc.so.6 #1 0x7f5274f19630 in () at /usr/lib/libxcb.so.1 #2 0x7f5274f1b2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f527260696b in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f527b4af9cc in () at /usr/lib/libQt5Core.so.5 #5 0x7f52793cfa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f527b328b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f5272a38400 (LWP 3210)): [KCrash Handler] #6 0x7f524ae8ff20 in () at /usr/lib/qt/plugins/kexi/3.1/forms/widgets/org.kexi-project.form.widgets.main.so #7 0x7f524b7ddd93 in KFormDesigner::InlineTextEditingCommand::execute() () at /usr/lib/libkformdesigner3.1.so.3.1 #8 0x7f524b7c1499 in KFormDesigner::Form::createInlineEditor(KFormDesigner::WidgetFactory::InlineEditorCreationArguments const&) () at /usr/lib/libkformdesigner3.1.so.3.1 #9 0x7f524b7a7829 in KFormDesigner::WidgetLibrary::startInlineEditing(QByteArray const&, QWidget*, KFormDesigner::Container*) () at /usr/lib/libkformdesigner3.1.so.3.1 #10 0x7f524b79f5eb in KFormDesigner::Container::eventFilter(QObject*, QEvent*) () at /usr/lib/libkformdesigner3.1.so.3.1 #11 0x7f527b66b60b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f527ba77e24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f527ba7f8b9 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f527b66b8f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f527ba7eb98 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, b
