[neon] [Bug 372918] KDE Neon wont boot after install
https://bugs.kde.org/show_bug.cgi?id=372918 --- Comment #1 from Lukas --- i just did an install without internet/downloading updates during install and without installing third party software. then i got the error message that it wasnt able to install grub into the target so the operating system wont be able to boot. i think that is the problem -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 372918] KDE Neon wont boot after install
https://bugs.kde.org/show_bug.cgi?id=372918 --- Comment #3 from Lukas --- i have found a work around viewtopic.php?f=309&t=134976&p=361816#p361816 but most likely instead of sda2 its sda1, you can use gparted or partitionmanager to figure it where your efi is mkdir efi sudo mount /dev/sda1 efi/ sudo cp efi/EFI/neon/* efi/EFI/ubuntu/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468881] New: Timestamps in directorysizes file for Trash shown in milliseconds instead of seconds since epoch
https://bugs.kde.org/show_bug.cgi?id=468881 Bug ID: 468881 Summary: Timestamps in directorysizes file for Trash shown in milliseconds instead of seconds since epoch Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lukas.sp...@web.de Target Milestone: --- SUMMARY When deleting a folder (moving it to trash) in Dolphin or with an icon on the desktop, then the directorysizes file stores a timestamp for that folder's trashinfo file in milliseconds since Epoch. However, according to the freedesktop.org specification, this should be seconds since Epoch: "Directory size cache (...) The modification time is stored as an integer, the number of seconds since Epoch." - https://specifications.freedesktop.org/trash-spec/trashspec-latest.html STEPS TO REPRODUCE 1. Delete a folder in Dolphin or from the desktop. 2. Check the content of the diretorysizes file (~/.local/share/Trash/directorysizes). OBSERVED RESULT The timestamp (second column) is shown in milliseconds since epoch EXPECTED RESULT The timestamp (second column) should be shown in seconds since epoch SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460448] New: Last 2 chars of device key are cut off
https://bugs.kde.org/show_bug.cgi?id=460448 Bug ID: 460448 Summary: Last 2 chars of device key are cut off Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 10.x Status: REPORTED Severity: minor Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: l.wolf0...@gmail.com Target Milestone: --- SUMMARY Last 2 chars of a key displayed after requesting a connection to a computer are cut off on android. STEPS TO REPRODUCE 1. Open App 2. Select 'Pair new Device' in Navbar 3. Select a device under 'Available Devices' 4. Select 'REQUEST PAIRING' OBSERVED RESULT The displayed key in the app is only 62 chars long - the displayed key on the computer is 64 chars long. The chars seems to be the same. (I'm not able to select and copy them because any idiot started the trend to make text unselectable :person-facepalming: EXPECTED RESULT The displayed keys in the android app and desktop app have the same length. SOFTWARE/OS VERSIONS: Windows: N/A macOS: N/A Linux/KDE Plasma: Kubuntu 22.04.1 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION KDE Connect Settings Version: 21.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445776] New: Umlaut ö counts as hundrets of chars
https://bugs.kde.org/show_bug.cgi?id=445776 Bug ID: 445776 Summary: Umlaut ö counts as hundrets of chars Product: kdeconnect Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: nicelu...@hotmail.com Target Milestone: --- SUMMARY *** *** STEPS TO REPRODUCE Start to write a SMS message and copy the following text: 102030405060708090aaa100aaa110aaa120130aaa140aaa150 äüÜÄÖö OBSERVED RESULT It shows 43/3 as used characters, so over 3 SMS. But the text length is under 160 characters. EXPECTED RESULT It should count the chars correctly, there should be the number 2 visible - so 158 characters. The problem is only the lower ö. When using the upper case letter Ö or the other umlauts ä or ü there is no problem. Just the ö is messed up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: KDE 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445776] Umlaut ö counts as several characters
https://bugs.kde.org/show_bug.cgi?id=445776 Lukas changed: What|Removed |Added Summary|Umlaut ö counts as hundrets |Umlaut ö counts as several |of chars|characters -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422583] kwin_x11 crash on login
https://bugs.kde.org/show_bug.cgi?id=422583 --- Comment #2 from Lukas --- I can't reproduce the issue anymore. Feel free to close this report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425276] Maximized Firefox goes under an "Always Visible" panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=425276 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #2 from Lukas --- This seems to affect not only Firefox but also other applications. I have observed it with Dolphin, Konsole, Kwrite, Chromium, Kate, and others. Usually a restore & maximize makes the window respect the panel. This bug is also still present in 5.19.90. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426759] New: Any popup of the panel is shown behind a window with the 'Always on top' property set instead of on top.
https://bugs.kde.org/show_bug.cgi?id=426759 Bug ID: 426759 Summary: Any popup of the panel is shown behind a window with the 'Always on top' property set instead of on top. Product: plasmashell Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lukas.sp...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When a window is set to 'Always on Top' then any of the popups of the panel (window previews, systray popups, application launcher) are shown *behind* that window instead of on top of it. STEPS TO REPRODUCE 1. Set window to 'Always on Top' 2. Move window near panel 3. Hover over any window in the window list or open any popup. OBSERVED RESULT The popup is shown behind the window with the 'Always on Top' property set. EXPECTED RESULT The popup is shown on top of the window with the 'Always on Top' property set. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I observed this behavior in 5.19.5 and now also in 5.19.90. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426759] Any popup of the panel is shown behind a window with the 'Always on top' property set instead of on top.
https://bugs.kde.org/show_bug.cgi?id=426759 Lukas changed: What|Removed |Added Platform|Other |Archlinux Packages --- Comment #1 from Lukas --- I forgot to add: This is using Plasma with Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426759] Wayland: Any popup of the panel is shown behind a window with the 'Always on top' property set instead of on top.
https://bugs.kde.org/show_bug.cgi?id=426759 Lukas changed: What|Removed |Added Summary|Any popup of the panel is |Wayland: Any popup of the |shown behind a window with |panel is shown behind a |the 'Always on top' |window with the 'Always on |property set instead of on |top' property set instead |top.|of on top. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426761] New: Wayland: QMenu::popup(QCursor::pos()) creates windowed menu not at cursor position.
https://bugs.kde.org/show_bug.cgi?id=426761 Bug ID: 426761 Summary: Wayland: QMenu::popup(QCursor::pos()) creates windowed menu not at cursor position. Product: plasmashell Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lukas.sp...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 131795 --> https://bugs.kde.org/attachment.cgi?id=131795&action=edit Simple Qt5 application illustrating observed behavior. SUMMARY In Wayland, for a Qt 5 application, showing a menu at cursor position shows the menu windowed centered on application window instead of as menu at the position of the cursor. In particular, I observed this behavior with a menu set as context menu to a QSystemTrayIcon. (Also, I wasn't sure which product this falls under.) STEPS TO REPRODUCE 1. Run attached app. 2. Right and Left click on tray icon. OBSERVED RESULT A right click open the context menu properly/normally. A left click calling QMenu::popup(QCursor::pos()) opens the context menu as window centered on application window. EXPECTED RESULT A left click opens the context menu at cursor position. SOFTWARE/OS VERSIONS Linux: Arch Linux (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I observed this same behavior on 5.19.5 and 5.19.90. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426759] Wayland: Any popup of the panel is shown behind a window with the 'Always on top' property set instead of on top.
https://bugs.kde.org/show_bug.cgi?id=426759 Lukas changed: What|Removed |Added Component|general |general Target Milestone|1.0 |--- Product|plasmashell |kwin Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426761] Wayland: QMenu::popup(QCursor::pos()) creates windowed menu not at cursor position.
https://bugs.kde.org/show_bug.cgi?id=426761 --- Comment #3 from Lukas --- Thanks for the comment. I might file a bug report against the Qt doc to get a note added there that this does not work on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426761] Wayland: QMenu::popup(QCursor::pos()) creates windowed menu not at cursor position.
https://bugs.kde.org/show_bug.cgi?id=426761 --- Comment #4 from Lukas --- https://bugreports.qt.io/browse/QTBUG-86780 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426784] New: [wayland] 'add panel' submenu of context menu for panel shown as window at the top left corner of screen
https://bugs.kde.org/show_bug.cgi?id=426784 Bug ID: 426784 Summary: [wayland] 'add panel' submenu of context menu for panel shown as window at the top left corner of screen Product: plasmashell Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: lukas.sp...@web.de Target Milestone: 1.0 SUMMARY In the context menu for the panel, the submenu for adding a new panel does not show up as submenu but windowed in the top left corner of the screen. STEPS TO REPRODUCE 1. Right click on panel 2. Move mouse to 'Add Panel' menu entry 3. Wait for submenu to show up OBSERVED RESULT Submenu opens in a window at the top left corner of the screen. EXPECTED RESULT Submenu should open at its proper location as menu. SOFTWARE/OS VERSIONS Linux: Arch Linux (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION All other menus/submenus of the panel I could find are shown properly, this seems to be the only one left misbehaving (there were a few more misbehaving in 5.19.5). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416869] [Wayland] Tooltip dismisses context menu of systray icons and they become unresponsive to mouse clicks
https://bugs.kde.org/show_bug.cgi?id=416869 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #3 from Lukas --- The issue described here is still present. Operating System: Arch Linux KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
https://bugs.kde.org/show_bug.cgi?id=419728 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #3 from Lukas --- kwin_wayland crashes for me also when multi-monitor mode is set to extend the desktop to the second screen. Unplugging the HDMI connection immediately crashes kwin_wayland. Operating System: Arch Linux KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413071] [Wayland] Kmail crashes when resized or maximized
https://bugs.kde.org/show_bug.cgi?id=413071 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #2 from Lukas --- The issue is stll happening on Wayland. Running kmail (or kontact) with QT_QPA_PLATFORM=xcb works but it is a little disappointing that ther ehasn't been any progress on this in years. KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426759] Wayland: Any popup of the panel is shown behind a window with the 'Always on top' property set instead of on top.
https://bugs.kde.org/show_bug.cgi?id=426759 --- Comment #2 from Lukas --- I have a shortcut set to set a window to be shown always on top. I then noticed that if a panel popup opens behind an 'always on top' window I can use that shortcut to move it to the top. Thus, it seems like all that is missing is to always set the 'always on top' window flag for the panel popups. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441532] Unable to adjust display backlight brightness on kernel 5.11
https://bugs.kde.org/show_bug.cgi?id=441532 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #1 from Lukas --- I observe the same issue (I think) with kernel 5.13.12 on Arch Linux. Adjusting the brightness level works just fine on Wayland, but has recently been broken on X11. Running `xbacklight` returns `No outputs have backlight property`, however, I *am* able to adjust the backlight from the command line using `echo [value] > /sys/class/backlight/intel_backlight/brightness`. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441532] Unable to adjust display backlight brightness on kernel 5.11
https://bugs.kde.org/show_bug.cgi?id=441532 --- Comment #2 from Lukas --- Changing from xorg-xbacklight to acpilight makes `xbacklight` work as expected again. Maybe the kernel changed how brightness is handled (on Intel (in my case) at least)? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421778] Add feature to navigate to next and previous documents in current folder
https://bugs.kde.org/show_bug.cgi?id=421778 --- Comment #5 from Lukas --- (In reply to Albert Astals Cid from comment #1) > Sincerely i don't see how this makes any sense in general. As I mentioned in Bug 42, this would make a lot of sense in a folder full of single-page plots. My workaround at the moment is to export each plot both to PDF and PNG so that I can look at the PNGs in sequence with an image viewer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
https://bugs.kde.org/show_bug.cgi?id=419728 --- Comment #5 from Lukas --- With the release of Plasma 5.20 things got slightly worse I'm afraid: 1. Plugging in HDMI monitor and telling Plasma to extend the display - works 2. Disabling the monitor and then unplugging it - works 3. Plugging the monitor in again and then extending the display - total crash, around 20 crash report windows open up. Operating System: Arch Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 424663] Could not find a package configuration file provided by "Qt5X11Extras"
https://bugs.kde.org/show_bug.cgi?id=424663 Lukas changed: What|Removed |Added CC||schweinefi...@freenet.de --- Comment #2 from Lukas --- I followed https://community.kde.org/Get_Involved/development and have the same problem using a clean environment and running "kdesrc-build --stop-on-failure dolphin". System: Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-51-generic -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 418811] Events stored in the database not displayed in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=418811 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #5 from Lukas --- Yup, same issue here. Some events are not shown in KOrganizer even though they are visibile in Nextcloud and on my Android calendar app. It didn't seem to matter from where I aceepted the event, some events that are not shown I accepted from Thunderbird and some from KMail. However, there are also some events that were created from invitation that *are* visible in KOrganizer. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 KMail version: 5.15.2 (20.08.2) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 428304] New: wifi applet changes network while typing the password to connect depending on the signal strength
https://bugs.kde.org/show_bug.cgi?id=428304 Bug ID: 428304 Summary: wifi applet changes network while typing the password to connect depending on the signal strength Product: plasma-nm Version: 5.19.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: lukas.bueh...@gmx.de Target Milestone: --- SUMMARY While trying to enter the wifi password to connecgt it switches through the different available networks depending on the frequency strength so you can accidentally try to enter a different network. STEPS TO REPRODUCE 1. try to connect to a wifi with a lot of different available wifis and changing signal strength. 2. type in password 3. observe it changing the network while typing in the password OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 428480] New: Discover (and systemsettings5, ksplashqml....) close unexpectedly
https://bugs.kde.org/show_bug.cgi?id=428480 Bug ID: 428480 Summary: Discover (and systemsettings5, ksplashqml) close unexpectedly Product: Discover Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: lukasce...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-12-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: just launching these apps. - Unusual behavior I noticed: Software Renderer in use - icon in the icon tray, no matter what I change to (automatic etc), it reverts back to software after reboot - so far all these close unexpectedtly: discover systemsettings5 ksplashqml (no login screen, tried switching to another, no luck + preview fails) launch button/icon top left corner doesn't work on click (but does on windows/cmd button press) The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f59b9491840 (LWP 9338))] Thread 10 (Thread 0x7f5987fff700 (LWP 9466)): #0 0x7f59bf2def59 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f59bf5e79d5 in QBasicMutex::lockInternal() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f59bed501cb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #3 0x7f59bed509e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7f59bed2a618 in QSslSocket::startClientEncryption() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f59bed2b330 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7f59bed32d39 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f59bf7c57f6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f59becf91f3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7f59becfbfb0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f59bed0af5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f59c05b04c1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f59c05b7970 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f59bf79c489 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f59bf7ee34a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f59bda66f2e in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f59bda671c8 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f59bda6725c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f59bf7ed743 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f59bf79b15b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f59bf5eae76 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f59bf5f4a67 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f59be78dfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #23 0x7f59bf2e44cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7f599cb7b700 (LWP 9459)): #0 0x7f59bf2d9819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f59bda67136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f59bda674c2 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f599ddef266 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f59bda8f415 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f59be78dfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f59bf2e44cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7f599d37c700 (LWP 9458)): #0 0x7f59bf2d9819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f59bda67136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f59bda6725c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f59bda672a1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f59bda8f415 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f59be78dfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x
[digikam] [Bug 479090] New: [Request (Plugin)] Object Recognition for automatic tag generation, easier searching
https://bugs.kde.org/show_bug.cgi?id=479090 Bug ID: 479090 Summary: [Request (Plugin)] Object Recognition for automatic tag generation, easier searching Classification: Applications Product: digikam Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: 4craftersoffic...@gmail.com Target Milestone: --- I was searching for an easy way to locate pictures within my collection when only knowing the content of the picture, and i found the Recognize Anything Paper (https://arxiv.org/pdf/2306.03514.pdf) and connected Github (https://github.com/xinyu1205/recognize-anything) from the OPPO Research Team licensed under the Apache-2.0 license. (But there are other open source solutions that would work too) This would allow for something analogous to the Face Tags, but more generalised, to enable easy searching. Just by typing in the subject you can find pictures the AI tagged, within your entire collection. For good integration you would need digikam to track these "Machine Tags" (in a separate .db, similar to recognition.db) and allow for searching- which seems easy enough since you can already search for tags with "A tag of the item contains", so adding some UI elements to differentiate them from normal tags and keep them separate for only search purposes would probably suffice. In my opinion, you could add a popup just like face recognition to download the python project, then pass pictures to the program and record the Machine Tags in a separate .db file, which then can be used for searching. Currently i am experimenting with adding these tags to the exif metadata, but this is suboptimal for multiple reasons, and an integration would obviously be superior. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479090] [Request (Plugin)] Object Recognition for automatic tag generation, easier searching
https://bugs.kde.org/show_bug.cgi?id=479090 Lukas <4craftersoffic...@gmail.com> changed: What|Removed |Added CC||4craftersoffic...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399708] Numpad moves cursor even if disabled
https://bugs.kde.org/show_bug.cgi?id=399708 Lukas changed: What|Removed |Added CC||l.wolf0...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Lukas --- Hello, I'm experiencing the exact same bug. This is an old bug. I already struggled with this a few years ago. I've hotfixed it by executing `setxkbmap -option keypad:pointerkeys` in a terminal according to [this forum thread]( https://forum.kde.org/viewtopic.php?t=106658#p247295 ). Then I was able to disable and enable cursor navigation by pressing SHIFT + NumLock instead of navigating to `systemsettings` » Accessibility » Cursor Navigation like described in the bug report. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399708] Numpad moves cursor even if disabled
https://bugs.kde.org/show_bug.cgi?id=399708 --- Comment #4 from Lukas --- (In reply to Lukas from comment #3) > Hello, I'm experiencing the exact same bug. > > This is an old bug. I already struggled with this a few years ago. > > I've hotfixed it by executing `setxkbmap -option keypad:pointerkeys` in a > terminal according to [this forum thread]( > https://forum.kde.org/viewtopic.php?t=106658#p247295 ). Then I was able to > disable and enable cursor navigation by pressing SHIFT + NumLock instead of > navigating to `systemsettings` » Accessibility » Cursor Navigation like > described in the bug report. > > Operating System: Kubuntu 22.04 > KDE Plasma Version: 5.24.6 > KDE Frameworks Version: 5.92.0 > Qt Version: 5.15.3 > Kernel Version: 5.15.0-52-generic (64-bit) > Graphics Platform: X11 I've noticed, that the workaround is only for the current session. So when you log off and on again, you have to execute the command again. To execute the command when you log in, you can add a desktop entry in ~/.config/autostart with the commands: ```bash # apply for this session setxkbmap -option keypad:pointerkeys; # create desktop entry to apply it for every session in the future echo -en "[Desktop Entry]\nExec=setxkbmap -option keypad:pointerkeys\nType=Application\nX-KDE-AutostartScript=true" > ~/.config/autostart/keypad_pointerkeys.desktop ``` -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 333219] An option to group hidden files in the end
https://bugs.kde.org/show_bug.cgi?id=333219 Lukas changed: What|Removed |Added CC||nicelu...@hotmail.com --- Comment #8 from Lukas --- Finally and luckily there is now an option in Dolphin in the sort by menu which is called "Hidden Files Last" and that is just doing what is wanted here :) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 423757] Crash at startup of desktop
https://bugs.kde.org/show_bug.cgi?id=423757 Lukas changed: What|Removed |Added CC||no.name.08154...@outlook.de -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431402] Make it possible to scale down/zoom out images further than the window width/height
https://bugs.kde.org/show_bug.cgi?id=431402 --- Comment #11 from Lukas --- To expand on Alberto's comment, I wouldn't say the issue is necessarily only about logo/icon review. Imagine you are browsing a list of photographs to select a subset for social media. Switching to thumbnail view and back repeatedly could be inconvenient. But I agree that zooming out to zoomToFit should still be the default when Ctrl+scrolling. Maybe the buttons in the bottom right corner might gain the ability to zoom out further? Or make Ctrl+Shift+scroll behave differently than Ctrl+scroll? The latter option would be difficult to discover for new users, though. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431402] Make it possible to scale down/zoom out images further than the window width/height
https://bugs.kde.org/show_bug.cgi?id=431402 --- Comment #18 from Lukas --- Perhaps this could be an acceptable compromise? We could make behavior consistent with how zooming works in web browsers (or at least Firefox) and reset zoom with Ctrl+0 and alternatively with the already existing "Fit" button in the bottom right corner. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425555] New: Shortcut to switch to the next/previous PDF in the same folder
https://bugs.kde.org/show_bug.cgi?id=42 Bug ID: 42 Summary: Shortcut to switch to the next/previous PDF in the same folder Product: okular Version: 1.11.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: lumpi...@gmail.com Target Milestone: --- SUMMARY About half the documents I open with Okular are single-page figures and plots generated, for example, with Matplotlib. In theses cases it would be convenient to have keyboard shortcuts or buttons in the toolbar for switching to the previous or next PDF in the same directory. STEPS TO REPRODUCE 1. Open single-page PDF figure (e.g., some vector graphic) from a folder that has several other PDF figures OBSERVED RESULT Nothing happens if I press the arrow keys or page up/down. (These keys should probably stay reserved to the current multi-page functionality.) EXPECTED RESULT Buttons in toolbar or file listing in a sidebar tab or an easy-to-remember key combination for flipping through documents in the same folder (e.g., Ctrl+left/right?). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro, kernel 5.8.1-3-MANJARO (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417198] KDEConnect SMS app is difficult to read with a Dark theme
https://bugs.kde.org/show_bug.cgi?id=417198 Lukas changed: What|Removed |Added CC||nicelu...@hotmail.com --- Comment #8 from Lukas --- Created attachment 138588 --> https://bugs.kde.org/attachment.cgi?id=138588&action=edit SMS Text invisible on Breath2Dark Color theme I'm using Manjaro with the preinstalled Breath2 Dark theme and the text in the input field is white on white background -> I'm sure you could imagine that it's hard to read ;) Also the buttons are not visible, only on Mouseover a frame appears -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417198] KDEConnect SMS app is difficult to read with a Dark theme
https://bugs.kde.org/show_bug.cgi?id=417198 Lukas changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 462742] New: Android: Trip interpreted in reverse order
https://bugs.kde.org/show_bug.cgi?id=462742 Bug ID: 462742 Summary: Android: Trip interpreted in reverse order Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: lukas.sp...@web.de Target Milestone: --- SUMMARY I'm travelling from Germany via Belgium to France. I have two tickets, one from Germany to Belgium (through DB) and one from Belgium to France (through SNCF), both coming from a single booking. The Android app properly detects that they are part of the same trip, but it interprets this as a trip from France to Germany and has the two tickets in reverse order, even though the times and everything are detected correctly. As a quick "fix", is there an option I missed to have the tickets not grouped? STEPS TO REPRODUCE 1. Import ticket from DB for Germany to Belgium 2. Import ticket from SNCF for Belgium to France OBSERVED RESULT The trip is interpreted in reverse order. EXPECTED RESULT The trip is interpreted in the right order. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434156] New: systemsettings crashes on closing
https://bugs.kde.org/show_bug.cgi?id=434156 Bug ID: 434156 Summary: systemsettings crashes on closing Product: systemsettings Version: 5.21.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: no.name.08154...@outlook.de Target Milestone: --- Application: systemsettings5 (5.21.2) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.11.2-arch1-1 x86_64 Windowing System: X11 Drkonqi Version: 5.21.2 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I closed the systemsettings application using the usual "close" button. This happens often, but not every time. The crash can be reproduced sometimes. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f32f862fa38 in QScopedPointer >::operator-> (this=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > const> (ptr=...) at global/qglobal.h:1135 #6 QObject::d_func (this=) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:132 #7 QObject::property (this=0x0, name=0x7f32f2977db0 "theme") at kernel/qobject.cpp:4085 #8 0x7f32f296d4d5 in ?? () from /usr/lib/libKF5Kirigami2.so.5 #9 0x7f32f2974cdf in ?? () from /usr/lib/libKF5Kirigami2.so.5 #10 0x7f32f8633d86 in QtPrivate::QSlotObjectBase::call (a=0x7ffea2823480, r=0x55e9d9066870, this=0x55e9d90669f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x55e9d9066870, signal_index=3, argv=0x7ffea2823480) at kernel/qobject.cpp:3886 #12 0x7f32f2968073 in ?? () from /usr/lib/libKF5Kirigami2.so.5 #13 0x7f32f8629532 in QObject::event (this=0x55e9d9066870, e=0x55e9da1e8fc0) at kernel/qobject.cpp:1314 #14 0x7f32f91bf752 in QApplicationPrivate::notify_helper (this=, receiver=0x55e9d9066870, e=0x55e9da1e8fc0) at kernel/qapplication.cpp:3632 #15 0x7f32f85fca2a in QCoreApplication::notifyInternal2 (receiver=0x55e9d9066870, event=0x55e9da1e8fc0) at kernel/qcoreapplication.cpp:1063 #16 0x7f32f85ff523 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55e9d8be4f50) at kernel/qcoreapplication.cpp:1817 #17 0x7f32f8656054 in postEventSourceDispatch (s=0x55e9d8bf0b30) at kernel/qeventdispatcher_glib.cpp:277 #18 0x7f32f62c8b84 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7f32f631cc21 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x7f32f62c73b1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7f32f8655691 in QEventDispatcherGlib::processEvents (this=0x55e9d8d01e20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f32f85fb3ac in QEventLoop::exec (this=this@entry=0x7ffea28238d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f32f8603844 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x55e9d77de960 in ?? () #25 0x7f32f7e7fb25 in __libc_start_main () from /usr/lib/libc.so.6 #26 0x55e9d77df47e in _start () [Inferior 1 (process 145452) detached] Possible duplicates by query: bug 433721, bug 433252, bug 433249, bug 433203, bug 432370. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 408719] New: Customized MenuItem/ComboBox causes TypeErrors in Kirigami
https://bugs.kde.org/show_bug.cgi?id=408719
Bug ID: 408719
Summary: Customized MenuItem/ComboBox causes TypeErrors in
Kirigami
Product: frameworks-kirigami
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: lukas.sp...@web.de
Target Milestone: Not decided
Created attachment 120881
--> https://bugs.kde.org/attachment.cgi?id=120881&action=edit
sample app producing described TypeErrors
SUMMARY
I created a very basic QML application (attached) that is based on QApplication
(and not QGuiApplication). I then add a Menu with a MenuItem that has a custom
contentItem set. When run the engine will produce a TypeError (though
everything still seems to work):
file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/MenuItem.qml:98:
TypeError: Cannot read property 'height' of null
Similarly, when adding a ComboBox also with customized contentItem then the
engine produces 5 TypeErrors for each instance of the ComboBox:
file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/ComboBox.qml:52:
TypeError: Cannot read property 'pressed' of null
file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/ComboBox.qml:178:
TypeError: Cannot read property 'selectionStart' of null
file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:62:
TypeError: Cannot read property 'selectedText' of null
file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:70:
TypeError: Cannot read property 'selectedText' of null
file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:78:
TypeError: Cannot read property 'canPaste' of null
The TypeError for the MenuItem can be hidden when adding the following line:
arrow: Item {}
I have not figured out a solution to prevent the 5 TypeErrors for the ComboBox.
STEPS TO REPRODUCE
1. Compile attached sample app
2. Run app
3.
OBSERVED RESULT
1 TypeError due to the MenuItem, 5 TypeErrors due to the ComboBox.
EXPECTED RESULT
No TypeErrors.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.16.0
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3
--
You are receiving this mail because:
You are watching all bug changes.
[unknown] [Bug 408719] Customized MenuItem/ComboBox causes TypeErrors in Kirigami
https://bugs.kde.org/show_bug.cgi?id=408719 Lukas changed: What|Removed |Added Target Milestone|Not decided |--- Component|general |general Assignee|notm...@gmail.com |unassigned-b...@kde.org Product|frameworks-kirigami |unknown --- Comment #1 from Lukas --- Edit: Changed Product to 'unknown'. I had it as Kirigami initially as the first TypeError happens in a line where Kirigami shows up, but it seems to be due to some id problems outside of Kirigami. I don't know which product this falls under, hence 'unknown'. -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 408719] Customized MenuItem/ComboBox causes TypeErrors
https://bugs.kde.org/show_bug.cgi?id=408719 Lukas changed: What|Removed |Added Summary|Customized |Customized |MenuItem/ComboBox causes|MenuItem/ComboBox causes |TypeErrors in Kirigami |TypeErrors -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 408719] Customized MenuItem/ComboBox causes TypeErrors in QtQuick/Controls.2/org.kde.desktop/
https://bugs.kde.org/show_bug.cgi?id=408719 Lukas changed: What|Removed |Added Summary|Customized |Customized |MenuItem/ComboBox causes|MenuItem/ComboBox causes |TypeErrors |TypeErrors in ||QtQuick/Controls.2/org.kde. ||desktop/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411962] New: konsole crashes when ctrl+shift+w on a frozen ssh session
https://bugs.kde.org/show_bug.cgi?id=411962 Bug ID: 411962 Summary: konsole crashes when ctrl+shift+w on a frozen ssh session Product: konsole Version: 19.08.0 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: lu...@aiya.cz Target Milestone: --- Application: konsole (19.08.0) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 5.2.0-2-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: I pressed ctrl+shift+w to close a tab when a ssh session froze. Konsole segfaulted. Happened several times already. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f313f5b5800 (LWP 2573))] Thread 4 (Thread 0x7f3136292700 (LWP 2576)): #0 0x7f31428d6db5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f3136748ffb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #2 0x7f3136748c17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #3 0x7f31428d0fb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f31453ad49f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f313c977700 (LWP 2575)): #0 0x7f31453a2edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f31420b6bf6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31420b6d1c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3143cc53e3 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3143c72cfb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3143ac2d8e in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3143229545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f3143acca07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31428d0fb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f31453ad49f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f313e3bf700 (LWP 2574)): #0 0x7f31453a2edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3142b05cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f3142b0791a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f313f174d79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f3143acca07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f31428d0fb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f31453ad49f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f313f5b5800 (LWP 2573)): [KCrash Handler] #6 0x7f31446286ce in QWidget::setFocus(Qt::FocusReason) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f3143c9d5c0 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31452555d2 in Konsole::TabbedViewContainer::activeViewChanged(Konsole::TerminalDisplay*) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.19 #9 0x7f314523dcd7 in Konsole::TabbedViewContainer::currentTabChanged(int) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.19 #10 0x7f3143c9d5c0 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f31447ae7fe in QTabWidget::currentChanged(int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f31447b0bdf in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f3143c9d463 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f314478fc1e in QTabBar::currentChanged(int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f314479423d in QTabBar::setCurrentIndex(int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f3143c9d5c0 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f31445e9f42 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f31445ec560 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f31445ece14 in QAction::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f31445f0501 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f31445f79b0 in QApplication::notify(QObject*, QEvent*) ()
[systemsettings] [Bug 420006] system settings crash
https://bugs.kde.org/show_bug.cgi?id=420006 Lukas changed: What|Removed |Added CC||l.wolf0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420006] system settings crash
https://bugs.kde.org/show_bug.cgi?id=420006 --- Comment #2 from Lukas --- attachment 128059 A restart of my computer did it. (I noticed, that every single KDE function (e.g. menu > shut down) didn't worked either after I've updated my driver) I have no idea if I should apply "RESOLVED" or not, because this solves only MY crash. So I leave it as it is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370258] No option to bring forward multiple windows of the same program
https://bugs.kde.org/show_bug.cgi?id=370258 Lukas changed: What|Removed |Added CC||k...@web.de --- Comment #2 from Lukas --- Just right-click on the icon and then click on minimize in the context menu. Alternatively, right-click on the taskbar and select "settings for icons-only task-manager". Then configure the middle-mouse button option dropdown menu to "minimize window/group". Now middle clicking should show or hide all windows of one application at once. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376250] New: ignored clicks
https://bugs.kde.org/show_bug.cgi?id=376250 Bug ID: 376250 Summary: ignored clicks Product: plasmashell Version: 5.9.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@web.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Plasmashell ignores mouse button clicks on the panel sometimes, which is annoying. To reproduce: Right-click on a panel. Don't select anything in the context menu, instead click on any open window, but not the panel, then the context menu will close. Then move the mouse back onto the panel and right-click. This time the right-click is ignored, and the context menu doesn't open. Again, right-click on a panel. Don't select anything in the context menu, instead click on any open window, but not the panel, then the context menu will close. Then move the mouse back onto the panel and left-click. The left-click is ignored, and no action is triggered. * right-click on panel, left-click in window, right-click (or left-click) on panel -> nothing happens * right-click on panel, left-click on panel, right-click (or left-click) on panel -> working What should happen: Clicks on the panel should immediatly trigger an action instead of being ignored. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 376314] New: timer, no notification shown when timer finishes if started in window
https://bugs.kde.org/show_bug.cgi?id=376314 Bug ID: 376314 Summary: timer, no notification shown when timer finishes if started in window Product: kdeplasma-addons Version: 5.9.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: timer Assignee: plasma-b...@kde.org Reporter: k...@web.de Target Milestone: --- Start the timer applet from krunner such that it opens in its own window. When the timer finishes, no notification is shown. The notification is shown if the applet was placed on the desktop, but not shown if it was opened in a window. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 376315] New: applets opened in windows don't have a reasonable minimum size
https://bugs.kde.org/show_bug.cgi?id=376315 Bug ID: 376315 Summary: applets opened in windows don't have a reasonable minimum size Product: kdeplasma-addons Version: 5.9.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: k...@web.de Target Milestone: --- Open an applet in krunner such that it shows in its own window. Shrink the window by resizing until it is <10 pixels wide. Now not even the close, minimize, etc. buttons are visible anymore, let alone the window contents. This shouldn't be possible, there should be a reasonable minimum size set for the window. -- You are receiving this mail because: You are watching all bug changes.
[lskat] [Bug 105124] advanced mode algorithm 'cheats'
https://bugs.kde.org/show_bug.cgi?id=105124 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #1 from Lukas --- More than 13 years later and I came here with the intention of reporting the exact same bug... Is anyone still working on LSkat? -- You are receiving this mail because: You are watching all bug changes.
[lskat] [Bug 105124] advanced mode algorithm 'cheats'
https://bugs.kde.org/show_bug.cgi?id=105124 Lukas changed: What|Removed |Added Version|1.0 |1.40 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383399] KDE Neon loads into GRUB Minimal after a clean install
https://bugs.kde.org/show_bug.cgi?id=383399 Lukas changed: What|Removed |Added CC||lukas.bueh...@gmx.de --- Comment #1 from Lukas --- same problem here. had internet connection on during install. the efi folder or whatever the name is, is completely empty, so no wonder it wont work :). this is a reacurring bug, see here: https://forum.kde.org/viewtopic.php?f=309&t=137368 the workaround worked for me for the time being, but the grub menu looks strange now :D -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376368] Window opening animations no longer work since Plasma 5.9
https://bugs.kde.org/show_bug.cgi?id=376368 Lukas changed: What|Removed |Added CC||lukas.sp...@web.de --- Comment #9 from Lukas --- Same problem here since upgrade to Plasma 5.9 (running Arch Linux). Only enabled effect affecting opening/closing of windows is the glide effect. When I disable and then enable it, it works until either the system is put into standby or the compositor is disabled and enabled again... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 384699] New: Wrong calculation of future balance based on planned transactions
https://bugs.kde.org/show_bug.cgi?id=384699 Bug ID: 384699 Summary: Wrong calculation of future balance based on planned transactions Product: kmymoney4 Version: 4.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: st...@lukasjacobs.de Target Milestone: --- Created attachment 107849 --> https://bugs.kde.org/attachment.cgi?id=107849&action=edit Screenshot of the planned transactions and predicted balance I have an account with a planned transaction of -4.95 €. After the transaction the predicted balance is 340.55 € too low, messing up my financial planning quite a bit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381280] Increased CPU usage with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=381280 Lukas changed: What|Removed |Added CC||luke-m...@online.de --- Comment #1 from Lukas --- I am experiencing similar issues with kwin_x11 and plasmashell. Both processes constantly eat up about 20% of CPU time. kwin_x11 CPU usage returns back to normal once I kill plasmashell. The issue arises during regular operation without secondary monitor although I have not testet it with a dock. An strace of plasmashell showed that it was pretty busy with various DRM systemcalls to the i915 Intel graphics driver although I have no idea whether this is in any way related to the issue. The issue first occurred after a system upgrade which comprised the following changes: Qt 5.8 -> Qt 5.9 kwin 5.10.1 -> 5.10.2 plasma-workspace 5.10.1 -> 5.10.2 I am running an Arch Linux installation on a Thinkpad T470: Intel Core i5-7200u Intel HD Graphics 620 A colleague with a Thinkpad X1 (also Intel CPU and Graphics) experiences the same issue. Please let me know if I can provide you with further information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496422] New: Plasma-emojier does not overlap the keycap emojis
https://bugs.kde.org/show_bug.cgi?id=496422 Bug ID: 496422 Summary: Plasma-emojier does not overlap the keycap emojis Classification: Plasma Product: plasmashell Version: 6.2.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: kdeistt...@gmx.de Target Milestone: 1.0 Created attachment 175917 --> https://bugs.kde.org/attachment.cgi?id=175917&action=edit Screenshot of the faulty behaviour SUMMARY The Emoji Selector App (plasma-emojier) does not display the keycap emojis correctly (see attachment) STEPS TO REPRODUCE 1. Open the Emoji Selector App 2. Search for 'keycap' (or scroll to it) OBSERVED RESULT The keycap symbol and the numbers / letters are not overlapping, instead displaying first the number / symbol, and then the keycap icon next to it. EXPECTED RESULT Overlapping keycap symbols and numbers / letters. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.7-300.fc41.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 498696] Undoing Liquify randomly crashes
https://bugs.kde.org/show_bug.cgi?id=498696 Lukas changed: What|Removed |Added CC||giga-zod...@gmx.net Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Assignee|krita-bugs-n...@kde.org |giga-zod...@gmx.net --- Comment #1 from Lukas --- I am sorry, but I cannot reproduce the bug on my system (Windows 10, 5.2.5 and krita-x64-5.3.0-prealpha-a05ebc35). Please add the output of help/System Information for Bug reports as well as more detailed version info (you put 5.2.6 in the report but two other versions in your comment). Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 502590] Text Tool Save Dialog Does Not Disappear and Text Resizing Not Working
https://bugs.kde.org/show_bug.cgi?id=502590 Lukas changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||giga-zod...@gmx.net --- Comment #1 from Lukas --- Was able to reproduce this, both in 5.2.9 and in 5.2.4. Not fully reproducable in 5.3.0-prealpha-a05ebc35 due to the text editor dialog not being used. Resizing with vector selection tool works better, but still not fully, only being able to move the text in X and Y dimensions and rotate it, resizing is still not working. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 499837] Unite turns line into rectangle
https://bugs.kde.org/show_bug.cgi?id=499837 Lukas changed: What|Removed |Added CC||giga-zod...@gmx.net Assignee|krita-bugs-n...@kde.org |giga-zod...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 499837] Unite turns line into rectangle
https://bugs.kde.org/show_bug.cgi?id=499837 Lukas changed: What|Removed |Added Assignee|giga-zod...@gmx.net |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 499837] Unite turns line into rectangle
https://bugs.kde.org/show_bug.cgi?id=499837 Lukas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Lukas --- (In reply to Yncke from comment #2) > I did some extra testing (because this flow worked on my old machine), and > found that the difference is in the Inkscape version. Copy pasting from > inkscape 0.47 and merging results in a correct text balloon. I could replicate the problem with your original file. I also tried the same steps with a vector created in Krita itself, which worked flawlessly. So I can confirm this is not an issue with Krita but with the original vector file you pasted into your project from inkscape. I'll go ahead and close this report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 498696] Undoing Liquify randomly crashes
https://bugs.kde.org/show_bug.cgi?id=498696 --- Comment #5 from Lukas --- Created attachment 181060 --> https://bugs.kde.org/attachment.cgi?id=181060&action=edit Backtrace from 3.2.9 crash reproduction -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 498696] Undoing Liquify randomly crashes
https://bugs.kde.org/show_bug.cgi?id=498696 Lukas changed: What|Removed |Added Version|5.2.6 |nightly build (please ||specify the git hash!) Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #6 from Lukas --- (In reply to Freya Lupen from comment #2) Thanks to Freyas detailed reproduction steps I was able to reproduce this crash in 5.2.9 and 5.3.0-prealpha-a05ebc35 on Windows 10 Pro (Version 10.0.19045 Build 19045): 1. Do a liquify brushstroke (so there’s one in the undo stack). 2. Hold the mouse button down to start another liquify brushstroke. 3. While holding the mouse down, hit undo (using the keyboard, given the mouse is occupied). 4. Move the held down mouse. 5. Crash. Changed status to confirmed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 501046] New: kioworker crashes when using dolphin
https://bugs.kde.org/show_bug.cgi?id=501046 Bug ID: 501046 Summary: kioworker crashes when using dolphin Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.11.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: no.name.08154...@outlook.de CC: kdelibs-b...@kde.org Target Milestone: --- Application: kioworker (6.11.0) ApplicationNotResponding [ANR]: false Qt Version: 6.8.2 Frameworks Version: 6.11.0 Operating System: Linux 6.13.5-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.3.2 [CoredumpBackend] -- Information about the crash: kioworker crashes when opening and using Dolphin. Upon first use of Dolphin, a multitude of crashes was reported within seconds. After some time, the reports stopped coming so fast. Now, after a few minutes (and a restart of Dolphin), the crashes are much less frequent and only occur occasionally, it does not seem to interfere with Dolphin, I can use it normally. The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x797acbcba067 in QFixed::toReal (this=, this=) at /usr/src/debug/qt6-base/qtbase/src/gui/painting/qfixed_p.h:42 #6 QTextLine::y (this=this@entry=0x7ffe25872260) at /usr/src/debug/qt6-base/qtbase/src/gui/text/qtextlayout.cpp:1482 #7 0x797a636c5def in KoTextDocumentLayout::positionAnchorTextRanges (this=0x5d6d8483e6b0, pos=, length=, effectiveDocument=) at /usr/src/debug/calligra/calligra-24.12.2/libs/textlayout/KoTextDocumentLayout.cpp:606 #8 0x797a636a11a6 in KoTextLayoutArea::layoutBlock (this=this@entry=0x5d6d84a10e10, cursor=cursor@entry=0x5d6d84a8fe50) at /usr/src/debug/calligra/calligra-24.12.2/libs/textlayout/KoTextLayoutArea.cpp:1328 #9 0x797a636a5cc5 in KoTextLayoutArea::layout (this=, cursor=0x5d6d84a8fe50) at /usr/src/debug/calligra/calligra-24.12.2/libs/textlayout/KoTextLayoutArea.cpp:668 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 501046] kioworker crashes when using dolphin
https://bugs.kde.org/show_bug.cgi?id=501046 --- Comment #1 from Lukas --- Created attachment 179104 --> https://bugs.kde.org/attachment.cgi?id=179104&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504781] Crash on clearing text field in text brush pipe mode
https://bugs.kde.org/show_bug.cgi?id=504781 --- Comment #3 from Lukas --- Created attachment 181743 --> https://bugs.kde.org/attachment.cgi?id=181743&action=edit sys info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504781] Crash on clearing text field in text brush pipe mode
https://bugs.kde.org/show_bug.cgi?id=504781 --- Comment #1 from Lukas --- Created attachment 181741 --> https://bugs.kde.org/attachment.cgi?id=181741&action=edit crash log with all crashes in different versions -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504781] New: Crash on clearing text field in text brush pipe mode
https://bugs.kde.org/show_bug.cgi?id=504781 Bug ID: 504781 Summary: Crash on clearing text field in text brush pipe mode Classification: Applications Product: krita Version First git master (please specify the git hash!) Reported In: Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: giga-zod...@gmx.net Target Milestone: --- Created attachment 181740 --> https://bugs.kde.org/attachment.cgi?id=181740&action=edit screenshot of text brush window with pipe mode checkbox SUMMARY Clearing the text input field in the pixel engines brush tip text tab while having pipemode enabled leads to a crash. STEPS TO REPRODUCE 1. select brush tool 2. open brush editor 3. select text tab in brush tip menu 4. check pipe mode 5. clear text input (select all + delete) (step 4 and 5 are interchangable) OBSERVED RESULT Crash EXPECTED RESULT Clearing input unchecks pipe mode without crashing (as in 5.1.5) SOFTWARE/OS VERSIONS Windows: 10 Pro, 10.0.19045 Build 19045 First version in regression without crash: 5.1.5 (I dont have any builds between 5.1.5 and 5.2.2) Crashing in: 5.2.2, 5.2.3., 5.2.4, 5.2.5, 5.2.9 and 5.3.0-prealpha-a05ebc35 ADDITIONAL INFORMATION see screenshot in attachements for exact window. I will also add the crash logs afterwards. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504781] Crash on clearing text field in text brush pipe mode
https://bugs.kde.org/show_bug.cgi?id=504781 --- Comment #2 from Lukas --- Created attachment 181742 --> https://bugs.kde.org/attachment.cgi?id=181742&action=edit krita log with all sessions in different versions -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 502855] (Pixel Art) Half mirrored pixel behaves as in between pixel mirror
https://bugs.kde.org/show_bug.cgi?id=502855 Lukas changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||giga-zod...@gmx.net Ever confirmed|0 |1 --- Comment #1 from Lukas --- I tested this on Windows 10 Pro and could confirm it. I can also confirm it is the same effect as reported in another bug https://bugs.kde.org/show_bug.cgi?id=499696 For explanation I included a video of it. In short: If you paint with the mirror tool enabled, the pixel is only placed when releasing the (mouse-)button OR when you start moving the mouse. If you do not move the mouse while holding the button, the pixel will be placed correctly. If you DO move the mouse while painting, the pixel will be placed offset by one pixel to the right or the buttom for the horizontal and vertical mirror tool respectively. I am not sure if this has anything to do with rounding, since it seems to depend on the type of you give (clicking and releasing VS. clicking and moving). Hopefully this helps! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 502855] (Pixel Art) Half mirrored pixel behaves as in between pixel mirror
https://bugs.kde.org/show_bug.cgi?id=502855 --- Comment #2 from Lukas --- Created attachment 181332 --> https://bugs.kde.org/attachment.cgi?id=181332&action=edit Clicking and releasing does not cause bug, clicking and moving does. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 502855] (Pixel Art) Half mirrored pixel behaves as in between pixel mirror
https://bugs.kde.org/show_bug.cgi?id=502855 --- Comment #3 from Lukas --- (In reply to Lukas from comment #1) > I tested this on Windows 10 Pro and could confirm it. I can also confirm it > is the same effect as reported in another bug > https://bugs.kde.org/show_bug.cgi?id=499696 CORRECTION: Scratch that connection to the other bug report, I misread the expected vs. observed result. This is probably a different bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 499696] Half-pixel aligned mirror tool sometimes broken
https://bugs.kde.org/show_bug.cgi?id=499696 --- Comment #3 from Lukas --- Created attachment 181339 --> https://bugs.kde.org/attachment.cgi?id=181339&action=edit Showing that a larger brush size can only mirror right halves of pixels. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 499696] Half-pixel aligned mirror tool sometimes broken
https://bugs.kde.org/show_bug.cgi?id=499696 Lukas changed: What|Removed |Added CC||giga-zod...@gmx.net Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Lukas --- Reproduced and confirmed this on Windows 10. I have included a video that also confirms which part of a subpixel you paint is important. As seen in the video, if your brush size is more than 1px (in this case 1.5px), you can paint 2 pixels at a time, but only the one that is "touched" by the cursor on its right half will get mirrored. One correction to the initial description: the canvas resolution doesnt matter, it depends on here you place the mirror. This bug only happens if the mirror is placed in the center of a subpixel, similar to this bug: https://bugs.kde.org/show_bug.cgi?id=502855 Possibly some could have something to do with the subpixel coordinates with a subpixel-mirror. I will try to test this further in the coming week. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504665] Applicatoin freeze after shortcut change
https://bugs.kde.org/show_bug.cgi?id=504665 Lukas changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Assignee|krita-bugs-n...@kde.org |giga-zod...@gmx.net CC||giga-zod...@gmx.net --- Comment #1 from Lukas --- Dear Dimon, I’m afraid I cannot reproduce your bug neither in Krita 5.2.9 nor in Krita Next. Could you please provide a bit more details about the bug? - clear steps to reproduce - video recording of how to reproduce the crash - Krita log from “Help->Show Krita log for bug reports” - Backtrace: Windows: crash log from %LOCALAPPDATA%\kritacrash.log - Windows (if the bug is reproducible, try with debugging symbols): https://docs.krita.org/en/reference_manual/dr_minw_debugger.html Here is a manual on how to get logs and backtraces on every platform: https://docs.krita.org/en/reference_manual/sharing_krita_logs.html -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 503761] In low resolutions, with scaling mode nearest neighbour, sometimes pixels dont display
https://bugs.kde.org/show_bug.cgi?id=503761 Lukas changed: What|Removed |Added CC||giga-zod...@gmx.net Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Lukas --- Hello Francisco, thank you for the detailed description and the video you attached. If I understood your problem correctly, then this does not seem like a bug to me. These gaps are simply artifacts of the nearest neighbor scaling mode (which means there is basically no scaling applied), your brush size of 1px and your zoom level. If you set your zoom level to 100%, that means each pixel on your canvas is represented by 1 pixel on your screen. If you zoom out, this means, each pixel on the canvas is smaller than each pixel on your screen. And because with nearest neighbor there is no scaling done, that means your screens pixels has to choose between more than 1 pixel of your canvas. I understand your confusion, but this is exactly as intended. As a work-around I would recommend only using >= 100% zoom level while painting with a 1px brush. I hope this helps! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 503020] Scale tools cause oom
https://bugs.kde.org/show_bug.cgi?id=503020 Lukas changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |giga-zod...@gmx.net CC||giga-zod...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 503020] Scale tools cause oom
https://bugs.kde.org/show_bug.cgi?id=503020 Lukas changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Lukas --- Hello Felix, thank you for your report and your detailed description. I tried to reproduce it following your exact steps, but I could not reproduce the increase in CPU and RAM usage. I tested on 5.2.9 and 5.2.5 on Windows 10. I can confirm the incorrect setting of the scaling dimensions to -1 though, so these might be two seperate issues, but its too early to tell. Your system information shows that you are using Windows 10 rather than 11, which you put into your description. Can you check this again and confirm which is correct? Can you please add more detailed steps to your discription, if there is anything I might have missed, like which exact tool you used to draw in step 2, or enabling a specific setting or something like that. If you can, record a video of it happening, as I could not even observe my layers being transformed while setting scale to -1. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 505986] Crash when enabling gradient overlay when no preset is selected
https://bugs.kde.org/show_bug.cgi?id=505986 Lukas changed: What|Removed |Added CC||giga-zod...@gmx.net Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Lukas --- Hello Noel, I tried replicating this on Windows 10 Pro and I could not reproduce it, not even with your attached project file. For me there seems to be a gradient selcted by default. Can you maybe add a screenshot that shows how the gradient window looks by default when you open it? Might be a Linux specific issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 506002] Brush outline (cursor ring) flickers, cuts off, or teleports when moved quickly — fixed in 5.3 nightly
https://bugs.kde.org/show_bug.cgi?id=506002 Lukas changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||giga-zod...@gmx.net --- Comment #1 from Lukas --- Hello Med, thank you for the video, which shows the difference between versions very nicely. I could reproduce this in 5.2.9 and also in 5.2.2. In both 5.1.5 and in 5.3.0-prealpha-a05ebc35, it is not present, so it seem to be a 5.2.X problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 505501] 5.3 (git 34f6765) - UI "On Canvas Brush Editor docker" does not respect Kinetic Scrolling
https://bugs.kde.org/show_bug.cgi?id=505501 Lukas changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||giga-zod...@gmx.net --- Comment #3 from Lukas --- Hey Wolfgang, I checked the Krita Artists thread too, but I still have troubles reproducing this. Can you add some more info on your system and settings? With my default Krita builds on Windows 10 I can not get the symbol size big enough to even have a scroll bar in the docker. I tried setting the DPi adjustment on Windows to 175% but that also did not add a scroll bar. Can you please add a step in your description on how you get that in the first place? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 505110] Colourise tool key strokes swatch size resets on change
https://bugs.kde.org/show_bug.cgi?id=505110 Lukas changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||giga-zod...@gmx.net --- Comment #1 from Lukas --- Hey Alexandre, Im having trouble following your steps. Can you please specify what you mean by "swatch"? Also, there is no default key binding with ctrl+mousewheel, did u manually add that by chance? If so, please specify which exact hotkey command you have bound this to. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 505986] Crash when enabling gradient overlay when no preset is selected
https://bugs.kde.org/show_bug.cgi?id=505986 Lukas changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Lukas --- I see, thanks for adding the video. Someone with the appropriate Linux build needs to verify this, as on my Windows it looks completely different and has a preselected gradient. Changing the status to reported again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457658] toggle layer soloing doesn't work properly in nightly build version (5.2.0 prealpha).
https://bugs.kde.org/show_bug.cgi?id=457658 Lukas changed: What|Removed |Added CC||giga-zod...@gmx.net --- Comment #1 from Lukas --- Created attachment 182693 --> https://bugs.kde.org/attachment.cgi?id=182693&action=edit Showing the behaviour of soloing shortcut -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 505280] New: Importing brush tip from clipboard does not work
https://bugs.kde.org/show_bug.cgi?id=505280 Bug ID: 505280 Summary: Importing brush tip from clipboard does not work Classification: Applications Product: krita Version First git master (please specify the git hash!) Reported In: Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: giga-zod...@gmx.net Target Milestone: --- SUMMARY In the brush engine editor predefined window, selecting "clipboard" will open a window that says "nothing copied to clipboard", even if there is an image file (tested with PNG and TIF) copied to the clip board. STEPS TO REPRODUCE 1. Copy a PNG or TIF file with ctrl+C 2. Open brush editor 3. Go to predefined tab 4. Select "clipboard" as the import mode OBSERVED RESULT Window says there is nothing copied to the clipboard and the save button is deactivated. EXPECTED RESULT It should show the PNG or TIF file in the preview window and the save button should be active, enabling you to save it as a brush tip. SOFTWARE/OS VERSIONS Windows: 10 Pro Tested and observed in 5.0.6, 5.1.5, 5.2.2, 5.2.3., 5.2.4, 5.2.5, 5.2.9 and 5.3.0-prealpha-a05ebc35 ADDITIONAL INFORMATION Only tested this with PNG and TIF files so far. The tooltip mouse-over on the "clipboard" button says "Creates a brush tip from the image in the clipboard". Either the tooltip is wrong because it needs a specific file type rather than an "image" in the clipboard, or the clipboard import does not work correctly for PNG and TIF. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 505279] New: Can't re-import brush tip that has been deleted before
https://bugs.kde.org/show_bug.cgi?id=505279 Bug ID: 505279 Summary: Can't re-import brush tip that has been deleted before Classification: Applications Product: krita Version First git master (please specify the git hash!) Reported In: Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: giga-zod...@gmx.net Target Milestone: --- Created attachment 182072 --> https://bugs.kde.org/attachment.cgi?id=182072&action=edit 5.0.6. database warning SUMMARY If you delete a brush tip in the predefined section and try to import the same file again, it shows a dialog box asking you to overwrite it. Despite confirming this, the brush tip will not be imported again. STEPS TO REPRODUCE 1. Delete a custom brush tip in the predefined section 2. Import new brush tip and select the same file of the previously deleted brush tip 3. Confirm dialog asking to overwrite existing brushtip OBSERVED RESULT After confirming the overwrite dialog, no new brushtip is created. EXPECTED RESULT There should not be a dialog warning about overwriting an existing tip, because we deleted it. The newly selected file should be imported as a new tip. SOFTWARE/OS VERSIONS Windows: 10 Pro Krita versions tested: 5.0.6 (!!) , 5.1.5, 5.2.2, 5.2.3., 5.2.4, 5.2.5, 5.2.9 and 5.3.0-prealpha-a05ebc35 ADDITIONAL INFORMATION I tested from 5.3.0-prealpha-a05ebc35 backwards. Upon opening 5.0.6 I got a warning saying the ressource database has changed and will be backed up (see screenshot attached). When opening the engine editor in 5.0.6 it shows me the previously supposedly deleted brush tips, so it appears they are not truly being deleted? Also, if you change the filename of a DIFFERENT file to the previously deleted brush tip, it will get successully imported. This might have something to do with how Krita is storing the imported brush tips. I also found this report about a crash that has been fixed, which seems to be connected because it happened on the same overwrite confirmation of an already deleted tip: https://bugs.kde.org/show_bug.cgi?id=450121 When checking the fix I can't really see how this could have led to the current behaviour, but maybe someone else can see it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457658] toggle layer soloing doesn't work properly in nightly build version (5.2.0 prealpha).
https://bugs.kde.org/show_bug.cgi?id=457658 --- Comment #2 from Lukas --- Hey, I independently stumbled upon this while testing today and recorded a short video of the behaviour and the possible workaround. Tested this in krita-x64-5.3.0-prealpha-88295ba7 aswell as in 5.2.9. Still the same behaviour as originally reported. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 505653] Mono audio is only played to left side of stereo outputs
https://bugs.kde.org/show_bug.cgi?id=505653 Lukas changed: What|Removed |Added CC||k...@lukas-middendorf.de --- Comment #9 from Lukas --- I'm seeing the same issue (also on Fedora 42). In qpwgraph the output appears as "playback_AUX0" instead of "playback_FL" and "playback_FR". It does not seem to be unique to kasts. While playing a mono mp3 file works fine in VLC directly, playing it in Kaffeine (also using libVLC) shows the same issue. Kaffeine allows setting options for libVLC and there the problem goes away if I add "--stereo-mode=1" to the options. So apparently the default value of that setting seems to be incorrect. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #2 from Lukas Jirkovsky --- The home directory is on a SSD, so the speed is decent. Also, I forgot to mention the versions: kdevplatform 6cf05bdad48f093dcf9efad4f78d8275ce44f7a6 kdevelop cbe05bc0d8218744cc30a0e0241f8c3f25497049 clang 3.9.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] New: KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 Bug ID: 372040 Summary: KDevelop editor become unresponsive when clicking into a problem Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- Created attachment 102016 --> https://bugs.kde.org/attachment.cgi?id=102016&action=edit perf record output If I click on an underlined identifier, the editor becomes unresponsive for several seconds. I noticed that when I navigate to the identifier in the editor using keyboard arrows, there is no slowdown and KDevelop is perfectly resnposive the whole time. This problem happens with a work-related project that can be considered somewhat peculiar. There are about 6000 includes in ~500 subdirectories in the include path. The project itself is only a small subset of sources - the problem occurs even with a small test project that consists only of a single file that includes only few of the includes, though it becomes worse with larger projects. The sources are mounted using samba from a locally running virtual machine. Attached is a profile generated using the linux perf utility with the following command: perf record -g -p sleep 3 which I executed just before clicking on a problem in the editor. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #4 from Lukas Jirkovsky --- There must be something different in how the reparse (if it's the reparse) is invoked. I just did few more experiments: Test #1 1. rename a variable 2. move to a previous use of the variable using arrow keys 3. in the meantime, the project is reparsed and all previous uses are now marked "Use of undeclared identifier" The whole time KDevelop is responsive. Another test 1. rename a variable 2. quickly click on a use before it gets marked as a problem KDevelop stays responsive Test #2 1. rename a variable 2. wait for the reparse to finish 3. click on a use that is now underlined The whole KDevelop UI (I didn't realize it wasn't just the editor before) freezes for about 5 seconds. In fact, any click on the problem freezes the UI. Maybe I should have emphasized that the UI freezes every time I click on a problem, even when the project is fully parsed, so the parser may not be the problem after all. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #5 from Lukas Jirkovsky --- Another bunch of tests: Test #1 The project sources are in tmpfs, includes are on the samba share => same behaviour Test #2 All sources, including includes are in tmpfs => everything's fine -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #7 from Lukas Jirkovsky --- I just got an idea, though I may be completely wrong. Is it possible that it's related to the Clang Fix-its? They don't show when navigating using keyboard. I'll try to get backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #8 from Lukas Jirkovsky --- I hope I sent interrupt at the right time... #0 0x74cc4c9b in __getdents64 () at /usr/lib/libc.so.6 #1 0x74cc4a10 in readdir_r () at /usr/lib/libc.so.6 #2 0x75556773 in () at /usr/lib/libQt5Core.so.5 #3 0x754dcc8c in () at /usr/lib/libQt5Core.so.5 #4 0x754dd4dd in () at /usr/lib/libQt5Core.so.5 #5 0x754ddd5c in QDirIterator::QDirIterator(QString const&, QStringList const&, QFlags, QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x754d6dcc in QDir::entryList(QStringList const&, QFlags, QFlags) const () at /usr/lib/libQt5Core.so.5 #7 0x7fffbdb12bf5 in (anonymous namespace)::scanIncludePaths(QString const&, QDir const&, int) (identifier=..., dir=..., maxDepth=maxDepth@entry=2) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:95 #8 0x7fffbdb12fbc in (anonymous namespace)::scanIncludePaths(QString const&, QDir const&, int) (identifier=..., dir=..., maxDepth=2, maxDepth@entry=3) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:105 #9 0x7fffbdb16ae3 in (anonymous namespace)::scanIncludePaths (includes=..., identifier=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:118 #10 0x7fffbdb16ae3 in (anonymous namespace)::includeFiles (file=..., declarations=..., identifier=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:390 #11 0x7fffbdb16ae3 in (anonymous namespace)::fixUnknownDeclaration(KDevelop::QualifiedIdentifier const&, KDevelop::Path const&, KDevelop::DocumentRange const&) (identifier=..., file=..., docrange=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:466 #12 0x7fffbdb172b6 in UnknownDeclarationProblem::solutionAssistant() const (this=0x7fff8d2e60f0) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:520 #13 0x72e9a6f7 in KDevelop::ProblemNavigationContext::html(bool) (this=0x2601e40, shorten=) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/problemnavigationcontext.cpp:172 #14 0x72e9fc16 in KDevelop::AbstractNavigationWidget::update() (this=this@entry=0x2821c50) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:148 #15 0x72ea0800 in KDevelop::AbstractNavigationWidget::setContext(QExplicitlySharedDataPointer, int) (this=this@entry=0x2821c50, context=..., initBrows=initBrows@entry=400) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:116 #16 0x7fffc22c04ba in ContextBrowserPlugin::navigationWidgetForPosition(KTextEditor::View*, KTextEditor::Cursor) (this=this@entry=0x118bef0, view=view@entry=0xe91640, position=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:539 #17 0x7fffc22c20b2 in ContextBrowserPlugin::showToolTip(KTextEditor::View*, KTextEditor::Cursor) (this=0x118bef0, view=0xe91640, position=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:585 #18 0x7fffc22c3e4f in ContextBrowserHintProvider::textHint(KTextEditor::View*, KTextEditor::Cursor const&) (this=0x118c068, view=, cursor=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:407 #19 0x71a4ffbf in () at /usr/lib/libKF5TextEditor.so.5 #20 0x71b518a5 in () at /usr/lib/libKF5TextEditor.so.5 #21 0x755e9659 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #22 0x755f66d8 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #23 0x755ea473 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7629de0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x762a5581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x755bdde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #27 0x756116ae in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #28 0x75611bd1 in () at /usr/lib/libQt5Core.so.5 #29 0x7fffec611587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #30 0x7fffec6117f0 in () at /usr/lib/libglib-2.0.so.0 #31 0x7fffec61189c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #32 0x7561270f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x755bc23a in QEventLoop::exe
[gwenview] [Bug 362474] Copy To/Move To does not remember path any more
https://bugs.kde.org/show_bug.cgi?id=362474 Lukas Polacek changed: What|Removed |Added CC||lu...@ksp.sk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364709] Activating desktop grid sometimes freezes X11
https://bugs.kde.org/show_bug.cgi?id=364709 Lukas Zavodny changed: What|Removed |Added CC||suc...@centrum.cz --- Comment #10 from Lukas Zavodny --- It happens to me almost every day on nVidia drivers nad kwin 5.8.3 9 desktops, 3 rows. Activation by left side of desktop. Only mouse is moving. Killing and starting kwin again helps with using computer without restart. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438317] Annoying download binary message at startup
https://bugs.kde.org/show_bug.cgi?id=438317 --- Comment #15 from Lukas Jirkovsky --- What about solution similar to how wine handles it's gecko and mono packages? They can be installed system-wide using package manager, or automatically during first startup. The face recognition data can be released separately from digiKam. * the face recognition data would be released separately from digiKam, so they don't have to be updated with every digiKam release * digikam would have to check both system folder and user folder * nice to have: have the notification less obtrusive, something like the notifications in kate eg. when you reload a file. * nice to have #2: if the files are not available, disable the affected functionality and notify user that they need the data when they try to use it. This would improve at least the following use cases: * users that manage multiple computers would download the system-wide package once and install it everywhere * shared computers - the system-wide package would need to be installed only once rather than for every user * users of linux distros that prefer to use packages to download&install stuff * windows users and any other users that doesn't care about downloading data separately would download the data on startup if they wanted to * in the system-wide install scenarios, digiKam updates would not require re-downloading the data, because they would be released separately -- You are receiving this mail because: You are watching all bug changes.
