[frameworks-baloo] [Bug 490480] Baloo crashes despite being disabled
https://bugs.kde.org/show_bug.cgi?id=490480 --- Comment #5 from Lukas Kucharczyk --- In coredumctl I see the latest crashes from 2024-07-18 even though they were reported to me yesterday and today as well so I think you're right, we can close this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 490480] Baloo crashes despite being disabled
https://bugs.kde.org/show_bug.cgi?id=490480 --- Comment #3 from Lukas Kucharczyk --- I have checked and it seems disabled and not running: grep Indexing ~/.config/baloofilerc Indexing-Enabled=false systemctl --user status kde-baloo.service ○ kde-baloo.service - Baloo File Indexer Daemon Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: disabled) Drop-In: /usr/lib/systemd/user/service.d └─10-timeout-abort.conf Active: inactive (dead) (Result: exec-condition) since Fri 2024-07-19 07:53:54 CEST; 1h 27min ago Condition: start condition unmet at Fri 2024-07-19 07:53:54 CEST; 1h 27min ago Process: 2243 ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=1/FAILURE) CPU: 5ms čec 19 07:53:54 nobara-pc systemd[1860]: Starting kde-baloo.service - Baloo File Indexer Daemon... čec 19 07:53:54 nobara-pc systemd[1860]: kde-baloo.service: Skipped due to 'exec-condition'. čec 19 07:53:54 nobara-pc systemd[1860]: Condition check resulted in kde-baloo.service - Baloo File Indexer Daemon being skipped. pgrep -l baloo reports nothing running. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 490480] New: Baloo crashes despite being disabled
https://bugs.kde.org/show_bug.cgi?id=490480
Bug ID: 490480
Summary: Baloo crashes despite being disabled
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.3.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: lu...@kucharczyk.xyz
Target Milestone: ---
Application: baloo_file_extractor (6.3.0)
Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.8.12-201.fsync.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: Nobara Linux 40 (KDE Plasma)
DrKonqi: 6.1.1 [CoredumpBackend]
-- Information about the crash:
The crash report might be the same as in
https://bugs.kde.org/show_bug.cgi?id=490446 but this report is not about that.
I have Baloo disabled and when I boot my computer, I see it crashed like 10
times based on the number of icons in the tray.
I checked via the File Search control panel and using balooctl6 status.
There should not even be any index since I purged it.
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation
fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[New LWP 12299]
[New LWP 12306]
Downloading separate debug info for /lib64/libz.so.1...
Downloading separate debug info for system-supplied DSO at 0x7ffc1718b000...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/kf6/baloo_file_extractor'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7fd1dd4adf40 (LWP 12299))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fd1dd4adf40 (LWP 12299))]
Thread 2 (Thread 0x7f91cca006c0 (LWP 12306)):
#0 0x7fd1deb1c67d in __GI___poll (fds=0x559b40e465e0, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fd1dd77cc34 in g_main_context_poll_unlocked (priority=2147483647,
context=0x7f91c8000c60, timeout=, fds=0x559b40e465e0, n_fds=3)
at ../glib/gmain.c:4521
#2 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7f91c8000c60, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4212
#3 0x7fd1dd71c383 in g_main_context_iteration (context=0x7f91c8000c60,
may_block=1) at ../glib/gmain.c:4282
#4 0x7fd1df4850a3 in QEventDispatcherGlib::processEvents
(this=0x7f91c8000b70, flags=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:394
#5 0x7fd1df1a3b03 in QEventLoop::exec (this=this@entry=0x7f91cc9ffaa0,
flags=..., flags@entry=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/global/qflags.h:34
#6 0x7fd1df2b7e4f in QThread::exec (this=this@entry=0x7fd1deffecc0
>::instance()::holder>) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/global/qflags.h:74
#7 0x7fd1def6fe41 in QDBusConnectionManager::run (this=0x7fd1deffecc0
>::instance()::holder>) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/dbus/qdbusconnectionmanager.cpp:144
#8 0x7fd1df35463c in operator() (__closure=) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:326
#9 (anonymous
namespace)::terminate_on_exception >
(t=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:262
#10 QThreadPrivate::start (arg=0x7fd1deffecc0
>::instance()::holder>) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:285
#11 0x7fd1deaa6507 in start_thread (arg=) at
pthread_create.c:447
#12 0x7fd1deb2a40c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 1 (Thread 0x7fd1dd4adf40 (LWP 12299)):
[KCrash Handler]
#5 0x7fd1df212693 in QArrayDataPointer::QArrayDataPointer
(this=0x7ffc17123a30, other=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/tools/qarraydatapointer.h:38
#6 QString::QString (this=0x7ffc17123a30, other=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/text/qstring.h:1186
#7 QVariant::Private::Private (this=0x7ffc17123a30, t=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/kernel/qvariant_p.h:98
#8 QVariant::QVariant (this=this@entry=0x7ffc17123a30, val=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/kernel/qvariant.cpp:948
#9 0x7fd1de54da8c in standardDeclarationForNode (node=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/tools/qlist.h:183
#10 0x7fd1de54ebca in QTextHtmlParser::declarationsForNode
(this=this@entry=0x7ff
[frameworks-baloo] [Bug 490446] New: Baloo crashes when indexing ebooks
https://bugs.kde.org/show_bug.cgi?id=490446
Bug ID: 490446
Summary: Baloo crashes when indexing ebooks
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.3.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: lu...@kucharczyk.xyz
Target Milestone: ---
Application: baloo_file_extractor (6.3.0)
Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.8.12-201.fsync.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: Nobara Linux 40 (KDE Plasma)
DrKonqi: 6.1.1 [CoredumpBackend]
-- Information about the crash:
I enabled Plasma Search to index my home directory which also includes my
Calibre library. Baloo File Extracted crashed, and I do not exaggerate, in
total tens of times, usually like 5 times in a row. If I excluded my Calibre
library, this behavior stopped.
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation
fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/libexec/kf6/baloo_file_extractor...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/b01d895ba9d020bc7ba787f8e2f5d6f2a8b1ff2f/debuginfo...
[New LWP 4379]
[New LWP 4394]
Downloading separate debug info for /lib64/libKF6FileMetaData.so.3...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/a0b53203525b3e951ec67744dc7b2195327945d8/debuginfo...
Downloading separate debug info for /lib64/libKF6ConfigCore.so.6...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/2fe29946b45dba87dbb6448c1f0b68d17c860800/debuginfo...
Downloading separate debug info for /lib64/libKF6Solid.so.6...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/ee61cbe86eef78b7458da0faf5fe0c4b9e66ed19/debuginfo...
Downloading separate debug info for /lib64/libKF6BalooEngine.so.6...
Downloading separate debug info for /lib64/libKF6Crash.so.6...
Downloading separate debug info for /lib64/libKF6IdleTime.so.6...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/4e647f378782c8fb8b1c9c9467eaba50994dfff1/debuginfo...
Downloading separate debug info for /lib64/libKF6I18n.so.6...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/e34e9bc67aec21f2a0c2f0ed22ca0b0732da5dbf/debuginfo...
Downloading separate debug info for /lib64/libKF6CoreAddons.so.6...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/9b9634c5fe3fe2066dd2ff8dc8e209099f88c657/debuginfo...
Downloading separate debug info for /lib64/libQt6Core.so.6...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/3b789cec719dc51552152b89d5427ef94e4f7237/debuginfo...
Downloading separate debug info for /lib64/libQt6DBus.so.6...
Downloading separate debug info for /lib64/libQt6Xml.so.6...
Downloading separate debug info for /lib64/libQt6Gui.so.6...
Downloading separate debug info for /lib64/libudev.so.1...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/8dcbca8ee116a49456c67650e14c66a2f35bd45c/debuginfo...
Downloading separate debug info for /lib64/libmount.so.1...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/20b0fc098c3b91b03ba2f9f02dda168b91f17c45/debuginfo...
Downloading separate debug info for /lib64/libimobiledevice-1.0.so.6...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/85180fe1be5e11f88271e45fe7ef22d9463fadeb/debuginfo...
Downloading separate debug info for /lib64/libplist-2.0.so.4...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/3a0d291c9441f00f64accf555ae24aadce32d291/debuginfo...
Downloading separate debug info for /lib64/liblmdb.so.0.0.0...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/38f75b3d8e5c5ec5c3486c61ad51d5903a5437ea/debuginfo...
Downloading separate debug info for /lib64/libicui18n.so.74...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/115376d2afa0cd8f1378405d855cda57bfb134b7/debuginfo...
Downloading separate debug info for /lib64/libicuuc.so.74...
Downloading separate debug info for /lib64/libglib-2.0.so.0...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/36b60dbd02e796145a982d0151ce37202ec05649/debuginfo...
Downloading separate debug info for /lib64/libz.so.1...
Downloading separate debug info for /lib64/libsystemd.so.0...
Downloading separate debug info for /lib64/libdouble-conversion.so.3...
Downloading separate debug info for /lib64/libb2.so.1...
Downloading separate debug info for /lib64/libpcre2-16.so.0...
Downloading separate debug info for
/home/lukas/.cache/debuginfod_client/6e05dd84eec29db1c88dceb8175251ace
[kwin] [Bug 103788] Input of arbitrary unicode characters as defined in ISO 14755
https://bugs.kde.org/show_bug.cgi?id=103788 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz --- Comment #31 from Lukas Kucharczyk --- (In reply to Nate Graham from comment #28) > Can someone explain in plain English what exactly is being requested here? > I'm not understanding what needs to be done to support it, because it isn't > clear to me what the feature is. Thanks! Typing arbitrary Unicode characters by their codepoint using a keyboard shortcut. You can even try exactly what people mean if you're running any GTK app in Plasma. For example https://unicode-explorer.com/c/237D can be typed by holding Ctrl+Shift+u and then typing 237d, then letting go. By the way, KRunner's Special Characters plugin can already do the conversion but copying characters from KRunner every time you want to do this is not ideal. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472340] OLED subpixel rendering support
https://bugs.kde.org/show_bug.cgi?id=472340 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 457672] Spotify notifications (coming from plasma-workspace, through XDG portal) plays error sound
https://bugs.kde.org/show_bug.cgi?id=457672 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 460407] Could not open access token file
https://bugs.kde.org/show_bug.cgi?id=460407 Lukas Kucharczyk changed: What|Removed |Added Summary|Reading access token from |Could not open access token |the keychain for|file |"@lordfrikk:matrix.org" | |Could not open access token | |file| |"/home/lukas/.var/app/org.k | |de.neochat/data/KDE/neochat | |/@lordfrikk_matrix.org" | -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 460407] New: Reading access token from the keychain for "@lordfrikk:matrix.org" Could not open access token file "/home/lukas/.var/app/org.kde.neochat/data/KDE/neochat/@lordfrikk_matrix
https://bugs.kde.org/show_bug.cgi?id=460407 Bug ID: 460407 Summary: Reading access token from the keychain for "@lordfrikk:matrix.org" Could not open access token file "/home/lukas/.var/app/org.kde.neochat/data/KDE/neochat /@lordfrikk_matrix.org" Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: lu...@kucharczyk.xyz CC: c...@carlschwan.eu Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When I open the app, the window appears with loading indicator that never finishes. Log: --- > flatpak run org.kde.neochat Reading access token from the keychain for "@lordfrikk:matrix.org" Could not open access token file "/home/lukas/.var/app/org.kde.neochat/data/KDE/neochat/@lordfrikk_matrix.org" > ls -ld > /home/lukas/.var/app/org.kde.neochat/data/KDE/neochat/@lordfrikk_matrix.org drwxr-xr-x - lukas 3 Oct 19:41 /home/lukas/.var/app/org.kde.neochat/data/KDE/neochat/@lordfrikk_matrix.org --- STEPS TO REPRODUCE 1. Open the app. 2. See the error. OBSERVED RESULT App doesn't load. EXPECTED RESULT App finished loading, ready to use. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: N/A ADDITIONAL INFORMATION This is the Flatpak nightly version: flatpak info org.kde.neochat NeoChat - A client for matrix, the decentralized communication protocol ID: org.kde.neochat Ref: app/org.kde.neochat/x86_64/master Arch: x86_64 Branch: master Version: 22.09 License: GPL-3.0 Origin: kdeapps Collection: Installation: system Installed: 115.7 MB Runtime: org.kde.Platform/x86_64/5.15-21.08 Sdk: org.kde.Sdk/x86_64/5.15-21.08 Commit: b369d5087f79c1bdc1081a231f0baa10c37801170131e3b272f964d7d323c887 Parent: fa23bbeebe42bc9df83ba00a10b0fdf5139f3cb06fc4088bfd593344a9c48722 Subject: Built on Fri Oct 14 04:41:12 CEST 2022 Date: 2022-10-14 02:43:44 + -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 430233] Please consider ReplayGain tags
https://bugs.kde.org/show_bug.cgi?id=430233 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz --- Comment #6 from Lukas Kucharczyk --- Would be really cool! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444024] [wayland] - dock leaves blurry area after hiding
https://bugs.kde.org/show_bug.cgi?id=444024 --- Comment #2 from Lukas Kucharczyk --- I have encountered this bug in 5.22 so I doubt it has any connection to it. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444093] New: Crash on startup
https://bugs.kde.org/show_bug.cgi?id=444093
Bug ID: 444093
Summary: Crash on startup
Product: lattedock
Version: 0.10.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: lu...@kucharczyk.xyz
Target Milestone: ---
Posting this manually since DrKonqi couldn't automatically send the bug report.
-- Information about the crash:
- What I was doing when the application crashed:
Logged in.
- Unusual behavior I noticed:
No latte dock.
- Custom settings of the application:
I have two docs, top and bottom. The top one has app window title, app buttons,
time, and tray. The bottom is the regular app launcher.
The crash can be reproduced every time.
-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 KDecoration2::DecorationSettings::font (this=this@entry=0x55e5212e8020) at
/usr/include/c++/11/bits/unique_ptr.h:173
#7 0x7fe807ac1187 in operator() (__closure=) at
/usr/src/debug/libkdecoration2-5.23.0-1.1.x86_64/src/decorationsettings.cpp:19
#8 KDecoration2::DecorationSettings::DecorationSettings (this=,
bridge=, parent=, this=,
bridge=, parent=) at
/usr/src/debug/libkdecoration2-5.23.0-1.1.x86_64/src/decorationsettings.cpp:34
#9 0x7fe807b07283 in
QSharedPointer::create
() at /usr/include/qt5/QtCore/qsharedpointer_impl.h:438
#10 Decoration::Applet::Settings::createSettings (this=0x55e5212dc1b0) at
/usr/src/debug/applet-window-buttons-0.9.0-2.2.x86_64/libappletdecoration/previewsettings.cpp:267
#11 0x7fe86309a013 in QtPrivate::QSlotObjectBase::call (a=0x7ffcda4917e0,
r=0x55e5212dc1b0, this=0x55e5212dc2f0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#12 doActivate (sender=0x55e5212dc1b0, signal_index=3,
argv=0x7ffcda4917e0) at kernel/qobject.cpp:3886
#13 0x7fe864c267df in QQmlPropertyData::writeProperty (flags=...,
value=0x7ffcda491848, target=, this=) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:375
#14 QObjectPointerBinding::write (this=0x55e5212dc4a0, result=...,
isUndefined=, flags=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/qml/qml/qqmlbinding.cpp:739
#15 0x7fe864c27f47 in QQmlNonbindingBinding::doUpdate (this=0x55e5212dc4a0,
watcher=..., flags=..., scope=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/qml/qml/qqmlbinding.cpp:258
#16 0x7fe864c25b64 in QQmlBinding::update (this=0x55e5212dc4a0, flags=...)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/qml/qml/qqmlbinding.cpp:194
#17 0x7fe864c33032 in QQmlObjectCreator::finalize (this=0x55e5212c2a50,
interrupt=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/qml/qml/qqmlobjectcreator.cpp:1394
#18 0x7fe864bc9ac5 in QQmlIncubatorPrivate::incubate (this=0x55e521126af0,
i=...) at /usr/include/qt5/QtCore/qscopedpointer.h:116
#19 0x7fe864bca0bd in QQmlEnginePrivate::incubate (this=0x55e520483060,
i=..., forContext=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/qml/qml/qqmlincubator.cpp:89
#20 0x7fe864bc39fb in QQmlComponent::create (this=,
incubator=..., context=, forContext=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/qml/qml/qqmlcomponent.cpp:1178
#21 0x7fe8653638da in KDeclarative::QmlObject::completeInitialization
(initialProperties=..., this=0x55e52112a860) at
/usr/src/debug/kdeclarative-5.86.0-1.3.x86_64/src/kdeclarative/qmlobject.cpp:307
#22 KDeclarative::QmlObject::completeInitialization (this=0x55e52112a860,
initialProperties=...) at
/usr/src/debug/kdeclarative-5.86.0-1.3.x86_64/src/kdeclarative/qmlobject.cpp:289
#23 0x7fe8656ca96b in PlasmaQuick::AppletQuickItem::init
(this=this@entry=0x55e5211268d0) at
/usr/src/debug/plasma-framework-5.86.0-1.3.x86_64/src/plasmaquick/appletquickitem.cpp:649
#24 0x7fe80ef37802 in AppletInterface::init (this=0x55e5211268d0) at
/usr/src/debug/plasma-framework-5.86.0-1.3.x86_64/src/scriptengines/qml/plasmoid/appletinterface.cpp:141
#25 0x7fe8656c7e11 in PlasmaQuick::AppletQuickItem::itemChange
(this=0x55e5211268d0, change=QQuickItem::ItemSceneChange, value=...) at
/usr/src/debug/plasma-framework-5.86.0-1.3.x86_64/src/plasmaquick/appletquickitem.cpp:927
#26 0x7fe8650483ab in QQuickItemPrivate::refWindow (this=0x55e521126980,
c=0x55e521150390) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/quick/items/qquickitem.cpp:3003
#27 0x7fe865048369 in QQuickItemPrivate::refWindow (this=0x55e520cbdfe0,
c=0x55e521150390) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/quick/items/qquickitem.cpp:2996
#28 0x7fe865048770 in QQuickItem::setParentItem
(this=this@entry=0x55e520ff06c0, parentIte
[lattedock] [Bug 444024] New: [Wayland] Dock leaves blurry area after hiding
https://bugs.kde.org/show_bug.cgi?id=444024 Bug ID: 444024 Summary: [Wayland] Dock leaves blurry area after hiding Product: lattedock Version: 0.10.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: lu...@kucharczyk.xyz Target Milestone: --- SUMMARY I have the dock on bottom set to auto-hide and dodge maximized. Sometimes when the dock hides, it leaves a blurry area instead of disappearing correctly. This area covers 100% of the width of the screen despite the dock not being 100% wide. It happens quite often but I have not been able to reproduce it reliably. STEPS TO REPRODUCE 1. Scroll to bottom edge to make dock appear. 2. Move the cursor out of the dock area. 3. Blurry area remains. OBSERVED RESULT Blurry area covers the bottom part of the screen after the dock is supposed to be hidden. EXPECTED RESULT No artifacts remain after the dock is hidden. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: N/A 5.23.0 (available in About System) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel version 5.14.12-arch1-1 (64-bit) This bug is not new, it has been happening for several weeks if not months. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440771] New: Plasma Wayland crashes on startup
https://bugs.kde.org/show_bug.cgi?id=440771 Bug ID: 440771 Summary: Plasma Wayland crashes on startup Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lu...@kucharczyk.xyz CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.6-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: After (automatically) logging into the desktop, I noticed the crash icon in the tray. This happens every startup. If it wasn't for the icon I wouldn't actually notice anything being wrong. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f7c2efcf980 (LWP 2186))] [KCrash Handler] #6 0x7f7c31f7fa40 in QScreen::name (this=0x5628fb3604e0) at kernel/qscreen.cpp:195 #7 0x5628f9957c2b in ?? () #8 0x7f7c31b36fb3 in QtPrivate::QSlotObjectBase::call (a=0x7ffeb2790da0, r=0x5628fb3974c0, this=0x5628fb5bdec0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x5628fb53ef60, signal_index=4, argv=0x7ffeb2790da0) at kernel/qobject.cpp:3886 #10 0x7f7c31b3047f in QMetaObject::activate (sender=, m=m@entry=0x7f7c33da4560, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffeb2790da0) at kernel/qobject.cpp:3946 #11 0x7f7c33d802f1 in KActivities::Consumer::serviceStatusChanged (this=, _t1=) at /usr/src/debug/kactivities5-5.84.0-1.1.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_consumer.cpp:253 #12 0x7f7c31b36fb3 in QtPrivate::QSlotObjectBase::call (a=0x7ffeb2790ee0, r=0x5628fb53ef60, this=0x5628fb5808a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x5628fb59be80, signal_index=11, argv=0x7ffeb2790ee0) at kernel/qobject.cpp:3886 #14 0x7f7c31b3047f in QMetaObject::activate (sender=sender@entry=0x5628fb59be80, m=m@entry=0x7f7c33da4620 , local_signal_index=local_signal_index@entry=8, argv=argv@entry=0x7ffeb2790ee0) at kernel/qobject.cpp:3946 #15 0x7f7c33d91312 in KActivities::ActivitiesCache::serviceStatusChanged (_t1=KActivities::Consumer::Running, this=0x5628fb59be80) at /usr/src/debug/kactivities5-5.84.0-1.1.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:412 #16 KActivities::ActivitiesCache::setAllActivities (this=0x5628fb59be80, _activities=...) at /usr/src/debug/kactivities5-5.84.0-1.1.x86_64/src/lib/activitiescache_p.cpp:270 #17 0x7f7c33d84677 in KActivities::ActivitiesCache::passInfoFromReply, void (KActivities::ActivitiesCache::*)(QList const&)> (f=, watcher=0x5628fb53d330, this=0x5628fb59be80) at /usr/src/debug/kactivities5-5.84.0-1.1.x86_64/src/lib/activitiescache_p.cpp:180 #18 KActivities::ActivitiesCache::setAllActivitiesFromReply (watcher=0x5628fb53d330, this=0x5628fb59be80) at /usr/src/debug/kactivities5-5.84.0-1.1.x86_64/src/lib/activitiescache_p.cpp:195 #19 KActivities::ActivitiesCache::qt_static_metacall (_o=0x5628fb59be80, _c=, _id=, _a=) at /usr/src/debug/kactivities5-5.84.0-1.1.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:201 #20 0x7f7c31b36fe8 in doActivate (sender=0x5628fb53d330, signal_index=3, argv=0x7ffeb2791150) at kernel/qobject.cpp:3898 #21 0x7f7c31b3047f in QMetaObject::activate (sender=, m=m@entry=0x7f7c3259c5c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeb2791150) at kernel/qobject.cpp:3946 #22 0x7f7c3257d01f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158 #23 0x7f7c31b2cf5e in QObject::event (this=0x5628fb53d330, e=0x5628fb3a9a80) at kernel/qobject.cpp:1314 #24 0x7f7c3288ca7f in QApplicationPrivate::notify_helper (this=, receiver=0x5628fb53d330, e=0x5628fb3a9a80) at kernel/qapplication.cpp:3632 #25 0x7f7c31b0096a in QCoreApplication::notifyInternal2 (receiver=0x5628fb53d330, event=0x5628fb3a9a80) at kernel/qcoreapplication.cpp:1064 #26 0x7f7c31b039b7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5628fb33e0c0) at kernel/qcoreapplication.cpp:1821 #27 0x7f7c31b587d3 in postEventSourceDispatch (s=s@entry=0x5628fb3dfad0) at kernel/qeventdispatcher_glib.cpp:277 #28 0x7f7c2fe2380f in g_main_dispatch (context=0x5628fb3aede0) at ../glib/gmain.c:3337 #29 g_main_context_dispatch (context=0x5628fb3aede0) at ../glib/gmain.c:4055 #30 0x7f7c2fe23b98 in g_main_context_iterate (context=context@entry=0x5628fb
[plasmashell] [Bug 417939] Task context menu disappears when Task's tooltip disappears
https://bugs.kde.org/show_bug.cgi?id=417939 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 161017] enqueue kio transfer operations
https://bugs.kde.org/show_bug.cgi?id=161017 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation
https://bugs.kde.org/show_bug.cgi?id=406725 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437134] New: Right-click menu appears underneath the launcher
https://bugs.kde.org/show_bug.cgi?id=437134 Bug ID: 437134 Summary: Right-click menu appears underneath the launcher Product: plasmashell Version: 5.21.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: lu...@kucharczyk.xyz CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Right-clicking launcher on panel when the launcher is open displays the right-click menu underneath the launcher. STEPS TO REPRODUCE 1. Open the Application Launcher by clicking on its icon on the panel. 2. With the launcher open, right-click the icon. 3. The menu appears under the launcher. OBSERVED RESULT Menu appears under the launcher. EXPECTED RESULT Either menu appears over the launcher or launcher is closed and menu is displayed instead. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 399249] Add support for scrobbling to last.fm
https://bugs.kde.org/show_bug.cgi?id=399249 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 431174] New: Crash when scrolling a track list
https://bugs.kde.org/show_bug.cgi?id=431174 Bug ID: 431174 Summary: Crash when scrolling a track list Product: elisa Version: 20.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: lu...@kucharczyk.xyz Target Milestone: --- Application: elisa (20.12.0) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.10.3-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Scrolling down an open album track list. - Unusual behavior I noticed: Application crashed. - Custom settings of the application: 3 library locations: /home/music and two SMB shares mounted to /NAS -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [KCrash Handler] #4 0x7ff6998bce80 in QHash::isEmpty (this=) at /usr/include/qt5/QtCore/qhash.h:285 #5 QHash::empty (this=) at /usr/include/qt5/QtCore/qhash.h:544 #6 QQmlIncubatorPrivate::incubate (this=0x56389a50a430, i=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/qml/qqmlincubator.cpp:333 #7 0x7ff6998bd4c2 in QQmlIncubationController::incubateFor (this=this@entry=0x5638953a0d50, msecs=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/qml/qqmlincubator.cpp:409 #8 0x7ff6980ef570 in QQuickWindowIncubationController::incubate (this=0x5638953a0d40) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/items/qquickwindow.cpp:171 #9 QQuickWindowIncubationController::timerEvent (this=0x5638953a0d40) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/quick/items/qquickwindow.cpp:154 #10 0x7ff69936724f in QObject::event (this=0x5638953a0d40, e=0x7ffcaceb1340) at kernel/qobject.cpp:1336 #11 0x7ff69a44650f in QApplicationPrivate::notify_helper (this=, receiver=0x5638953a0d40, e=0x7ffcaceb1340) at kernel/qapplication.cpp:3632 #12 0x7ff69933b2ea in QCoreApplication::notifyInternal2 (receiver=0x5638953a0d40, event=0x7ffcaceb1340) at kernel/qcoreapplication.cpp:1063 #13 0x7ff699391c03 in QTimerInfoList::activateTimers (this=0x5638950f4fe0) at kernel/qtimerinfo_unix.cpp:643 #14 0x7ff699392484 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #15 0x7ff696f65e57 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #16 0x7ff696f661d8 in ?? () from /usr/lib64/libglib-2.0.so.0 #17 0x7ff696f6628f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #18 0x7ff69939283f in QEventDispatcherGlib::processEvents (this=0x5638950f5120, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x7ff699339cab in QEventLoop::exec (this=this@entry=0x7ffcaceb1580, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #20 0x7ff699341f20 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #21 0x563894c5a375 in main (argc=, argv=) at /usr/src/debug/elisa-20.12.0-1.1.x86_64/src/main.cpp:165 [Inferior 1 (process 8739) detached] The reporter indicates this bug may be a duplicate of or related to bug 428585. Possible duplicates by query: bug 430019, bug 428889, bug 428697, bug 428585, bug 427328. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429240] Plasma crashes shortly after login
https://bugs.kde.org/show_bug.cgi?id=429240 --- Comment #2 from Lukas Kucharczyk --- I have physically disconnected the second (1080p 240 Hz) monitor and: 1. Upon disconnecting the cable while still logged in, I was either logged out or the whole session crashed. 2. Upon restarting, the crash no longer happens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429240] Plasma crashes shortly after login
https://bugs.kde.org/show_bug.cgi?id=429240 --- Comment #1 from Lukas Kucharczyk --- This also happens when I restart the computer and it automatically logs in. My default session (set in settings Startup and Shutdown -> Login Screen (SDDM) -> Advanced -> Automatically log in with session) to Plasma (Full Wayland). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429240] New: Plasma crashes shortly after login
https://bugs.kde.org/show_bug.cgi?id=429240 Bug ID: 429240 Summary: Plasma crashes shortly after login Product: plasmashell Version: 5.20.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lu...@kucharczyk.xyz CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.2) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.1-2-default x86_64 Windowing system: Wayland Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: I came back to a computer after being AFK for a while and tried logging back in. - Unusual behavior I noticed: When logged back in, it was as if I was completely logged out (possibly by the session crashing) instead of the screen just being locked. - Custom settings of the application: I have two different scaling factors. One is 200% on a 4K screen, the other is default 100% on a 1080p screen. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 5656] [New LWP 5699] [New LWP 5728] [New LWP 5729] [New LWP 5730] [New LWP 5731] [New LWP 5732] [New LWP 5733] [New LWP 5734] [New LWP 5735] [New LWP 5736] [New LWP 5737] [New LWP 5738] [New LWP 5739] [New LWP 5740] [New LWP 5741] [New LWP 5742] [New LWP 5807] [New LWP 5808] [New LWP 5809] [New LWP 5834] [New LWP 5836] [New LWP 5846] [New LWP 5847] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f651a84fa6f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f6518739840 (LWP 5647))] Thread 25 (Thread 0x7f647fbff640 (LWP 5847)): #0 0x7f6519d9b6b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f651abffdfb in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55b145de9680) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x7f651000ed10, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f651c913b57 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7f651c915fe9 in ?? () from /usr/lib64/libQt5Quick.so.5 #5 0x7f651abf9de1 in QThreadPrivate::start (arg=0x7f651000ec70) at thread/qthread_unix.cpp:329 #6 0x7f6519d953e9 in start_thread () from /lib64/libpthread.so.0 #7 0x7f651a85ab73 in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f64a0bf9640 (LWP 5846)): #0 0x7f6519d9b6b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f650ea32e2b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f650ea322e7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f6519d953e9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f651a85ab73 in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f64ab815640 (LWP 5836)): #0 0x7f6519d9b6b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f650ea32e2b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f650ea322e7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f6519d953e9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f651a85ab73 in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f64c0833640 (LWP 5834)): #0 0x7f651abfa34f in QMutex::unlock (this=this@entry=0x55b145d804f0) at /usr/include/c++/10/bits/atomic_base.h:776 #1 0x7f651ae30ec5 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #2 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:243 #3 QThreadData::canWaitLocked (this=0x55b145d804c0) at ../../include/QtCore/5.15.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:272 #4 postEventSourcePrepare (timeout=, s=0x7f64b0001540) at kernel/qeventdispatcher_glib.cpp:260 #5 postEventSourceCheck (source=0x7f64b0001540) at kernel/qeventdispatcher_glib.cpp:270 #6 0x7f65192109d9 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #7 0x7f6519210f65 in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x7f65192110df in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x7f651ae30a9b in QEventDispatcherGlib::processEvents (this=0x7f64bb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #10 0x7f651add7eeb in QEventLoop::exec (this=this@entry=0x7f64c0832c80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #11 0x7f651abf8c9e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #12 0x7f651c867926 in ?? () from /usr/lib64/libQt5Quick.so.5 #13 0x7f651abf9de1 in QThreadPrivate::start (arg=0x55b145dd53d0) at thread/qthread_unix.cpp:329 #14 0x7f6519d953e9
[krunner] [Bug 324617] KDE text search (ex: filtering lists, krunner ) to enhance diacritics matching
https://bugs.kde.org/show_bug.cgi?id=324617 --- Comment #11 from Lukas Kucharczyk --- I agree with the above comment. Both need to be searched. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 324617] KDE text search (ex: filtering lists, krunner ) to enhance diacritics matching
https://bugs.kde.org/show_bug.cgi?id=324617 --- Comment #3 from Lukas Kucharczyk --- Tested it just now and both "system" and "systém" work. But for example pisma (== "fonts" in Czech) doesn't work but search for "font" finds "Písma" so I'm thinking in some cases it is the case where diacritics are accounted for and in other cases it doesn't find keywords. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 324617] KDE text search (ex: filtering lists, krunner ) to enhance diacritics matching
https://bugs.kde.org/show_bug.cgi?id=324617 --- Comment #2 from Lukas Kucharczyk --- Sorry for my previous comment, it sounded too confrontational. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 324617] KDE text search (ex: filtering lists, krunner ) to enhance diacritics matching
https://bugs.kde.org/show_bug.cgi?id=324617 Lukas Kucharczyk changed: What|Removed |Added Component|general |filesearch Keywords||usability Version|unspecified |5.19.2 Platform|unspecified |Archlinux Packages Assignee|unassigned-b...@kde.org |baloo-bugs-n...@kde.org Product|kde |krunner CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 324617] KDE text search (ex: filtering lists, krunner ) to enhance diacritics matching
https://bugs.kde.org/show_bug.cgi?id=324617 Lukas Kucharczyk changed: What|Removed |Added CC||lu...@kucharczyk.xyz Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Lukas Kucharczyk --- This issue still exists and it is confusing because no other platform I've used differentiates between something like system and systém. Is there any reason why it shouldn't be as easy to solve as stripping the diacritics from words by converting it to ASCII? -- You are receiving this mail because: You are watching all bug changes.
