[yakuake] [Bug 493548] New: Graphical glitches when using yakuake themes with shadow effect and rounded corners (Wayland)
https://bugs.kde.org/show_bug.cgi?id=493548 Bug ID: 493548 Summary: Graphical glitches when using yakuake themes with shadow effect and rounded corners (Wayland) Classification: Applications Product: yakuake Version: 24.08.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: azero...@gmail.com Target Milestone: --- Created attachment 173998 --> https://bugs.kde.org/attachment.cgi?id=173998&action=edit Black spots visible in the corners of the terminal when using ROUNDED theme. SUMMARY When a theme with shadow effect or rounded corners is used, black spots appear in the corners of yakuake terminal. This only happens when using Wayland (with X11 there are no issues). STEPS TO REPRODUCE 1. Login to a Wayland session; 2. Start yakuake; 3. Download and apply one of the themes with shadows/rounded corners. For example: ROUNDED, Materia Dark, Prof Light; 4. Press F12 to drop down the terminal. OBSERVED RESULT Black spots in the corners of the terminal are be visible. For some themes spots are big (ROUNDED), medium (Prof Light) or single pixel (Plastik Light). EXPECTED RESULT Shadows and rounded corners are displayed without glitches. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: openSUSE Tumbleweed 20240922 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION I can only use themes without shadows and without rounded corners (like Arc Dark). I attach a screenshot depicting the issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491473] digikam 8.4 does not start
https://bugs.kde.org/show_bug.cgi?id=491473 --- Comment #7 from Filip Rozsypal --- (In reply to Maik Qualmann from comment #6) > It may be confusing for a Linux beginner, but Snap or Flat packages are not > suitable for digiKam due to the sandbox function. We are not the creators of > the Snap packages, they may not contain all the components needed to run > digiKam correctly. > A native package would be ideal, but Ubuntu does not provide one. We > ourselves provide an AppImage bundle. Please test whether it works for you, > you just need to make it executable and then you can start it. > > AppImage Download: https://files.kde.org/digikam/ > > Maik Dear Maik Thanks for this. I will try to go the appimage way. As I mentioned earlier, I already tried it once and had other type of problems (digikam responding to arrows only with a one key press delay)... I will download it and possibly report a new bug. Filip -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 491473] digikam 8.4 does not start
https://bugs.kde.org/show_bug.cgi?id=491473 --- Comment #5 from Filip Rozsypal --- (In reply to Maik Qualmann from comment #4) > The message "parent is null" at the end comes from the notification widget. > It indicates that no main window was created, I suspect a problem with > openGL. > > Copy the "digikam_systemrc" from the following bug report into your home > directory ".config" > > https://bugs.kde.org/show_bug.cgi?id=484107#c1 > > Maik (In reply to Maik Qualmann from comment #4) > The message "parent is null" at the end comes from the notification widget. > It indicates that no main window was created, I suspect a problem with > openGL. > > Copy the "digikam_systemrc" from the following bug report into your home > directory ".config" > > https://bugs.kde.org/show_bug.cgi?id=484107#c1 > > Maik I tried that, it does not change anything. For your information, previously, I deleted both digikam_systemrc and digikamrc, as suggested in the instalation part of documentation in order to revert back to factory setting. It seems that these files do not get re-created after restarting digikam, even with --platform xcb option on. (I am really a linux beginner) here is the terminal output: $ digikam libEGL warning: egl: failed to create dri2 screen digikam.widgets: Use installed icons digikam.general: AlbumWatch is disabled digikam.general: Database Parameters: Type:"QSQLITE" DB Core Name: "/home/filip_rozsypal/Pictures/db_new/digikam4.db" DB Thumbs Name: "/home/filip_rozsypal/Pictures/db_new/thumbnails-digikam.db" DB Face Name: "/home/filip_rozsypal/Pictures/db_new/recognition.db" DB Similarity Name: "/home/filip_rozsypal/Pictures/db_new/similarity.db" Connect Options: "" Host Name: "" Host Port: -1 WAL Mode:false Internal Server: false Internal Server Path:"" Internal Server Init Cmd:"" Internal Server Admin Cmd: "" Internal Server Program Cmd: "" Internal Server Upgrade Cmd: "" Username:"" Password:"" digikam.dbengine: Loading SQL code from config file "/snap/digikam/90/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.dbengine: WAL mode is disabled for "digikam4.db" digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 16 digikam.coredb: Core database: makeUpdates 16 to 16 digikam.database: Creating new Location "/" uuid "volumeid:?path=/home/filip_rozsypal/Pictures&fileuuid=e12ffaac-3c20-443a-997d-ada6c714bde0" qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) digikam.database: Location for "/home/filip_rozsypal/Pictures" is available: true => case sensitivity: 2 digikam.general: Allowing a cache size of 1024 MB digikam.dbengine: WAL mode is disabled for "thumbnails-digikam.db" digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0 digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0 digikam.thumbsdb: Thumbs database: have a structure version "3" digikam.general: Thumbnails database ready for use digikam.dbengine: WAL mode is disabled for "similarity.db" digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0 digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0 digikam.similaritydb: Similarity database: have a structure version "1" digikam.similaritydb: Similarity database ready for use digikam.dimg: QList() digikam.dimg: Desktop platform is not X11 digikam.general: [GeolocationSettingsContainer] distanceUnit(0), angleUnit(1), stillQuality(3), animationQuality(1), mapFont(QFont(Cantarell,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1)), inertialRotation(true), mouseRotation(true), volatileTileCacheLimit(100), persistentTileCacheLimit(99), showGrid(true), showCross(false), showAtmosphere(false), showSunShading(false), showCities(true), showRelief(true) digikam.g
[digikam] [Bug 491473] digikam 8.4 does not start
https://bugs.kde.org/show_bug.cgi?id=491473
--- Comment #2 from Filip Rozsypal ---
(In reply to Maik Qualmann from comment #1)
> Please enable debug output by setting the environment variable in the
> terminal:
>
> export QT_LOGGING_RULES="digikam*=true"
>
> Maik
Thanks you for your help! here it is:
(also, if it helps, I have GTX 3070. I also tried appimage and it starts, but
has the same problems as running with --platform xcb)
$ digikam
libEGL warning: egl: failed to create dri2 screen
digikam.widgets: Use installed icons
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type:"QSQLITE"
DB Core Name:
"/home/filip_rozsypal/Pictures/db_new/digikam4.db"
DB Thumbs Name:
"/home/filip_rozsypal/Pictures/db_new/thumbnails-digikam.db"
DB Face Name:
"/home/filip_rozsypal/Pictures/db_new/recognition.db"
DB Similarity Name:
"/home/filip_rozsypal/Pictures/db_new/similarity.db"
Connect Options: ""
Host Name: ""
Host Port: -1
WAL Mode:false
Internal Server: false
Internal Server Path:""
Internal Server Init Cmd:""
Internal Server Admin Cmd: ""
Internal Server Program Cmd: ""
Internal Server Upgrade Cmd: ""
Username:""
Password:""
digikam.dbengine: Loading SQL code from config file
"/snap/digikam/90/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.dbengine: WAL mode is disabled for "digikam4.db"
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 16
digikam.coredb: Core database: makeUpdates 16 to 16
digikam.database: Creating new Location "/" uuid
"volumeid:?path=/home/filip_rozsypal/Pictures&fileuuid=e12ffaac-3c20-443a-997d-ada6c714bde0"
qt.core.qobject.connect: QObject::connect: No such signal
Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
qt.core.qobject.connect: QObject::connect: No such signal
Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType,
QVariant, QString)
qt.core.qobject.connect: QObject::connect: No such signal
Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
qt.core.qobject.connect: QObject::connect: No such signal
Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType,
QVariant, QString)
digikam.database: Location for "/home/filip_rozsypal/Pictures" is available:
true => case sensitivity: 2
digikam.general: Allowing a cache size of 1024 MB
digikam.dbengine: WAL mode is disabled for "thumbnails-digikam.db"
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
digikam.thumbsdb: Thumbs database: have a structure version "3"
digikam.general: Thumbnails database ready for use
digikam.dbengine: WAL mode is disabled for "similarity.db"
digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
digikam.similaritydb: Similarity database: have a structure version "1"
digikam.similaritydb: Similarity database ready for use
digikam.dimg: QList()
digikam.dimg: Desktop platform is not X11
digikam.general: [GeolocationSettingsContainer]
distanceUnit(0),
angleUnit(1),
stillQuality(3),
animationQuality(1),
mapFont(QFont(Cantarell,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1)),
inertialRotation(true),
mouseRotation(true),
volatileTileCacheLimit(100),
persistentTileCacheLimit(99),
showGrid(true),
showCross(false),
showAtmosphere(false),
showSunShading(false),
showCities(true),
showRelief(true)
digikam.general: Camera XML data:
"/home/filip_rozsypal/snap/digikam/90/.local/share/digikam/cameras.xml"
digikam.metaengine: ExifTool config path: "/snap/digikam/90/usr/bin/exiftool"
digikam.metaengine: Path to ExifTool: "/snap/digikam/90/usr/bin/exiftool"
digikam.metaengine: ExifToolProcess::start(): create new ExifTool instance:
"/snap/digikam/90/usr/bin/exiftool" QList("-stay_open", "true", "-@", "-",
"-common_args", "-charset", "filename=UTF8", "-charset", "iptc=UTF8")
digikam.metaengine: ExifTool process started
digikam.general: Starting to load external tools.
digikam.general: DK_PLUGIN_PATH env.variable detected. We will use it to load
plugin...
digikam.general: Parsing plugins from
QList("/snap/digikam/90/usr/lib/x86_64
[digikam] [Bug 491473] New: digikam 8.4 does not start
https://bugs.kde.org/show_bug.cgi?id=491473 Bug ID: 491473 Summary: digikam 8.4 does not start Classification: Applications Product: digikam Version: 8.4.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: filip.rozsy...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY digikam 8.4 installed via App Center in Ubuntu 24.04 does not start. It runs once after installation but after restart it fails to start up. STEPS TO REPRODUCE 1. install from app center 2. restart pc 3. start digikam OBSERVED RESULT the start-up window appears for a moment. It dissapears after "loading tools" is displayed, but main digikam windows does not appear. if I uninstall and run it again, it starts for the first time ok, but then it gets back to not starting properly. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 24.04 ADDITIONAL INFORMATION workaround: somewhere (I cant find it anymore) I found that starting with --platform xcb might help. Indeed, it does make digikam start fine, but then it does not work well (window turns black, responds to keyboard with a delay). Interestingly, after quitting digikam that started this way, I can then start digikam normally and it seems to work fine. However, if I quite this instance and start it again, it reverts to not starting again. terminal output of this sequence (digikam (does not start) -> digikam --platform xcb (starts but not usable) -> digikam ()works fine) -> digikam (does not start) ) looks like this $ digikam libEGL warning: egl: failed to create dri2 screen qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) digikam.general: DK_PLUGIN_PATH env.variable detected. We will use it to load plugin... Path override failed for key base::DIR_APP_DICTIONARIES and path '/snap/digikam/90/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/snap/digikam/90/kf6/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/snap/digikam/90/kf6/usr/lib/qt6/libexec/qtwebengine_dictionaries' Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed kf.sonnet.core: Unable to handle language from dictionary "kmr_Latn" "C" kf.sonnet.core: Unable to handle language from dictionary "ko_KR" "ko_KR" kf.sonnet.core: Unable to handle language from dictionary "ko" "ko_KR" kf.xmlgui: Unhandled container to remove : Digikam::DigikamApp digikam.general: parent is null ** (digikam:9589): WARNING **: 09:26:29.750: atk-bridge: get_device_events_reply: unknown signature $ digikam --platform xcb Gtk-Message: 09:21:01.239: Failed to load module "canberra-gtk-module" Gtk-Message: 09:21:01.239: Failed to load module "canberra-gtk-module" Qt: Session management error: Could not open network socket qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString) qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) digikam.general: DK_PLUGIN_PATH env.variable detected. We will use it to load plugin... Path override failed for key base::DIR_APP_DICTIONARIES and path '/snap/digikam/90/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/snap/digikam/90/kf6/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/snap/digikam/90/kf6/usr/lib/qt6/libexec/qtwebengine_dictionaries' KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permis
[kde] [Bug 490309] Gdzie najlepsze wróżby online?
https://bugs.kde.org/show_bug.cgi?id=490309 Filip changed: What|Removed |Added URL||https://twoje-wrozby.online -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490309] New: Gdzie najlepsze wróżby online?
https://bugs.kde.org/show_bug.cgi?id=490309 Bug ID: 490309 Summary: Gdzie najlepsze wróżby online? Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ortali...@gmail.com Target Milestone: --- Gdzie najlepiej zrobią mi wróżby online? Mam wiele dylematów i nie wiem już do kogo mam się zwrócić, dlatego napisałem tutaj. Polecono mi jedną witrynę jednak jeszcze nie testowałem. Może ktoś z was już z niej korzystał? Muszę przyznać, że wygląda bardzo wiarygodnie i ceny za usługi wróżbiarskie czy tarot są dość tanie. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 489183] New: "Open new files in tab" not working as expected
https://bugs.kde.org/show_bug.cgi?id=489183 Bug ID: 489183 Summary: "Open new files in tab" not working as expected Classification: Applications Product: okular Version: 23.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: gamer...@wp.pl Target Milestone: --- Option "Open new files in tab" is not working when opening PDF file by double clicking it in OS level explorer, but works when opening new file by using inapp menu "File -> Open". I would expect that file would open in existing Okular window, in new tab, even when opening it from OS level. Windows: 22H2 19045.4529 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 474368] New: Elisa crashes on system wake-up
https://bugs.kde.org/show_bug.cgi?id=474368 Bug ID: 474368 Summary: Elisa crashes on system wake-up Classification: Applications Product: Elisa Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: fcve...@gmail.com Target Milestone: --- Application: elisa (23.04.3) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.2.0-10018-tuxedo x86_64 Windowing System: X11 Distribution: TUXEDO OS 2 DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: I have two screens connected to my Zephyrus G14 (2020) running Tuxedo OS 2. Sometimes, on system wake-up, the entire desktop is messed up and the windows are blinking between the two screens. I fix this by disconnecting one of the screens and reconnecting it. Elisa crashed during this process (possibly before disconnecting the screen). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [KCrash Handler] #4 0x7ff03f56c4e8 in QScreen::handle() const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7ff03ad62d24 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #6 0x7ff03f58fe51 in QOpenGLContext::create() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7ff03fe1a328 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff03fe1c18c in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff03fe1cec7 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7ff03e8cebd3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7ff03e094b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #12 0x7ff03e126a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 10 (Thread 0x7ff0137fe640 (LWP 29082) "elisa"): #1 __pselect (nfds=5, readfds=0x7ff0137f5b40, writefds=0x0, exceptfds=0x0, timeout=, sigmask=) at ../sysdeps/unix/sysv/linux/pselect.c:56 #2 0x7ff03892803d in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #3 0x7ff038928d88 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #4 0x7ff03e094b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #5 0x7ff03e126a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 9 (Thread 0x7ff013fff640 (LWP 29081) "threaded-ml"): #1 0x7ff02944721d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7ff0294305a1 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7ff02943b0bb in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7ff02943b170 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7ff02944b37d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7ff023ec6cb3 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-15.99.so #7 0x7ff03e094b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #8 0x7ff03e126a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 8 (Thread 0x7ff018ff9640 (LWP 29080) "QThread"): #1 0x7ff03e0e56dd in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/sysv/linux/clock_gettime.c:42 #2 0x7ff03eb15c05 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff03eb144ad in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff03eb14a69 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff03eb1671e in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff03d2518e7 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7ff03d2a7123 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7ff03d24f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7ff03eb163ae in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff03eabb76b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7ff03e8cd962 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff03e8cebd3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7ff03e094b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7ff03e126a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 7 (Thread 0x7ff0197fa640 (LWP 29079) "QThread"): #1 0x7ff03e0e56dd in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/sysv/linux/clock_gettime.c:42 #2 0x7ff03eb15c05 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff03eb144ad in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff03eb14a69 in QTimerInfoList::timerWait
[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21
https://bugs.kde.org/show_bug.cgi?id=473745 --- Comment #11 from Filip Jorissen --- I can confirm that the current HEAD works again for me :) Thanks! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21
https://bugs.kde.org/show_bug.cgi?id=473745 --- Comment #7 from Filip Jorissen --- Bisection results: This commit works: 6ce0979884a8f246c80a098333ceef1a7b7f694d This is the first one that fails: 60f7e89ba32b54d73b9e36d49e28d0f559ade0b9 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21
https://bugs.kde.org/show_bug.cgi?id=473745 --- Comment #3 from Filip Jorissen --- I'm getting: ==15== Memcheck, a memory error detector ==15== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==15== Using Valgrind-3.22.0.GIT and LibVEX; rerun with -h for copyright info ==15== Command: pwd ==15== --15-- << --15---- REDIR STATE after VG_(redir_initialise) -- --15--TOPSPECS of soname (hardwired) --15-- ld-linux-x86-64.so.2 strlen RL-> (.0) 0x580bfe72 --15-- ld-linux-x86-64.so.2 index RL-> (.0) 0x580bfe8c --15---- ACTIVE -- --15-- 0xff60 (??? ) R-> (.0) 0x580bfe54 ??? --15-- 0xff600400 (??? ) R-> (.0) 0x580bfe5e ??? --15-- 0xff600800 (??? ) R-> (.0) 0x580bfe68 ??? --15-- >> --15-- Reading syms from /usr/bin/pwd --15--svma 0x002710, avma 0x10a710 --15-- << --15---- REDIR STATE after VG_(redir_notify_new_DebugInfo) -- --15--TOPSPECS of soname NONE filename /usr/bin/pwd --15--TOPSPECS of soname (hardwired) --15-- ld-linux-x86-64.so.2 strlen RL-> (.0) 0x580bfe72 --15-- ld-linux-x86-64.so.2 index RL-> (.0) 0x580bfe8c --15---- ACTIVE -- --15-- 0xff60 (??? ) R-> (.0) 0x580bfe54 ??? --15-- 0xff600400 (??? ) R-> (.0) 0x580bfe5e ??? --15-- 0xff600800 (??? ) R-> (.0) 0x580bfe68 ??? --15-- >> --15-- Reading syms from /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --15--svma 0x002090, avma 0x0004002090 MWE for future reference: echo FROM ubuntu:22.04 > Dockerfile echo "RUN apt-get update && apt-get -y install g++ autoconf libtool libtool-bin git subversion gfortran cmake ant" >> Dockerfile echo "RUN git clone git://sourceware.org/git/valgrind.git && cd valgrind && ./autogen.sh && ./configure --prefix=/usr/local && make -j8 && make install -j7" >> Dockerfile echo "RUN apt-get update && apt-get install -y libc6-dbg" >> Dockerfile docker image build -t testvalgrind . docker run -t testvalgrind valgrind --trace-redir=yes pwd -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21
https://bugs.kde.org/show_bug.cgi?id=473745 --- Comment #1 from Filip Jorissen --- There was an error in my original post. The clone command that does not work is "git clone git://sourceware.org/git/valgrind.git" instead of "git clone git://sourceware.org/git/valgrind.git -b VALGRIND_3_21_0". At the time of writing that is commit dc6669cee7b557945fd41417bf531c7f5c9f1093 . -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 473745] New: must-be-redirected function - strlen - for valgrind 3.22 but not 3.21
https://bugs.kde.org/show_bug.cgi?id=473745 Bug ID: 473745 Summary: must-be-redirected function - strlen - for valgrind 3.22 but not 3.21 Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: filip.joris...@builtwins.com Target Milestone: --- SUMMARY Valgrind 3.22 crashes/stops on Docker/Ubuntu 22.10 with the error below. STEPS TO REPRODUCE Relevant parts of the Dockerfile that created the image that produces this error: FROM ubuntu:22.04 RUN apt-get update && apt-get -y install g++ autoconf libtool libtool-bin RUN git clone git://sourceware.org/git/valgrind.git -b VALGRIND_3_21_0 && cd valgrind && ./autogen.sh && ./configure --prefix=/usr/local && make -j8 && make install -j7 RUN apt-get update && apt-get install -y libc6-dbg When replacing above code with RUN git clone git://sourceware.org/git/valgrind.git -b VALGRIND_3_21_0 the error is not produced and valgrind works correctly. It seems therefore that a bug was recently introduced? OBSERVED RESULT ==2287== Memcheck, a memory error detector ==2287== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==2287== Using Valgrind-3.22.0.GIT and LibVEX; rerun with -h for copyright info ==2287== Command: ./standalone -m ZoneWithAlgebraicLoopPostProcessing -s 0.00 -e 1.00 -t 5.00e-04 -i20 -w ==2287== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. EXPECTED RESULT No error SOFTWARE/OS VERSIONS Docker image ubuntu:22.04 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472915] Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 --- Comment #6 from Filip --- It does not depend on the application, it happens during switching windows (various apps used, everytime all of them crash). I would say it is quite urgent because I cannot work anymore, it happens very often. Tried several kernel versions (down to 6.3.12), still happens. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472915] Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 --- Comment #2 from Filip --- Created attachment 160731 --> https://bugs.kde.org/attachment.cgi?id=160731&action=edit New crash information added by DrKonqi akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.9 Crashes during Google Meet screen sharing in Chrome, but not every time. Crashes during normal work, just moving a mouse and all windows just shut down. -- Backtrace (Reduced): #4 0x562ee912f29b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f24f44c8264 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f24f449d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f24f44a0984 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f24f44eec27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472915] Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 Filip changed: What|Removed |Added CC||filipba...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469952] New: Spectacle crashes after screens power on due to moving mouse.
https://bugs.kde.org/show_bug.cgi?id=469952 Bug ID: 469952 Summary: Spectacle crashes after screens power on due to moving mouse. Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: fkwil...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (23.04.0) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.15-300.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I left computer for few minutes and screens turned black(thats normal). When i came back and moved mouse screens turned on and i saw notification about crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x0380 in ?? () #5 0x7fc8578e8651 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x7fc857d5f074 in QGuiApplication::screenRemoved(QScreen*) () from /lib64/libQt5Gui.so.5 #7 0x7fc857d93dc0 in QScreen::~QScreen() () from /lib64/libQt5Gui.so.5 #8 0x7fc857d93f35 in QScreen::~QScreen() () from /lib64/libQt5Gui.so.5 #9 0x7fc857d4a0c3 in QWindowSystemInterface::handleScreenRemoved(QPlatformScreen*) () from /lib64/libQt5Gui.so.5 #10 0x7fc8598c3854 in QtWaylandClient::QWaylandDisplay::registry_global_remove(unsigned int) () from /lib64/libQt5WaylandClient.so.5 #11 0x7fc857b80be6 in ffi_call_unix64 () from /lib64/libffi.so.8 #12 0x7fc857b7d4bf in ffi_call_int.lto_priv () from /lib64/libffi.so.8 #13 0x7fc857b8018e in ffi_call () from /lib64/libffi.so.8 #14 0x7fc859f4af0e in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #15 0x7fc859f4b793 in dispatch_event.isra () from /lib64/libwayland-client.so.0 #16 0x7fc859f4ba3c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #17 0x7fc8598beb4d in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #18 0x7fc8578df73b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7fc8591aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7fc8578b3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7fc8578b71f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x7fc857906e2f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x7fc85544339c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7fc8554a1438 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #25 0x7fc855440a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7fc857906919 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7fc8578b270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7fc8578ba99b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x56079cfec8bf in main () [Inferior 1 (process 15332) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467863] New: Dolphin opened by tmodloder crashes after closing it
https://bugs.kde.org/show_bug.cgi?id=467863
Bug ID: 467863
Summary: Dolphin opened by tmodloder crashes after closing it
Classification: Applications
Product: dolphin
Version: 22.12.3
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: fkwil...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (22.12.3)
Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.1.18-200.fc37.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.27.3 [KCrashBackend]
-- Information about the crash:
Afrer opening dolphin using tmodloder opening files with dolphin takes long
time. And dolphin opened by tmodloder often crashes after closing it.
Code that tmodloder uses to open folders:
private static void OpenFolderXdg(string folderPath)
{
ProcessStartInfo processStartInfo = new ProcessStartInfo {
FileName = "xdg-open",
Arguments = folderPath,
UseShellExecute = true,
CreateNoWindow = true
};
processStartInfo.EnvironmentVariables["LD_LIBRARY_PATH"] =
"/usr/lib:/lib";
Process.Start(processStartInfo);
}
The crash can be reproduced sometimes.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#4 0x7f7e9efa3ac6 in QWidgetWindow::handleMouseEvent(QMouseEvent*) [clone
.cold] () from /lib64/libQt5Widgets.so.5
#5 0x7f7e9f00e060 in QWidgetWindow::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#6 0x7f7e9efaed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#7 0x7f7e9e29d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8 0x7f7e9e76ad6d in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib64/libQt5Gui.so.5
#9 0x7f7e9e749f1c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib64/libQt5Gui.so.5
#10 0x7f7e9b75f604 in userEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5WaylandClient.so.5
#11 0x7f7e9c063c7f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#12 0x7f7e9c0ba118 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#13 0x7f7e9c060f00 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#14 0x7f7e9e2ee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#15 0x7f7e9e29bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#16 0x7f7e9e2a4002 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#17 0x5566d1a1d135 in main ()
[Inferior 1 (process 21336) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 Filip Brcic changed: What|Removed |Added CC||filip.br...@brcha.com --- Comment #8 from Filip Brcic --- I get the blank white screen for html mail as well. But if I open the mail in a new window everything works as expected. Operating System: NixOS 22.11 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-lqx1 Graphics Platform: Wayland Processors: AMD Ryzen 5 3600X (12) @ 3.800GHz Memory: 32 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060 SUPER -- You are receiving this mail because: You are watching all bug changes.
[kpackagekit] [Bug 262055] Do not allow my password, does not allow installing the required packages.
https://bugs.kde.org/show_bug.cgi?id=262055 --- Comment #7 from Filip Ciklevski --- No longer using the software. On Tue, Dec 20, 2022 at 8:49 AM Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=262055 > > Justin Zobel changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #6 from Justin Zobel --- > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463291] New: Dolphin could occasionally call "sync" to avoid data corruption
https://bugs.kde.org/show_bug.cgi?id=463291 Bug ID: 463291 Summary: Dolphin could occasionally call "sync" to avoid data corruption Classification: Applications Product: dolphin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sh...@paranoici.org CC: kfm-de...@kde.org Target Milestone: --- Hi, I use a lot removable storage. Be it pendrive or ssd for Virtual Machine. I need to force myself to remember to call sync. I do wonder if it's possible for dolphin to handle itself. Adding some animation would make it clear. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 463127] Weird polish translation of Kickoff application launcher
https://bugs.kde.org/show_bug.cgi?id=463127 --- Comment #1 from Filip Laszczak --- Of course it doesn't have HTML tags in translation, i want only to specify which tooltip are in bold font. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 463127] Weird polish translation of Kickoff application launcher
https://bugs.kde.org/show_bug.cgi?id=463127 Filip Laszczak changed: What|Removed |Added Summary|Weird translation of|Weird polish translation of |Kickoff application |Kickoff application |launcher|launcher -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 463127] New: Weird translation of Kickoff application launcher
https://bugs.kde.org/show_bug.cgi?id=463127 Bug ID: 463127 Summary: Weird translation of Kickoff application launcher Classification: Translations Product: i18n Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: pl Assignee: kdei18n-pl-uw...@lists.sourceforge.net Reporter: filip.laszczak.1...@gmail.com Target Milestone: --- Created attachment 154630 --> https://bugs.kde.org/attachment.cgi?id=154630&action=edit Screenshot of issue The problem is that in the Polish version of KDE, the Kickoff Application Launcher component has a very strangely translated tooltip when you hover the mouse over it. In direct translation it is: Program Launcher. Launcher to launch programs It looks strange in my opinion, we have to deal with the same word repeated three times, which is not so much misleading, but simply looks wrong. STEPS TO REPRODUCE 1. Hover a mouse on runner, in left bottom corner. OBSERVED RESULT Uruchamiacz programów Uruchamiacz do uruchamiania programów EXPECTED RESULT I don't know. Maybe delete second line, and leave only "Uruchamiacz programów"? SOFTWARE/OS VERSIONS Windows: -- macOS: -- Linux/KDE Plasma: Arch Linux / 5.26.4 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION My first issue, please leave a info, if i do something wrong. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 427178] I have connected second screen to my computer. Always when I close the laptop cover, screen's layout crashes and sets first screen above second after opening.
https://bugs.kde.org/show_bug.cgi?id=427178 --- Comment #4 from Filip Koperkiewicz --- I have no way to check if this bug still apply to the latest version of KDE Plasma. I don't have latest version, because it's not provided by my GNU/Linux distribution yet. You mark an issue as "resolved", but nobody confirmed it, nobody did a pull request mentioning this issue, so how can you tell it's resolved? Inactivity is not a good sign of problem solved, sometimes bugs keeps unfixed for years. https://www.youtube.com/watch?v=1lYgB_NHFYk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413298] Incorrect refresh rate reported
https://bugs.kde.org/show_bug.cgi?id=413298 Filip Fila changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Filip Fila --- There's no drop down anymore, it just says 60 Hz is the only rate the laptop reports so I'm going to say it got fixed along the way. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447774] File system expose cannot expose certain folders on Android 11
https://bugs.kde.org/show_bug.cgi?id=447774 Filip changed: What|Removed |Added CC||fi...@teknik.io -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458751] Laptop (Lenovo p15v gen1) awaken using mouse while lid is closed
https://bugs.kde.org/show_bug.cgi?id=458751 Filip Jakab changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458751] New: Laptop (Lenovo p15v gen1) awaken using mouse while lid is closed
https://bugs.kde.org/show_bug.cgi?id=458751 Bug ID: 458751 Summary: Laptop (Lenovo p15v gen1) awaken using mouse while lid is closed Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jakabfilip...@gmail.com Target Milestone: --- SUMMARY After closing the lid on my notebook the system correctly goes to sleep but when I then move my mouse (accidentally) it awakens from the sleep with lid still being closed.. STEPS TO REPRODUCE 1. Start your system (Manjaro, KDE) 2. Close lid to force system to sleep 3. Move with external mouse 4. Computer boots again OBSERVED RESULT Computer boots again EXPECTED RESULT Computer stays asleep SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.60-manjaro (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Display server: X11 Mouse used: unifying reciever with MX Master 3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455448] System freeze/crash when turning off and on monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=455448 Filip changed: What|Removed |Added CC||thebelle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450488] Wayland - turning DP monitor off and back on causes plasmashell hang
https://bugs.kde.org/show_bug.cgi?id=450488 Filip changed: What|Removed |Added CC||thebelle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237 filip changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from filip --- The problem no longer exists. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237 --- Comment #3 from filip --- In the current version KMail 5.20.1 (22.04.1) with Framework 5.94.0 the crash does not occur anymore. In addition, I had recreated the last filter list. Perhaps this also contributed to the problem solution. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452416] kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416 filip changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from filip --- The problem no longer exists. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452416] kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416 --- Comment #3 from filip --- The problem no longer exists. In the current version KMail 5.20.1 (22.04.1) with Framework 5.94.0 the crash does not occur anymore. In addition, I had recreated the last filter list. Perhaps this also contributed to the problem solution. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237 filip changed: What|Removed |Added Component|general |mail Version|unspecified |5.20.0 --- Comment #2 from filip --- Description from original BUG 452416: I have more than one filters to delete spam mails from spam folder. Already configured filters work without any problems. When i try to enter a new filter rule e.g. "From" contains "xyz.com" with Filter action "Delete" kmail crashes always. New: Also the navigation through the mail filter definitions crashes the Applikation -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237 --- Comment #1 from filip --- Original reported in BUG 452416 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452416] kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416 --- Comment #2 from filip --- (In reply to filip from comment #1) > Same Problem with the new framework and Applikation Version > See BUG report 543237 (sorry... drkonqi has created a new BUG report) New BUG report => 453237 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452416] kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416 --- Comment #1 from filip --- Same Problem with the new framework and Applikation Version See BUG report 543237 (sorry... drkonqi has created a new BUG report) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] New: kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237
Bug ID: 453237
Summary: kmail/kontakt crash when navigate in filter dialog or
add new filter
Product: kontact
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: v8fi...@gmail.com
Target Milestone: ---
Application: kontact (5.20.0 (22.04.0))
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Navigate through "Filter" dialog or add new filter rule
Same problem as in BUG 452416 in the new Framework and Application Version
The crash can be reproduced every time.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __gnu_cxx::__atomic_add (__val=1, __mem=0x10009) at
/usr/include/c++/11/ext/atomicity.h:71
#7 __gnu_cxx::__atomic_add_dispatch (__val=1, __mem=0x10009) at
/usr/include/c++/11/ext/atomicity.h:111
#8 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_add_ref_copy
(this=0x10001) at /usr/include/c++/11/bits/shared_ptr_base.h:148
#9 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count (__r=...,
this=0x7ffcb61238d8) at /usr/include/c++/11/bits/shared_ptr_base.h:712
#10 std::__shared_ptr::__shared_ptr (this=,
this=) at /usr/include/c++/11/bits/shared_ptr_base.h:1152
#11 std::shared_ptr::shared_ptr (this=0x7ffcb61238d0)
at /usr/include/c++/11/bits/shared_ptr.h:150
#12 MailCommon::SearchRuleWidgetLister::setRuleList (aList=0x5644db2bebe8,
this=0x5644db18b650) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/search/searchpatternedit.cpp:449
#13 MailCommon::SearchPatternEdit::setSearchPattern (this=0x5644db189ca0,
aPattern=0x5644db2bebe8) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/search/searchpatternedit.cpp:639
#14 0x7f72e7c5923f in MailCommon::KMFilterDialog::slotFilterSelected
(this=0x5644da815600, aFilter=0x5644db2bebe0) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/filter/kmfilterdialog.cpp:480
#15 0x7f7377bf7453 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb6123ab0,
r=0x5644da815600, this=0x5644db287500) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate (sender=0x5644da017cf0, signal_index=10,
argv=0x7ffcb6123ab0) at kernel/qobject.cpp:3886
#17 0x7f7377bf07af in QMetaObject::activate
(sender=sender@entry=0x5644da017cf0, m=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcb6123ab0)
at kernel/qobject.cpp:3946
#18 0x7f72e7c25d9b in MailCommon::KMFilterListBox::filterSelected
(_t1=, this=0x5644da017cf0) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/build/src/KF5MailCommon_autogen/CSB7XD6IZM/moc_kmfilterlistbox.cpp:291
#19 MailCommon::KMFilterListBox::slotSelected (this=0x5644da017cf0, aIdx=5) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/filter/kmfilterlistbox.cpp:386
#20 0x7f7377bf7453 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb6123bd0,
r=0x5644da017cf0, this=0x5644db17cc60) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x5644da6dd630, signal_index=23,
argv=0x7ffcb6123bd0) at kernel/qobject.cpp:3886
#22 0x7f7377bf07af in QMetaObject::activate
(sender=sender@entry=0x5644da6dd630, m=m@entry=0x7f7378cad4a0
, local_signal_index=local_signal_index@entry=8,
argv=argv@entry=0x7ffcb6123bd0) at kernel/qobject.cpp:3946
#23 0x7f7378a2e801 in QListWidget::currentRowChanged
(this=this@entry=0x5644da6dd630, _t1=) at
.moc/moc_qlistwidget.cpp:417
#24 0x7f7378a2f67b in QListWidgetPrivate::_q_emitCurrentItemChanged
(this=, current=..., previous=...) at
itemviews/qlistwidget.cpp:1236
#25 0x7f7377bf7488 in doActivate (sender=0x5644da6eaf30,
signal_index=4, argv=0x7ffcb6123d40) at kernel/qobject.cpp:3898
#26 0x7f7377bf07af in QMetaObject::activate
(sender=sender@entry=0x5644da6eaf30, m=m@entry=0x7f7377e94e60
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcb6123d40)
at kernel/qobject.cpp:3946
#27 0x7f7377b6b653 in QItemSelectionModel::currentChanged
(this=this@entry=0x5644da6eaf30, _t1=..., _t2=...) at
.moc/moc_qitemselectionmodel.cpp:482
#28 0x7f7377b6f039 in QItemSelectionModel::setCurrentIndex
(this=0x5644da6eaf30, index=..., command=...) at
itemmodels/qitemselectionmodel.cpp:1416
#29 0x7f73789e5a13 in QAbstractItemView::mousePressEvent
(this=0x5644da6dd630, event=) at
itemviews/qabstractitemview.cpp:1786
#30 0x7f73787b3cde in QWidget::event (this=this@entry=0x5644da6dd630,
event=event@entry=0x7ffcb61243f0) at kernel/qwidget.cpp:9020
#31 0x
[kmail2] [Bug 452416] kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416 filip changed: What|Removed |Added Version|unspecified |5.19.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452416] New: kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416
Bug ID: 452416
Summary: kmail crash when add new filter rule
Product: kmail2
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: v8fi...@gmail.com
Target Milestone: ---
Application: kmail (5.19.3 (21.12.3))
Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.17.1-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
I have more than one filters to delete spam mails from spam folder.
Already configured filters work without any problems.
When i try to enter a new filter rule e.g. "From" contains "xyz.com" with
Filter action "Delete"
kmail crashes always.
The crash can be reproduced every time.
-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 QByteArray::QByteArray (a=..., this=0x7ffe35dc3408) at
/usr/include/qt5/QtCore/qbytearray.h:524
#7 MailCommon::SearchRule::field (this=0x5634fd65b7da) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/search/searchrule/searchrule.cpp:507
#8 0x7fd0ee8d572b in MailCommon::SearchRuleWidget::setRule
(this=0x56319e4cacd0, aRule=std::shared_ptr (use count
2, weak count 0) = {...}) at /usr/include/c++/11/bits/shared_ptr_base.h:1295
#9 0x7fd0ee8dfed1 in MailCommon::SearchRuleWidgetLister::setRuleList
(aList=0x56319e239048, this=0x56319d45e260) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/search/searchpatternedit.cpp:454
#10 MailCommon::SearchPatternEdit::setSearchPattern (this=0x56319d45bcc0,
aPattern=0x56319e239048) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/search/searchpatternedit.cpp:646
#11 0x7fd0ee8a71ef in MailCommon::KMFilterDialog::slotFilterSelected
(this=0x56319e105240, aFilter=0x56319e239040) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/filter/kmfilterdialog.cpp:480
#12 0x7fd0ef382503 in QtPrivate::QSlotObjectBase::call (a=0x7ffe35dc36b0,
r=0x56319e105240, this=0x56319e200300) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x56319d3e30a0, signal_index=10,
argv=0x7ffe35dc36b0) at kernel/qobject.cpp:3886
#14 0x7fd0ef37b9cf in QMetaObject::activate
(sender=sender@entry=0x56319d3e30a0, m=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe35dc36b0)
at kernel/qobject.cpp:3946
#15 0x7fd0ee86e3eb in MailCommon::KMFilterListBox::filterSelected
(_t1=, this=0x56319d3e30a0) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/build/src/KF5MailCommon_autogen/CSB7XD6IZM/moc_kmfilterlistbox.cpp:291
#16 MailCommon::KMFilterListBox::slotSelected (this=this@entry=0x56319d3e30a0,
aIdx=5) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/filter/kmfilterlistbox.cpp:407
#17 0x7fd0ee871ae4 in MailCommon::KMFilterListBox::applyFilterChanged
(this=0x56319d3e30a0, closeAfterSaving=) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/filter/kmfilterlistbox.cpp:341
#18 0x7fd0ee8a6c43 in MailCommon::KMFilterListBox::slotAccepted
(this=) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/filter/kmfilterlistbox.cpp:329
#19 MailCommon::KMFilterDialog::slotSaveSize (this=0x56319e105240) at
/usr/src/debug/mailcommon-21.12.3-1.2.x86_64/src/filter/kmfilterdialog.cpp:466
#20 0x7fd0ef382503 in QtPrivate::QSlotObjectBase::call (a=0x7ffe35dc3870,
r=0x56319e105240, this=0x56319e201b90) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x56319d3e7ae0, signal_index=9,
argv=0x7ffe35dc3870) at kernel/qobject.cpp:3886
#22 0x7fd0ef37b9cf in QMetaObject::activate
(sender=sender@entry=0x56319d3e7ae0, m=m@entry=0x7fd0f041a4e0
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe35dc3870)
at kernel/qobject.cpp:3946
#23 0x7fd0effeff32 in QAbstractButton::clicked
(this=this@entry=0x56319d3e7ae0, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#24 0x7fd0efff01aa in QAbstractButtonPrivate::emitClicked
(this=0x56319d5a2c20) at widgets/qabstractbutton.cpp:415
#25 0x7fd0efff1d70 in QAbstractButtonPrivate::click (this=0x56319d5a2c20)
at widgets/qabstractbutton.cpp:408
#26 0x7fd0efff1f93 in QAbstractButton::mouseReleaseEvent
(this=0x56319d3e7ae0, e=0x7ffe35dc3e10) at widgets/qabstractbutton.cpp:1044
#27 0x7fd0eff3e8de in QWidget::event (this=0x56319d3e7ae0,
event=0x7ffe35dc3e10) at kernel/qwidget.cpp:9020
#28 0x7fd0efefca7f in QApplicationPrivate::notify_helper
(this=this@entry=0x563197c9e850, receiver=receiver@entry=0x56319d3e7ae0,
e=e@entry=0x7ffe35dc3e10) at kernel/qapplication.cpp:3632
#29 0x7fd0eff04584 in QApplication::notify (this=,
receiver=0x56319d3e7ae0, e=0x7ffe35dc3e10) at kernel
[frameworks-baloo] [Bug 449355] New: High memory usage when idle
https://bugs.kde.org/show_bug.cgi?id=449355 Bug ID: 449355 Summary: High memory usage when idle Product: frameworks-baloo Version: 5.90.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: k...@autom.zone Target Milestone: --- Created attachment 146065 --> https://bugs.kde.org/attachment.cgi?id=146065&action=edit Screenshots SUMMARY The process baloo_file is sitting on 6.4 Gb of memory, while ksysguard reports the confusing "Status: idle, 75% done" (and has done so for ~20 hours). STEPS TO REPRODUCE Not sure if this will reproduce my problem, bit this is what I've done recently: 1. My Windows computer gave up the ghost so I dumped all files from that drive into my downloads folder, and baloo started indexing it. That's 277.3 GB of all kinds of files. 2. After four days it was still indexing and maxing out HDD bandwidth, so I blacklisted the downloads folder (using ksysguard). 3. ksysguard reported that baloo did some index cleanup and now says idle. I let the computer run overnight to see if baloo would release the memory, it hadn't. 4. I tried rebooting, but baloo always ramps up to the same memory usage in a few minutes after startup. OBSERVED RESULT Above. EXPECTED RESULT I know baloo uses a lot of resources, but I expect at least a message in ksysguard that is more helpful in explaining what's going on; it is clearly doing something and not idling. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.2-1-MANJARO (64 bt) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Baloo 5.90.0 Relevant screenshots attached. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446042] New: PC not waking properly after inactivity sleep
https://bugs.kde.org/show_bug.cgi?id=446042 Bug ID: 446042 Summary: PC not waking properly after inactivity sleep Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: jakabfilip...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 143908 --> https://bugs.kde.org/attachment.cgi?id=143908&action=edit File containing logs since wake starts (search for "### SUSPENDING HERE" to skip to the beginning of sequence) SUMMARY When I left PC running it switched itself to sleep (for inactivity). When I wake it up by pressing keyboard key/moving mouse (in latest incident pressing `ESC`). The CPU fan spins up and power LEDs start to blink (I think this is normal) but neither monitor not keyboard backlight turn on STEPS TO REPRODUCE This does not happen always.. 1. Let PC fall asleep after inactivity, 2. Wake it somehow OBSERVED RESULT The PC wakes but provides no visible output. I can either kill the PC (holding power button) or now I tried the reset button which worked. EXPECTED RESULT PC awakes regularly. SOFTWARE/OS VERSIONS Info center: https://ibb.co/MpRx2TQ ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 443395] KSysGuard's 'History' tab causes enourmeous lagging
https://bugs.kde.org/show_bug.cgi?id=443395 --- Comment #4 from Filip Jakab --- Sorry for waiting. I use Nvidia GeForce 1060 6G. Once you mentioned the driver I realized I forgot to install proprietary nvidia driver and instead used the default nouveau.. After installing nvidia driver the issue disappeared.. Sorry for inconvenience. For the record the nouveau package was: xf86-video-nouveau 1.0.17-1 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 372464] Simple editing/annotation features (drawing Arrows / Text / Highlighting) after doing screenshot
https://bugs.kde.org/show_bug.cgi?id=372464 Filip Jakab changed: What|Removed |Added CC||jakabfilip...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443396] New: Reordering titlebar buttons is troublesome
https://bugs.kde.org/show_bug.cgi?id=443396 Bug ID: 443396 Summary: Reordering titlebar buttons is troublesome Product: systemsettings Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jakabfilip...@gmail.com Target Milestone: --- SUMMARY First issue is that right-aligned buttons overflow beyond the dummy window's titlebar. Second thing is that dragging button from options list to the titlebar visually does nothing.. But saving the changes after each modification does the trick in the end. But coming back to the edit, the buttons are not there anyway. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.8-arch1-1 64-bit (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 443395] New: KSysGuard's 'History' tab causes enourmeous lagging
https://bugs.kde.org/show_bug.cgi?id=443395 Bug ID: 443395 Summary: KSysGuard's 'History' tab causes enourmeous lagging Product: plasma-systemmonitor Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: jakabfilip...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY The 'History' tab of KSysGuard causes lags (mouse position is updated like each second.. When in edit mode, its very little bit better. I found that 'minimum update time' for each graph is set to 'No limit' initially so updating it to 1 second intervals makes it little bit more bearable but still laggy compared to 'Applications' tab for example. STEPS TO REPRODUCE 1. Open KSysGuard 2. Switch to 'History' tab OBSERVED RESULT Its lagging. EXPECTED RESULT It should not lag. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.8-arch1-1 64bit (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I have Ryzen 5 3600 6-core CPU with 64G of RAM, if that makes a difference.. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443392] New: Sort mechanism of 'Get new (global themes for example)' does not work
https://bugs.kde.org/show_bug.cgi?id=443392 Bug ID: 443392 Summary: Sort mechanism of 'Get new (global themes for example)' does not work Product: systemsettings Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jakabfilip...@gmail.com Target Milestone: --- Created attachment 142207 --> https://bugs.kde.org/attachment.cgi?id=142207&action=edit Evidence of incorrect order in 'Get new...' modal window SUMMARY Changing sort in 'Get new global themes' to 'Most downloaded' does not correlate to what downloads numbers in list says. STEPS TO REPRODUCE 1. Open Global themes 2. Click 'Sort by' -> 'Most downloaded first' OBSERVED RESULT Result is not sorted EXPECTED RESULT Result is sorted SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch linux (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438177] Anti-aliasing setting not written to /etc/sddm.conf.d/kde_settings.conf during a sync
https://bugs.kde.org/show_bug.cgi?id=438177 Filip Fila changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||filipfila@gmail.com Status|REPORTED|NEEDSINFO --- Comment #9 from Filip Fila --- Lua, you seem to be talking about the lock screen and not the login screen. SDDM and its KCM handle the login screen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 439847] Breeze SVGs used for third-party themes even though they shouldn't be
https://bugs.kde.org/show_bug.cgi?id=439847 Filip Fila changed: What|Removed |Added CC||aleix...@kde.org, ||niccolo.venera...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 439847] New: Breeze SVGs used for third-party themes even though they shouldn't be
https://bugs.kde.org/show_bug.cgi?id=439847 Bug ID: 439847 Summary: Breeze SVGs used for third-party themes even though they shouldn't be Product: frameworks-plasma Version: 5.84.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: filipfila@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 140060 --> https://bugs.kde.org/attachment.cgi?id=140060&action=edit SVGs drawn when they shouldn't be SUMMARY Updating frameworks to 5.84 breaks the "fromCurrentTheme" property for SVGs. This property is used in PlasmoidHeading so that nothing gets drawn when the theme doesn't have an SVG for the headings. Without that property, Breeze's SVGs get imposed on other themes, which is what has started happening now. It looks pretty bad and breaks third-party themes. STEPS TO REPRODUCE 1. Update to 5.84 2. Use some Plasma theme that doesn't have SVGs for PlasmoidHeading (e.g. WhiteSur, ChromeOS, ROUNDED) 3. Observe that PlasmoidHeadings are now drawn and that it looks pretty bad OBSERVED RESULT PlasmoidHeading drawn when it shouldn't be. EXPECTED RESULT PlasmoidHeading not drawn when it shouldn't be. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.22.3 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437153] filenamesearch crashes in KCoreDirLister
https://bugs.kde.org/show_bug.cgi?id=437153 --- Comment #9 from Filip Fila --- (In reply to postix from comment #8) > (In reply to Filip Fila from comment #7) > > I'm using Frameworks 5.83 and I still get "The process for the filename > > search protocol died unexpectedly" error when trying to search in Dolphin. > > Do you have a complete stacktrace? For me it's fixed on openSUSE TW, > Frameworks 5.83. This is Manjaro so I don't have debug symbols. I'm running 5.83.0 with Baloo completely disabled. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437153] filenamesearch crashes in KCoreDirLister
https://bugs.kde.org/show_bug.cgi?id=437153 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #7 from Filip Fila --- I'm using Frameworks 5.83 and I still get "The process for the filename search protocol died unexpectedly" error when trying to search in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416437] Search shows entry with no text when searching for "tra" twice
https://bugs.kde.org/show_bug.cgi?id=416437 --- Comment #9 from Filip Fila --- (In reply to Nate Graham from comment #8) > I'm no longer able to reproduce this the way I could before. Can anyone > still reproduce it in Plasma 5.22? no -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436137] After typing the password, when synchronizing SDDM settings, there's nothing indicating that the process is done
https://bugs.kde.org/show_bug.cgi?id=436137 Filip Fila changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #5 from Filip Fila --- *** Bug 437868 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437868] Provide Confirmation That Synchronization Happened
https://bugs.kde.org/show_bug.cgi?id=437868 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Filip Fila --- *** This bug has been marked as a duplicate of bug 436137 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 434398] Wallpaper grid delegates position gets messed up on window resize
https://bugs.kde.org/show_bug.cgi?id=434398 --- Comment #7 from Filip Fila --- (In reply to Nate Graham from comment #6) > Thanks for the video. I just got it to happen by resizing the window > violently a lot. :) I can't figure out what action or movement makes it > happen, but I can confirm the issue now. > > I cannot reproduce it with any System Settings KCMs using grid views when I > open them up in KCMshell and try the same violent resizing. Can you? Yeah it does take some violence to trigger :) Can't confirm with KCMs either. And what's really interesting is that I can't reproduce the bug on a different machine with the same software versions, but with Nvidia proprietary drivers. (I'm seeing the bug on an Intel iGPU machine) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 434398] Wallpaper grid delegates position gets messed up on window resize
https://bugs.kde.org/show_bug.cgi?id=434398 --- Comment #5 from Filip Fila --- Created attachment 136720 --> https://bugs.kde.org/attachment.cgi?id=136720&action=edit Video of the bug I don't know but here's a recording of the bug. (not related to theming either, I checked with stock settings) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 434398] Wallpaper grid delegates position gets messed up on window resize
https://bugs.kde.org/show_bug.cgi?id=434398 --- Comment #3 from Filip Fila --- Yes, I can still reproduce it. Do you have wallpapers with long strings whose names get elided? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 434398] Wallpaper grid delegates position gets messed up on window resize
https://bugs.kde.org/show_bug.cgi?id=434398 --- Comment #1 from Filip Fila --- Created attachment 136669 --> https://bugs.kde.org/attachment.cgi?id=136669&action=edit Missing delegats Can also result in delegates missing from the grid -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 434398] New: Wallpaper grid delegates position gets messed up on window resize
https://bugs.kde.org/show_bug.cgi?id=434398 Bug ID: 434398 Summary: Wallpaper grid delegates position gets messed up on window resize Product: frameworks-kdeclarative Version: 5.79.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: filipfila@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 136668 --> https://bugs.kde.org/attachment.cgi?id=136668&action=edit Broken grid SUMMARY Resizing the wallpaper chooser window can result in grid delegates being wrongly positioned. STEPS TO REPRODUCE 1. (Have a decent amount of wallpapers) 2. Resize the wallpaper chooser window OBSERVED RESULT The grid gets broken, some delegates intersect each other. EXPECTED RESULT The grid is not broken. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434324] Panel icon sizes don't change gradually enough
https://bugs.kde.org/show_bug.cgi?id=434324 Filip Fila changed: What|Removed |Added CC||n...@kde.org Assignee|plasma-b...@kde.org |niccolo.venera...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434324] New: Panel icon sizes don't change gradually enough
https://bugs.kde.org/show_bug.cgi?id=434324 Bug ID: 434324 Summary: Panel icon sizes don't change gradually enough Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: filipfila@gmail.com Target Milestone: 1.0 Created attachment 136612 --> https://bugs.kde.org/attachment.cgi?id=136612&action=edit Example of big icon with panel height at 38 SUMMARY I noticed that in Plasma 5.21 using the panel with the height set at 38 results in the panel icons being bigger than before. This also mean the icon is now very close to the highlight effect's line. When reducing the panel height to 36, the icon sizes are reduced and there is more vertical padding. As Nate said, "seems like the icon sizes jump to the next biggest size a little bit too early to feel comfortable". STEPS TO REPRODUCE 1. Compare icon sizes when alternating between two panel heights: 36 and 38 OBSERVED RESULT Fairly big icons with panel height at 38 EXPECTED RESULT Normal sized icons with panel height at 36 SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 --- Comment #34 from Filip Fila --- I still have this problem on my laptop with a SATA SSD and formatted as ext4. System updates or just about any significant file operation will lock the system up. But I managed to completely solve the problem on my PC (where I had the same issues) when I migrated to a NVMe SSD formatted as f2fs. I don't think the NVMe part should have been that significant because SATA is still plenty fast and doesn't lock up in other DEs or OS'. Ext4 is also fine in other DEs from recollection, but perhaps something in KDE just doesn't work well with it but works OK with f2fs. IIRC changing the schedulers doesn't help. If someone wants me to do more rigorous testing just give me steps and I'll give it a try. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432930] Synced font data not actually taking effect on login screen
https://bugs.kde.org/show_bug.cgi?id=432930 --- Comment #5 from Filip Fila --- The currently supported way of syncing the font isn't too friendly. See: https://www.reddit.com/r/kde/comments/j6vz2u/tip_how_to_change_the_font_on_the_login_screen/ For SDDM versions 0.19 and up we can actually properly sync the font if we land this: https://phabricator.kde.org/D23257 Nate and/or David, can you check if it still works and push it? If not, I can give it a try when I find some time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428590] Provide apply langauge/locales system-wide
https://bugs.kde.org/show_bug.cgi?id=428590 Filip Fila changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INTENTIONAL |--- CC||filipfila@gmail.com Ever confirmed|0 |1 --- Comment #11 from Filip Fila --- This is a legitimate issue and at least partly our issue, let's not dismiss it by saying it's Minecraft's problem. Here's a real life situation: - you're good in English - you've installed Linux and set up English as the locale - your login screen is in English and uses its formats - other users (family) that are going to be using the computer turn up - they don't want a login screen in English because they don't know it - but you can't change it anywhere in the GUI I've tried to help by having the user locale be synced to SDDM. I was not successful, but we should try to come up with something nevertheless. The argument that the fact that changing the system's locale requires root permission makes it not our responsibility can't really hold because our entire SDDM KCM is already doing root things. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428754] KDEConnect shows notification on desktop if VLC is paused on desktop
https://bugs.kde.org/show_bug.cgi?id=428754 Filip changed: What|Removed |Added CC||fi...@teknik.io --- Comment #3 from Filip --- (In reply to Daniel from comment #2) > Can confirm. As far as I can tell it happens with every media player which > supports MPRIS, and for that KDEConnect sends a media control notification > to Android, from there a new notification is sent to the PC/other devices. +1 Disabling media control notification plugin on Android works around the issue btw. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427712] Option to select custom category under unsplash picture of the day
https://bugs.kde.org/show_bug.cgi?id=427712 Filip Fila changed: What|Removed |Added CC||i...@guoyunhe.me -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424639] Selected SDDM is not remembered in KCM: Not pre-selected, apply button turns on always on selection
https://bugs.kde.org/show_bug.cgi?id=424639 Filip Fila changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Filip Fila --- Thanks for the quick reply. I'm also running Manjaro (Plasma is at 5.20) but it works for me. Going to switch back the status to "Reported" since I can't reproduce it but additional info was provided. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403933] SDDM Theme Store Crashed
https://bugs.kde.org/show_bug.cgi?id=403933 Filip Fila changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|NEEDSINFO CC||filipfila@gmail.com --- Comment #1 from Filip Fila --- Since this was reported on an older version of everything, please check if the problem persists with recent software. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411504] "You will be asked to authenticate before saving" takes a few milliseconds to appear below the header of SDDM kcm
https://bugs.kde.org/show_bug.cgi?id=411504 Filip Fila changed: What|Removed |Added Ever confirmed|0 |1 CC||filipfila@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Filip Fila --- If you switch to Icon View-ed system settings and open it directly from the launcher, more elements also don't show up immediately. Worth it to investigate if it's a problem with system settings itself. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424639] Selected SDDM is not remembered in KCM: Not pre-selected, apply button turns on always on selection
https://bugs.kde.org/show_bug.cgi?id=424639 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Filip Fila --- I can't reproduce it, but it reminds me of this older permissions issue. Check the permissions on etc/sddm.conf or etc/sddm.conf.d/kde_settings.conf. Or to make it easier, just go into the Advanced tab and press Sync. That will fix the permissions. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427726] Test Mode option for SSDM KCM
https://bugs.kde.org/show_bug.cgi?id=427726 Filip Fila changed: What|Removed |Added Ever confirmed|0 |1 CC||filipfila@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Filip Fila --- I agree. It will probably have to wait for the KCM rewrite though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425395] Synch touchpad settings with SDDM
https://bugs.kde.org/show_bug.cgi?id=425395 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Filip Fila --- I tried to sync all of this but unfortunately couldn't get SDDM to follow Plasma settings. SDDM itself probably needs patches to even support configuring this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 427178] New: I have connected second screen to my computer. Always when I close the laptop cover, screen's layout crashes and sets first screen above second after opening.
https://bugs.kde.org/show_bug.cgi?id=427178 Bug ID: 427178 Summary: I have connected second screen to my computer. Always when I close the laptop cover, screen's layout crashes and sets first screen above second after opening. Product: KScreen Version: 5.12.8 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: fkoperkiew...@gmail.com Target Milestone: --- Created attachment 132031 --> https://bugs.kde.org/attachment.cgi?id=132031&action=edit Excepted and observed result SUMMARY I have connected second screen to my computer. Always when I close the laptop cover, screen's layout crashes and sets first screen above second after opening. STEPS TO REPRODUCE 1. Set sleep mode after closing laptop cover in power settings. 2. Connect additional screen to computer. 3. Configure this screen to extend desktop at right side (KScreen) 4. Close the cover, wait for sleep and open. OBSERVED RESULT See: summary. I think when laptop cover is closing, system thinks that one of screens - build-in or additional is disconnected. EXPECTED RESULT System should remember layout of screens and restore it when they'll be connected again. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Problem doesn't happen if screen lock is enabled after closing the cover in power settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #364 from Filip Fila --- Guys it's been a long time and you can clearly see that: a) this isn't a priority for developers; b) complaining has an adverse effect on their interest I sympathize with all of you since I used to fervently lobby for my issues. I couldn't understand why developers didn't view some of them as important. Eventually I switched my approach to trying to change as much as I could myself, although that wasn't much. After some time, that evolved into seeing that, in the greater scheme of things and life, the desire to have my computer environment be exactly how I want it to be really isn't too important. Maybe my experience can resonate with some of you. Besides, ancient wisdom says we should try to cease worrying over all the things we have no influence over. But if you still feel strongly about this, the only thing I see as a way out is to create a bounty of sorts that someone would then be more likely to take you up on instead of working pro bono. But as most main KDE developers are already paid to work on KDE, it would most likely have to be someone else doing the work... which given that they would not be a maintainer makes it impossible to guarantee that their patches would get accepted. So it seems to me that a reasonable path forward is to first communicate with developers if they would be open to a patch from a third-party via a bounty. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422339] KDE Plasma Login-screen bug (NEW)
https://bugs.kde.org/show_bug.cgi?id=422339 Filip Fila changed: What|Removed |Added Keywords|needs_verification | Status|REPORTED|CONFIRMED Version|5.18.5 |5.19.0 CC||filipfila@gmail.com Ever confirmed|0 |1 --- Comment #2 from Filip Fila --- This is indeed a problem. I already tried to add locale settings to the list of things that can be synced from Plasma but unfortunately I believe I could never override /etc/locale.conf. The locale settings module could have an option to apply settings globally instead of just for the current user. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422339] Login screen locale not synced with user
https://bugs.kde.org/show_bug.cgi?id=422339 Filip Fila changed: What|Removed |Added Summary|KDE Plasma Login-screen bug |Login screen locale not |(NEW) |synced with user -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420769] Font rendering is different (not quite as sharp) in applications that use Kirigami
https://bugs.kde.org/show_bug.cgi?id=420769 Filip Fila changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from Filip Fila --- Yeah this should be a qt5ct bug. I just reproduced it by setting the QT_QPA_PLATFORMTHEME to qt5ct. It insists on doing its own font rendering for QML and disobeys the Plasma setting. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420769] Font rendering is different (not quite as sharp) in applications that use Kirigami
https://bugs.kde.org/show_bug.cgi?id=420769 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #4 from Filip Fila --- I can't reproduce this, but it looks like hinting is turned off in Discover (QML). What's in the .config/fontconfig folder? Btw you should avoid using qt5ct as it tries to take over Plasma theming and doesn't do as good of a job as Plasma. It's precisely known for messing up QML apps. You could also try removing it to see if it changes anything. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 404927] FrameSvgItem corruption: Right end of OSD volume indicator bar is sometimes rounded, sometimes flat, sometimes chopped-up
https://bugs.kde.org/show_bug.cgi?id=404927 --- Comment #8 from Filip Fila --- Created attachment 128820 --> https://bugs.kde.org/attachment.cgi?id=128820&action=edit Bug-free 'bar_meter_horizontal' SVG from the Matcha-Color theme -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 404927] FrameSvgItem corruption: Right end of OSD volume indicator bar is sometimes rounded, sometimes flat, sometimes chopped-up
https://bugs.kde.org/show_bug.cgi?id=404927 Filip Fila changed: What|Removed |Added CC||noaha...@gmail.com --- Comment #7 from Filip Fila --- Actually (and fortunately) it might just be an SVG problem. Gonna attach an SVG from the Matcha-Color theme that doesn't have this issue. Noah, do you have an idea what we're doing wrong and they're doing right? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404927] Right end of OSD volume indicator bar is sometimes rounded, sometimes flat, sometimes chopped-up
https://bugs.kde.org/show_bug.cgi?id=404927 --- Comment #5 from Filip Fila --- Created attachment 128816 --> https://bugs.kde.org/attachment.cgi?id=128816&action=edit A naughty hack that makes the bug go away -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404927] Right end of OSD volume indicator bar is sometimes rounded, sometimes flat, sometimes chopped-up
https://bugs.kde.org/show_bug.cgi?id=404927 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #4 from Filip Fila --- I've looked into what could be causing this. How to reproduce and test changes: you need to log out and in again because restarting plasmashell makes the bug go away What's not causing it: the PlasmaComponents qml files themselves, both PC2 and PC3 The culprit is most likely frameSvgItem. If you replace it with a circular Rectangle as the indicator you'll see this bug doesn't happen. See attached hack. It shouldn't be a problem with our SVGs since I've seen it happen with other themes but can't say for sure. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411668] Different mouse pointer speed on wayland with the same settings
https://bugs.kde.org/show_bug.cgi?id=411668 --- Comment #8 from Filip Fila --- (In reply to Nate Graham from comment #6) > Yes please. Not sure #2 is fixable though. If it is, Filip will know! :) I don't see any pointer speed property we can set in SDDM's config file. I also tried to see if it would read our kcminputrc file and it can't. It's probably a similar situation as with fonts: it's following some Qt default setting and modifying plus exposing the option would require an SDDM patch. We'd then add that to list of things synced in sddm-kcm. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 378504] [proposal] Add LCD filter settings to font config
https://bugs.kde.org/show_bug.cgi?id=378504 --- Comment #7 from Filip Fila --- I lacked certain information when suggesting this. Apparently the LCDFilter is only necessary for distros (like openSUSE) that use some ClearType subpixel renderer. Distros like Arch still use FreeType's own product, which doesn't struggle with color fringing and what's more toggling the lcdfilter is actually useless. Taking that into account, distros that need it should probably turn it on themselves. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)
https://bugs.kde.org/show_bug.cgi?id=414396 --- Comment #44 from Filip Fila --- Actually, why are you getting this "half-configured" message? I haven't used apt in a while, but the internet says you can do: sudo dpkg --configure -a to fix all of such issues, or for this specific package: sudo apt-get install --reinstall kde-config-sddm -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)
https://bugs.kde.org/show_bug.cgi?id=414396 Filip Fila changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #42 from Filip Fila --- I tested Kubuntu 19.10 with 5.18.2 (backports). Everything works. I used the exact same themes and even added a custom background. It should also be impossible for the Sync function to save the theme since that's not what its code does. There should be no reason for Kubuntu and Arch to behave differently. Sorry, I have tried everything at this point. I can reopen if another user shows up or investigate further if you post the following: 1) output of 'apt list kde-config-sddm' (I can't see it in your logs because all they show is KDE Frameworks and Applications, there is not a single Plasma package there) 2) if the output of the command above shows 5.18.2 is installed then a screen recording of the issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)
https://bugs.kde.org/show_bug.cgi?id=414396 --- Comment #39 from Filip Fila --- Sorry, I've now tried multiple times and whichever theme I save the settings window will highlight it correctly the next time it's started. My sddm.conf is empty and the theme is being saved correctly to kde_settings.conf. The only way I can reproduce your troubles is if I change the theme and then immediately go to 'Advanced' and press 'Sync' instead of actually clicking 'Apply' on the bottom. Clicking 'Sync' is not the proper way to change the theme since it only applies what the sync function is supposed to do. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)
https://bugs.kde.org/show_bug.cgi?id=414396 --- Comment #37 from Filip Fila --- Can you tell us again in one or two short sentences what the problem is? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 404396] Page titles are no longer the same size as a level 1 Heading
https://bugs.kde.org/show_bug.cgi?id=404396 --- Comment #7 from Filip Fila --- Headings in QML KCMs still seem slightly smaller than in QWidgets one, although the difference doesn't seem to be as profound as it was before. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413298] Incorrect refresh rate reported
https://bugs.kde.org/show_bug.cgi?id=413298 Filip Fila changed: What|Removed |Added Version|5.17.0 |5.18.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407689] Preview of sddm themes and icons look pixelated in "Startup and Shutdown" when fractional display scale is used
https://bugs.kde.org/show_bug.cgi?id=407689 Filip Fila changed: What|Removed |Added Version|5.16.90 |5.18.1 CC||i...@guoyunhe.me --- Comment #11 from Filip Fila --- Yunhe, you've been working on HiDPI improvements in Plasma, would you be interested in fixing this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418339] Improve default icon arrangement on desktop
https://bugs.kde.org/show_bug.cgi?id=418339 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #3 from Filip Fila --- What Gerardo is saying makes sense to me. A desktop is not a a resizeable window so I don't think using the same layout as in a file manager is necessarily warranted due to consistency reasons. It does tend to be easier to do drag-and-drop if desktop icons are arranged in column. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418348] Breeze GTK3 is currently Breeze-Dark GTK3 in Plasma 5.18.2 in Kubuntu 19.10 and 20.04
https://bugs.kde.org/show_bug.cgi?id=418348 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #1 from Filip Fila --- The Breeze GTK theme gets recolored based on your color scheme so I assume you're using a dark color scheme? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418195] Scroll bar and vertical line overlap icons in side bar when size of emoji picker window is reduced
https://bugs.kde.org/show_bug.cgi?id=418195 Filip Fila changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/d0247bf5695413f ||8de83e5c48e4b05874d077752 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.18.3 --- Comment #2 from Filip Fila --- Git commit d0247bf5695413f8de83e5c48e4b05874d077752 by Filip Fila. Committed on 27/02/2020 at 13:12. Pushed by filipf into branch 'Plasma/5.18'. [emojier] Set minimum window height and width Summary: There are two problems right now with the emojier's window: - when shrinking the window a scrollbar is drawn *over* the category drawer's icons - the whole window can be shrunk to be only 1px wide and only several pixels tall To solve both issues this patch sets a minimum height that is equal to the height of the category drawer's content, thereby removing the possibility of a scrollbar appearing. Minimum width is then set to be somewhat bigger than minimum height to account for monitor aspect ratios. In practice this amounts to about 465x370 on a 1080p screen. FIXED-IN: 5.18.3 Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D27679 M +2-0applets/kimpanel/backend/ibus/emojier/ui/emojier.qml https://commits.kde.org/plasma-desktop/d0247bf5695413f8de83e5c48e4b05874d077752 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418195] Scroll bar and vertical line overlap icons in side bar when size of emoji picker window is reduced
https://bugs.kde.org/show_bug.cgi?id=418195 --- Comment #1 from Filip Fila --- Seems to me like the problem is that this window has no minimum height or width set, which results in even worse visuals than this if you shrink it as much as you can. I'll make a patch to set some minimum values. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418195] Scroll bar and vertical line overlap icons in side bar when size of emoji picker window is reduced
https://bugs.kde.org/show_bug.cgi?id=418195 Filip Fila changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||filipfila@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
