[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 Marian changed: What|Removed |Added CC||daretm...@gmail.com --- Comment #62 from Marian --- I confirm this bug on: Desktop: KDE Plasma 5.25.5 Distro: KDE neon 20.04 5.25 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 488037] New: Can't use large numbers with delimiters to calculate
https://bugs.kde.org/show_bug.cgi?id=488037 Bug ID: 488037 Summary: Can't use large numbers with delimiters to calculate Classification: Applications Product: kcalc Version: 24.05.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: evan.te...@gmail.com Reporter: marian...@web.de Target Milestone: --- SUMMARY In 24.05.0 it's no longer possible for me to use a large pasted number with a delimiter (a dot that seperates group of thousands) and use it for a calculation. It produces an "input error". In previous versions KCalc was able to use these numbers. It doesn't even matter if the delimiter is a dot or a comma. STEPS TO REPRODUCE 1. Copy a large number that has dots in it that seperate group of thousands, like "2.560.275.623" 2. Paste it into KCalc 3. Divide by 1024 OBSERVED RESULT KCalc says "input error" EXPECTED RESULT It should be able to calculate "2560275623 / 1024" and give "2500269,16309" as a result, just like older versions of KCalc. SOFTWARE/OS VERSIONS Manjaro KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION It used to work in older versions just fine! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Marian changed: What|Removed |Added CC||marianpol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418352] Kate crashes when moving selections of text with Crtl+Shift+Arrow keys
https://bugs.kde.org/show_bug.cgi?id=418352 --- Comment #12 from Marian --- Created attachment 133203 --> https://bugs.kde.org/attachment.cgi?id=133203&action=edit New crash information added by DrKonqi kwrite (20.08.2) using Qt 5.15.0 - What I was doing when the application crashed: It was lua script (with lua settings). - cut out all text (CTRL-X) - insert text again (CTRL-V) I wantend to update all Tabs to lua style. -- Backtrace (Reduced): #4 QV4::Heap::Base::mark (markStack=0x7ffcae43c910, this=0x7eff101b57d0) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:190 #5 QV4::Managed::mark (markStack=0x7ffcae43c910, this=0x7eff101b57e0) at jsruntime/qv4managed_p.h:204 #6 QV4::MemoryManager::collectFromJSStack (this=, markStack=0x7ffcae43c910) at memory/qv4mm.cpp:1219 #7 0x7eff637e9450 in QV4::MemoryManager::collectRoots (this=0x55c745ee9f80, markStack=0x7ffcae43c910) at memory/qv4mm.cpp:876 #8 0x7eff637e96a1 in QV4::MemoryManager::mark (this=this@entry=0x55c745ee9f80) at memory/qv4mm.cpp:916 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418352] Kate crashes when moving selections of text with Crtl+Shift+Arrow keys
https://bugs.kde.org/show_bug.cgi?id=418352 Marian changed: What|Removed |Added CC||daretm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474840] Baloo File Extractor crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=474840 Marian changed: What|Removed |Added CC||daretm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474840] Baloo File Extractor crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=474840 --- Comment #1 from Marian --- Created attachment 163328 --> https://bugs.kde.org/attachment.cgi?id=163328&action=edit New crash information added by DrKonqi baloo_file_extractor (5.111.0) using Qt 5.15.11 Fail after login to system kde nein -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140268995529024) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140268995529024) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140268995529024, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f92ece42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f92ece287f3 in __GI_abort () at ./stdlib/abort.c:79 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 476488] New: SystemMonitor crash on switch to Application
https://bugs.kde.org/show_bug.cgi?id=476488 Bug ID: 476488 Summary: SystemMonitor crash on switch to Application Classification: Applications Product: plasma-systemmonitor Version: 5.27.9 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: marianpol...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.2.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: when click to application or any other tab - app crash The crash can be reproduced every time. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f8c4265600b in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f8c4265607d in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f8c427e7b56 in QAccessibleQuickItem::role() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f8c43f73f5a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f8c43f76cd8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7f8c43f78502 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7f8c4266464b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f8c4266bef6 in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f8c4266c441 in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f8c3825c889 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #15 0x7f8c41bd3dff in QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*, QQmlTableInstanceModel::DestructionMode) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #16 0x7f8c41bfbe69 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #17 0x7f8c41bd3800 in QQmlTableInstanceModel::drainReusableItemsPool(int) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #18 0x7f8c4275c9f0 in QQuickTableView::geometryChanged(QRectF const&, QRectF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f8c4266324f in QQuickItem::setSize(QSizeF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f8c41ce0565 in QQuickControlPrivate::resizeContent() () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #21 0x7f8c41cdcf80 in QQuickControlPrivate::setRightPadding(double, bool) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #22 0x7f8c496f5ef3 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f8c496f6db7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7f8c496f4914 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7f8c496d12c5 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7f8c47ef3ebb in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f8c496780db in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7f8c496f5ec8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7f8c496f6db7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7f8c496f4914 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #31 0x7f8c496d12c5 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #32 0x7f8c47ef3ebb in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f8c42664698 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #35 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #36 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #37 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #38 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #39 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #40 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #41 0x7f8c426645cb in QQuickItemPrivate::set
[Falkon] [Bug 400120] New: Feature Request: PDF View Support
https://bugs.kde.org/show_bug.cgi?id=400120 Bug ID: 400120 Summary: Feature Request: PDF View Support Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: mariana...@icloud.com Target Milestone: --- SUMMARY As of v3.0.1 Falkon does not support viewing PDF files directly in the browser. This is a pretty standard feature in almost any major navigator and important probably not only to me. STEPS TO REPRODUCE 1. Open Falkon 2. Open any URL which is in a .PDF format OBSERVED RESULT The target file of the URL in .PDF format will be prompted to download. DESIRED RESULT The target file of the URL in .PDF format will open in a new tab and rendered directly in the browser. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Arch 4.17.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Marian changed: What|Removed |Added CC||mariana...@icloud.com --- Comment #20 from Marian --- I will comment on this rather than open a new issue (what I was about to do). This should be moved to kwin/decorations. I am currently working on a fork of breeze and encountered the mechanics for this to be the following: People will usually triggere this when using transparencies with rounded corners. The desktop blur effect system plugin also highlights this but it's actually not it's fault. It just makes visible how your window is being drawn by Qt. Yes breeze does have support for blur (although not being accessible by any configuration, so you might debate about what is "support" I guess), because it does not at all depend on the decoration. It depends on the desktop effect plugin. Any Qt drawn opacity below 1.0 will get the blur from the plugin applied if it is activated. Breeze even has the compatibility boolean in its JSON file set to false. But this is not important to the issue. The QDecoration Class (which is archived by Qt since 4.8 and even back then was flagged for _embedded_ Linux) is used to paint the foreground chunk of the window decorations in breeze. It is the top level widget window. Qt is explicit about this: >From https://doc.qt.io/archives/qt-4.8/qwidget.html#autoFillBackground-prop [...] autoFillBackground : bool This property holds whether the widget background is filled automatically. If enabled, this property will cause Qt to fill the background of the widget before invoking the paint event. The color used is defined by the QPalette::Window color role from the widget's palette. In addition, Windows are always filled with QPalette::Window, unless the WA_OpaquePaintEvent or WA_NoSystemBackground attributes are set. This property cannot be turned off (i.e., set to false) if a widget's parent has a static gradient for its background. [...] Emphasis on the second last sentence. Further you will find that the first painting action for a non-special (shaded etc.) situation for breeze is this: painter->fillRect(rect(), Qt::transparent); So according to the Qt documentation our top level QRect from the Decoration Class is now drawn with a transparent QtGlobalColor. If you delete this line it will default to the same transparent color. You can change this to Qt::red or any other prominent color to clearly make this visible. After changing the color of the top level rectangle you can see that it is always drawn as simple QRect, be it with XRender or OpenGL. If you apply transparency in this situation you can clearly appreciate the underlying top level rectangle. The blur effect visually reinforces this construction by applying the blur to the transparent top level QRect. Now suddenly it is not just transparent anymore. I see two possible approaches to this which I'm not able to implement myself: 1. Make the top level widget a rounded rectangle. This seems to be difficult to me as Qt does not provide a direct approach for this. The QRect Class has no such implementation. 2. Find a way to not have the top level widget be filled. The mentioned article may be of help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Marian changed: What|Removed |Added Platform|Neon Packages |unspecified Component|aurorae |decorations -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 --- Comment #21 from Marian --- Here are some images for the described behavior. REFER TO PREVIOUS POST! https://imgur.com/r0gQuaX https://imgur.com/fGqZAql https://imgur.com/AJ0pHCS -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 405460] New: error while loading shared libraries: libdouble-conversion.so.3.0.0
https://bugs.kde.org/show_bug.cgi?id=405460 Bug ID: 405460 Summary: error while loading shared libraries: libdouble-conversion.so.3.0.0 Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mariana...@icloud.com Target Milestone: --- SUMMARY The upgrade from Plasma 5.15.2 to 5.15.3 made starting KDE impossible because of a wrong call to libdouble-conversion.so.3.0.0 which does not exist. Instead the existing symlink to the latest updated library is called /usr/lib/libdouble-conversion.so.3 without any zeros. Changing the name of the symlink to /usr/lib/libdouble-conversion.so.3.0.0 and adjusting the symlink /usr/lib/libdouble-conversion.so would remedy this temporarily. KDE should make the right call to the original symlink though. STEPS TO REPRODUCE 1. Update KDE Plasma desktop from 5.15.2 to 5.15.3 2. Reboot 3. Start X OBSERVED RESULT X will error out stating "Could not start kdeinit5. Check your installation." and return to the console. EXPECTED RESULT X should start normally without errors. SOFTWARE/OS VERSIONS Linux: 5.0.0-arch1-1-ARCH KDE Plasma Version: 5.15.3-1 KDE Frameworks Version: 5.56.1-1 Qt Version: 5.12.1-2 UPDATED PACKAGES: [2019-03-13 17:52] [ALPM] upgraded double-conversion (3.1.1-1 -> 3.1.4-1) [2019-03-13 17:52] [ALPM] upgraded bluedevil (1:5.15.2-1 -> 1:5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kdecoration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded breeze (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded breeze-gtk (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded protobuf (3.6.1.3-1 -> 3.7.0-1) [2019-03-13 17:52] [ALPM] upgraded clementine (1.3.1-20 -> 1.3.1-21) [2019-03-13 17:52] [ALPM] upgraded kirigami2 (5.56.0-2 -> 5.56.1-1) [2019-03-13 17:52] [ALPM] upgraded discover (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded drkonqi (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded gtk-update-icon-cache (3.24.5-1 -> 3.24.7-1) [2019-03-13 17:52] [ALPM] upgraded gtk3 (3.24.5-1 -> 3.24.7-1) [2019-03-13 17:52] [ALPM] upgraded kactivitymanagerd (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kde-cli-tools (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded libksysguard (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-framework (5.56.0-3 -> 5.56.1-1) [2019-03-13 17:52] [ALPM] upgraded milou (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwin (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-integration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-workspace (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kdeplasma-addons (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kgamma5 (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded khotkeys (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kinfocenter (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kmenuedit (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded knetattach (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded libkscreen (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kscreen (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded ksshaskpass (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded ksysguard (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwallet-pam (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwayland-integration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwrited (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded oxygen (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-browser-integration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded polkit-kde-agent (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded systemsettings (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-desktop (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-nm (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-pa (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-sdk (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-vault (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-workspace-wallpapers (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded powerdevil (5.15.2-2 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded python-psutil (5.5.0-1 -> 5.6.0-1) [2019-03-13 17:52] [ALPM] upgraded sddm-kcm (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded user-manager (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded xdg-desktop-portal-kde (5.15.2-1 -> 5.15.3-1) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 Marian changed: What|Removed |Added CC||marian.vi...@gmail.com --- Comment #123 from Marian --- Same Problem. Application: baloo_file_extractor (5.64.0) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.20.17-042017-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: Error message after login. The crash can be reproduced every time. -- Backtrace: Application: Extraktor súborov Baloo (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa242f5fc80 (LWP 2379))] Thread 3 (Thread 0x7fa22f5d1700 (LWP 2398)): #0 0x7fa23fa25bf9 in __GI___poll (fds=0x7fa22801a8e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa23c0ea5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa23c0ea6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa240378b9b in QEventDispatcherGlib::processEvents (this=0x7fa228000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa24031906a in QEventLoop::exec (this=this@entry=0x7fa22f5d0d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fa2401343aa in QThread::exec (this=this@entry=0x7fa241fa6d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #6 0x7fa241d2f0e5 in QDBusConnectionManager::run (this=0x7fa241fa6d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7fa240135b52 in QThreadPrivate::start (arg=0x7fa241fa6d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:360 #8 0x7fa23e28d6db in start_thread (arg=0x7fa22f5d1700) at pthread_create.c:463 #9 0x7fa23fa3288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fa234968700 (LWP 2391)): #0 0x7fa23fa25bf9 in __GI___poll (fds=0x7fa234967ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa23bc79747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa23bc7b36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa23774de10 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fa240135b52 in QThreadPrivate::start (arg=0x559965564f60) at thread/qthread_unix.cpp:360 #5 0x7fa23e28d6db in start_thread (arg=0x7fa234968700) at pthread_create.c:463 #6 0x7fa23fa3288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fa242f5fc80 (LWP 2379)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7fa23f951801 in __GI_abort () at abort.c:79 #8 0x7fa23ec3d932 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x7fa23ec327b5 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7fa23ec339bb in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7fa23ec33c29 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7fa23ec35854 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7fa23ec389ee in mdb_cursor_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7fa23ec3b72b in mdb_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7fa2423db60c in Baloo::PositionDB::put (this=this@entry=0x7fff97965340, term=..., list=...) at ./src/engine/positiondb.cpp:82 #16 0x7fa2423ed16e in Baloo::WriteTransaction::commit (this=0x5599655bf4e0) at ./src/engine/writetransaction.cpp:333 #17 0x7fa2423e3dd1 in Baloo::Transaction::commit (this=0x5599655c5eb0) at ./src/engine/transaction.cpp:304 #18 0x5599650132f4 in Baloo::App::processNextFile (this=0x7fff97965b10) at ./src/file/extractor/app.cpp:119 #19 0x7fa2403586b4 in QtPrivate::QSlotObjectBase::call (a=0x7fff979654c0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #20 QSingleShotTimer::timerEvent (this=0x5599655da200) at kernel/qtimer.cpp:318 #21 0x7fa24034c3eb in QObject::event (this=0x5599655da200, e=) at kernel/qobject.cpp:1282 #22 0x7fa24111feac in QApplicationPrivate::notify_helper (this=this@entry=0x55996553d120, receiver=receiver@entry=0x5599655da200, e=e@entry=0x7fff97965800) at kernel/qapplication.cpp:3703 #23 0x7fa2411274b0 in QApplication::notify (this=0x7fff97965ae0, receiver=0x5599655da200, e=0x7fff97965800) at kernel/qapplication.cpp:3449 #24 0x7fa24031af08 in QCoreApplication::notifyInternal2 (receiver=0x5599655da200, event=0x7fff97965800) at kernel/qcoreapplication.cpp:1095 #25 0x7fa240378009 in QTimerInfoList::activateTimers (this=0x55996559c930) at kernel/qtimerinfo_unix.cpp:643 #26 0x7fa2403787d1 in time
[plasmashell] [Bug 393388] Font vertical alignment problem in Global Menu
https://bugs.kde.org/show_bug.cgi?id=393388 Marian changed: What|Removed |Added CC||mariana...@icloud.com --- Comment #11 from Marian --- Can confirm this too on Arch 4.16.3 with Plasma 5.12.4 I tried to fiddle with the font settings and found that the global menu seems to take its font size only from the "General" font size setting. Maybe the font size adjustment calls depending on height got messed up? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher
https://bugs.kde.org/show_bug.cgi?id=351055 Marian changed: What|Removed |Added CC||mariana...@icloud.com --- Comment #27 from Marian --- (In reply to Martin Gräßlin from comment #26) > > I'd like to ask for some specific steps on fixing, for example, Firefox > > icons. > > This can only be fixed by Firefox by installing larger icons on their > windows. The version I use only installs a 48x48 icon and that's too small. > We would need icons of size 128x128 or better 512x512. That's something only > Firefox can do. So to get this fixed you would need to create a bug against > Firefox. Where do I have to search for those icons to confirm? I can reproduce this behaviour for so many applications. Take Vivaldi browser, it ships with a huge variety of dimensions of their icon in .png format in /opt/vivaldi AND in /usr/share/hicolor including sizes of 128 and 256 yet the large icon task switcher totally ignores them and any other icon provided in hicolor or the installed theme or pixmaps or /opt/vivaldi. Indeed xprop tells me that _NET_WM_ICON(CARDINAL) =Icon (32 x 32) Which to me looks like it's actually an issue with some programmed lines not so much icon structures, but that really doesn't help me at all. This is so annoying to even try to get a hint on where to start to report... Another test case for me is Nylas Mail. I played around with their icons in hicolor and pixmaps, replacing their original .png images with own ones. Now the task switcher shows the logo icon for X11 and there is no xprop for _NET_WM_ICON at all. And here is another completely weird example: Encryptr (password storage app). I can find a high resolution .png of their logo in /usr/share/pixmaps, no icons in /opt/encryptr, no icons in hicolor and apparently it has scalable svgs in the installed theme. Yet the large icon task switcher found a totally different high resolution icon for the application which I don't even remotely know where it could be stored since it's completely foreign to me and I have never seen it before nor can I find it in my installed themes...Here xprop tells me that: _NET_WM_ICON(CARDINAL) = Yet it shows a high resolution icon which is not the default X11 icon. Frustrating to debug... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher
https://bugs.kde.org/show_bug.cgi?id=351055 --- Comment #29 from Marian --- (In reply to Martin Gräßlin from comment #28) > > Where do I have to search for those icons to confirm? > > KWin takes the icon you can see in xprop. If there is only one in 32x32 that > one will be used. KWin does not use any installed icon as that is not how > it's supposed to be done for X11 window managers. > > For Qt/KDE applications we are able to use the installed icons thanks to an > extension. Maybe it could be possible to define a window rule for the > .desktop file of a window. Thanks for clarifying! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493379] New: plasma crash on idle several times in a row
https://bugs.kde.org/show_bug.cgi?id=493379 Bug ID: 493379 Summary: plasma crash on idle several times in a row Classification: Plasma Product: plasmashell Version: 6.1.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: marianpol...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.5) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.8.0-40-generic x86_64 Windowing System: Wayland Distribution: KDE neon 6.1 DrKonqi: 6.1.5 [CoredumpBackend] -- Information about the crash: fresh booted machine being idle for several minutes start to restart plasme due to crash The crash can be reproduced sometimes. -- Backtrace (Reduced): #7 0x7c2adda1cf2b in QtWaylandClient::QWaylandEglWindow::updateSurface(bool) (this=0x5a94f41d1cc0, create=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qpoint.h:129 #8 0x7c2ae473a1a9 in QWindow::resize(QSize const&) (this=0x7c2ac8033b10, newSize=...) at ./src/gui/kernel/qwindow.cpp:2027 #9 0x7c2ae6a3c9ee in PlasmaQuick::DialogPrivate::syncToMainItemSize() (this=0x5a94f198b470) at ./src/plasmaquick/dialog.cpp:664 #10 0x7c2ae4263afb in doActivate(QObject*, int, void**) (sender=0x5a94f4df3010, signal_index=26, argv=0x7ffcf091fe08) at ./src/corelib/kernel/qobject.cpp:4098 #11 0x7c2ae59e78bc in QQuickItem::geometryChange(QRectF const&, QRectF const&) (this=0x5a94f4df3010, newGeometry=, oldGeometry=...) at ./src/quick/items/qquickitem.cpp:3893 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493379] plasma crash on idle several times in a row
https://bugs.kde.org/show_bug.cgi?id=493379 --- Comment #1 from Marian --- Created attachment 173894 --> https://bugs.kde.org/attachment.cgi?id=173894&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470203] New: Custom keyboard shortcuts handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=470203 Bug ID: 470203 Summary: Custom keyboard shortcuts handled incorrectly Classification: Applications Product: kate Version: 23.04.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mciob...@gmail.com Target Milestone: --- SUMMARY I'm trying to customize the key shortcuts but I ran into an issue where a conflict is detected and supposedly solved when assigning the shortcut. When pressing the key combination, I get told to solve the ambiguity. STEPS TO REPRODUCE 1. Go to Settings / Configure Keyboard Shortcuts. 2. Find "Move to Top of View" and assign "Ctrl+PgUp" 3. Get prompted with "The "Ctrl+PgUp" shortcut is ambiguous with the following shortcut. Do you want to assign an empty shortcut to this action? Shortcut 'Alt+Left' for action 'Previous Tab'" 4. Choose "Reassign". 5. Close the settings dialog and back in the edit window press "Ctrl+PgUp". OBSERVED RESULT A message pops up, stating: "The key sequence 'Ctrl+PgUp' is ambiguous. Use 'Configure Keyboard Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered." EXPECTED RESULT The cursor should move to the top of the page. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: Probably latest, as I'm on opeSUSE Tumbleweed. Not sure how to find it, but I don't see it in "About System" KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Workaround: Open "Configure Keyboard Shortcuts", find "Previous Tab" and unassign the alternate or make some other change (once I saw a Ctrl+PgUp there, but mostly it's "Back"). Open /home/$USER/.local/share/kxmlgui5/kate/kateui.rc go to the end, find view_prev_tab, and remove Ctrl+PgUp from its entry. Before edit: After edit it's -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470203] Custom keyboard shortcuts handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=470203 --- Comment #2 from Marian Ciobanu --- (In reply to Paul Worrall from comment #1) > This does not seem to be an issue with Kate but with how plasma handles > shortcuts in general (see bug #434851). Thanks, but I'm not sure what the next step should be. Should I reassign this to another product? Do you have any suggestion regarding which one, though? There are so many ... (Looking at https://bugs.kde.org/show_bug.cgi?id=434851, it seems that not much is likely to change if left as is.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450057] Unable to delete bookmark folders
https://bugs.kde.org/show_bug.cgi?id=450057 Marian Ciobanu changed: What|Removed |Added CC||mciob...@gmail.com --- Comment #4 from Marian Ciobanu --- I couldn't find "Bookmarks > Edit Bookmarks" either, but there is a workaround of sorts: Edit the text file where these are stored, namely /home/$USER/.local/share/dolphin/bookmarks.xml -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 --- Comment #5 from Marian Kyral --- I can confirm it is still broken in 6.0.3 and the unfortunately applying revert patch does not work anymore. So I have to call kwin_wayland --replace, but this kills running application including plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 443690] kioslave5 crashed after click to icon in tasks list
https://bugs.kde.org/show_bug.cgi?id=443690 --- Comment #3 from Marian Kyral --- I'm using less opened windows recently, so they are not grouped and panel is not crashing for now. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451790] System Monitor Sensor breaks WeatherWidget-2 from the KDE store on KDE Framework 5.92
https://bugs.kde.org/show_bug.cgi?id=451790 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 443690] kioslave5 crashed after click to icon in tasks list
https://bugs.kde.org/show_bug.cgi?id=443690
Marian Kyral changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #5 from Marian Kyral ---
Today Plasmashell crashed again. I was clicking apps icons in taskbar to switch
between application. I missclicked so I clicked again on correct application.
But an incomplete blank tooltip window was shown and plasmashell crashed. I'm
not sure whether this is the same bug or rather a new one. BT seems to be
different.
Maybe it could be some timing issue - I click to switch to application and
tooltip window can't be properly destroyed at this time.
Gentoo, Xorg-21.1.3, kde-plasma/plasma-desktop-5.25.3, Qt-5.15.5
=== New BT ===
Application: Plasma (plasmashell), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 0x7fcfe529216c in __pthread_kill_implementation () from
/lib64/libc.so.6
#7 0x7fcfe5246722 in raise () from /lib64/libc.so.6
#8 0x7fcfe5231469 in abort () from /lib64/libc.so.6
#9 0x7fcfe5891933 in qt_message_fatal (message=...,
context=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:1914
#10 QMessageLogger::fatal (this=this@entry=0x7fcf4fffd9c8,
msg=msg@entry=0x7fcfe5b7bb08 "ASSERT failure in %s: \"%s\", file %s, line %d")
at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:893
#11 0x7fcfe5890a6a in qt_assert_x (where=where@entry=0x7fcfe7858108
"QVector::at", what=what@entry=0x7fcfe78580de "index out of range",
file=file@entry=0x7fcfe7858068 "/usr/include/qt5/QtCore/qvector.h",
line=line@entry=449) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qglobal.cpp:3366
#12 0x7fcfe752ff50 in QVector::at (i=1, this=0x7fcf44116f90) at
/usr/include/qt5/QtCore/qvector.h:449
#13 0x7fcfe753005b in QVector::at (i=1, this=0x7fcf44116f90) at
/usr/include/qt5/QtGui/qopenglfunctions.h:693
#14 QQuickCustomMaterialShader::updateState (this=, state=...,
newEffect=, oldEffect=) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/items/qquickopenglshadereffectnode.cpp:149
#15 0x7fcfe75c9dd2 in QSGBatchRenderer::Renderer::renderUnmergedBatch
(this=0x7fcf44258b20, batch=) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3193
#16 0x7fcfe75ce9c7 in QSGBatchRenderer::Renderer::renderBatches
(this=0x7fcf44258b20) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4050
#17 0x7fcfe75cf2fb in QSGBatchRenderer::Renderer::render (this=) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4343
#18 0x7fcfe75b5ece in QSGRenderer::renderScene (bindable=...,
this=0x7fcf44258b20) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/coreapi/qsgrenderer.cpp:264
#19 QSGRenderer::renderScene (this=0x7fcf44258b20, bindable=...) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220
#20 0x7fcfe7628d57 in QSGOpenGLLayer::grab (this=0x7fcf44050dc0) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/qsgopengllayer.cpp:447
#21 0x7fcfe762943d in QSGOpenGLLayer::updateTexture (this=0x7fcf44050dc0)
at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/qsgopengllayer.cpp:187
#22 0x7fcfe77a0635 in QQuickOpenGLShaderEffectMaterial::updateTextures
(this=0x7fcf4423e1f0) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/items/qquickopenglshadereffectnode.cpp:474
#23 0x7fcfe75b66a5 in QSGRenderer::preprocess (this=0x7fcf44006500) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/coreapi/qsgrenderer.cpp:337
#24 0x7fcfe75b5e94 in QSGRenderer::renderScene (bindable=warning: RTTI
symbol not found for class 'QSGRenderer::renderScene(unsigned int)::B'
..., this=0x7fcf44006500) at
/var/tmp/portage/dev-qt/qtdeclarative-5.15.5/work/qtdeclarative-everywhere-src-5.15.5/src/quick/scenegraph/coreapi/qsgrenderer.cpp:238
#25 QSGRenderer::renderScene (this=0x7fcf44006500, bindable=warning: RTTI
symbol not found for class 'QSGRenderer::renderScene(unsigned int)::B'
...) at
/var/tmp/portage/dev-qt/qt
[kio-extras] [Bug 407431] STL thumbnailer
https://bugs.kde.org/show_bug.cgi?id=407431 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 443690] New: kioslave5 crashed after click to icon in tasks list
https://bugs.kde.org/show_bug.cgi?id=443690 Bug ID: 443690 Summary: kioslave5 crashed after click to icon in tasks list Product: frameworks-kio Version: 5.87.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: mky...@email.cz CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Plasma panel crashed after click on application icon in Tasks list. Application: kioslave5 (kioslave5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f3b3b039780 (LWP 11500))] [KCrash Handler] #6 0x7f3b3f3a6a64 in KIO::SlaveBase::setKillFlag (this=0x7fffc18b19b0) at /var/tmp/portage/kde-frameworks/kio-5.87.0/work/kio-5.87.0/src/core/slavebase.cpp:1530 #7 0x7f3b3f3a6a8f in genericsig_handler (sigNumber=) at /var/tmp/portage/kde-frameworks/kio-5.87.0/work/kio-5.87.0/src/core/slavebase.cpp:245 #8 #9 0x7f3b3e3b91e0 in __futex_abstimed_wait_common64 () from /lib64/libpthread.so.0 #10 0x7f3b3e3b2d20 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #11 0x7f3b3ee5659b in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55fa94e61ba0) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/thread/qwaitcondition_unix.cpp:146 #12 QWaitCondition::wait (this=this@entry=0x55fa94e62878, mutex=0x55fa94e62858, deadline=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/thread/qwaitcondition_unix.cpp:225 #13 0x7f3b3ee4f517 in QThread::wait (this=, deadline=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/thread/qthread_unix.cpp:755 #14 0x7f3b3e3de253 in QDBusConnectionManager::~QDBusConnectionManager (this=0x7f3b3e466dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>, __in_chrg=) at ../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qdeadlinetimer.h:68 #15 0x7f3b3e3de2e9 in (anonymous namespace)::Q_QGS__q_manager::Holder::~Holder (this=, __in_chrg=) at /var/tmp/portage/dev-qt/qtdbus-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/dbus/qdbusconnection.cpp:77 #16 0x7f3b3e9d8ed3 in __run_exit_handlers () from /lib64/libc.so.6 #17 0x7f3b3e9d907a in exit () from /lib64/libc.so.6 #18 0x7f3b3e9c1804 in __libc_start_main () from /lib64/libc.so.6 #19 0x55fa944eb4da in _start () [Inferior 1 (process 11500) detached] STEPS TO REPRODUCE Happens randomly OBSERVED RESULT Plasma crash EXPECTED RESULT Clicked application get focus SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Plasma is crashing for me from time to time after click on icon in tasks list. But first time I got this. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441698] Gwenview fails to open and preview RAW images (NEF, ARW, etc.) : mimetype is detected as TIFF
https://bugs.kde.org/show_bug.cgi?id=441698 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz --- Comment #43 from Marian Kyral --- I have the same issue on Gentoo. I can confirm that patch works. Hope it will be fixed in next release. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443757] Please bring back cover switch effect
https://bugs.kde.org/show_bug.cgi?id=443757 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443757] Please bring back cover switch effect
https://bugs.kde.org/show_bug.cgi?id=443757 --- Comment #3 from Marian Kyral --- My favorite switch :-( All remaining switches are too boring and lack cool effect. Even these in store. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436151] New: Energy saving in powerdevil has confusing and broken user interface for suspend-then-hibernate
https://bugs.kde.org/show_bug.cgi?id=436151 Bug ID: 436151 Summary: Energy saving in powerdevil has confusing and broken user interface for suspend-then-hibernate Product: systemsettings Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: mkleins...@gmail.com CC: k...@privat.broulik.de Target Milestone: --- Power devil user interface is confusing. I am using Kubuntu 21.04 systemctl / systemd underlying system (backend) Go to Energy saving/On battery. 0) Hybrid sleep is never working. 1) The checkbox "While asleep, hibernate after a period of inactivity." with indentation under Suspend session makes sense only when sleep is selected in the list for Suspend session. It is ignored for other choices. Consider adding a new item to the list "sleep+hibernate" instead. 2) This checkbox in 1) also affects functionality under "Button events handling" again when "sleep" is selected in the list. It is not clear from UI it should. Consider repeating checkbox under "Button events handling" or adding a new item to the list "Sleep+hibernate" 3) it is not clear after how long period of inactivity hibernate should follow. Either display read-only (non-editable) value from `cat /etc/systemd/sleep.conf | grep HibernateDelaySec` with some information/help to point user to the configuration file. or add input field to specify the time and update the config file. Linux/KDE Plasma: kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0-0ubuntu1 Qt Version: 5.15.2+dfsg-5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436151] Energy saving in powerdevil has confusing and broken user interface for suspend-then-hibernate
https://bugs.kde.org/show_bug.cgi?id=436151 --- Comment #1 from Marian Klein --- Created attachment 137893 --> https://bugs.kde.org/attachment.cgi?id=137893&action=edit powerdevil confusing/broken UI -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436151] Energy saving in powerdevil has confusing and broken user interface for suspend-then-hibernate
https://bugs.kde.org/show_bug.cgi?id=436151 --- Comment #2 from Marian Klein --- If the UI is not self-contained and relies on other configuration elsewhere, please educate user (with Info message in dialog) where to look. Educate user he should look at config /etc/systemd/logind.conf For example for the point 2) "Button events handling" I have marian@HPSpectre:~$ cat /etc/systemd/logind.conf | grep HandleLidSwitch HandleLidSwitch=suspend-then-hibernate #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436383] New: give more control and visibility to user which microphone is being used and how sensitive it is
https://bugs.kde.org/show_bug.cgi?id=436383 Bug ID: 436383 Summary: give more control and visibility to user which microphone is being used and how sensitive it is Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mkleins...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 When I am on conference talk and others don't hear me well it is not blatantly obvious in KDE what mic is being used (built-in mic or headset mic) and if I should get closer to the laptop or adjust microphone at the headset. Several situations demand better user control (in addition to the automation), it is about security and confidentiality: Consider for now only built-in laptop microphone and combo audio jack (microphone, speaker). Ignore for now bluetooth and usb microphones/headsets. Some laptops have a way to notify kernel if audio jack is plugged. 1) Sometimes laptops kernel do not detect (due to hardware limitation or bug in kernel) the plugged standard 3.5 mm combo audio jack (in/out headphone/microphone) , so the OS cannot switch the default audio out/in source/sink. 2) sometimes audio combo jack headset/microphone is bad, weak or buggy and user wants to make sure or test he/she is talking to the active microphone in the headset and wants to disable built-in microphone 3) user wants to have a confidence he/she is not being spied on or she does not want to make an easy mistake due to confusing user interface (many marriages have been broken by disclosing the secrets by mistake). User can easily unplug headset to make sure microphone is NOT being used. However the user cannot easily unplug (without hardware kill switch) the built-in microphone. The user has never the confidence the built-in laptop microphone is not being used possibly due to software bug or virus, confusion or mistake. Especially if there is an automatic switching source mechanism in place when audio jack is plugged in the confusion and doubt can creep in what source is being used. All those situations could be handled if both audio sources/microphones (built-in one and combo audio jack mic) are available in the system tray audio volume all the time (and especially if the audio jack is plugged) and what is switched (if possible) is only the default audio source/mic. Also volume meter with mute and mic boost checkbox for each mic in audio volume applet/widget (including bluetooth and usb mics) would be great too. To avoid confusion the checkbox mute must be next to the explicitly stated location: Built-in/internal microphone at all times, and another checkbox next to the "audio jack" microphone/headset (when plugged in) at least when the headset/microphone is plugged in (if possible to detect). I would avoid displaying name such as "Digital microphone" in audio volume applet/widget. (as it is doing now to me).What matters to me is where the mic is , not what type it is. The name "External" is not good as well as there can be multiple bluetooth or usb microphones/headsets, but the 'audio jack' headset is just one. +35dB boost checkbox next to those microphones would be great next to the volume meter for each mic (including usb and bluetooth mics). Some feature can be put in systemsettings/pulse/audio Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.4-0ubuntu1 KDE Frameworks Version: plasma-framework 5.80.0-0ubuntu1 Qt Version: 5.15.2+dfsg-5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436383] give more control and visibility to user which microphone is being used and how sensitive it is
https://bugs.kde.org/show_bug.cgi?id=436383 --- Comment #1 from Marian Klein --- Created attachment 138020 --> https://bugs.kde.org/attachment.cgi?id=138020&action=edit single microphone when headset audio jack is plugged in In my case the only mic volume meter is responding to the sound (noise) from built-in laptop microphone, not the audio jack headset mic, when headset is plugged in. Is it pulse problem, hardware problem, kernel problem or no problem? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 436383] give more control and visibility to user which microphone is being used and how sensitive it is
https://bugs.kde.org/show_bug.cgi?id=436383 --- Comment #2 from Marian Klein --- marian@HPSpectre:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofsoundwire [sof-soundwire], device 1: Headset mic (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 3: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 4: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359146] Impossible to use AltGr as modifier
https://bugs.kde.org/show_bug.cgi?id=359146 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359146] Impossible to use AltGr as modifier
https://bugs.kde.org/show_bug.cgi?id=359146 --- Comment #2 from Marian Kyral --- Also I can't find a way, how to use AltGr in "Send text input" part. I want to enter the "|" character. In Czech layout I can do it with AltGr+Q. I've tried ALT+Q, ALTGR+Q, ALT_R+Q, but none work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 295633] custom shortcuts: send keyboard input does not work for keys requiring AltGr
https://bugs.kde.org/show_bug.cgi?id=295633 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 295633] custom shortcuts: send keyboard input does not work for keys requiring AltGr
https://bugs.kde.org/show_bug.cgi?id=295633 --- Comment #5 from Marian Kyral --- Any change to get this fixed? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 295633] custom shortcuts: send keyboard input does not work for keys requiring AltGr
https://bugs.kde.org/show_bug.cgi?id=295633 --- Comment #6 from Marian Kyral --- I've looked at it and I think that main issue is that AltGr is not handled as a modifier in QT: https://doc.qt.io/qt-5/qt.html#Modifier-enum It probably could be overpassed, but will need more knowledge and work :-( -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 428022] New: ksmserver-logout-greeter crashing on logout
https://bugs.kde.org/show_bug.cgi?id=428022 Bug ID: 428022 Summary: ksmserver-logout-greeter crashing on logout Product: ksmserver Version: 5.20.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mky...@email.cz CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132587 --> https://bugs.kde.org/attachment.cgi?id=132587&action=edit ksmserver-logout-greeter-20201020-162044.kcrash SUMMARY After upgrade to plasma 5.20 I can't logout/reboot/poweroff. ksmserver-logout-greeter keeps crashing STEPS TO REPRODUCE 1. Start plasma desktop 2. Try logout/restart/poweroff OBSERVED RESULT ksmserver-logout-greeter crash, session is not closed EXPECTED RESULT Session is closed, computer rebooted or switched off SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo linux (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75 Qt Version: 5.15.1 ADDITIONAL INFORMATION Full crash log attached. Thread 1 (Thread 0x7f6ddbda2800 (LWP 5775)): [KCrash Handler] #6 0x7f6ddfc646c1 in raise () from /lib64/libc.so.6 #7 0x7f6ddfc4e53b in abort () from /lib64/libc.so.6 #8 0x7f6de00f3bff in qt_message_fatal (context=..., message=...) at /var/tmp/portage/dev-qt/qtcore-5.15.1-r1/work/qtbase-everywhere-src-5.15.1/src/corelib/global/qlogging.cpp:1914 #9 QMessageLogger::fatal (this=this@entry=0x7ffd3b05f570, msg=msg@entry=0x7f6de1420310 "QDBusArgument: read from a write-only object") at /var/tmp/portage/dev-qt/qtcore-5.15.1-r1/work/qtbase-everywhere-src-5.15.1/src/corelib/global/qlogging.cpp:893 #10 0x7f6de13a5dc9 in QDBusArgumentPrivate::checkRead (d=) at /var/tmp/portage/dev-qt/qtdbus-5.15.1/work/qtbase-everywhere-src-5.15.1/include/QtCore/../../src/corelib/global/qlogging.h:90 #11 0x7f6de13a5e19 in QDBusArgumentPrivate::checkRead (d=) at /var/tmp/portage/dev-qt/qtdbus-5.15.1/work/qtbase-everywhere-src-5.15.1/include/QtCore/../../src/corelib/global/qlogging.h:90 #12 QDBusArgumentPrivate::checkReadAndDetach (d=) at /var/tmp/portage/dev-qt/qtdbus-5.15.1/work/qtbase-everywhere-src-5.15.1/src/dbus/qdbusargument.cpp:152 #13 0x7f6de13fb7b9 in QDBusArgument::beginArray (this=0x7ffd3b05f620) at /var/tmp/portage/dev-qt/qtdbus-5.15.1/work/qtbase-everywhere-src-5.15.1/src/dbus/qdbusargument.cpp:1010 #14 0x7f6de254e6f6 in SystemdSeat::getSessions() () from /usr/lib64/libkworkspace5.so.5 #15 0x7f6de254755a in getSessionsForSeat(QDBusObjectPath const&) () from /usr/lib64/libkworkspace5.so.5 #16 0x7f6de254907b in KDisplayManager::localSessions(QList&) () from /usr/lib64/libkworkspace5.so.5 #17 0x7f6dd1117af2 in SessionsModel::reload (this=this@entry=0x560240b9c730) at /var/tmp/portage/kde-plasma/plasma-workspace-5.20.0/work/plasma-workspace-5.20.0/components/sessionsprivate/sessionsmodel.cpp:162 #18 0x7f6dd11185f7 in SessionsModel::SessionsModel (this=0x560240b9c730, parent=) at /var/tmp/portage/kde-plasma/plasma-workspace-5.20.0/work/plasma-workspace-5.20.0/components/sessionsprivate/sessionsmodel.cpp:42 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 428022] ksmserver-logout-greeter crashing on logout
https://bugs.kde.org/show_bug.cgi?id=428022 --- Comment #2 from Marian Kyral --- One think. This happen only on one of three my computers with Gentoo. The same versions. I have no idea what is the difference :-( -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 428022] ksmserver-logout-greeter crashing on logout
https://bugs.kde.org/show_bug.cgi?id=428022 --- Comment #4 from Marian Kyral --- Always. I have to call "poweroff" command in konsole to switch computer down. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478765] dolphin-plugins-git Target "fileviewgitplugin" links to: KF6::XmlGui
https://bugs.kde.org/show_bug.cgi?id=478765
Marian Kyral changed:
What|Removed |Added
CC||mky...@email.cz
--- Comment #2 from Marian Kyral ---
This is an issue in Gentoo ebuild, when it removes unused modules:
src_prepare() {
ecm_src_prepare
# solid, qtdbus only required by mountiso
ecm_punt_qt_module DBus
ecm_punt_kf_module Solid
# kxmlgui, qtnetwork only required by dropbox
ecm_punt_qt_module Network
ecm_punt_kf_module XmlGui
# delete non-${PN} translations
find po -type f -name "*po" -and -not -name "*${MY_PLUGIN_NAME}plugin"
-delete || die
}
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage with certain screen arrangements
https://bugs.kde.org/show_bug.cgi?id=425271 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 333262] NTLM proxy authentization dialog does not store the password in kwallet
https://bugs.kde.org/show_bug.cgi?id=333262 --- Comment #9 from Marian Kyral --- Sorry, I'm no more using such proxy, I can't test. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 463132] Gwenview Removed Support for All RAW Files (Regression)
https://bugs.kde.org/show_bug.cgi?id=463132 Marian Kyral changed: What|Removed |Added CC||mky...@email.cz --- Comment #3 from Marian Kyral --- I have the same issue. RAW files works correctly in latest gwenview with kimageformats-5.98. But after update kimageformats to version 5.99+, RAW images fails to load. -- You are receiving this mail because: You are watching all bug changes.
[basket] [Bug 289488] Copying by selection and paste by middle click does not work
https://bugs.kde.org/show_bug.cgi?id=289488 Marian Kyral changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Marian Kyral --- Hi, thanks for the info, unfortunately I don't use Basket anymore. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] New: add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 Bug ID: 437326 Summary: add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status Product: systemsettings Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mkleins...@gmail.com Target Milestone: --- SUMMARY In display settings/configuration ( that you can invoke also with marian@HPSpectre:~$ systemsettings5 kcm_kscreen ) add a new checkbox with label auto-orientation. It is a missing feature in KDE especially useful for tablets/touchscreens and convertible laptops with touchscreens. Take advantage of the binary /usr/bin/monitor-sensor (package iio-sensor-proxy in ubuntu/debian) to detect orientation of the hardware (normal, inverted , sideways) from accelerometer and use this status to change the screen orientation with xrandr or equivalent automatically on background/deamon. See https://gist.github.com/mildmojo/48e9025070a2ba40795c (marian556, mikelduke) https://github.com/mikelduke/rotate-touchscreen STEPS TO REPRODUCE missing feature -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 --- Comment #1 from Marian Klein --- make sure it works also with wayland (and Xorg) and with HiDPI -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 --- Comment #3 from Marian Klein --- I have kubuntu 21.04 (hirsute) marian@HPSpectre:~$ apt search QtSensors Sorting... Done Full Text Search... Done python3-pyqt5.qtsensors/hirsute 5.15.4+dfsg-1 amd64 Python 3 bindings for QtSensors module python3-pyqt5.qtsensors-dbg/hirsute 5.15.4+dfsg-1 amd64 Python 3 bindings for QtSensors module (debug extension) python3-pyside2.qtsensors/hirsute 5.15.2-1 amd64 Python bindings for Qt5 Sensors module (Python 3) qml-module-qtsensors/hirsute,now 5.15.2-2 amd64 [installed] Qt 5 Sensors QML module qtsensors5-doc/hirsute,hirsute,now 5.15.2-2 all [installed] Qt 5 Sensors documentation qtsensors5-doc-html/hirsute,hirsute 5.15.2-2 all Qt 5 Sensors HTML documentation qtsensors5-examples/hirsute,now 5.15.2-2 amd64 [installed] Qt 5 sensors examples Is it this qml-module-qtsensors ? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 Marian Klein changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- Ever confirmed|0 |1 --- Comment #4 from Marian Klein --- I installed qml-module-qtsensors and the feature is still not present. Display configuration has no new feature. Please explain how to enable from user perspective (not developer perspective) the automatic screen rotation on sensor/accelarator input in KDE, if that is possible at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 --- Comment #5 from Marian Klein --- Libraries and components for the developers implementing the feature is not sufficient. The KDE user interface (configuration/settings) with the feature must be available by default and must be intuitive enough and placed in the prominent and appropriate location Display configuration for the user to notice and take advantage of it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 --- Comment #7 from Marian Klein --- Yes. I am using X11, because there is no hardware acceleration for 4k video decoding videos in chrome on wayland. It does work on X11 though. Also scaling for HiDPI does not work consistently on wayland. Is there a plan to backport feature to X11? Why the feature is wayland related only? I will test it on wayland though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] For X11/Xorg add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 Marian Klein changed: What|Removed |Added Summary|add to display |For X11/Xorg add to display |configuration a new |configuration a new |feature/checkbox to |feature/checkbox to |automatically adjust screen |automatically adjust screen |orientation based on|orientation based on |accelerometer sensor (if|accelerometer sensor (if |available) status |available) status -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] For X11/Xorg add to display configuration a new feature/checkbox to automatically adjust screen orientation based on accelerometer sensor (if available) status
https://bugs.kde.org/show_bug.cgi?id=437326 Marian Klein changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #9 from Marian Klein --- I can confirm the feature works for Wayland. Reducing the scope of this to X11/Xorg. I still would like to see it working for Xorg/X11. Reopening this one last time. Wayland still has many issues , than can prevent many people to switch. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437326] Automatic screen rotation on X11 (already works on Wayland)
https://bugs.kde.org/show_bug.cgi?id=437326 --- Comment #10 from Marian Klein --- Is wishlist a synonym for 'never gonna happen' bin? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437585] New: scaling (200%) on HiDPI wayland ignored when switched into X11 plasma and back into wayland
https://bugs.kde.org/show_bug.cgi?id=437585 Bug ID: 437585 Summary: scaling (200%) on HiDPI wayland ignored when switched into X11 plasma and back into wayland Product: systemsettings Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mkleins...@gmail.com Target Milestone: --- SUMMARY When logged out or rebooted from wayland plasma the scaling (200%) global scaling is remembered and works fine. When however I log out from wayland into sddm , login into X11 and then log out of X11 plasma and log in into wayland plasma I can see small letters again. When I look in "display settings" it shows properly 200%, but it is not acted on as all letters in plasma (K) menu are small. As a workaround I need to adjust slightly to 175% , press apply button and then go back to 200% and press apply. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Small letters in menu. Scaling not applied although it shows 200% in display settings. EXPECTED RESULT Proper scaling in effect. SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu 21.04 KDE Plasma Version: 5.21.4 marian@HPSpectre:~$ dpkg -l | grep plasma | grep Runtime ii libkf5plasma5:amd64 5.80.0-0ubuntu1 amd64Plasma Runtime components ii libkf5plasmaquick5:amd64 5.80.0-0ubuntu1 amd64Plasma Runtime components ii plasma-framework 5.80.0-0ubuntu1 amd64Plasma Runtime components KDE Frameworks Version: 5.80 Qt Version: marian@HPSpectre:~$ dpkg -l | grep qt5core ii libqt5core5a:amd645.15.2+dfsg-5 amd64Qt 5 core module ADDITIONAL INFORMATION See attached files -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437585] scaling (200%) on HiDPI wayland ignored when switched into X11 plasma and back into wayland
https://bugs.kde.org/show_bug.cgi?id=437585 --- Comment #1 from Marian Klein --- Created attachment 138723 --> https://bugs.kde.org/attachment.cgi?id=138723&action=edit dpkg -l | grep "plasma\|qt\|kde" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437585] scaling (200%) on HiDPI wayland ignored when switched into X11 plasma and back into wayland
https://bugs.kde.org/show_bug.cgi?id=437585 --- Comment #2 from Marian Klein --- Created attachment 138724 --> https://bugs.kde.org/attachment.cgi?id=138724&action=edit kubuntu version -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437585] scaling (200%) on HiDPI wayland ignored when switched into X11 plasma and back into wayland
https://bugs.kde.org/show_bug.cgi?id=437585 --- Comment #4 from Marian Klein --- Created attachment 138726 --> https://bugs.kde.org/attachment.cgi?id=138726&action=edit wayland OK before -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437585] scaling (200%) on HiDPI wayland ignored when switched into X11 plasma and back into wayland
https://bugs.kde.org/show_bug.cgi?id=437585 --- Comment #5 from Marian Klein --- Created attachment 138727 --> https://bugs.kde.org/attachment.cgi?id=138727&action=edit X11 plasma ok X11 plasma ok -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437585] scaling (200%) on HiDPI wayland ignored when switched into X11 plasma and back into wayland
https://bugs.kde.org/show_bug.cgi?id=437585 --- Comment #6 from Marian Klein --- Created attachment 138728 --> https://bugs.kde.org/attachment.cgi?id=138728&action=edit wayland after X11 entry wrong -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426108] No audio after update to 20.04 - pipewire 0.3.8-1 - snd_hda_intel
https://bugs.kde.org/show_bug.cgi?id=426108 Marian Klein changed: What|Removed |Added CC||mkleins...@gmail.com --- Comment #52 from Marian Klein --- See https://bugzilla.kernel.org/show_bug.cgi?id=212465 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426108] No audio after update to 20.04 - pipewire 0.3.8-1 - snd_hda_intel
https://bugs.kde.org/show_bug.cgi?id=426108 --- Comment #53 from Marian Klein --- https://lists.ubuntu.com/archives/kernel-team/2021-May/120227.html -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 437685] New: Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 Bug ID: 437685 Summary: Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases Product: frameworks-kwayland Version: 5.80.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: mkleins...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- 4k@60fps youtube video footage hardware decoding acceleration works for on X11/Xorg in google-chrome but it does not work for the same laptop/OS and browser binary on wayland. See also https://gitlab.freedesktop.org/wayland/wayland/-/issues/212 SOFTWARE/OS VERSIONS: Kubuntu 21.04 Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #1 from Marian Klein --- Created attachment 138791 --> https://bugs.kde.org/attachment.cgi?id=138791&action=edit hardware video decoding accelerator works on X11 for an application -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #2 from Marian Klein --- Trying to play the same 4k video on wayland produces Kde crash handler: #4 0x7f02b44a841a in wl_proxy_marshal_constructor () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #5 0x7f02b452bb57 in QtWaylandClient::QWaylandDisplay::createSurface(void*) () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #6 0x7f02b4537d7a in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #7 0x7f02b453075a in QtWaylandClient::QWaylandWindow::initializeWlSurface() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x7f02b45375ad in QtWaylandClient::QWaylandShmWindow::QWaylandShmWindow(QWindow*, QtWaylandClient::QWaylandDisplay*) () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x7f02b451ec39 in QtWaylandClient::QWaylandIntegration::createPlatformWindow(QWindow*) const () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #10 0x7f02b60421e4 in QWindowPrivate::create(bool, unsigned long long) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7f02b6890fa5 in QWidgetPrivate::create() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f02b68914ee in QWidget::create(unsigned long long, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f02b689e77e in QWidgetPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f02b6a5e868 in QDialog::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x55ddb1e516e0 in ?? () #16 0x7f02b55a5565 in __libc_start_main (main=0x55ddb1e50050, argc=19, argv=0x7ffc6214bd68, init=, fini=, rtld_fini=, stack_end=0x7ffc6214bd58) at ../csu/libc-start.c:332 #17 0x55ddb1e52a7e in _start () [Inferior 1 (process 2388) detached] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #3 from Marian Klein --- Created attachment 138792 --> https://bugs.kde.org/attachment.cgi?id=138792&action=edit video hardware decoding not working on wayland. Everything else the same. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #4 from Marian Klein --- When I tried to play 4k video footage straight after switching to wayland from X11, google-chrome crashed in /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 . When I removed ~/.config/google-chrome I could get to playing 4k footage again. Then I pressed CTRL+SHIFT+i, and I looked up media tab (via more tools) in built-in info/debug browser right section tool. For wayland you can see "Decoder name:Dav1dVideoDecoder" and "Hardware decoder: false" whereas for X11 you can see "Decoder name:VideoDecoderAccelerator" and "Hardware decoder:true". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #5 from Marian Klein --- The same behaviour is for both variants of google-chrome , stable and unstable: marian@HPSpectre:~/.config$ dpkg -l | grep chrome ii google-chrome-stable 90.0.4430.212-1 amd64The web browser from Google ii google-chrome-unstable92.0.4512.4-1 amd64The web browser from Google -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #6 from Marian Klein --- marian@HPSpectre:~/.config$ vainfo libva info: VA-API version 1.10.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.10 (libva 2.10.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 21.1.1 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain : VAEntrypointEncSliceLP VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointEncSliceLP VAProfileVP9Profile0: VAEntrypointVLD VAProfileVP9Profile1: VAEntrypointVLD VAProfileVP9Profile2: VAEntrypointVLD VAProfileVP9Profile3: VAEntrypointVLD VAProfileHEVCMain12 : VAEntrypointVLD VAProfileHEVCMain12 : VAEntrypointEncSlice VAProfileHEVCMain422_10 : VAEntrypointVLD VAProfileHEVCMain422_10 : VAEntrypointEncSlice VAProfileHEVCMain422_12 : VAEntrypointVLD VAProfileHEVCMain422_12 : VAEntrypointEncSlice VAProfileHEVCMain444: VAEntrypointVLD VAProfileHEVCMain444: VAEntrypointEncSliceLP VAProfileHEVCMain444_10 : VAEntrypointVLD VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP VAProfileHEVCMain444_12 : VAEntrypointVLD VAProfileHEVCSccMain: VAEntrypointVLD VAProfileHEVCSccMain: VAEntrypointEncSliceLP VAProfileHEVCSccMain10 : VAEntrypointVLD VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP VAProfileHEVCSccMain444 : VAEntrypointVLD VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP VAProfileAV1Profile0: VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #9 from Marian Klein --- Hi David. The browser that crashed on wayland was google-chrome. (See comment 4). When I removed ~/.config/google-chrome , the crashing stopped , but I still did not have hardware acceleration. I got one mainstream browser working with hardware acceleration on wayland for me now. It is firefox. Even though it was crashing too in each tab when acceleration enable originally. I fixed firefox crashes by setting environment variable MOZ_DISABLE_CONTENT_SANDBOX=1 I may open another ticket for this somewhere. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437685] Please make wayland compatible with X11 with respect to video decoding hardware acceleration in all cases
https://bugs.kde.org/show_bug.cgi?id=437685 --- Comment #11 from Marian Klein --- Hi Nate. Do firefox and google-chrome have different execution paths in their code for X11 and for wayland in respect to video hardware acceleration? If they do then it is a bad design. If they don't and they don't care/know what they are running on then swapping one for another one (wayland for X11) for the same binary should not change behaviour or start/stop crashing. The indication is combination of My Laptop +kubuntu 21.04 + google-chroome + X11 supports video decoding hardware acceleration.However the similar combination (with the same binary for google-chrome) with wayland replacing X11 is crashing or not supporting hardware acceleration. >From the outside I can only tell the wayland is the blame or an library wayland uses and X11 does not. I am less concerned about google-chrome now as I got firefox video acceleration working on wayland with MOZ_DISABLE_CONTENT_SANDBOX=1 I have not tested chromium yet. Only google-chrome and firefox. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434533] New: Plasma crash when Task manager should expand group
https://bugs.kde.org/show_bug.cgi?id=434533 Bug ID: 434533 Summary: Plasma crash when Task manager should expand group Product: plasmashell Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mky...@email.cz CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.21.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.6-gentoo x86_64 Windowing System: X11 Drkonqi Version: 5.21.2 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: I want to switch to another Firefox window. So I clicked in Task manager on Firefox icon to expand grouped list of windows. But list of windows is not shown, plasma crash and it is restarted. Then I repeat the action and it works as expected in this case. Can't figure out conditions to replicate, this happen to me once or twice per day. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fbf3ad8e7c0 (LWP 6436))] [KCrash Handler] #6 0x7fbf3e6e5971 in raise () from /lib64/libc.so.6 #7 0x7fbf3e6cf536 in abort () from /lib64/libc.so.6 #8 0x7fbf3ead6bff in qt_message_fatal (context=..., message=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/global/qlogging.cpp:1914 #9 QMessageLogger::fatal (this=this@entry=0x7fbefca87cd0, msg=msg@entry=0x7fbf3eddf9c8 "ASSERT failure in %s: \"%s\", file %s, line %d") at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/global/qlogging.cpp:893 #10 0x7fbf3ead5be8 in qt_assert_x (where=where@entry=0x7fbf40bd71aa "QVector::at", what=what@entry=0x7fbf40bd7197 "index out of range", file=file@entry=0x7fbf40bd7000 "/usr/include/qt5/QtCore/qvector.h", line=line@entry=454) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/global/qglobal.cpp:3366 #11 0x7fbf408a1d68 in QVector::at (this=, i=2) at /usr/include/qt5/QtCore/qvector.h:454 #12 QQuickCustomMaterialShader::updateState (this=, state=..., newEffect=, oldEffect=) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/items/qquickopenglshadereffectnode.cpp:149 #13 0x7fbf4093bbb4 in QSGBatchRenderer::Renderer::renderMergedBatch (batch=0x7fbed02fd290, this=0x7fbed00d7b80) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3097 #14 QSGBatchRenderer::Renderer::renderMergedBatch (this=0x7fbed00d7b80, batch=0x7fbed02fd290) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3026 #15 0x7fbf40941d65 in QSGBatchRenderer::Renderer::renderBatches (this=0x7fbed00d7b80) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4066 #16 0x7fbf4094235f in QSGBatchRenderer::Renderer::render (this=) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4363 #17 0x7fbf4092661e in QSGRenderer::renderScene (bindable=..., this=0x7fbed00d7b80) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/coreapi/qsgrenderer.cpp:264 #18 QSGRenderer::renderScene (this=0x7fbed00d7b80, bindable=...) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220 #19 0x7fbf40926b33 in QSGRenderer::renderScene (this=, fboId=) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/coreapi/qsgrenderer.cpp:212 #20 0x7fbf40997c43 in QSGDefaultRenderContext::renderNextFrame (this=0x565206023860, renderer=0x7fbed00d7b80, fboId=) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/qsgdefaultrendercontext.cpp:228 #21 0x7fbf40a0be81 in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x5652060233a0, size=..., surfaceSize=...) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/items/qquickwindow.cpp:617 #22 0x7fbf409a6299 in QSGRenderThread::syncAndRender (this=0x565209538d80, grabImage=0x0) at /var/tmp/portage/dev-qt/qtdeclarative-5.15.2/work/qtdeclarative-everywhere-src-5.15.2/src/quick/scenegraph/qsgthreadedrenderloop.cpp:837 #23 0x7fbf409aabb7 in QSGRenderThread::run (this=0x565209538d80) at /var/t
[plasmashell] [Bug 434533] Plasma crash when Task manager should expand group
https://bugs.kde.org/show_bug.cgi?id=434533 --- Comment #1 from Marian Kyral --- Created attachment 136776 --> https://bugs.kde.org/attachment.cgi?id=136776&action=edit The group that should be open -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434533] Plasma crashes in QSGBatchRenderer::Renderer::renderMergedBatch when Task manager attempts to display tooltip
https://bugs.kde.org/show_bug.cgi?id=434533 --- Comment #3 from Marian Kyral --- I clicked on Firefox logo. It is quicker than waiting for hover delay. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] New: Hovering over an icon with touchscreen is not the same as hovering with touchpad. Tap/Click/Launch not triggered.
https://bugs.kde.org/show_bug.cgi?id=407951 Bug ID: 407951 Summary: Hovering over an icon with touchscreen is not the same as hovering with touchpad. Tap/Click/Launch not triggered. Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: mkleins...@gmail.com Target Milestone: --- SUMMARY Still the problem exist with kubuntu 19.04/disco in May 2019. This is a shame. There are plenty of convertable devices laptop/tablet on the market. HP spectre x360 Convertible. model 13-ae053na. Touchscreen hover is not the same as touchpad hover. Or it has different action associated in plasma. Hovering over an icon gets the focus of the icon for a touchpad , but not with a touchscreen. With the focus on the icon the click or double click work for a touchpad. To test: I can always trigger a tap/single click/double click on touchscreen , when previously hovering with touchpad over the icon. I always open/launch the icon like that. If not touchpad hover , then it is striggle to launch the icon. STEPS TO REPRODUCE 1. Get kubuntu 19.04 with any convertible laptop with a touchscreen. 2. hover with touch screen over the icon 3. hover with touchpad over the same icon, you get different behaviour 4. you can tap/click in touchscreen only when hovered on touchpad previously OBSERVED RESULT Cannot trigger/launch icon on touchscreen EXPECTED RESULT Touchscreen hover and touchpad hover should behave the same way (by default.) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.04/disco (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Hovering over an icon with touchscreen is not the same as hovering with touchpad. Tap/Click/Launch not triggered.
https://bugs.kde.org/show_bug.cgi?id=407951 Marian Klein changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Hovering over an icon with touchscreen is not the same as hovering with touchpad. Tap/Click/Launch not triggered.
https://bugs.kde.org/show_bug.cgi?id=407951 --- Comment #1 from Marian Klein --- By hovering on touchscreen on the icon, I mean both moving along the surface of the touchscreen from outside icon towards inside the icon or jumping inside the icon from outside the icon. In both ways the outcome is different from touchpad. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Hovering over an icon with touchscreen is not the same as hovering with touchpad. Tap/Click/Launch not triggered.
https://bugs.kde.org/show_bug.cgi?id=407951 Marian Klein changed: What|Removed |Added Version|unspecified |5.58.0 --- Comment #2 from Marian Klein --- I made an effort . Downloaded neon-developer-20190514-0001.iso and installed that inside the virtualbox 6 on top of kubuntu 19.04. Touchscreen and touchpad is working and displays the behaviour as reported even for latest trunk Plasma 5.16.80, Qt Version 5.12.0, kde-frameworks 5.59.0 and kernel 4.18.0-18-generic -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 407980] New: kmplot expression editor with constants does not scale after setting higher value in force font dpi in system settings
https://bugs.kde.org/show_bug.cgi?id=407980 Bug ID: 407980 Summary: kmplot expression editor with constants does not scale after setting higher value in force font dpi in system settings Product: kmplot Version: 1.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: mkleins...@gmail.com Target Milestone: --- SUMMARY Modern HiDpi laptops/convertables need to set higher value in force fonts DPI setting. I use 288. Kmplot does not display expression editor correctly for hi dpi setting. STEPS TO REPRODUCE 1. use HiDPI laptop with resolution at least 3200x1800. I use HP spectre x360 convertible with resolution 3840x2160. Set the highest resolution of the laptop. 2. use neon-developer-20190514-0001.iso, update packages (as of 27may 2019) 3. set the highest resolution of the laptop and set true/genuine dpi for that resolution in force font dpi setting. you calculate true dpi by taking horizontal resolution of the screen and divide horizontal dimension of the screen in inches . In my case 3840 / 29.5cm = 3840/11.6 inch= 330dpi OBSERVED RESULT kmplot expression editor , (which you get after click on the button after function line ) is totally unusable, unreadable. Fonts scale, but the widgets and window don't scale correspondingly to accommodate for bigger font and cover font letters. EXPECTED RESULT Readable editor. SOFTWARE/OS VERSIONS I used neon-developer-20190514-0001.iso Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 Kernel Version: 5.0.0-15-lowlatency OS Type: 64-bit Processor: 1 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 3.9 GiB of RAM ADDITIONAL INFORMATION Used inside virtualbox6 for testing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tap/Click/Launch of every desktop icon almost never possibly on any icon when using with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 Marian Klein changed: What|Removed |Added Summary|Hovering over an icon with |Tap/Click/Launch of every |touchscreen is not the same |desktop icon almost never |as hovering with touchpad. |possibly on any icon when |Tap/Click/Launch not|using with touchscreen. |triggered. | Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #4 from Marian Klein --- It IS a bug, please acknowledge it first. This is a basic essential feature that needs to work reliably on touchscreen even for Xorg. No time to way for maturing Xwayland. It is quite urgent requirement. Tablets and convertibles are widespread now. Complex multi-touch gestures can wait for wayland. Opening a folder or launching an application by tapping on the icon on desktop by single or double click must work reliably on touchscreen. I want it to JUST WORK. This is a showstopper. I cannot use KDE on my convertible laptop in tablet mode. I can do it in all other desktop environments , gnome, cinnamon, budgie otn Xorg and wayland. That is a shame. How come they can do it and plasma/kde cannot do it with Xorg? How you do it is your business. After my short investigation I offered my insight that can help you to sort out the problem . When I hovered the mouse pointer with my touchpad over the icon first then I could ALWAYS reliably launch an application by tapping on touchscreen. You can choose to use this information or you can choose to ignore it . However make the launching of the application by tapping single click and/or double click always work on touchscreen reliably, please. It is essential. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 Marian Klein changed: What|Removed |Added Summary|Tap/Click/Launch of every |Tapping and/or single click |desktop icon almost never |and/or double click on each |possibly on any icon when |application icon almost |using with touchscreen. |never works reliably with ||touchscreen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 --- Comment #5 from Marian Klein --- Another observation you can take into account. Although clicking/tapping on the desktop icons on touchscreen almost never works. Clicking/tapping on the touchscreen on the icons in the menu (all three alternatives: classic menu,full screen dashboard,and default launcher) always WORKS reliably. So it must be fixable. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 --- Comment #6 from Marian Klein --- If someone points me to the source codes where to start investigating I can start looking into it. I can use 'sudo evtest' to monitor touchscreen events on device level. How can I monitor touchscreen events on QT/plasma/KDE level? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 407951] Tapping and/or single click and/or double click on each application icon almost never works reliably with touchscreen.
https://bugs.kde.org/show_bug.cgi?id=407951 --- Comment #7 from Marian Klein --- I noticed https://community.kde.org/KDE_Visual_Design_Group/Gestures , which is related to this bug. What is the difference between touchpad and touchscreen in operation? There is no direct correspondence (size , aspect ratio) between touchpad and screen/display so touchpad must captures delta/relative moves: If you lift your finger from touchpad and move into another place , the pointer does NOT jump, it continues from where you left it. On the other hand touchscreen has to maintain direct one-to-one correspondence between touch sensor and display to stay in sync, so it needs to capture absolute positions. Jumps in finger must translate as jump in pointer. Other than that, there is not much difference between touchpad and touchscreen. Currently plasma (desktop area) implements : 1) Touchpad moves without holding left button as a relative change of pointer location resulting potentially into hovering or/and change of application focus. 2) touchpad moves with holding left button as dragging /selection. 3) application can be openned by 3a)left touchpad/mouse button single click or double click once the pointer is hovering over icon 3b) single click or double click on touchpad once the pointer is hovering over an icon 4) touchscreen (one finger) moves (or maybe small consecutive jumps) as dragging/selection (as if holding left mouse/touchpad button) To treat both touchpad and touchscreen in the same fashion. Can we have a virtual on screen "sticky left touchscreen button" on plasma to change between default hovering/focus change mode and selection/dragging mode? This way we can unify touchpad and touchscreen behaviour and reuse touchpad settings for touchscreen as generic touch sensors devices. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] New: Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 Bug ID: 408003 Summary: Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: mkleins...@gmail.com Target Milestone: --- SUMMARY Modern HiDpi laptops/tablets/convertibles need to set higher value in force fonts DPI in systems setting. The logic that calculates default panel height does not take system settings force font dpi" into account. Panel height can be set manually by user easily if user is not happy and fonts/icons are too small. But when the screen resolution is constantly changing as is the face for users of virtualbox with "auto-resize guest display" feature then this is no longer an option. Please review the logic for default/automatic panel height setting. STEPS TO REPRODUCE 1. use HiDPI laptop with resolution at least 3200x1800. I use HP spectre x360 convertible with resolution 3840x2160. Set the highest resolution of the laptop. 2. Use virtualbox 6 and install neon-developer-20190514-0001.iso into it, update packages (as of 27may 2019) 3. In both the host and guest(neon) system set the highest resolution of the laptop and set true/genuine dpi for that resolution in force font dpi setting. You calculate true dpi by taking horizontal resolution of the screen and divide horizontal dimension of the screen in inches . In my case 3840 / 29.5cm = 3840/11.6 inch= 330dpi OBSERVED RESULT In the guest system neon the plasma panel height is too small and initially can be set manually to an acceptable height to make opened applications names readable. When resizing the window in virtualbox with "auto-resize guest display" feature the panel height is not preserved "readable" height as set manually because the kde/plasma always resets panel height to a very small height as it was initially. Opened application titles are not readable with that height on hidpi laptops. EXPECTED RESULT Either panel height does not change with each display resolution change inside the virtual box after setting the height manually or logic for the default/automatic panel height respects "force font dpi" value in system setting. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 Kernel Version: 5.0.0-15-lowlatency OS Type: 64-bit Processor: 1 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 3.9 GiB of RAM Note that menu/launcher/dashboard is not affected and fonts is always correct when resizing display. Just the panel at the bottom is affected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 --- Comment #1 from Marian Klein --- Additional information. The Display Graphic Controller in VirtualBox 6 setting is VboxSVGA. This allows guest OS(neon) display resizing with "auto-resize guest display" feature. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 --- Comment #2 from Marian Klein --- Interesting when virtualbox window is in maximized state the guest OS panel height (neon) is set correctly even with high "force font dpi" system settings. The problem is only in windowed mode (not maximised state) in virtual box. Even if the size of virtual box window in windowed mode is close to actual size of maximized window there is big difference between height of panel. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 --- Comment #3 from Marian Klein --- The problem can be seen for those VirtualBox 6.0 Graphics controllers: VBoxSVGA,VBoxVGA. The last one VMSVGA caused VM to set display in 800x600 resolution only so I could not test it panel. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 --- Comment #4 from Marian Klein --- So I used VMSVGA graphic controller with Guest OS additions provided by VirtualBox so I had flexibility in display size. The problem can be reproduced as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 408007] New: wayland plasma does not resize in virtualbox 6.0 with "auto resize guest display"
https://bugs.kde.org/show_bug.cgi?id=408007
Bug ID: 408007
Summary: wayland plasma does not resize in virtualbox 6.0 with
"auto resize guest display"
Product: frameworks-kwayland
Version: 5.58.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mgraess...@kde.org
Reporter: mkleins...@gmail.com
Target Milestone: ---
SUMMARY
Some features of VirtualBox 6.0 don't work ("Auto resize guest display" and
resize to a specific resolutions) when wayland plasma is picked.
STEPS TO REPRODUCE
1. Use virtualbox 6 and install neon-developer-20190514-0001.iso into it,
update packages (as of 27may 2019)
2. try to use auto resize guest display feautre
3.
OBSERVED RESULT
Resizing does not work.
EXPECTED RESULT
Resizing should work as in Xorg plasma.
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.0
Kernel Version: 5.0.0-15-lowlatency
OS Type: 64-bit
Processor: 1 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 3.9 GiB of RAM
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwayland] [Bug 408007] wayland plasma does not resize in virtualbox 6.0 with "auto resize guest display"
https://bugs.kde.org/show_bug.cgi?id=408007 --- Comment #1 from Marian Klein --- Additional information. Wayland seems to inherit the resolution of sddm size. Whatever size of virtualbox guest window is picked via resizing when sddm login is displayed , this size will get fixed for wayland. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 408007] wayland plasma does not resize in virtualbox 6.0 with "auto resize guest display"
https://bugs.kde.org/show_bug.cgi?id=408007 --- Comment #2 from Marian Klein --- observation: ubuntu(gnome) on wayland works properly with resizing in virtualbox, so it should be doable for plasma on wayland too. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408003] Plasma panel height is not respecting "force font dpi" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408003 Marian Klein changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #6 from Marian Klein --- Who said it is not recommended? Why the "force font DPI" is in the system then? Remove it then. Even if something is not recommended as you said and system allows it and system misbehave when it is used then it is still bug. I am not happy you keep closing the valid bugs for me. Do you want to keep your bug list short? I am reporting the problem from the user perspective as it is the status now, not from ideal design perspective far in the future. So do a temporary fix now and then you revisit later. -- You are receiving this mail because: You are watching all bug changes.
