[okular] [Bug 443819] Ctrl+Scroll to zoom is incompatible with inertia touchpads
https://bugs.kde.org/show_bug.cgi?id=443819 --- Comment #2 from Roberto --- Maybe I did not explain myself clearly. The problem occurs when one scrolls fast with the touchpad and then raises the hand so that due to inertia the page keeps scrolling. During such inertia scrolling (withouth any touchpad contact), if one presses ctrl (for example ctrl+f to find some text, or other shortcuts with ctrl) the page becomes huge or minute, depending on the scroll direction. *inertia* triggering zoom is definitely not "what it is supposed to do", because one cannot control the zoom level in that way. I see two ways to solve this bug: 1) ctrl+scroll shortcut to zoom acting only until fingers are in contact with the touchpad 2) provide an option to disable ctrl+scroll to zoom the page I think the second way is clean and simple, and I would vote for it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444016] New: On x11 plasmashell crashes while hovering mouse over running program icon.
https://bugs.kde.org/show_bug.cgi?id=444016 Bug ID: 444016 Summary: On x11 plasmashell crashes while hovering mouse over running program icon. Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142600 --> https://bugs.kde.org/attachment.cgi?id=142600=edit How to trigger. SUMMARY Hovering the mouse over a running program icon on the taskmanager (any taskmanager) crashes plasmashell. It only happens on x11 session and for running programs STEPS TO REPRODUCE 1. Log into x11 2. Launch any program/app 3. Hover the mouse over the already running app/program. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse tumbleweed KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Backtrace #0 0x7f2a6fdb5a4b in pthread_sigmask@GLIBC_2.2.5 () at /lib64/libc.so.6 #1 0x7f2a6fd6399d in sigprocmask () at /lib64/libc.so.6 #2 0x7f2a7233a84b in KCrash::setCrashHandler(void (*)(int)) () at /lib64/libKF5Crash.so.5 #3 0x7f2a7233cd5e in KCrash::defaultCrashHandler(int) () at /lib64/libKF5Crash.so.5 #4 0x7f2a6fd637a0 in () at /lib64/libc.so.6 #5 doActivate(QObject*, int, void**) (sender=0x55ba0ee2d540, signal_index=3, argv=0x0) at kernel/qobject.h:132 #6 0x7f2a6008d784 in () at /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so #7 0x7f2a6008dc9b in () at /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so #8 0x7f2a71f4a648 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) (this=0x55ba0b8dc890, item=0x55ba0c0f2860) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:3872 #9 0x7f2a71f4abeb in QQuickWindowPrivate::updateDirtyNodes() (this=this@entry=0x55ba0b8dc890) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:3617 #10 0x7f2a71f4c7ec in QQuickWindowPrivate::syncSceneGraph() (this=this@entry=0x55ba0b8dc890) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:524 #11 0x7f2a71ec9389 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) (this=0x55ba0b7abdd0, window=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/scenegraph/qsgrenderloop.cpp:751 #12 0x7f2a71f5adaf in QQuickWindow::event(QEvent*) (this=0x55ba0bd1d1f0, e=0x7fff42e7f630) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:1858 #13 0x7f2a711b6a7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55ba0bd1d1f0, e=0x7fff42e7f630) at kernel/qapplication.cpp:3632 #14 0x7f2a704209ea in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55ba0bd1d1f0, event=0x7fff42e7f630) at kernel/qcoreapplication.cpp:1064 #15 0x7f2a70868794 in QPlatformWindow::deliverUpdateRequest() (this=) at kernel/qplatformwindow.cpp:789 #16 QPlatformWindow::windowEvent(QEvent*) (this=, event=) at kernel/qplatformwindow.cpp:476 #17 0x7f2a711bdb76 in QApplication::notify(QObject*, QEvent*) (this=0x7fff42e7fc80, receiver=0x55ba0bd1d1f0, e=0x7fff42e7f8c0) at kernel/qapplication.cpp:2874 #18 0x7f2a704209ea in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55ba0bd1d1f0, event=0x7fff42e7f8c0) at kernel/qcoreapplication.cpp:1064 #19 0x7f2a7047725b in QTimerInfoList::activateTimers() (this=0x55ba0b1de4d0) at kernel/qtimerinfo_unix.cpp:643 #20 0x7f2a70477b04 in timerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at kernel/qeventdispatcher_glib.cpp:183 #21 0x7f2a6e778d5f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #22 0x7f2a6e7790e8 in () at /lib64/libglib-2.0.so.0 #23 0x7f2a6e77919f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #24 0x7f2a70477ec4 in QEventDispatcherGlib::processEvents(QFlags) (this=0x55ba0b1de520, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #25 0x7f2a7041f3eb in QEventLoop::exec(QFlags) (this=this@entry=0x7fff42e7fb00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #26 0x7f2a704276d0 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #27 0x7f2a7086d19c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1867 #28 0x7f2a711b69f5 in QApplication::exec() () at kernel/qapplication.cpp:2824 #29 0x55ba0b0523e6 in main(int, char**) (argc=, argv=0x7fff42e7fcc0) at /usr/src/debug/plasma5-workspace-5.23.80git.20211018T145130~d01061522-ku.27.1.x86_64/shell/main.cpp:238 -- You are receiving this mail because: You are watching all
[Powerdevil] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 --- Comment #14 from Arek Guzinski --- I Completely forgot about this bug... It works fine for me now on Plasma 5.23.0 Frameworks 5.87.0 Kernel 5.11.0-37-generic systemd 245.4-4ubuntu3 and has so for a few weeks now. I also never had any networking issues because of this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374740] Unplugging controller causes 100% usage of one CPU core
https://bugs.kde.org/show_bug.cgi?id=374740 Nagy Tibor changed: What|Removed |Added CC||xnagyti...@gmail.com --- Comment #4 from Nagy Tibor --- I can also reproduce this with 5.23. I may be entirely wrong but this is what I see happening: 1. You pull out the joystick cable. 2. Joystick's device file gets nuked. 3. This select call [1] starts always returning immediately without timeouts. No errors thrown. 4. This read call [2] doesn't read anything anymore. No errors thrown. 5. Event loop goes hyperspeed because of the lack of timeouts. [1] https://invent.kde.org/plasma/plasma-desktop/-/blob/58f29efd5d2975129c07dcdc4a9eb78669c5eb67/kcms/joystick/joydevice.cpp#L292 [2] https://invent.kde.org/plasma/plasma-desktop/-/blob/58f29efd5d2975129c07dcdc4a9eb78669c5eb67/kcms/joystick/joydevice.cpp#L298 No idea about how to properly fix it though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441645] Shortcut keys for filters
https://bugs.kde.org/show_bug.cgi?id=441645 Reinold Rojas changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |rojasrein...@gmail.com CC||rojasrein...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444015] plasmashell crashes at showing window thumbnails
https://bugs.kde.org/show_bug.cgi?id=444015 qydwhotm...@gmail.com changed: What|Removed |Added Summary|plasmashell crashes at |plasmashell crashes at |startup (thumbnail |showing window thumbnails |related?) | CC||vlad.zahorod...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #179 from Bharadwaj Raju --- Strange. Could you check ~/.config/plasma-org.kde.plasma.desktop-appletsrc before and after each resolution change and post them? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444015] plasmashell crashes at startup (thumbnail related?)
https://bugs.kde.org/show_bug.cgi?id=444015 --- Comment #2 from qydwhotm...@gmail.com --- After updating these packages, the bug occurs: kdeclarative-components kdeclarative-devel kwin5 kwin5-devel libKF5CalendarEvents5 libKF5Declarative5 libKF5Plasma5 libKF5QuickAddons5 plasma-framework plasma-framework-components plasma-framework-devel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444015] plasmashell crashes at startup (thumbnail related?)
https://bugs.kde.org/show_bug.cgi?id=444015 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/609 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443252] WM_CLASS not respected all the time on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=443252 Srevin Saju changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Srevin Saju --- Apologize for the delay, I have these in my chromium flags (~/.config/chromium-flags.conf). ``` --enable-features=UseOzonePlatform --ozone-platform=wayland ``` Does this look correct? Or am I missing any other chromium flags? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443221] 'sleep' sometimes fails to put laptop to sleep
https://bugs.kde.org/show_bug.cgi?id=443221 Mariusz Libera changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443890] Can't create either a new window or subwindow
https://bugs.kde.org/show_bug.cgi?id=443890 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443252] WM_CLASS not respected all the time on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=443252 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443258] KWin crashed
https://bugs.kde.org/show_bug.cgi?id=443258 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442228] Latte-dock causes Microsoft Edge to crash
https://bugs.kde.org/show_bug.cgi?id=442228 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 443243] I am unable to use Mysql database as data source.
https://bugs.kde.org/show_bug.cgi?id=443243 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 443315] "Expected expression" error declaring a variable immediately after a case label
https://bugs.kde.org/show_bug.cgi?id=443315 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443172] Firefox leaves sticky/persistent tooltips/popups
https://bugs.kde.org/show_bug.cgi?id=443172 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443221] 'sleep' sometimes fails to put laptop to sleep
https://bugs.kde.org/show_bug.cgi?id=443221 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442526] Kate crashed when pressing the "custom" button where you choose color for highlighted brackets.
https://bugs.kde.org/show_bug.cgi?id=442526 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444015] plasmashell crashes at startup (thumbnail related?)
https://bugs.kde.org/show_bug.cgi?id=444015 qydwhotm...@gmail.com changed: What|Removed |Added Summary|plasmashell crashs at |plasmashell crashes at |startup |startup (thumbnail ||related?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444015] New: plasmashell crashs at startup
https://bugs.kde.org/show_bug.cgi?id=444015
Bug ID: 444015
Summary: plasmashell crashs at startup
Product: plasmashell
Version: master
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: qydwhotm...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.23.80)
Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.14.11-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.80 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Start plasmashell.
Wait until the panel appears.
plasmashell crashs.
The crash can be reproduced every time.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 doActivate(QObject*, int, void**) (sender=0x5611d18a7b10,
signal_index=3, argv=0x0) at kernel/qobject.h:132
#7 0x7f93d07b54ff in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x5611d18a7b10, m=m@entry=0x7f93d2582800
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#8 0x7f93d22090f0 in QSGTextureProvider::textureChanged()
(this=this@entry=0x5611d18a7b10) at .moc/moc_qsgtextureprovider.cpp:131
#9 0x7f93ac12a784 in
Plasma::WindowTextureProvider::setTexture(QSGTexture*) (texture=, this=0x5611d18a7b10) at
/usr/src/debug/plasma-framework-5.88.0git.20211018T112254~9f2d4dcde-ku.5.1.x86_64/src/declarativeimports/core/windowthumbnail.cpp:126
#10 Plasma::WindowThumbnail::iconToTexture(Plasma::WindowTextureProvider*)
(this=this@entry=0x5611d185afb0,
textureProvider=textureProvider@entry=0x5611d18a7b10) at
/usr/src/debug/plasma-framework-5.88.0git.20211018T112254~9f2d4dcde-ku.5.1.x86_64/src/declarativeimports/core/windowthumbnail.cpp:384
#11 0x7f93ac12ac9b in
Plasma::WindowThumbnail::windowToTexture(Plasma::WindowTextureProvider*)
(textureProvider=0x5611d18a7b10, this=0x5611d185afb0) at
/usr/src/debug/plasma-framework-5.88.0git.20211018T112254~9f2d4dcde-ku.5.1.x86_64/src/declarativeimports/core/windowthumbnail.cpp:520
#12 Plasma::WindowThumbnail::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) (this=0x5611d185afb0, oldNode=0x0,
updatePaintNodeData=) at
/usr/src/debug/plasma-framework-5.88.0git.20211018T112254~9f2d4dcde-ku.5.1.x86_64/src/declarativeimports/core/windowthumbnail.cpp:317
#13 0x7f93d22af648 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*)
(this=0x5611d0ac62b0, item=0x5611d185afb0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:3872
#14 0x7f93d22afbeb in QQuickWindowPrivate::updateDirtyNodes()
(this=this@entry=0x5611d0ac62b0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:3617
#15 0x7f93d22b17ec in QQuickWindowPrivate::syncSceneGraph()
(this=this@entry=0x5611d0ac62b0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:524
#16 0x7f93d222e389 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
(this=0x5611cf7bce30, window=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/scenegraph/qsgrenderloop.cpp:751
#17 0x7f93d22bfdaf in QQuickWindow::event(QEvent*) (this=0x5611d00d6e30,
e=0x7ffec61240b0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:1858
#18 0x7f93d151ba7f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5611d00d6e30, e=0x7ffec61240b0) at
kernel/qapplication.cpp:3632
#19 0x7f93d07859ea in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5611d00d6e30, event=0x7ffec61240b0) at
kernel/qcoreapplication.cpp:1064
#20 0x7f93d0bcd794 in QPlatformWindow::deliverUpdateRequest()
(this=) at kernel/qplatformwindow.cpp:789
#21 QPlatformWindow::windowEvent(QEvent*) (this=,
event=) at kernel/qplatformwindow.cpp:476
#22 0x7f93d1522b76 in QApplication::notify(QObject*, QEvent*)
(this=0x7ffec6124700, receiver=0x5611d00d6e30, e=0x7ffec6124340) at
kernel/qapplication.cpp:2874
#23 0x7f93d07859ea in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5611d00d6e30, event=0x7ffec6124340) at
kernel/qcoreapplication.cpp:1064
#24 0x7f93d07dc25b in QTimerInfoList::activateTimers()
(this=this@entry=0x5611cf175c20) at kernel/qtimerinfo_unix.cpp:643
#25 0x7f93d07dcb04 in timerSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=source@entry=0x5611cf175bc0) at kernel/qeventdispatcher_glib.cpp:183
#26 0x7f93ceaddd5f in g_main_dispatch (context=0x7f93c4005000) at
../glib/gmain.c:3381
#27
[plasmashell] [Bug 444014] Plasma crashes on logging into 21.10 Kubuntu Wayland desktop, every time
https://bugs.kde.org/show_bug.cgi?id=444014 geoffrey bays changed: What|Removed |Added CC||chariote...@gmail.com --- Comment #1 from geoffrey bays --- Installed Kubuntu upgrade version 21.10, then tried to login to Plasma-Wayland desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444014] New: Plasma crashes on logging into 21.10 Kubuntu Wayland desktop, every time
https://bugs.kde.org/show_bug.cgi?id=444014 Bug ID: 444014 Summary: Plasma crashes on logging into 21.10 Kubuntu Wayland desktop, every time Product: plasmashell Version: 5.23.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: chariote...@gmail.com Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. boot into Plasma-Wayland desktop from 21.10 login screen 2. 3. OBSERVED RESULT Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140210511816256) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140210511816256) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140210511816256, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f8581839476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f858181f7b7 in __GI_abort () at abort.c:79 #9 0x7f858181f6db in __assert_fail_base (fmt=0x7f85819d3770 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f857c455034 "kref", file=0x7f857c45501e "../nouveau/pushbuf.c", line=728, function=) at assert.c:92 #10 0x7f8581830e26 in __GI___assert_fail (assertion=0x7f857c455034 "kref", file=0x7f857c45501e "../nouveau/pushbuf.c", line=728, function=0x7f857c4551f0 "nouveau_pushbuf_data") at assert.c:101 #11 0x7f857c452de7 in nouveau_pushbuf_data () from /lib/x86_64-linux-gnu/libdrm_nouveau.so.2 #12 0x7f857c452d47 in nouveau_pushbuf_data () from /lib/x86_64-linux-gnu/libdrm_nouveau.so.2 #13 0x7f857c452e62 in ?? () from /lib/x86_64-linux-gnu/libdrm_nouveau.so.2 #14 0x7f857c4530c7 in ?? () from /lib/x86_64-linux-gnu/libdrm_nouveau.so.2 #15 0x7f857c453e0d in ?? () from /lib/x86_64-linux-gnu/libdrm_nouveau.so.2 #16 0x7f8576f83540 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #17 0x7f8576f9369c in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #18 0x7f85771ff61f in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #19 0x7f85767ced44 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #20 0x7f857696f6c4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #21 0x7f8576971c8c in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #22 0x7f8576971d79 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #23 0x7f858389781e in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f8583897d58 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #25 0x7f8583898138 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #26 0x7f8583894114 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #27 0x7f858387abdc in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #28 0x7f85838803a5 in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #29 0x7f8583880bd2 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #30 0x7f8583867fd4 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #31 0x7f85838684a3 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #32 0x7f85838ce2c7 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #33 0x7f858393dd19 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7f85838dcd0d in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #35 0x7f85838dd6b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #36 0x7f8581d02a71 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f858188b927 in start_thread (arg=) at pthread_create.c:435 #38 0x7f858191b9e4 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Thread 9 (Thread 0x7f854e8c9640 (LWP 1866) "QSGRenderThread"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x56045481bff4) at futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x56045481bff4, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7f858188a920 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56045481bfa0, cond=0x56045481bfc8) at pthread_cond_wait.c:504 #4 ___pthread_cond_wait (cond=0x56045481bfc8, mutex=0x56045481bfa0) at pthread_cond_wait.c:628 #5 0x7f8581d08abb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 --- Comment #10 from Joel --- Please do not close this issue...There is still a problem here. It looks like the only reason the OP was able to get digiKam started was they happened to have db files from an old digiKam installation laying around. I'm trying to install digiKam for first time on Windows 10. I'm attaching the dialog that pops up "The Sqlite core database was not found, please set the correct location in the next dialog" The next dialog allows a folder to be selected on my hard drive. However, no matter what folder I choose, it just continues to loop back to the first dialog "The sqlite core database was not found..." So it is impossible to get digiKam to open up at this moment, on a new install on Windows 10. Is there any other information I can provide that would help troubleshoot this bug? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 --- Comment #9 from Joel --- Created attachment 142599 --> https://bugs.kde.org/attachment.cgi?id=142599=edit Select sqlite database location -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 Joel changed: What|Removed |Added CC||j...@szwarga.com --- Comment #8 from Joel --- Created attachment 142598 --> https://bugs.kde.org/attachment.cgi?id=142598=edit The sqlite core database was not found -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443910] [Plasma 5.23] Black screen with totally responsive pointer and keyboard on after upgrade from 5.22.
https://bugs.kde.org/show_bug.cgi?id=443910 Alvin Smith changed: What|Removed |Added CC||alvinsmith...@gmail.com --- Comment #6 from Alvin Smith --- same issue here for Mac VMware Kali. Radeon Pro 555X 4 GB Intel UHD Graphics 630 1536 MB -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 444013] New: regression: can no longer have fullscreen project monitor on second screen
https://bugs.kde.org/show_bug.cgi?id=444013 Bug ID: 444013 Summary: regression: can no longer have fullscreen project monitor on second screen Product: kdenlive Version: git-master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: s_chriscoll...@hotmail.com Target Milestone: --- I used to be able to have the project monitor displayed fullscreen on my second screen, with the main Kdenlive application on my primary screen. Now with the current release (21.08.2, both AppImage and KDE neon packages) and daily build (kdenlive-21.11.70-020bb22-x86_64.appimage), the project/clip monitor can only be fullscreen on the primary screen, with no way to move it to the secondary screen, at least that I can find. I'm not sure in which Kdenlive version this changed, as I've been using Kdenlive on and off over the past year, but it must have been fairly recent. ## My System * OS: KDE Neon 5.23 User Edition (Plasma Desktop 5.23.0, KDE Frameworks 5.87.0, Qt 5.15.3) * Linux Kernel: 5.10.74-xanmod1 * CPU: Intel Core i7-990x Gulftown (3.46 GHz hexa-core, Socket 1366) * RAM: 24GB (6x G.Skill 4GB DDR3 PC3-10666 1333 MHz) @ 1333 MHz * Video: EVGA NVIDIA GeForce GTX 980 Ti SC GAMING ACX 2.0+ w/ 6GB RAM * NVIDIA video driver: 470.74 * Screen 1 (DVI-I-1, marked as primary): - Monitor: ASUS VG248QE 24" LCD Monitor - Resolution: 1920 x 1280 @ 120 Hz * Screen 2 (HDMI-0): - Monitor: Dell P170Sb 17" LCD Monitor - Resolution: 1280 x 1024 @ 75 Hz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444012] New: GTK apps do not respect keyboard layout on wayland session
https://bugs.kde.org/show_bug.cgi?id=444012 Bug ID: 444012 Summary: GTK apps do not respect keyboard layout on wayland session Product: plasmashell Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Input Method Assignee: plasma-b...@kde.org Reporter: i...@mikelpr.com CC: aleix...@kde.org Target Milestone: 1.0 SUMMARY annoyingly GTK apps do not respect whichever keyboard layout is set when on the wayland session STEPS TO REPRODUCE 1. set a keyboard layout different from US 2. open a GTK app like Chrome OBSERVED RESULT stays on US layout EXPECTED RESULT uses selected layout SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION my default is Spanish and it does not respect that so I don't think it uses your default and not changes when you switch but rather always uses US layout -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443852] Cannot scroll timeline horizontally
https://bugs.kde.org/show_bug.cgi?id=443852 Eoin O'Neill changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/07d7dc860 |hics/krita/commit/9c28a4633 |b51f06889826450093f68d63b78 |2b408ba5907c0da1bd51eacdef4 |8579|2108 --- Comment #5 from Eoin O'Neill --- Git commit 9c28a46332b408ba5907c0da1bd51eacdef42108 by Eoin O'Neill. Committed on 19/10/2021 at 02:19. Pushed by eoinoneill into branch 'krita/5.0'. Fixed default scrollwheel behavior on timeline to be consistent w/ old versions. Instead of scrolling up and down, the scroll wheel will continue to scrub like old versions of Krita. If you want to scroll up and down the list of pinned layers, you will want to have your mouse over the layers list instead. This should make it possible to allow both scrolling layers and scrubbing with the mouse wheel where mouse position represents "intent." (cherry picked from commit 07d7dc860b51f06889826450093f68d63b788579) M +3-2plugins/dockers/animation/KisAnimTimelineFramesView.cpp https://invent.kde.org/graphics/krita/commit/9c28a46332b408ba5907c0da1bd51eacdef42108 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444007] Swap layout when Kickoff launched in upper position
https://bugs.kde.org/show_bug.cgi?id=444007 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- We considered doing this, but we had complaints about the reversed layout, and ultimately we couldn't reverse *everything*; un-reversed search results were important for example. And hacing the header" at the bottom did look a bit weird. In the end we decided to do away with the dynamism and just use the same layout in all cases for simplicity's sake. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443852] Cannot scroll timeline horizontally
https://bugs.kde.org/show_bug.cgi?id=443852 --- Comment #4 from Eoin O'Neill --- Hi again Dan, I just want you to know that I've gone ahead and made the behavior closer to the original scroll behavior in krita 4, where scrubbing should occur when using the mouse wheel. I believe this is the source of your issues in the case of trying to use two-finger scrolling, so I think this issue is resolved now. However, There's something that is still different than Krita 4 that you should be aware of; In order to fix another bug where it was difficult to scroll up and down the pinned layer list, the scroll wheel can also scroll the view up and down based on the current mouse position. Basically, if your mouse is over any of the pinned layer entries, scrolling the mouse wheel will instead scroll you up and down. This should be better than the current design, where the shift key had to be pressed down in order to scrub horiztonally since it is more consistent with older versions of Krita. So try the latest nightly in a few days and see if this issue is resolved. If problems persist, feel free to reopen the issue and provide some extra details. Thanks for taking the time to report a bug! Eoin. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click
https://bugs.kde.org/show_bug.cgi?id=443882 --- Comment #9 from Emmanuel --- Maybe a correct bug would be about the possibly missing documentation that would explain the way it works. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click
https://bugs.kde.org/show_bug.cgi?id=443882 --- Comment #8 from Emmanuel --- Ok. If it's not a bug, I see it as a lost feature. My solution was initially to downgrade to okular version 21.04.3 for which popup menu work in both mode, till someone told me that I had to use a browse mode in order to do things related with annotation instead of text selection. I don't find that very intuitive or practical. It raises the question of how people will learn this new restriction for annotation. -- You are receiving this mail because: You are watching all bug changes.
[kiten] [Bug 444008] Radical selector results do not dynamically reflow
https://bugs.kde.org/show_bug.cgi?id=444008 --- Comment #1 from Yaman Qalieh <1kdebugtrac...@qalieh.com> --- Better SUMMARY: When horizontally resizing the radical selector window, search results do not reflow into the new space or lack of space. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443852] Cannot scroll timeline horizontally
https://bugs.kde.org/show_bug.cgi?id=443852 Eoin O'Neill changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/07d7dc860 ||b51f06889826450093f68d63b78 ||8579 --- Comment #3 from Eoin O'Neill --- Git commit 07d7dc860b51f06889826450093f68d63b788579 by Eoin O'Neill. Committed on 19/10/2021 at 02:08. Pushed by eoinoneill into branch 'master'. Fixed default scrollwheel behavior on timeline to be consistent w/ old versions. Instead of scrolling up and down, the scroll wheel will continue to scrub like old versions of Krita. If you want to scroll up and down the list of pinned layers, you will want to have your mouse over the layers list instead. This should make it possible to allow both scrolling layers and scrubbing with the mouse wheel where mouse position represents "intent." M +3-2plugins/dockers/animation/KisAnimTimelineFramesView.cpp https://invent.kde.org/graphics/krita/commit/07d7dc860b51f06889826450093f68d63b788579 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 guimarcalsi...@gmail.com changed: What|Removed |Added CC||guimarcalsi...@gmail.com --- Comment #13 from guimarcalsi...@gmail.com --- Hi. I'm not sure if my issue is completely related to this one, but on Neon after suspending and come=ing back plasmashell doesn't get loaded. If I press ALT+F2 I can summon Krunner and type "plasmashell" and things go back to normal. I'm on a Wayland session and my kernel is 5.11. I'm on Plasma 5.23 too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443852] Cannot scroll timeline horizontally
https://bugs.kde.org/show_bug.cgi?id=443852 --- Comment #2 from Eoin O'Neill --- Hi Dan, Just to get more details, when you are talking about scrolling, do you mean scrolling with the mouse wheel (or simulated using 2 button scrolling?) or are you unable to move the scroll bar at the bottom of the timeline at all? Because I can confirm that the scroll-wheel does seem to have a regression where the time no longer scrubs as expected which I will work to solve. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444011] New: cursor huge under wayland
https://bugs.kde.org/show_bug.cgi?id=444011 Bug ID: 444011 Summary: cursor huge under wayland Product: kwin Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: i...@mikelpr.com Target Milestone: --- SUMMARY the cursor is huge when under wayland STEPS TO REPRODUCE 1. open the wayland session OBSERVED RESULT huge cursor EXPECTED RESULT normal sized cursor SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION this has happened in all previous versions of the plasma wayland session I tried but I'm finally filling the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444010] New: port slider effect to realtime gestures
https://bugs.kde.org/show_bug.cgi?id=444010 Bug ID: 444010 Summary: port slider effect to realtime gestures Product: kwin Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: i...@mikelpr.com Target Milestone: --- SUMMARY sliding between desktops (horizontal) still lacks realtime gestures STEPS TO REPRODUCE 1. drag 4 fingers sideways OBSERVED RESULT desktop slides until you release the fingers EXPECTED RESULT sliding follows fingers gliding SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION the Desktop Grid effect does have them but it's much less useful for switching fast (but both need them realtime gestures, not one or the other) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444009] New: Applications can be triggered by clicking in the top left corner of the screen on Wayland
https://bugs.kde.org/show_bug.cgi?id=444009 Bug ID: 444009 Summary: Applications can be triggered by clicking in the top left corner of the screen on Wayland Product: plasmashell Version: 5.23.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mistrasser...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 142597 --> https://bugs.kde.org/attachment.cgi?id=142597=edit Offending area highlighted. SUMMARY Under Wayland, if System Tray is present and any application is present in the System Tray upon login, in the top left corner of the screen there'll be a small, invisible area in the shape of a square that if clicked on, will trigger an application found in System Tray. Your cursor might change when you hover over the offending area. It happens regardless of the panel's size, height, and edge. Clicking several things in the System Tray, or closing all applications in the System Tray makes it stop. STEPS TO REPRODUCE 1. Prerequisites: Have System Tray but avoid having it near our area of interest, which is the top left corner of the screen. Ensure that you have a startup application that hides in the tray. 2. Log to a Wayland session without touching the System Tray. 3. Do a single click in the top left corner. If nothing happens, try adjusting the pointer to in all directions slightly while continuously clicking. OBSERVED RESULT An application will trigger as if it was clicked over on the actual system tray's location. EXPECTED RESULT There shouldn't be any clickable area in the top left corner of the screen with this widget under Wayland. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Garuda Linux (available in About System) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Applications that I have on Autostart are Caprine, Discord, MEGAsync, Flameshot, Latte, Yakuake, Signal, Steam and Xtreme Download Manager. In the attached screenshot I tried to highlight the offending area. -- You are receiving this mail because: You are watching all bug changes.
[kiten] [Bug 444008] New: Radical selector results do not dynamically reflow
https://bugs.kde.org/show_bug.cgi?id=444008 Bug ID: 444008 Summary: Radical selector results do not dynamically reflow Product: kiten Version: 21.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jker...@gmail.com Reporter: 1kdebugtrac...@qalieh.com Target Milestone: --- Created attachment 142596 --> https://bugs.kde.org/attachment.cgi?id=142596=edit Observed result when resizing after results appear SUMMARY When resizing the STEPS TO REPRODUCE 1. Make a partial search (i.e. select a radical) so that results appear 2. Expand the width of the radical selector window OBSERVED RESULT Results stay in the same area as original window size (see attachment). EXPECTED RESULT Results should expand to fill empty area. SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443506] Not all icons update when a new Plasma Theme is applied that contains them
https://bugs.kde.org/show_bug.cgi?id=443506 --- Comment #2 from doncb...@gmail.com --- (In reply to Nate Graham from comment #1) > I have periodically seem this as well. > > Are you seeing that it only affects System Tray icons, or other > Plasma-themed icons elsewhere too? While I haven't gone out of my way to test every single configuration, I know the sticky notes widget also has this issue. Since few themers will be looking through source code to see which icon is used where, it can be a bit difficult finding themes that contain the icons. The ChromeOS theme has [knotes.svg?], so you can view the icon not being changed in sticky notes until you replace plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 Matthew Oros changed: What|Removed |Added CC||orosmatt...@protonmail.com --- Comment #20 from Matthew Oros --- I am having the same issue however, windows will seem to minimize to whichever task manager I last interacted with. For example, if I were to unpin and pin a random icon in the task manager on my left (secondary) monitor then all minimize window animations will go to that screen and if I unpin and pin on my right (primary) monitor, they will always animate to minimize there. Although, sometimes this randomly gets swapped every now and then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444007] New: Swap layout when Kickoff launched in upper position
https://bugs.kde.org/show_bug.cgi?id=444007 Bug ID: 444007 Summary: Swap layout when Kickoff launched in upper position Product: plasmashell Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: gudv...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In Plasma 5.23 Kickoff buttons were moved to the bottom. While it might be a good solution for default panel placement, it was convenient to use when Kickoff is opened sticked to the top. Now instead of making less movement you need to make more. I suggest to either swap switchers when Kickoff at the top or make it configurable. STEPS TO REPRODUCE 1. Open Kickoff at the top left corner OBSERVED RESULT Observe layout inconvenient to use in this position EXPECTED RESULT Layout more useful in this position SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.12-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 443983] khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 Friedrich W. H. Kossebau changed: What|Removed |Added Version Fixed In||21.08.3 CC||kosse...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 443983] khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 Friedrich W. H. Kossebau changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/kio-extras/commit/80986 ||3617a3fb76ce43f11dec541d4b9 ||4f63925a --- Comment #7 from Friedrich W. H. Kossebau --- Git commit 809863617a3fb76ce43f11dec541d4b94f63925a by Friedrich W. H. Kossebau. Committed on 19/10/2021 at 00:24. Pushed by kossebau into branch 'release/21.08'. man kio: fix crash due to bad memory pointer on REQ_ps handling 7d11a0932af2379cd46d338c49f758bc509acec7 accidentally moved the memory pointer increase out of the '+'-handling branch, which would either result in bad number being read or the pointer getting behind the end and resulting in garbage memory processing, potentially ending in a crash. Also changing to using dedicated own variable "sign" instead of reusing function-global variable "j" with meaningless name. global Fixed-in: 21.08.3 M +9-8man/man2html.cpp https://invent.kde.org/network/kio-extras/commit/809863617a3fb76ce43f11dec541d4b94f63925a -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 443037] Kontact Crashed When Starting
https://bugs.kde.org/show_bug.cgi?id=443037 --- Comment #1 from john4deidre2...@xtra.co.nz --- Created attachment 142595 --> https://bugs.kde.org/attachment.cgi?id=142595=edit New crash information added by DrKonqi kontact (5.18.2 (21.08.2)) using Qt 5.15.2 - What I was doing when the application crashed: When you intermittently start kontact it will crash with a seqfault. this is still happening with the most recent stable version of the kde pim -- Backtrace (Reduced): #6 0x7f0f6c97ea75 in QScopedPointer >::operator-> (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 [...] #9 QAction::setText (this=this@entry=0x0, text=...) at kernel/qaction.cpp:714 #10 0x7f0f059b5f8a in KMMainWidget::updateFolderMenu (this=0x556cac5103b0) at /usr/src/debug/kmail-21.08.2-1.1.x86_64/src/kmmainwidget.cpp:3996 #11 0x7f0f059ad746 in KMMainWidget::setupActions (this=0x556cac5103b0) at /usr/src/debug/kmail-21.08.2-1.1.x86_64/src/kmmainwidget.cpp:3384 #12 0x7f0f05997c14 in KMMainWidget::KMMainWidget (this=, parent=, aGUIClient=, actionCollection=, config=..., this=, parent=, aGUIClient=, actionCollection=, config=...) at /usr/src/debug/kmail-21.08.2-1.1.x86_64/src/kmmainwidget.cpp:249 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 443037] Kontact Crashed When Starting
https://bugs.kde.org/show_bug.cgi?id=443037 john4deidre2...@xtra.co.nz changed: What|Removed |Added CC||john4deidre2...@xtra.co.nz -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444004] New: formattest segmentation fault
https://bugs.kde.org/show_bug.cgi?id=444004
Bug ID: 444004
Summary: formattest segmentation fault
Product: okular
Version: 21.08.2
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: tel...@posteo.de
Target Milestone: ---
Application: okular (5.18.2 (21.08.2))
(Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.12-gentoo-dist x86_64
Windowing System: X11
Distribution: Gentoo Linux
DrKonqi: 5.23.0 [KCrashBackend]
Compiler: Clang 13.0.0
C{,XX}FLAGS: -march=znver2 -O3 -glldb -fPIC -fstack-protector-strong
-D_FORTIFY_SOURCE=2 -pipe
-- Information about the crash:
- What I was doing when the application crashed:
Running tests.
The crash can be reproduced every time.
-- Backtrace:
Application: formattest (formattest), signal: Segmentation fault
[KCrash Handler]
#4 KJS::JSCell::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:319
#5 KJS::JSValue::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:377
#6 KJS::JSObject::put (this=0x7f8b15b809c0, exec=0x558841946d80,
propertyName=..., value=0x7f8b15b80a00, attr=4) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/object.cpp:247
#7 0x7f8b1a35ea98 in KJS::ErrorPrototype::ErrorPrototype
(this=0x7f8b15b809c0, exec=0x558841946d80, objectProto=,
funcProto=0x7f8b15b800c0) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/error_object.cpp:53
#8 0x7f8b1a3680fc in KJS::Interpreter::initGlobalObject
(this=0x558841946d60) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/interpreter.cpp:385
#9 0x7f8b1bdd35ff in KJSInterpreter::KJSInterpreter (this=0x5588419f4f90,
global=...) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/api/kjsinterpreter.cpp:111
#10 0x7f8b1d2fe5f9 in Okular::ExecutorKJSPrivate::initTypes
(this=this@entry=0x5588419f4a40) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:60
#11 0x7f8b1d2fe94c in Okular::ExecutorKJSPrivate::ExecutorKJSPrivate
(this=0x5588419f4a40, doc=0x5588418e8f90) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:43
#12 Okular::ExecutorKJS::ExecutorKJS (this=0x5588419f48e0, doc=0x5588418e8f90)
at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:89
#13 0x7f8b1d2c6deb in Okular::Scripter::execute (this=0x5588419f48a0,
type=Okular::JavaScript, script=...) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/scripter.cpp:65
#14 0x7f8b1d29bae7 in Okular::DocumentPrivate::executeScriptEvent
(this=0x5588418e8f90, event=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 1, weak count 0) = {...},
linkscript=linkscript@entry=0x5588419eab60) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/document.cpp:2110
#15 0x7f8b1d2937e2 in Okular::Document::processFormatAction
(this=0x5588418e1dd0, action=0x5588419eab60, fft=0x5588419ea0b0) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/document.cpp:4062
#16 0x5588407b8033 in FormatTest::testTimeFormat
(this=this@entry=0x7ffd9d2a0fa8) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/autotests/formattest.cpp:77
#17 0x5588407b9f58 in FormatTest::qt_static_metacall
(_o=_o@entry=0x7ffd9d2a0fa8, _c=1100246400,
_c@entry=QMetaObject::InvokeMetaMethod, _id=1100874952, _id@entry=2,
_a=) at autotests/formattest_autogen/include/formattest.moc:104
#18 0x7f8b1ca6c4ff in QMetaMethod::invoke (this=0x5588418e28b0,
object=0x7ffd9d2a0fa8, connectionType=, returnValue=...,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.cpp:2303
#19 0x7f8b1d33cd5d in QMetaMethod::invoke (this=,
object=0x558841946d80, object@entry=0x0, connectionType=Qt::DirectConnection,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.h:122
#20 QTest::TestMethods::invokeTestOnData (this=this@entry=0x7ffd9d2a0e80,
index=index@entry=0) at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:938
#21 0x7f8b1d33d7d8 in QTest::TestMethods::invokeTest
(this=this@entry=0x7ffd9d2a0e80, index=index@entry=0, data=data@entry=0x0,
watchDog=watchDog@entry=0x5588418e1e80) at
[okular] [Bug 444006] New: calculatetexttest segmentation fault
https://bugs.kde.org/show_bug.cgi?id=444006
Bug ID: 444006
Summary: calculatetexttest segmentation fault
Product: okular
Version: 21.08.2
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: tel...@posteo.de
Target Milestone: ---
Application: okular (5.18.2 (21.08.2))
(Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.12-gentoo-dist x86_64
Windowing System: X11
Distribution: Gentoo Linux
DrKonqi: 5.23.0 [KCrashBackend]
Compiler: Clang 13.0.0
C{,XX}FLAGS: -march=znver2 -O3 -glldb -fPIC -fstack-protector-strong
-D_FORTIFY_SOURCE=2 -pipe
-- Information about the crash:
- What I was doing when the application crashed:
Running tests.
The crash can be reproduced every time.
-- Backtrace:
Application: calculatetexttest (calculatetexttest), signal: Segmentation fault
[KCrash Handler]
#4 KJS::JSCell::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:319
#5 KJS::JSValue::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:377
#6 KJS::JSObject::put (this=0x7f67955e09c0, exec=0x55edf76d1cf0,
propertyName=..., value=0x7f67955e0a00, attr=4) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/object.cpp:247
#7 0x7f6799dc4a98 in KJS::ErrorPrototype::ErrorPrototype
(this=0x7f67955e09c0, exec=0x55edf76d1cf0, objectProto=,
funcProto=0x7f67955e00c0) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/error_object.cpp:53
#8 0x7f6799dce0fc in KJS::Interpreter::initGlobalObject
(this=0x55edf76d1cd0) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/interpreter.cpp:385
#9 0x7f679b8395ff in KJSInterpreter::KJSInterpreter (this=0x55edf774d300,
global=...) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/api/kjsinterpreter.cpp:111
#10 0x7f679cd645f9 in Okular::ExecutorKJSPrivate::initTypes
(this=this@entry=0x55edf774c3a0) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:60
#11 0x7f679cd6494c in Okular::ExecutorKJSPrivate::ExecutorKJSPrivate
(this=0x55edf774c3a0, doc=0x55edf76744a0) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:43
#12 Okular::ExecutorKJS::ExecutorKJS (this=0x55edf774c990, doc=0x55edf76744a0)
at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:89
#13 0x7f679cd2cdeb in Okular::Scripter::execute (this=0x55edf774c870,
type=Okular::JavaScript, script=...) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/scripter.cpp:65
#14 0x7f679ccf8d15 in Okular::Document::processAction (this=0x55edf766cbf0,
action=action@entry=0x55edf774b0d0) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/document.cpp:4012
#15 0x7f679ccf8553 in Okular::DocumentPrivate::recalculateForms
(this=0x55edf76744a0) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/document.cpp:1139
#16 0x7f679cd1e669 in Okular::EditFormTextCommand::redo
(this=0x55edf774c2e0) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/documentcommands.cpp:451
#17 0x7f679cc0b0de in QUndoStack::push(QUndoCommand*) () from
/usr/lib64/libQt5Widgets.so.5
#18 0x7f679cd09c14 in Okular::Document::editFormText (this=,
pageNumber=, form=0x55edf772c600, newContents=...,
newCursorPos=, prevCursorPos=,
prevAnchorPos=) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/document.cpp:3748
#19 0x55edf6dcdef6 in CalculateTextTest::testSimpleCalculate
(this=this@entry=0x7ffcb86c1658) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/autotests/calculatetexttest.cpp:72
#20 0x55edf6dce9ad in CalculateTextTest::qt_static_metacall
(_o=_o@entry=0x7ffcb86c1658, _c=4151123184,
_c@entry=QMetaObject::InvokeMetaMethod, _id=-143460120, _id@entry=2,
_a=) at
autotests/calculatetexttest_autogen/include/calculatetexttest.moc:80
#21 0x7f679c4d24ff in QMetaMethod::invoke (this=0x55edf7669c30,
object=0x7ffcb86c1658, connectionType=, returnValue=...,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.cpp:2303
#22 0x7f679cda2d5d in QMetaMethod::invoke (this=,
object=0x55edf76d1cf0, object@entry=0x0, connectionType=Qt::DirectConnection,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.h:122
#23 QTest::TestMethods::invokeTestOnData (this=this@entry=0x7ffcb86c1520,
index=index@entry=0) at
[okular] [Bug 444005] New: visibilitytest segmentation fault
https://bugs.kde.org/show_bug.cgi?id=444005
Bug ID: 444005
Summary: visibilitytest segmentation fault
Product: okular
Version: 21.08.2
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: tel...@posteo.de
Target Milestone: ---
Application: okular (5.18.2 (21.08.2))
(Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.12-gentoo-dist x86_64
Windowing System: X11
Distribution: Gentoo Linux
DrKonqi: 5.23.0 [KCrashBackend]
Compiler: Clang 13.0.0
C{,XX}FLAGS: -march=znver2 -O3 -glldb -fPIC -fstack-protector-strong
-D_FORTIFY_SOURCE=2 -pipe
-- Information about the crash:
- What I was doing when the application crashed:
Running tests.
The crash can be reproduced every time.
-- Backtrace:
Application: visibilitytest (visibilitytest), signal: Segmentation fault
[KCrash Handler]
#4 KJS::JSCell::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:319
#5 KJS::JSValue::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:377
#6 KJS::JSObject::put (this=0x7f9b588509c0, exec=0x559bece21040,
propertyName=..., value=0x7f9b58850a00, attr=4) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/object.cpp:247
#7 0x7f9b5d039a98 in KJS::ErrorPrototype::ErrorPrototype
(this=0x7f9b588509c0, exec=0x559bece21040, objectProto=,
funcProto=0x7f9b588500c0) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/error_object.cpp:53
#8 0x7f9b5d0430fc in KJS::Interpreter::initGlobalObject
(this=0x559bece21020) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/interpreter.cpp:385
#9 0x7f9b5eaae5ff in KJSInterpreter::KJSInterpreter (this=0x559bece21000,
global=...) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/api/kjsinterpreter.cpp:111
#10 0x7f9b5ffd95f9 in Okular::ExecutorKJSPrivate::initTypes
(this=this@entry=0x559bece20710) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:60
#11 0x7f9b5ffd994c in Okular::ExecutorKJSPrivate::ExecutorKJSPrivate
(this=0x559bece20710, doc=0x559becd3c400) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:43
#12 Okular::ExecutorKJS::ExecutorKJS (this=0x559bece20610, doc=0x559becd3c400)
at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:89
#13 0x7f9b5ffa1deb in Okular::Scripter::execute (this=0x559bece205d0,
type=Okular::JavaScript, script=...) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/scripter.cpp:65
#14 0x7f9b5ff6dd15 in Okular::Document::processAction (this=0x559becd43320,
action=0x559bece1e890) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/document.cpp:4012
#15 0x559beaf0825f in VisibilityTest::testJavaScriptVisibility
(this=0x7ffddb979200) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/autotests/visibilitytest.cpp:92
#16 0x7f9b5f7474ff in QMetaMethod::invoke (this=0x559becd42ad0,
object=0x7ffddb979200, connectionType=, returnValue=...,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.cpp:2303
#17 0x7f9b60017d5d in QMetaMethod::invoke (this=,
object=0x559bece21040, object@entry=0x0, connectionType=Qt::DirectConnection,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.h:122
#18 QTest::TestMethods::invokeTestOnData (this=this@entry=0x7ffddb9790e0,
index=index@entry=0) at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:938
#19 0x7f9b600187d8 in QTest::TestMethods::invokeTest
(this=this@entry=0x7ffddb9790e0, index=index@entry=0, data=data@entry=0x0,
watchDog=watchDog@entry=0x559becd427d0) at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1166
#20 0x7f9b6001970a in QTest::TestMethods::invokeTests
(this=this@entry=0x7ffddb9790e0, testObject=0x7ffddb979200) at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1507
#21 0x7f9b60019d55 in QTest::qRun () at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1934
#22 0x7f9b60019a1e in QTest::qExec
(testObject=testObject@entry=0x7ffddb979200, argc=,
argv=argv@entry=0x7ffddb979348) at
[okular] [Bug 444003] New: kjsfunctionstest segmentation fault
https://bugs.kde.org/show_bug.cgi?id=444003
Bug ID: 444003
Summary: kjsfunctionstest segmentation fault
Product: okular
Version: 21.08.2
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: tel...@posteo.de
Target Milestone: ---
Application: okular (5.18.2 (21.08.2))
(Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.12-gentoo-dist x86_64
Windowing System: X11
Distribution: Gentoo Linux
DrKonqi: 5.23.0 [KCrashBackend]
Compiler: Clang 13.0.0
C{,XX}FLAGS: -march=znver2 -O3 -glldb -fPIC -fstack-protector-strong
-D_FORTIFY_SOURCE=2 -pipe
-- Information about the crash:
- What I was doing when the application crashed:
Running tests.
The crash can be reproduced every time.
-- Backtrace:
Application: kjsfunctionstest (kjsfunctionstest), signal: Segmentation fault
[KCrash Handler]
#4 KJS::JSCell::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:319
#5 KJS::JSValue::isObject (this=0x3) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/value.h:377
#6 KJS::JSObject::put (this=0x7f41e68d09c0, exec=0x559956d1fe20,
propertyName=..., value=0x7f41e68d0a00, attr=4) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/object.cpp:247
#7 0x7f41eb0b2a98 in KJS::ErrorPrototype::ErrorPrototype
(this=0x7f41e68d09c0, exec=0x559956d1fe20, objectProto=,
funcProto=0x7f41e68d00c0) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/error_object.cpp:53
#8 0x7f41eb0bc0fc in KJS::Interpreter::initGlobalObject
(this=0x559956d1fe00) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/interpreter.cpp:385
#9 0x7f41ecb275ff in KJSInterpreter::KJSInterpreter (this=0x559956d1fde0,
global=...) at
/usr/src/debug/kde-frameworks/kjs-5.87.0/kjs-5.87.0/src/kjs/api/kjsinterpreter.cpp:111
#10 0x7f41ee0525f9 in Okular::ExecutorKJSPrivate::initTypes
(this=this@entry=0x559956d1f910) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:60
#11 0x7f41ee05294c in Okular::ExecutorKJSPrivate::ExecutorKJSPrivate
(this=0x559956d1f910, doc=0x559956c36060) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:43
#12 Okular::ExecutorKJS::ExecutorKJS (this=0x559956d1f7c0, doc=0x559956c36060)
at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/script/executor_kjs.cpp:89
#13 0x7f41ee01adeb in Okular::Scripter::execute (this=0x559956d1f780,
type=Okular::JavaScript, script=...) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/scripter.cpp:65
#14 0x7f41edfe6d15 in Okular::Document::processAction (this=0x559956c2e730,
action=0x559956d1e680) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/core/document.cpp:4012
#15 0x5599569b4bdb in KJSFunctionsTest::testNthFieldName
(this=0x7ffea87a03a0) at
/var/tmp/portage/kde-apps/okular-21.08.2/work/okular-21.08.2/autotests/kjsfunctionstest.cpp:124
#16 0x7f41ed7c04ff in QMetaMethod::invoke (this=0x559956c2ec80,
object=0x7ffea87a03a0, connectionType=, returnValue=...,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.cpp:2303
#17 0x7f41ee090d5d in QMetaMethod::invoke (this=,
object=0x559956d1fe20, object@entry=0x0, connectionType=Qt::DirectConnection,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at
../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qmetaobject.h:122
#18 QTest::TestMethods::invokeTestOnData (this=this@entry=0x7ffea87a0280,
index=index@entry=0) at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:938
#19 0x7f41ee0917d8 in QTest::TestMethods::invokeTest
(this=this@entry=0x7ffea87a0280, index=index@entry=0, data=data@entry=0x0,
watchDog=watchDog@entry=0x559956c2e750) at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1166
#20 0x7f41ee09270a in QTest::TestMethods::invokeTests
(this=this@entry=0x7ffea87a0280, testObject=0x7ffea87a03a0) at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1507
#21 0x7f41ee092d55 in QTest::qRun () at
/usr/src/debug/dev-qt/qttest-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/testlib/qtestcase.cpp:1934
#22 0x7f41ee092a1e in QTest::qExec
(testObject=testObject@entry=0x7ffea87a03a0, argc=,
argv=argv@entry=0x7ffea87a04e8) at
[amarok] [Bug 141991] custom metadata readout and creation (id3v2)
https://bugs.kde.org/show_bug.cgi?id=141991 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #13 from Eric S --- If this were implemented would the ability to search on such custom fields automatically come with it, or should that be another feature request? I'd love to be able to search by conductor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443546] Plasma wayland renders inverted colors in window previews
https://bugs.kde.org/show_bug.cgi?id=443546 kassindornelles changed: What|Removed |Added Platform|Archlinux Packages |openSUSE RPMs Version|5.22.90 |5.23.0 --- Comment #2 from kassindornelles --- i can confirm it's still broken, i tested first on arch and now opensuse tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #178 from Nick Stefanov --- I'm on Plasma 5.23 and it doesn't work for me as well. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 119539] Request: Support for multiple genres / artists / composers / etc.
https://bugs.kde.org/show_bug.cgi?id=119539 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #61 from Eric S --- Use of slash (/) is very common for separating multiple artist names also, e.g. "Alice / Bob" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 --- Comment #3 from Quartz --- ** This issue also occurs on the Task Manager (not just the icons only widget) taskbar widget when items are grouped. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #177 from Uwe Dippel --- (Think my comment was gone as well, sorry if it pops up twice) Confirmed. Doesn't work here. Have attached three screenshots: Layout before switching (2560x1440) (I left out the mess after switching to 1440x900) Layout after rearranging the icons on the smaller screen Messed up layout after switching back to 2560x1440 Here are the files, for double confirmation (.orig is the one I saved from the original install): -rw-r--r-- 1 root root 14050 Okt 19 00:19 FolderViewLayer.qml -rw-r--r-- 1 root root 14169 Okt 19 00:19 FolderViewLayer.qml.orig I am on Plasma 5.18.5 (20_04); just for information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #176 from Uwe Dippel --- Created attachment 142594 --> https://bugs.kde.org/attachment.cgi?id=142594=edit Back to the original desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #175 from Uwe Dippel --- Created attachment 142593 --> https://bugs.kde.org/attachment.cgi?id=142593=edit Scaled down and rearranged -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444002] New: Akonadi Crash when adding Google Groupware
https://bugs.kde.org/show_bug.cgi?id=444002 Bug ID: 444002 Summary: Akonadi Crash when adding Google Groupware Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: justin.zo...@gmail.com Target Milestone: --- Application: akonadi_google_resource (5.17.3 (21.04.3)) Qt Version: 5.15.2 Frameworks Version: 5.87.0 Operating System: Linux 5.14.11-300.fc35.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: "Fedora release 35 (Thirty Five)" -- Information about the crash: Crash after adding Google Groupware account The crash can be reproduced every time. -- Backtrace: Application: Google Groupware (not configured) (akonadi_google_resource), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fcb5742b940 (LWP 436291))] [KCrash Handler] #6 0x7fcb5eb6c164 in std::default_delete::operator()(QTcpServer*) const (__ptr=0x561c2916d580, this=) at /usr/include/c++/11/bits/unique_ptr.h:79 #7 std::unique_ptr >::~unique_ptr() (this=0x561c29643bc8, __in_chrg=) at /usr/include/c++/11/bits/unique_ptr.h:361 #8 KGAPI2::FullAuthenticationJob::Private::~Private() (this=0x561c29643ba0, __in_chrg=) at /usr/src/debug/libkgapi-21.04.3-1.fc35.x86_64/src/core/private/fullauthenticationjob.cpp:30 #9 QScopedPointerDeleter::cleanup(KGAPI2::FullAuthenticationJob::Private*) (pointer=0x561c29643ba0) at /usr/include/qt5/QtCore/qscopedpointer.h:60 #10 QScopedPointerDeleter::cleanup(KGAPI2::FullAuthenticationJob::Private*) (pointer=0x561c29643ba0) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #11 QScopedPointer >::~QScopedPointer() (this=0x561c293eedc8, __in_chrg=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #12 KGAPI2::FullAuthenticationJob::~FullAuthenticationJob() (this=0x561c293eedb0, __in_chrg=) at /usr/src/debug/libkgapi-21.04.3-1.fc35.x86_64/src/core/private/fullauthenticationjob.cpp:160 #13 0x7fcb5eb6c26d in KGAPI2::FullAuthenticationJob::~FullAuthenticationJob() (this=0x561c293eedb0, __in_chrg=) at /usr/src/debug/libkgapi-21.04.3-1.fc35.x86_64/src/core/private/fullauthenticationjob.cpp:160 #14 0x7fcb5d9e378a in QObjectPrivate::deleteChildren() (this=this@entry=0x561c29650fe0) at kernel/qobject.cpp:2104 #15 0x7fcb5d9eb08c in QObject::~QObject() (this=0x561c296510b0, __in_chrg=) at kernel/qobject.cpp:1082 #16 0x7fcb5eb78fcd in KGAPI2::AuthJob::~AuthJob() (this=0x561c296510b0, __in_chrg=) at /usr/src/debug/libkgapi-21.04.3-1.fc35.x86_64/src/core/authjob.cpp:60 #17 0x7fcb5d9e378a in QObjectPrivate::deleteChildren() (this=this@entry=0x561c29094510) at kernel/qobject.cpp:2104 #18 0x7fcb5e5c6556 in QWidget::~QWidget() (this=this@entry=0x561c2916cdf0, __in_chrg=) at kernel/qwidget.cpp:1522 #19 0x7fcb5e796e1e in QDialog::~QDialog() (this=this@entry=0x561c2916cdf0, __in_chrg=) at dialogs/qdialog.cpp:426 #20 0x561c27406273 in GoogleSettingsDialog::~GoogleSettingsDialog() (this=0x561c2916cdf0, __in_chrg=) at /usr/src/debug/kdepim-runtime-21.04.3-1.fc35.x86_64/resources/google-groupware/googlesettingsdialog.cpp:85 #21 GoogleSettingsDialog::~GoogleSettingsDialog() (this=0x561c2916cdf0, __in_chrg=) at /usr/src/debug/kdepim-runtime-21.04.3-1.fc35.x86_64/resources/google-groupware/googlesettingsdialog.cpp:85 #22 0x7fcb5f35ba73 in Akonadi__ControlAdaptor::qt_metacall(QMetaObject::Call, int, void**) (this=0x7fcb38004f40, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7ffe741277b0) at /usr/src/debug/kf5-akonadi-server-21.04.3-1.fc35.x86_64/redhat-linux-build/src/agentbase/controladaptor.moc:176 #23 0x7fcb5dcc91eb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) (this=, object=, msg=, metaTypes=, slotIdx=) at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190 #24 0x7fcb5dcccf07 in QDBusConnectionPrivate::activateCall(QObject*, int, QDBusMessage const&) (this=this@entry=0x7fcb3c003a00, object=0x7fcb38004f40, flags=flags@entry=273, msg=...) at qdbusintegrator.cpp:911 #25 0x7fcb5dccd649 in QDBusConnectionPrivate::activateCall(QObject*, int, QDBusMessage const&) (msg=..., flags=273, object=, this=0x7fcb3c003a00) at qdbusintegrator.cpp:853 #26 QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&, QDBusMessage const&, int) (this=0x7fcb3c003a00, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1497 #27 0x7fcb5dccf9fc in QDBusActivateObjectEvent::placeMetaCall(QObject*) (this=0x561c293f16e0) at qdbusintegrator.cpp:1617 #28 0x7fcb5d9e4f09 in QObject::event(QEvent*) (this=0x7ffe74127e60, e=0x561c293f16e0) at kernel/qobject.cpp:1314 #29 0x7fcb5e588443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7ffe74127e60, e=0x561c293f16e0)
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 --- Comment #2 from Quartz --- Machine is not thrashing or under performance load for this to occur. It occurs under normal circumstances. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #174 from Uwe Dippel --- Created attachment 142592 --> https://bugs.kde.org/attachment.cgi?id=142592=edit Original layout -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 443845] Database won't load after update to Kubuntu 21.10/Tellico 3.4.1
https://bugs.kde.org/show_bug.cgi?id=443845 --- Comment #6 from Robby Stephenson --- (In reply to Jim Sanderson from comment #4) > (In reply to Robby Stephenson from comment #2) > > Could you email me the data file privately (or attach it here if you're ok > > with that)? I'd like to figure out why the difference myself and fix it. > > The file is 9.6 MB (compressed). Will your e-mail accept that? Or would > you just like the offending record? I guess the images are included in the file? The offending record would be enough, I think. I can copy it into a Tellico 3.3 file and then see what happens in the 3.4 load. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 --- Comment #1 from Quartz --- Workflow, especially with multiple windows gets slowed down and gives overall poor usability and experience. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438273] Titlebar colors not changed correctly when switching from a header-color-using color scheme to a non-header-color-using color scheme
https://bugs.kde.org/show_bug.cgi?id=438273 --- Comment #8 from Nate Graham --- Next challenge is to find the actual piece of code that reads kdeglobals and applies the color scheme there to apps. Something in there is broken but I can't find where the code lives... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 Quartz changed: What|Removed |Added Keywords||accessibility, efficiency, ||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443819] Ctrl+Scroll to zoom is incompatible with inertia touchpads
https://bugs.kde.org/show_bug.cgi?id=443819 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||aa...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- This is exactly what it is supposed to do, i don't understand why it should not do that? Don't press Ctrl if you don't want to change the zoom? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] New: Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 Bug ID: 444001 Summary: Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows. Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: thomwalker...@mail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When having more than 3-5 windows (of the same type) open on the taskbar and they get grouped together [such as 15 firefox windows minimized]... ...shine hover animation becomes evidently and noticeably impacted framerate wise and the cursor, as well as the icon itself starts to stagger. STEPS TO REPRODUCE 1. Open 10, 20 or more windows of the same program (in my case, it was firefox) 2. Let them group. 3. While having other running programs, attempt to hover left and right between each and observe what happens when going over the program with lots of grouped windows. OBSERVED RESULT Slow, staggered animation, possibly even slowed cursor? Unnatural animation transition. Becomes an annoyance when working with multiple windows. EXPECTED RESULT Smooth animation transition between icons on the taskbar without staggering. SOFTWARE/OS VERSIONS OS: Manjaro Linux x86_64 Host: TUF Gaming FX505DY_FX505DY 1.0 Kernel: 5.13.19-2-MANJARO Uptime: 3 hours, 23 mins Packages: 1548 (pacman), 4 (flatpak) Shell: bash 5.1.8 Resolution: 1920x1080 DE: Plasma 5.22.5 WM: KWin Theme: Breath2 2021 Light [Plasma], Breeze [GTK2/3] Icons: [Plasma], breath2 [GTK2/3] Terminal: konsole CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx (8) @ 2.100GHz GPU: AMD ATI 05:00.0 Picasso GPU: AMD ATI Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X Memory: 11126MiB / 15688MiB KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Compositor is off/disabled. GPU drivers are installed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click
https://bugs.kde.org/show_bug.cgi?id=443882 --- Comment #7 from Albert Astals Cid --- Oh, you meant right click on a highlight annotation while on text selection mode. I misunderstood your initial text and thought you were right clicking on a text selection. Yes that is somewhat on purpose, ideally we would work further on merging browse and text selection modes, but there are unsolved issues. I don't consider this really a bug, more of a whishlist. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443786] Enabling Accent Color features adds a header to color schemes that don't have one
https://bugs.kde.org/show_bug.cgi?id=443786 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |ebd4e8e9a229e8222409f9cf403 |ef1b01c680ca1961757e4509f89 |826b50232ec52 |0d89def1cfc66 --- Comment #10 from Nate Graham --- Git commit ef1b01c680ca1961757e4509f890d89def1cfc66 by Nate Graham. Committed on 18/10/2021 at 22:02. Pushed by ngraham into branch 'Plasma/5.23'. kcms/colors: Don't apply header accent colors to non-Header color schemes When applying an accent color, the color was added to the color scheme's Header color group. But not all color schemes have this group, and adding it made the color scheme break in creative ways. FIXED-IN: 5.23.1 (cherry picked from commit ebd4e8e9a229e8222409f9cf403826b50232ec52) M +8-0kcms/colors/colorsapplicator.cpp https://invent.kde.org/plasma/plasma-workspace/commit/ef1b01c680ca1961757e4509f890d89def1cfc66 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443786] Enabling Accent Color features adds a header to color schemes that don't have one
https://bugs.kde.org/show_bug.cgi?id=443786 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||ebd4e8e9a229e8222409f9cf403 ||826b50232ec52 Version Fixed In||5.23.1 Status|ASSIGNED|RESOLVED --- Comment #9 from Nate Graham --- Git commit ebd4e8e9a229e8222409f9cf403826b50232ec52 by Nate Graham. Committed on 18/10/2021 at 21:30. Pushed by ngraham into branch 'master'. kcms/colors: Don't apply header accent colors to non-Header color schemes When applying an accent color, the color was added to the color scheme's Header color group. But not all color schemes have this group, and adding it made the color scheme break in creative ways. FIXED-IN: 5.23.1 M +8-0kcms/colors/colorsapplicator.cpp https://invent.kde.org/plasma/plasma-workspace/commit/ebd4e8e9a229e8222409f9cf403826b50232ec52 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438273] Titlebar colors not changed correctly when switching from a header-color-using color scheme to a non-header-color-using color scheme
https://bugs.kde.org/show_bug.cgi?id=438273 --- Comment #7 from Nate Graham --- Found the real bug. People who are affected have at least one more kdeglobals file on their system besides ~/.config/keglobals, and this other kdeglobals file has a color scheme specified in it that includes a [Colors:Header] group. Those people can work around it by removing the [Colors:Header] and [Colors:Header][Inactive] groups from that file. When this file exists, the code that deletes the [Colors:Header] group when switching to a non-header color scheme doesn't actually delete the group and all its entries, it sets the keys' values to [$d] which is supposed to override the other file. However something about this does not work with the way we read colors from the color scheme to actually apply them to the system. Probably we are failing to check for whether the [Colors:Header] group exists or not, and are instead unconditionally reading its entries, rather than either checking for the group's existence using hasGroup() or verifying the existence of its entries' values with hasKey(). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443875] [resources/brush tip] Cannot overwrite a brushtip in ~/.local/share/krita/brushes/ directory
https://bugs.kde.org/show_bug.cgi?id=443875 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Keywords||regression, release_blocker --- Comment #3 from Tiar --- In theory, you should just save as you did, and then use it to create a new brush preset. It should show up in the Brush Tips widget. Now I see that it only works once (so if you first create a brush tip, then edit it and save, then it works, but if you save again, it won't work). Probable reason: It uses `QVector resources = model.resourcesForFilename(QFileInfo(path).fileName());`. This only looks for a current active resource which *current* filename is the same as the as the provided filename. Here the problem is, it looks for `Tip_A.gbr` but the filename of the `Tip A` resource is now `Tip_A.0001.gbr`. I guess either changing the filename of the document, or using a better function (that looks up resources with filenames no matter which version they were) would fix this issue. So yeah, there is a very clear bug and regression there as well. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click
https://bugs.kde.org/show_bug.cgi?id=443882 --- Comment #6 from Emmanuel --- Here is (finally) a small video showing the difference between "browse" mode and "selection text" mode. Sorry for the quite unpolished english commentaries (and the previously sent mistaken links). https://drive.google.com/file/d/1LmOxcMDwC7yP0kDRAonMy1lD0VlqMy4E/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426565] Flatpak: Refuses to remove a faulty remote
https://bugs.kde.org/show_bug.cgi?id=426565 Aleix Pol changed: What|Removed |Added Version Fixed In||5.23.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443455] Disabled Flatpak repos can't be successfully removed
https://bugs.kde.org/show_bug.cgi?id=443455 Aleix Pol changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #16 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 426565 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426565] Flatpak: Refuses to remove a faulty remote
https://bugs.kde.org/show_bug.cgi?id=426565 Aleix Pol changed: What|Removed |Added CC||ad...@happyassassin.net --- Comment #8 from Aleix Pol --- *** Bug 443455 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426565] Flatpak: Refuses to remove a faulty remote
https://bugs.kde.org/show_bug.cgi?id=426565 Aleix Pol changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/97b1a453 |ma/discover/commit/0f2f62b8 |0c03e84208799786d158a0331dd |412892df23787439c1d1cd4a5b6 |5ec40 |eeb83 --- Comment #7 from Aleix Pol --- Git commit 0f2f62b8412892df23787439c1d1cd4a5b6eeb83 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 18/10/2021 at 21:53. Pushed by apol into branch 'Plasma/5.23'. flatpak: Don't reuse GError instances It might already be filled and that makes libostree to assert out when it's the case. (cherry picked from commit 97b1a4530c03e84208799786d158a0331dd5ec40) M +3-2libdiscover/backends/FlatpakBackend/FlatpakSourcesBackend.cpp https://invent.kde.org/plasma/discover/commit/0f2f62b8412892df23787439c1d1cd4a5b6eeb83 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426565] Flatpak: Refuses to remove a faulty remote
https://bugs.kde.org/show_bug.cgi?id=426565 Aleix Pol changed: What|Removed |Added Resolution|UPSTREAM|FIXED Latest Commit||https://invent.kde.org/plas ||ma/discover/commit/97b1a453 ||0c03e84208799786d158a0331dd ||5ec40 --- Comment #6 from Aleix Pol --- Git commit 97b1a4530c03e84208799786d158a0331dd5ec40 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 18/10/2021 at 21:52. Pushed by apol into branch 'master'. flatpak: Don't reuse GError instances It might already be filled and that makes libostree to assert out when it's the case. M +3-2libdiscover/backends/FlatpakBackend/FlatpakSourcesBackend.cpp https://invent.kde.org/plasma/discover/commit/97b1a4530c03e84208799786d158a0331dd5ec40 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 443144] Marble always crashes on exit
https://bugs.kde.org/show_bug.cgi?id=443144 --- Comment #1 from daciabrown6...@protonmail.com --- Created attachment 142591 --> https://bugs.kde.org/attachment.cgi?id=142591=edit New crash information added by DrKonqi marble (2.2.20 (2.3 development version)) using Qt 5.15.2 - What I was doing when the application crashed: Closed application after viewing OpenStreetMap -- Backtrace (Reduced): #10 0x7fbacb86f2b0 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #11 0x7fbaccf78668 in KXmlGuiWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5 #12 0x7fbacc317d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7fbacb8423ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7fbacb8454b9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 443144] Marble always crashes on exit
https://bugs.kde.org/show_bug.cgi?id=443144 daciabrown6...@protonmail.com changed: What|Removed |Added CC||daciabrown6502@protonmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443786] Enabling Accent Color features adds a header to color schemes that don't have one
https://bugs.kde.org/show_bug.cgi?id=443786 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1126 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 444000] Screen layout with 2 identical monitors resets after reboot. wayland/nvidia
https://bugs.kde.org/show_bug.cgi?id=444000 jbhors...@gmail.com changed: What|Removed |Added Summary|Screen layout with 2 of the |Screen layout with 2 |same screen resets after|identical monitors resets |reboot. wayland/nvidia |after reboot. ||wayland/nvidia -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438273] Titlebar colors not changed correctly when switching from a header-color-using color scheme to a non-header-color-using color scheme
https://bugs.kde.org/show_bug.cgi?id=438273 --- Comment #6 from Nate Graham --- Never mind, that was a red herring. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443786] Enabling Accent Color features adds a header to color schemes that don't have one
https://bugs.kde.org/show_bug.cgi?id=443786 --- Comment #7 from Nate Graham --- Never mind, they are independent issues. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 444000] New: Screen layout with 2 of the same screen resets after reboot. wayland/nvidia
https://bugs.kde.org/show_bug.cgi?id=444000 Bug ID: 444000 Summary: Screen layout with 2 of the same screen resets after reboot. wayland/nvidia Product: KScreen Version: 5.22.90 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: jbhors...@gmail.com Target Milestone: --- Created attachment 142590 --> https://bugs.kde.org/attachment.cgi?id=142590=edit kscreen .local config folder & kscreen-console output I have 3 monitors, 2 of which are the same model. I setup the monitors in this arrangement [a][b][c] where a and c are the same model and this works fine. After restarting they are rearranged such that the a and c monitors show duplicated content: [b][ac] I then have to go in to settings and arrange them again. STEPS TO REPRODUCE 1. Plug in 2 identical monitors 2. Setup a multi screen layout 3. restart OBSERVED RESULT The screens are incorrectly arranged after reboot EXPECTED RESULT The screens retain the layout SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.10-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 ADDITIONAL INFORMATION I suspect because they have the same display 'ID' it is loading the config file incorrectly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 443997] hasGroup() does not take into account groups "deleted" using deleteGroup()
https://bugs.kde.org/show_bug.cgi?id=443997 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Nate Graham --- Never mind, I was holding it wrong. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443999] Dolphin Flatpak unable to edit File Type Options for file properties
https://bugs.kde.org/show_bug.cgi?id=443999 --- Comment #1 from denni...@selectedovr.com --- Folders are also impacted. UPDATED STEPS TO REPRODUCE 1. Open dolphin 2. Right click on any file type OR FOLDER (.ods, .png, folder, etc) 3. Click on the File Type Options button under Type -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 443845] Database won't load after update to Kubuntu 21.10/Tellico 3.4.1
https://bugs.kde.org/show_bug.cgi?id=443845 --- Comment #5 from Jim Sanderson --- (In reply to Robby Stephenson from comment #3) > > 6. Compressed as Zip file and changed .zip suffix back to .tc. > > Also, as an FYI, Tellico can load the XML file directly without compressing > and without ax extension change. Did not know that. I'll have to try it out. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443999] New: Dolphin Flatpak unable to edit File Type Options for file properties
https://bugs.kde.org/show_bug.cgi?id=443999 Bug ID: 443999 Summary: Dolphin Flatpak unable to edit File Type Options for file properties Product: dolphin Version: 21.08.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: denni...@selectedovr.com CC: kfm-de...@kde.org Target Milestone: --- Dolphin Flatpak unable to edit File Type Options for file properties. I have tried allowing all permissions in Flatseal and that did not produce a different result. STEPS TO REPRODUCE 1. Open dolphin 2. Right click on any file type (.ods, .png, etc) 3. Click on the File Type Options button under Type OBSERVED RESULT An message box pops up with Could not start the "keditfiletype5" executable, please check your installation. EXPECTED RESULT Being able to edit file type options when that button is clicked. SOFTWARE/OS VERSIONS OS: Arch Linux x86_64 Kernel: 5.14.12-arch1-1 (available in About System) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Dolphin flatpak version: 21.08.2 Flatpak version: flatpak 1.12.2-1 Flatseal version: 1.7.4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 443997] hasGroup() does not take into account groups "deleted" using deleteGroup()
https://bugs.kde.org/show_bug.cgi?id=443997 --- Comment #1 from Nate Graham --- This is a bit of an inconsistency since hasKey() will return false for any of the group's entries that have been marked as deleted, but hasGroup() will return true for the group itself if queried with hasGroup(). -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 443845] Database won't load after update to Kubuntu 21.10/Tellico 3.4.1
https://bugs.kde.org/show_bug.cgi?id=443845 --- Comment #4 from Jim Sanderson --- (In reply to Robby Stephenson from comment #2) > Could you email me the data file privately (or attach it here if you're ok > with that)? I'd like to figure out why the difference myself and fix it. The file is 9.6 MB (compressed). Will your e-mail accept that? Or would you just like the offending record? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #173 from Nick Stefanov --- Thank you. Unfortunately this is not worksing on my end. I even restarted the OS to no avail. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441077] Plasmashell panels may freeze, usually unrelated but unresponsive NFS/SMB mounts are involved
https://bugs.kde.org/show_bug.cgi?id=441077 --- Comment #7 from Kai Krakow --- (In reply to Nate Graham from comment #5) > That's what kio-fuse was meant to solve. Do you have it installed? Ah ok, didn't know how it worked - and it was eventually kicked from the system previously by some conflict. I now reinstalled it and reloaded my systemd daemon. Observation: Opening files for non-KIO aware programs spawns a fuse mount. Looks like it doesn't do that for KIO-aware programs (at least I see no additional folders created in the mount directory). Let's see how I can use that for me. But I will still depend on NFS mounts from the local network, e.g. by backup repository will be mounted via an automounter (daily full system backup with borg). Usually, the NAS is available 24x7 but sometimes it will restart for updates - and that's when the plasmashell rarely but eventually blocks. Why does it look for network mounts that actually have no business with my user account, or does it? Any way to debug this when it happens? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443998] New: Feature request: Notification if phone has charged to a specified percentage
https://bugs.kde.org/show_bug.cgi?id=443998 Bug ID: 443998 Summary: Feature request: Notification if phone has charged to a specified percentage Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: public.paul.meier+...@gmail.com Target Milestone: --- SUMMARY Batteries live longest if kept between 20% to 80%. It would be nice if KDE Connect could notify the user on the desktop side of things if a specified battery charge has been reached. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 443983] khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 Albert Astals Cid changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #6 from Albert Astals Cid --- Jonathan i can reproduce the crash with kio-man from 21.08 branch but not with the one from master, i see you've done some changes in master. Is this something you fixed on purpose? (or maybe was a side fix?) Could you have a look to see if you can find which commit fixes it and backport it for the final 21.08.3 ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 443997] New: hasGroup() does not take into account groups "deleted" using deleteGroup()
https://bugs.kde.org/show_bug.cgi?id=443997
Bug ID: 443997
Summary: hasGroup() does not take into account groups "deleted"
using deleteGroup()
Product: frameworks-kconfig
Version: 5.87.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: matt...@mjdsystems.ca
Reporter: n...@kde.org
CC: kdelibs-b...@kde.org
Target Milestone: ---
deleteGroup() may not actually delete the group; instead it can change the
values of all of the group's keys to "[$d]". In this case, the actual group
name will still exist unchanged. So then calling hasGroup() on it will return
true.
This leads to the following fairly unintuitive situation:
myConfig->deleteGroup("someGroupName");
myConfig->hasGroup("someGroupName"); // returns true!!!
Technically this is valid because [someGroupName] is still present in the
config file. But it's quite unintuitive that explicitly deleting a group with
deleteGroup() will not cause the group to be considered deleted from the
perspective of hasGroup();
The docs have nothing to say about this either.
--
You are receiving this mail because:
You are watching all bug changes.
