[Breeze] [Bug 371914] Icon request: Claws-mail
https://bugs.kde.org/show_bug.cgi?id=371914 --- Comment #3 from andreas --- I will check the app icon but do we have a breeze icon theme for claws-mail? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 372119] list-remove-symbolic.svg uses wrong image
https://bugs.kde.org/show_bug.cgi?id=372119 andreas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/bree ||ze-icons/78b0964689d5f3aef4 ||ca0b1b1374ed2ecfb8287b --- Comment #1 from andreas --- Git commit 78b0964689d5f3aef4ca0b1b1374ed2ecfb8287b by andreas kainz. Committed on 05/11/2016 at 22:04. Pushed by andreask into branch 'master'. fix BUG:372119 list-remove-symcolic use wrong image T +77 -1icons/actions/symbolic/list-remove-symbolic.svg http://commits.kde.org/breeze-icons/78b0964689d5f3aef4ca0b1b1374ed2ecfb8287b -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 372111] New icon for Google Drive
https://bugs.kde.org/show_bug.cgi?id=372111 andreas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/bree ||ze-icons/d496eb50ca88d65952 ||c326a54ebf19826a748b4b --- Comment #1 from andreas --- Git commit d496eb50ca88d65952c326a54ebf19826a748b4b by andreas kainz. Committed on 06/11/2016 at 12:16. Pushed by andreask into branch 'master'. add gdrive icon instead of a generic cloud icon T +13 -1icons/places/16/folder-gdrive.svg T +13 -1icons/places/22/folder-gdrive.svg T +319 -1icons/places/32/folder-gdrive.svg T +304 -1icons/places/64/folder-gdrive.svg http://commits.kde.org/breeze-icons/d496eb50ca88d65952c326a54ebf19826a748b4b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 359165] Config dialog icons are white on white
https://bugs.kde.org/show_bug.cgi?id=359165 andreas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 354820] KMail2 Tray icon doesn't match Breeze icon theme
https://bugs.kde.org/show_bug.cgi?id=354820 andreas changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #16 from andreas --- in general I'm not sure if it's "only" a breeze issue. It would be easier to solve this problem together with the kmail team. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371914] Icon request: Claws-mail
https://bugs.kde.org/show_bug.cgi?id=371914 andreas changed: What|Removed |Added Latest Commit||http://commits.kde.org/bree ||ze-icons/92510347590deb ||f96b6d9b5724e8d31905b5 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from andreas --- Git commit 92510347590debf96b6d9b5724e8d31905b5 by andreas kainz. Committed on 13/11/2016 at 01:11. Pushed by andreask into branch 'master'. add claws icon from jens (thanks) I'll make also a breeze theme A +579 -0icons-dark/apps/48/claws_mail_icon.svg A +579 -0icons/apps/48/claws_mail_icon.svg http://commits.kde.org/breeze-icons/92510347590debf96b6d9b5724e8d31905b5 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371914] Icon request: Claws-mail
https://bugs.kde.org/show_bug.cgi?id=371914 --- Comment #6 from andreas --- Created attachment 102197 --> https://bugs.kde.org/attachment.cgi?id=102197&action=edit claws icon theme please test the icon theme (I didn't use claws) will send the theme to the app developer if everything works fine. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371914] Icon request: Claws-mail
https://bugs.kde.org/show_bug.cgi?id=371914 andreas changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #7 from andreas --- feedback for the claws icon theme is needed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 372461] Missing RAR MIME type icon with shared-mime-info 1.7
https://bugs.kde.org/show_bug.cgi?id=372461 andreas changed: What|Removed |Added Latest Commit||http://commits.kde.org/bree ||ze-icons/f9d574b0138a53961c ||3983a179d024536f3d9e1f Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from andreas --- Git commit f9d574b0138a53961c3983a179d024536f3d9e1f by andreas kainz. Committed on 14/11/2016 at 11:45. Pushed by andreask into branch 'master'. add vnd.rar mime for shared-mime-info 1.7 A +1-0icons-dark/mimetypes/16/application-vnd.rar.svg A +1-0icons-dark/mimetypes/22/application-vnd.rar.svg A +1-0icons-dark/mimetypes/32/application-vnd.rar.svg A +1-0icons-dark/mimetypes/64/application-vnd.rar.svg A +1-0icons/mimetypes/16/application-vnd.rar.svg A +1-0icons/mimetypes/22/application-vnd.rar.svg A +1-0icons/mimetypes/32/application-vnd.rar.svg A +1-0icons/mimetypes/64/application-vnd.rar.svg http://commits.kde.org/breeze-icons/f9d574b0138a53961c3983a179d024536f3d9e1f -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 372461] Missing RAR MIME type icon with shared-mime-info 1.7
https://bugs.kde.org/show_bug.cgi?id=372461 andreas changed: What|Removed |Added Latest Commit|http://commits.kde.org/bree |http://commits.kde.org/oxyg |ze-icons/f9d574b0138a53961c |en-icons/bfbc27488559dd0aa7 |3983a179d024536f3d9e1f |c22e7528c0ccf9ea9f6094 --- Comment #6 from andreas --- Git commit bfbc27488559dd0aa7c22e7528c0ccf9ea9f6094 by andreas kainz. Committed on 14/11/2016 at 12:05. Pushed by andreask into branch 'master'. add application-vnd.rar icon A +1-0128x128/mimetypes/application-vnd-rar.png A +1-016x16/mimetypes/application-vnd-rar.png A +1-022x22/mimetypes/application-vnd-rar.png A +1-0256x256/mimetypes/application-vnd-rar.png A +1-032x32/mimetypes/application-vnd-rar.png A +1-048x48/mimetypes/application-vnd-rar.png A +1-064x64/mimetypes/application-vnd-rar.png http://commits.kde.org/oxygen-icons/bfbc27488559dd0aa7c22e7528c0ccf9ea9f6094 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 372383] desktoptheme/default/widgets/tasks.svgz contains unresolvable SVG gradient "radialGradient4857"
https://bugs.kde.org/show_bug.cgi?id=372383 andreas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-framework/18ff230d814fa7 ||051fec8bfc5fc403612cf40c92 --- Comment #1 from andreas --- Git commit 18ff230d814fa7051fec8bfc5fc403612cf40c92 by andreas kainz. Committed on 15/11/2016 at 12:22. Pushed by andreask into branch 'master'. remove radialGradient4857 M +---src/desktoptheme/breeze/widgets/tasks.svgz http://commits.kde.org/plasma-framework/18ff230d814fa7051fec8bfc5fc403612cf40c92 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369408] Icon request: 0ad, Blockify, CodeLite, Eclipse, Freeciv, Freecol, GNU Emacs, NetBeans, OpenRA, SuperTux, Visual Studio Code, etc
https://bugs.kde.org/show_bug.cgi?id=369408 --- Comment #1 from andreas --- Hi, thanks for the bug report. 1. some icons have licence issues (thunderbird) 2. I don't think that you need for every application an breeze styled icon. Sometime you loose the app identification. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371914] Icon request: Claws-mail
https://bugs.kde.org/show_bug.cgi?id=371914 --- Comment #8 from andreas --- the app icons in "hardcoded" /usr/share/pixmap/ so it can't be changed in the task manager. sorry -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 373087] New: plasma icons from system settings icon theme
https://bugs.kde.org/show_bug.cgi?id=373087 Bug ID: 373087 Summary: plasma icons from system settings icon theme Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: kain...@gmail.com Target Milestone: --- plasma use the icon's for the system tray from the plasma theme. when you look at gnome and xfce the system tray and panel icons come from the icon theme (/usr/share/icons/...). Most popular icon designers add support for system tray icons in there icon set it would be awesome if plasma can use this icons and only as backup the icons from the plasma theme were used. Not every icon designer want to make a new plasma theme only to have the right icons in the system tray. In addition since plasma 5 all kde applications use first the icons from system settings and if there isn't the needed icon the icon from the app source was used. why should there be a difference for plasma. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 373087] plasma icons from system settings icon theme
https://bugs.kde.org/show_bug.cgi?id=373087 andreas changed: What|Removed |Added CC||kain...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373087] plasma icons from system settings icon theme
https://bugs.kde.org/show_bug.cgi?id=373087 --- Comment #1 from andreas --- If I remove the icons folder from breeze/default, the icons from system settings were used. Problem: the system tray isn't monochrome any more. Solution: -symbolic or -panel suffix -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373148] No Breeze icon for Marble
https://bugs.kde.org/show_bug.cgi?id=373148 andreas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from andreas --- we had an breeze icon but marble prefer the oxygen ones and that's the reason we remove the breeze ones. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464935] Add option to save session in Logout screen
https://bugs.kde.org/show_bug.cgi?id=464935 andreas changed: What|Removed |Added CC||kain...@gmail.com --- Comment #4 from andreas --- On SDDM you have at the bottom a "toolbar" where you can switch between keyboard layouts or x11/wayland. This layout can be used for session save where you can define a name and at the next login (SDDM) you can choose one of the saved session. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 465602] New: Search in audio library
https://bugs.kde.org/show_bug.cgi?id=465602 Bug ID: 465602 Summary: Search in audio library Classification: Applications Product: amarok Version: 2.9.71 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: andreas.privatadre...@gmail.com Target Milestone: kf5 Application: amarok (2.9.71) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.10-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: After entering a single letter to filter my local audio library (some 50k tracks), amarok crashed. This effect is reproducable. Since it occurs already for the first letter, it is not posssible do any filtering at all right now. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault [KCrash Handler] #4 0x7f4c4f44001e in CollectionTreeItem::row() const () from /lib64/libamaroklib.so.1 #5 0x7f4c4f44e850 in CollectionTreeItemModelBase::itemIndex(CollectionTreeItem*) const () from /lib64/libamaroklib.so.1 #6 0x7f4c4f443340 in CollectionTreeItemModelBase::parent(QModelIndex const&) const () from /lib64/libamaroklib.so.1 #7 0x7f4c4dcb09b1 in ?? () from /lib64/libQt5Core.so.5 #8 0x7f4c4dd1360c in ?? () from /lib64/libQt5Core.so.5 #9 0x7f4c4dc7628c in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #10 0x7f4c4f450103 in CollectionTreeItemModelBase::tracksLoaded(AmarokSharedPointer const&, QModelIndex const&, QList > const&) () from /lib64/libamaroklib.so.1 #11 0x7f4c4dd07d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f4c4e9a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7f4c4dcdc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f4c4dcdf181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #15 0x7f4c4dd34413 in ?? () from /lib64/libQt5Core.so.5 #16 0x7f4c4af1ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x7f4c4af1be48 in ?? () from /lib64/libglib-2.0.so.0 #18 0x7f4c4af1bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x7f4c4dd33c16 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7f4c4dcdac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7f4c4dce2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #22 0x55f0c7ed6f76 in ?? () #23 0x7f4c4d42c5b0 in __libc_start_call_main () from /lib64/libc.so.6 #24 0x7f4c4d42c679 in __libc_start_main_impl () from /lib64/libc.so.6 #25 0x55f0c7ed7805 in ?? () [Inferior 1 (process 4584) detached] The reporter indicates this bug may be a duplicate of or related to bug 08. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 Andreas changed: What|Removed |Added CC||opendr...@gmail.com --- Comment #130 from Andreas --- Created attachment 156492 --> https://bugs.kde.org/attachment.cgi?id=156492&action=edit nvidia-settings second monitor I have the same issues with Plasma 5.27 on Leap 15.4, X11, NVIDIA. - settings are not saved after reconnecting the monitor - after waking up from sleep (for example, after 15 minutes), the second monitor does not turn on and the reboot does not help. Also, the second monitor does not work in offload mode, nvidia-settings shows the connected monitor, but it is not in the Plasma settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443355] Incorrect DPI settings on KDE Plasma when switched GPU
https://bugs.kde.org/show_bug.cgi?id=443355 --- Comment #11 from Andreas --- In Plasma 5.27 GTK applications don't scale when you switch to a second GPU. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443355] Incorrect DPI settings on KDE Plasma when switched GPU
https://bugs.kde.org/show_bug.cgi?id=443355 --- Comment #12 from Andreas --- (In reply to Andreas from comment #11) > In Plasma 5.27 GTK applications don't scale when you switch to a second GPU. If I add GDK_SCALE=2 then applications are scaled 4x -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466363] New: Digikam AppImage 7.9.0 on Debian 12 - cannot start
https://bugs.kde.org/show_bug.cgi?id=466363 Bug ID: 466363 Summary: Digikam AppImage 7.9.0 on Debian 12 - cannot start Classification: Applications Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: andr...@1107.se Target Milestone: --- SUMMARY AppImage doesn't work, at least not on Debian 12 STEPS TO REPRODUCE 1. Download Appimage 2. Try to launch OBSERVED RESULT ./digiKam-7.9.0-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. --to extract the bundle contents locally, use option '--appimage-extract' on the command line. -- Detected host Linux -64- -- AppImage mounted directory: /tmp/.mount_digiKaZ8kSlO Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/tmp/.mount_digiKaZ8kSlO/usr/lib/libavif.so.13:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 /tmp/.mount_digiKaZ8kSlO/AppRun: line 204: 37089 Segmentation fault digikam $@ EXPECTED RESULT App launches SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 12 (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.
[digikam] [Bug 466363] Digikam AppImage 7.9.0 on Debian 12 - cannot start
https://bugs.kde.org/show_bug.cgi?id=466363 --- Comment #2 from Andreas --- Sorry! Debug below: ./digiKam-7.9.0-x86-64.appimage debug -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. --to extract the bundle contents locally, use option '--appimage-extract' on the command line. -- Detected host Linux -64- -- AppImage mounted directory: /tmp/.mount_digiKaRKnfkr Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/tmp/.mount_digiKaRKnfkr/usr/lib/libavif.so.13:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 Starting digiKam into GDB... Use 'bt' command on debugger prompt to get a crash backtrace. Use 'q' command to quit debugger session. /tmp/.mount_digiKaRKnfkr/AppRun: line 183: gdb: command not found -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466363] Digikam AppImage 7.9.0 on Debian 12 - cannot start
https://bugs.kde.org/show_bug.cgi?id=466363 --- Comment #4 from Andreas --- Aha. Ok - installed it and re-ran, the output: ./digiKam-7.9.0-x86-64.appimage debug -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. --to extract the bundle contents locally, use option '--appimage-extract' on the command line. -- Detected host Linux -64- -- AppImage mounted directory: /tmp/.mount_digiKaK8aoyC Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/tmp/.mount_digiKaK8aoyC/usr/lib/libavif.so.13:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 Starting digiKam into GDB... Use 'bt' command on debugger prompt to get a crash backtrace. Use 'q' command to quit debugger session. GNU gdb (Debian 12.1-4+b1) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from digikam... (No debugging symbols found in digikam) Starting program: /tmp/.mount_digiKaK8aoyC/usr/bin/digikam [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffbc1ff6c0 (LWP 132701)] [New Thread 0x7fffbb5ff6c0 (LWP 132702)] [New Thread 0x7fffb27ff6c0 (LWP 132704)] [New Thread 0x7fffb1ffe6c0 (LWP 132705)] [New Thread 0x7fffb17fd6c0 (LWP 132706)] [New Thread 0x7fffb0ffc6c0 (LWP 132707)] [New Thread 0x7fffa4dff6c0 (LWP 132708)] [New Thread 0x7fff86c0 (LWP 132709)] [New Thread 0x7fff87fff6c0 (LWP 132710)] [New Thread 0x7fff8f7fe6c0 (LWP 132711)] [New Thread 0x7fff8effd6c0 (LWP 132712)] [New Thread 0x7fff8e7fc6c0 (LWP 132713)] [New Thread 0x7fff8dffb6c0 (LWP 132714)] [New Thread 0x7fff8d7fa6c0 (LWP 132715)] [New Thread 0x7fff8cff96c0 (LWP 132716)] [New Thread 0x7fff877fe6c0 (LWP 132717)] [New Thread 0x7fff86ffd6c0 (LWP 132718)] [New Thread 0x7fff867fc6c0 (LWP 132719)] [New Thread 0x7fff85ffb6c0 (LWP 132720)] Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76 76 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466363] Digikam AppImage 7.9.0 on Debian 12 - cannot start
https://bugs.kde.org/show_bug.cgi?id=466363 --- Comment #6 from Andreas --- We are getting there! :-) Now with backtrace: ./digiKam-7.9.0-x86-64.appimage debug -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. --to extract the bundle contents locally, use option '--appimage-extract' on the command line. -- Detected host Linux -64- -- AppImage mounted directory: /tmp/.mount_digiKamWVPvz Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/tmp/.mount_digiKamWVPvz/usr/lib/libavif.so.13:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 Starting digiKam into GDB... Use 'bt' command on debugger prompt to get a crash backtrace. Use 'q' command to quit debugger session. GNU gdb (Debian 12.1-4+b1) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from digikam... (No debugging symbols found in digikam) Starting program: /tmp/.mount_digiKamWVPvz/usr/bin/digikam [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffbc1ff6c0 (LWP 133345)] [New Thread 0x7fffbb5ff6c0 (LWP 133346)] [New Thread 0x7fffb27ff6c0 (LWP 133348)] [New Thread 0x7fffb1ffe6c0 (LWP 133349)] [New Thread 0x7fffb17fd6c0 (LWP 133350)] [New Thread 0x7fffb0ffc6c0 (LWP 133351)] [New Thread 0x7fffa4dff6c0 (LWP 133352)] [New Thread 0x7fff97fff6c0 (LWP 133353)] [New Thread 0x7fff977fe6c0 (LWP 133354)] [New Thread 0x7fff96ffd6c0 (LWP 133355)] [New Thread 0x7fff967fc6c0 (LWP 133356)] [New Thread 0x7fff95ffb6c0 (LWP 133357)] [New Thread 0x7fff957fa6c0 (LWP 133358)] [New Thread 0x7fff94ff96c0 (LWP 133359)] [New Thread 0x7fff6bfff6c0 (LWP 133360)] [New Thread 0x7fff6b7fe6c0 (LWP 133361)] [New Thread 0x7fff63fff6c0 (LWP 133362)] [New Thread 0x7fff6affd6c0 (LWP 133363)] [New Thread 0x7fff6a7fc6c0 (LWP 133364)] Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76 76 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76 #1 0x729354f0 in QByteArray::QByteArray(char const*, int) () from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Core.so.5 #2 0x7fffbaa09175 in ?? () from /tmp/.mount_digiKamWVPvz/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so #3 0x7fffbaa0a654 in ?? () from /tmp/.mount_digiKamWVPvz/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so #4 0x7fffbaa07ee7 in ?? () from /tmp/.mount_digiKamWVPvz/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so #5 0x7fffbea3ea22 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5XcbQpa.so.5 #6 0x73367b8f in QOpenGLContext::create() () from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Gui.so.5 #7 0x7fffe2d20f1e in QtWebEngineCore::initialize() () from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5WebEngineCore.so.5 #8 0x72ad96a7 in QCoreApplicationPrivate::init() () from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Core.so.5 #9 0x7331bb0f in QGuiApplicationPrivate::init() () from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Gui.so.5 #10 0x73d63849 in QApplicationPrivate::init() () --Type for more, q to quit, c to continue without paging-- from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Widgets.so.5 #11 0x55404673 in ?? () #12 0x76a4618a in __libc_start_call_main ( main=main@entry=0x55404540, argc=argc@entry=1, argv=argv@entry=0x7fffd668) at ../sysd
[digikam] [Bug 466363] Digikam AppImage 7.9.0 on Debian 12 - cannot start
https://bugs.kde.org/show_bug.cgi?id=466363 --- Comment #8 from Andreas --- (In reply to caulier.gilles from comment #7) > It crash in Qt XCB plugin used to deal with X11 extension to render on > screen. Did you use Wayland instead X11 ? Yes, I ran loginctl SESSION UID USERSEAT TTY 2 1000 andreas seat0 tty2 and then loginctl show-session 2 -p Type" and it says Type=wayland It's the default in Debian, I didn't change anything about this. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 465602] Search in audio library
https://bugs.kde.org/show_bug.cgi?id=465602 --- Comment #2 from Andreas --- Hi Tuomas My version of amarok is the latest from OpenSuse Tumbleweed: 2.9.75git.20221114T020258~457db492b4-1.3 but the same error occurs. Maybe there is an issue with the size of the library which is almost 400GB and I guess some 70k tracks. I could not try the version from KDE:Unstable:Extra since I just arrived today. But I will try it soon. Thanks and best regards Andreas Am 10.03.23 um 09:28 schrieb Tuomas Nurmi: > https://bugs.kde.org/show_bug.cgi?id=465602 > > Tuomas Nurmi changed: > > What|Removed |Added > > CC||tuo...@norsumanageri.org > > --- Comment #1 from Tuomas Nurmi --- > A fix forhttps://bugs.kde.org/show_bug.cgi?id=08 has been in GIT since > 7th > Feb 2023, and I'd believe this is the same bug. The most readily available > Amarok packages for openSUSE Tumbleweed seem to be > 2.9.75git.20221114T02 in repository KDE:Extra and > 2.9.75git.20230309T01 in repository KDE:Unstable:Extra > > Can you confirm / check from package management (or check from About Amarok -> > Build date) if the version you are using is an older build than 7th Feb 2023, > and if so, try if the newer version in KDE:Unstable:Extra works for you? > -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] New: K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 Bug ID: 467530 Summary: K3b - wrong (less) permissions to some programms Classification: Applications Product: k3b Version: 21.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: andreaskleine.onl...@web.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 157392 --> https://bugs.kde.org/attachment.cgi?id=157392&action=edit screen shot after the second permission change request SUMMARY *** NOTE: This is NOT a crash report; there is a problem with the rights for cdrecord: /usr/bin/wodim; cdrdao: /usr/bin/cdrdao; growisofs: /usr/bin/growisofs STEPS TO REPRODUCE 1. k3b installed 2. open "Einstellungen - K3b-einrichten" goto "Programme - Berechtigungen" 3. give the requested permissions through clicking the button "Berechtigungen ändern" 4. click "ok" to leave the dialog 5. open "Einstellungen - K3b-einrichten" again goto "Programme - Berechtigungen" again 6. new permissions are shown by K3b, so i push the button "Berechtigungen ändern" again to confirm the requested change again. confirm the button "ok" to close the dialog. OBSERVED RESULT the message is shown, that are not enough permissions for the listed programms when you enter the "Einstellungen - K3b-einrichten"-"Programme - Berechtigungen" again, K3b makes no further suggestions to give the right permissions back to the first change request EXPECTED RESULT no error message about wrong permissions to the programms so i can burn a medium SOFTWARE/OS VERSIONS Linux/KDE Plasma:Kubuntu 22.04.2 LTS (available in About System) 5.15.0-67-generic (64-bit); X11 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version:5.15.3 ADDITIONAL INFORMATION three screen shots -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 --- Comment #1 from Andreas --- Created attachment 157394 --> https://bugs.kde.org/attachment.cgi?id=157394&action=edit dialog message about the wrong/missing permissions -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 --- Comment #2 from Andreas --- Created attachment 157395 --> https://bugs.kde.org/attachment.cgi?id=157395&action=edit screen shot of the burner device found -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 Andreas changed: What|Removed |Added CC||andreaskleine.onl...@web.de -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 468757] New: Extended Data analyse
https://bugs.kde.org/show_bug.cgi?id=468757 Bug ID: 468757 Summary: Extended Data analyse Classification: Applications Product: filelight Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kain...@gmail.com CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY *** Filelight show the size of folders, I would like to extend filelight with additional views for folder analysis. *** What I want to show is the folder activities, so in which folder was more activities and in which one less, click on the folder will show the recent edited files. So in general as a user you know where you have worked on recently. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 468757] Extended Data analyse
https://bugs.kde.org/show_bug.cgi?id=468757 --- Comment #1 from andreas --- I'm no developer, but I wouldn't have issues if someone can mentor me what can be used for the UI. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466363] digiKam AppImage 7.9.0 on Debian 12 - cannot start with Wayland.
https://bugs.kde.org/show_bug.cgi?id=466363 --- Comment #10 from Andreas --- Hi Gilles - thanks for checking. I can't check whether it works in 8.0.0 via the default repositories because Debian Bookworm is still with package 7.9.0: https://packages.debian.org/bookworm/digikam I tried to install 7.9.0 now and I can open the app. Perhaps other packages in Bookworm were updated and so 7.9.0 works better on Debian Bookworm (from Digikam about page: "Build date: 13/01/2023 07:08 (target: Debian)") However: 7.9.0 has serious UI issues. It looks much better and is more stable than the Flathub version, but displays similar random "twitches" to Flathub 8.0.0 version - see below, triggering these seems random: (Screenshot from 2023-05-04 07-50-10.png) and (Screenshot from 2023-05-04 07-51-15.png) I installed 8.0.0 via Flathub just now to check it out as well - https://flathub.org/en-GB/apps/org.kde.digikam The Flathub version can start on Debian Bookworm but has many UI issues. For example, in Flathub version when I open Settings and close it the app will (often) start to look funny (Screenshot from 2023-05-04 07-38-02.png). The contrasts will be a bit off always on buttons (Screenshot from 2023-05-04 07-35-07.png) or the app will go blank (Screenshot from 2023-05-04 07-37-30.png). I can't tie this to any particular thing I'm doing, it could be browsing photos or changing settings. Another experience of the Flathub version for me was that it crashed quite often for no reason. For example on 8.0.0, it crashes when I try to switch the colour scheme. I tried Flathub earlier mostly on Ubuntu 20.04 LTS and it had too many issues to be usable. It seems the issues are the same for the Debian Flathub version. Usually the version from Ubuntu repositories didn't have so many issues and worked well, but now the Debian repository version displays similar issues (but a bit less) than the Flathub version. Thanks! Andreas 3 May 2023, 1:31 pm by bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=466363 > > --- Comment #9 from caulier.gil...@gmail.com --- > @Andreas, > > digiKam 8.0.0 is out. This entry still valid with this release ? > > Best regards > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466363] digiKam AppImage 7.9.0 on Debian 12 - cannot start with Wayland.
https://bugs.kde.org/show_bug.cgi?id=466363 --- Comment #16 from Andreas --- Ah yes, now I remember (and read the subject line) :-) I just tried to download the appimage and run and it works perfectly so far. This is great - thank you! 4 May 2023, 8:17 am by bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=466363 > > --- Comment #15 from caulier.gil...@gmail.com --- > Andreas, > > This issue is not for Flatpak or Snap bundles, it's for "AppImage" > > Forget flatpak and snap, there are sand-boxed and mostly unusable with complex > application as digiKam. > > Try the AppImage bundle that WE (digiKam team) provide and support officially. > > The 8.0.0 files are available here : > > https://download.kde.org/stable/digikam/8.0.0/digiKam-8.0.0-x86-64.appimage.mirrorlist > > How to run? it's very very simple : > > https://docs.digikam.org/en/getting_started/installation.html#digikam-on-linux > > Best > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[isoimagewriter] [Bug 469452] New: wrong app icon usage
https://bugs.kde.org/show_bug.cgi?id=469452 Bug ID: 469452 Summary: wrong app icon usage Classification: Applications Product: isoimagewriter Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@jriddell.org Reporter: kain...@gmail.com Target Milestone: --- On Windows the app use an black/white icon instead of the colorfull Iso Image writer icon from https://apps.kde.org/de/isoimagewriter/ -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447017] Breeze Icons shouldn't include icons for third-party softwares
https://bugs.kde.org/show_bug.cgi?id=447017 --- Comment #4 from andreas --- To be fair, when the breeze inkscape action icons were added, the origin inkscape action icons look alien within KDE. Nowadays the Inscape icons from the Inkscape package look really good AND they work very well within breeze, cause the design language of the action icons are very similar. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 433212] Arrow keys don't move in 1-pixel steps
https://bugs.kde.org/show_bug.cgi?id=433212 Andreas changed: What|Removed |Added CC||kde.av33...@sutor.info --- Comment #1 from Andreas --- Working on notebook with openSUSE LEAP 15.4. Resizing a rectangular can't be done with arrow keys. Only moving this box in greater steps is possible. But not with constant steps for- and backward. This functionality was given in previous version and seems to be solved again, when using openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 481760] KDEconnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=481760 Andreas changed: What|Removed |Added CC||a.szek...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 481760] KDEconnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=481760 --- Comment #1 from Andreas --- Created attachment 170864 --> https://bugs.kde.org/attachment.cgi?id=170864&action=edit New crash information added by DrKonqi kdeconnectd (23.08.5) using Qt 5.15.9 I installed the KDE workspace on a clean GNOME Fedora 40, works fine. I did the same on a clean Oracle Linux 9.4 where I replaced the GNOME environment with KDE workspace. Consistent daemon crash already after boot on this system. Otherwise no problems on this system. (lacking icon on the taskbar for the KDE start menu ) The PC is the same, I use fresh harddisks for every system I try. I am kind of novice to the numerous Linux distros.. -- Backtrace (Reduced): #4 0x7ffb8d3b6036 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.23 #5 0x7ffb8d3b962d in KdeConnectConfig::deviceInfo() () from /lib64/libkdeconnectcore.so.23 #6 0x7ffb8d3a60b5 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.23 #7 0x7ffb8c003c69 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7ffb8c006eee in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 478788] New: Amarok crashes when searching the library
https://bugs.kde.org/show_bug.cgi?id=478788 Bug ID: 478788 Summary: Amarok crashes when searching the library Classification: Applications Product: amarok Version: 2.9.71 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: andreas.privatadre...@gmail.com Target Milestone: kf5 Application: amarok (2.9.71) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.6.3-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: When entering more than two words in the search field to find a title within the library, amarok crashes reproducably. I don't know if it is related to the relatively large size of my library (I guess some 400GB, approx. 7 songs). I run amarok under opsensuse tumbleweed. Amarok version 2.9.71 KDE Frameworks 5.112.0 The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault [KCrash Handler] #4 0x0001 in ?? () #5 0x7f7ed05fc602 in Collections::SqlQueryMaker::abortQuery() () from /lib64/libamarok-sqlcollection.so.1 #6 0x7f7ed0600f2a in Collections::SqlQueryMaker::~SqlQueryMaker() () from /lib64/libamarok-sqlcollection.so.1 #7 0x7f7ed06010e9 in Collections::SqlQueryMaker::~SqlQueryMaker() () from /lib64/libamarok-sqlcollection.so.1 #8 0x7f7ee9718d17 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f7eea3a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #10 0x7f7ee96ed198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7f7ee96f0791 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #12 0x7f7ee97468c3 in ?? () from /lib64/libQt5Core.so.5 #13 0x7f7ee4266f30 in ?? () from /lib64/libglib-2.0.so.0 #14 0x7f7ee4268b58 in ?? () from /lib64/libglib-2.0.so.0 #15 0x7f7ee426920c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #16 0x7f7ee97460d6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f7ee96ebc2b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #18 0x7f7ee96f40c0 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #19 0x5564d9261f76 in ?? () #20 0x7f7ee8c281b0 in __libc_start_call_main () from /lib64/libc.so.6 #21 0x7f7ee8c28279 in __libc_start_main_impl () from /lib64/libc.so.6 #22 0x5564d9262825 in ?? () [Inferior 1 (process 8807) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 Andreas changed: What|Removed |Added CC||hoheneg...@web.de --- Comment #9 from Andreas --- I can report that the Reddit workaround https://www.reddit.com/r/kdeneon/comments/1aenouy/kde_neon_wont_boot_after_fresh_install_cryptsetup/ works (where I replaced /dev/nvme0n1p2 with my root partition path inferred from, e.g., partitionmanager) --- On the running system, out of curiosity I re-added the keyfile to the key slots of my two encrypted partitions by calling this: sudo cryptsetup luksAddKey /dev/nvme0n1p2 /crypto_keyfile.bin To my surprise when checking sudo cryptsetup luksDump /dev/nvme0n1p2 before and after adding of the keyfile, I found out that the new key slot data does not match any of the old slots. It looks like the keyfile was not added correctly to the slots before. Also I put the /crypto_keyfile.bin back into the /etc/crypttab (replacing the none's) but did not add back the keyscript=/bin/cat. I read in the man page of crypttab that the third parameter is the keyfile. I didn't see the need to add the keyscript at all. sudo update-initramfs -c -k all and reboot This can be done after booting the installed system as follows from an (initramfs) prompt https://discuss.kde.org/t/disk-encryption-not-working-on-recent-neon-isos-but-is-working-on-older-images/9505/4 - cryptsetup luksOpen /dev/disk/by-id/[deviceid] luks- and enter the password. Then run exec run-init /root /sbin/init /root/dev/console - -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477292] Request - Create Flatpak of Spectacle, also put on FlatHub
https://bugs.kde.org/show_bug.cgi?id=477292 Andreas changed: What|Removed |Added CC||opendr...@gmail.com --- Comment #2 from Andreas --- I also support, I use all possible KDE applications in Flatpak, since I use an LTS distribution. The only thing missing is Spectacle and Kate. For example, in Spectacle from the repositories I have a bug that is not in new versions of Spectacle and I have no way out because it is not in Flatpak https://bugs.kde.org/show_bug.cgi?id=469022 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #63 from Andreas --- But what should users of LTS distributions like Kubuntu or openSUSE Leap do? There is no version of Spectacle in the flatpak. Where is this fix so that it can be backported? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484662] New: Usability bug in Systemsettings Sound dialog
https://bugs.kde.org/show_bug.cgi?id=484662 Bug ID: 484662 Summary: Usability bug in Systemsettings Sound dialog Classification: Applications Product: systemsettings Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_pulseaudio Assignee: plasma-b...@kde.org Reporter: hoheneg...@web.de CC: m...@ratijas.tk Target Milestone: --- SUMMARY I may not be aware of all use cases, but the selection of the profile in the Sound dialog of the systemsettings app appears to be counter-intuitive. Based on tests of the interface and comparison to pavucontrol, the selection of a "Profile" determines which Input and Playback Devices etc. are active. Since the dropdownlist appears in general repeatedly, for each device or device type, placed behind the "Port" of the device, the global role of the function is not represented well in the GUI: Switching the profile will affect all devices. It appears that it would better appear only once and be placed above the listing of the device types. Also, "Input Devices" may better correspond to the user's expectation than "Recording Devices". STEPS TO REPRODUCE 1. Start systemsettings. 2. Go to "Input & Output" -> "Sound" 3. Observe the GUI -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 484929] New: Okular crashes when changing annotations
https://bugs.kde.org/show_bug.cgi?id=484929 Bug ID: 484929 Summary: Okular crashes when changing annotations Classification: Applications Product: okular Version: 24.02.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: hoheneg...@web.de Target Milestone: --- Application: okular (24.02.1) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.5.0-10027-tuxedo x86_64 Windowing System: Wayland Distribution: KDE neon 6.0 DrKonqi: 6.0.3 [KCrashBackend] -- Information about the crash: With all PDFs I have tried so far okular crashes when I modify annotations since upgrade to current plasma, frameworks and apps. I also switched from Xorg to Wayland recently. The behaviour can be triggered by adding a note (Pop-up or Inline) and deleting it again by selecting that option from the right-click menu. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139534905563840) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139534905563840) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139534905563840, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7ee804042476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7ee8040287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7ee804cdb597 in qAbort () at ./src/corelib/global/qglobal.cpp:161 #10 0x7ee804cd67f5 in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2003 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7ffc4d4c1340) at ./src/corelib/global/qlogging.cpp:378 #12 0x7ee804cdbfc3 in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:901 #13 0x7ee804ca0387 in qt_assert_x (where=, what=what@entry=0x7ee7e43dae98 "Called object is not of the correct type (class destructor may have already run)", file=file@entry=0x7ee7e43dae58 "/usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h", line=line@entry=129) at ./src/corelib/global/qassert.cpp:77 #14 0x7ee7e43069cd in QtPrivate::assertObjectType (o=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:129 #15 0x7ee7e4306c86 in QtPrivate::assertObjectType (o=0x591570f151e0) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:526 #16 QtPrivate::FunctorCall, QtPrivate::List<>, void, void (AnnotWindow::*)()>::call(void (AnnotWindow::*)(), AnnotWindow*, void**) (arg=, o=0x591570f151e0, f=(void (AnnotWindow::*)(AnnotWindow * const)) 0x7ee7e4308c50 ) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:144 #17 QtPrivate::FunctionPointer::call, void>(void (AnnotWindow::*)(), AnnotWindow*, void**) (arg=, o=0x591570f151e0, f=(void (AnnotWindow::*)(AnnotWindow * const)) 0x7ee7e4308c50 ) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:182 #18 QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=, this_=, r=0x591570f151e0, a=, ret=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:520 #19 0x7ee804c3c3ce in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #20 doActivate (sender=0x591571519e60, signal_index=7, argv=0x7ffc4d4c1508) at ./src/corelib/kernel/qobject.cpp:4039 #21 0x7ee804c3c6ab in doActivate (sender=0x59157152fb30, signal_index=3, argv=0x7ffc4d4c15d8) at ./src/corelib/kernel/qobject.cpp:4051 #22 0x7ee805c13c28 in QWidgetTextControl::qt_metacall (this=0x59157152fb30, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffc4d4c16d8) at ./obj-x86_64-linux-gnu/src/widgets/Widgets_autogen/include/moc_qwidgettextcontrol_p.cpp:741 #23 0x7ee804c3c4b8 in doActivate (sender=0x59157152fd10, signal_index=4, argv=0x7ffc4d4c16d8) at ./src/corelib/kernel/qobject.cpp:4065 #24 0x7ee80534ab3c in QTextDocumentPrivate::finishEdit (this=0x591571390f40) at ./src/gui/text/qtextdocument_p.cpp:1218 #25 0x7ee805329961 in QSyntaxHighlighter::setDocument (this=this@entry=0x5915715981e0, doc=doc@entry=0x0) at ./src/gui/text/qsyntaxhighlighter.cpp:302 #26 0x7ee805329dbd in QSyntaxHighlighter::~QSyntaxHighlighter (this=, this=) at ./src/gui/text/qsyntaxhighlighter.cpp:284 #27 0x7ee7e4463d5d in Sonnet::Highlighter::~Highlighter (this=, this=) at ./src/ui/highlighter.cpp:168 #28 0x7ee804bcb2ca in QObjectPrivate::deleteChildren (this=this@entry=0x591571598640) at ./src/corelib/kernel/qobject.cpp:2207 #29 0x7ee804bd2198 in QObject::~QObject (this=, this=) at ./src/corelib/kernel/qobject.cpp:115
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 Andreas changed: What|Removed |Added CC||opendr...@gmail.com --- Comment #58 from Andreas --- Operating System: openSUSE Leap 15.6 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.4.0-150600.12-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Xeon® E-2186M CPU @ 2.90GHz Graphics Processor: Mesa Intel® UHD Graphics P630 / Nvidia Quadro P3200 Product Name: Precision 7530 Spectacle: 23.08.5 I have the same issue, Spectacle GUI becomes transparent when selecting rectangular screenshot mode. The bug is present on Intel iGPU, if you disable composer, the problem disappears. Everything is also in order on Nvidia dGPU. Spectacle 24.02.1 on Plasma 6.0.3 and X11 does not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483631] New: Legacy VI-Mode config crashes kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=483631
Bug ID: 483631
Summary: Legacy VI-Mode config crashes kate and kwrite
Classification: Applications
Product: kate
Version: 24.02.0
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: hoheneg...@web.de
Target Milestone: ---
SUMMARY
Kate and kwrite fail to digest certain legacy configuration and crash during
startup.
STEPS TO REPRODUCE
1. Insert specific config in your $HOME/.config/katevirc :
[Kate Vi Input Mode Settings]
Command Mode Mapping Keys=
Command Mode Mappings=
Command Mode Mappings Recursion=
Insert Mode Mapping Keys=
Insert Mode Mappings=
Insert Mode Mappings Recursion=
Macro Completions=
Macro Contents=
Macro Registers=
Map Leader=,
Normal Mode Mapping Keys=,,vw
Normal Mode Mappings="+gP,"+gP,vb
Normal Mode Mappings Recursion=false,false,false
ViRegisterContents=inconclusive,\t\t\t\t\t\n\t\t\t\t\t\tIn contrast to
previous evaluation\\, the evaluator determined that no additional
packages that be acquired this time. The distribution DVDs are in fact
self-contained. \n\t\t\t\t\t\t\n\t\t\t\t\t\n,\n
The extended components definition in ASE_ECD.\n
\n \n \n
\n The remaining\\, non-mandatory parts of the ST.\n
\n \n \n
ViRegisterFlags=0,1,0
ViRegisterNames=-,0,^
Visual Mode Mapping Keys=,,,
Visual Mode Mappings="+y,"+x,"+x,"+y
Visual Mode Mappings Recursion=false,false,false,false
2. Run kate or kwrite
3. Observe the crash
OBSERVED RESULT
The application crashes during startup.
Output of "strace kwrite" is:
readlink("/home", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid argument)
readlink("~", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid argument)
readlink("~/.config", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid argument)
readlink("~/.config/katevirc", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid
argument)
openat(AT_FDCWD, "/home/andreas/.config/katevirc", O_RDONLY|O_CLOEXEC) = 19
statx(19, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0600,
stx_size=1666, ...}) = 0
statx(19, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0600,
stx_size=1666, ...}) = 0
statx(19, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0600,
stx_size=1666, ...}) = 0
read(19, "[Kate Vi Input Mode Settings]\nCo"..., 16384) = 1666
read(19, "", 14718) = 0
close(19) = 0
openat(AT_FDCWD, "/dev/tty", O_RDONLY|O_CLOEXEC) = 19
close(19) = 0
write(2, "ASSERT: \"rc <= 0x\" in file /"..., 89ASSERT: "rc <= 0x" in
file /usr/include/x86_64-linux-gnu/qt6/QtCore/qchar.h, line 79
) = 89
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
gettid()= 680280
getpid()= 680280
tgkill(680280, 680280, SIGABRT) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=680280, si_uid=1001}
---
+++ killed by SIGABRT +++
Aborted
I do not get offered a debug option, therefore, no complete debug logs
included.
EXPECTED RESULT
Kwrite and kate handle the apparently invalid config gracefully and startup
normally.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon user edition
KDE Plasma Version: 6.0.2
KDE Frameworks Version: Version 6.0.0
Qt Version: 6.6.2
ADDITIONAL INFORMATION
I upgraded from KDE Neon user edition where the config used to work.
It suffices to remove the line
Visual Mode Mapping Keys=,,,
from above config.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 483631] Legacy VI-Mode config crashes kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=483631 --- Comment #2 from Andreas --- As mentioned I do unfortunately not have a backtrace. How could I enforce its creation without compiling from sources? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483631] Legacy VI-Mode config crashes kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=483631 --- Comment #3 from Andreas --- Would that suffice (does not seem to provide a lot more info)? ~> gdb kwrite GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from kwrite... Reading symbols from /usr/lib/debug/.build-id/da/b5cd68711f7c03f634e7e3f0e426cf8808d3cb.debug... (gdb) run Starting program: /usr/bin/kwrite This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.neon.kde.org/: Enable debuginfod for this session? (y or [n]) y Debuginfod has been enabled. To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x703ff640 (LWP 3265322)] [New Thread 0x7fffeef5d640 (LWP 3265323)] [New Thread 0x7fffee75c640 (LWP 3265324)] [New Thread 0x7fffed952640 (LWP 3265543)] [New Thread 0x7fffed151640 (LWP 3265750)] [New Thread 0x7fffec950640 (LWP 3265751)] [New Thread 0x7fffd6dff640 (LWP 3265752)] [New Thread 0x7fffd65fe640 (LWP 3265753)] [New Thread 0x7fffd5dfd640 (LWP 3265754)] [New Thread 0x7fffd55fc640 (LWP 3265755)] [New Thread 0x7fffd4dfb640 (LWP 3265756)] [New Thread 0x7fffb7fff640 (LWP 3265757)] [New Thread 0x7fffb77fe640 (LWP 3265758)] [New Thread 0x7fffb6ffd640 (LWP 3265759)] [Thread 0x7fffb6ffd640 (LWP 3265759) exited] [Thread 0x7fffb77fe640 (LWP 3265758) exited] [Thread 0x7fffb7fff640 (LWP 3265757) exited] [Thread 0x7fffd4dfb640 (LWP 3265756) exited] ASSERT: "rc <= 0x" in file /usr/include/x86_64-linux-gnu/qt6/QtCore/qchar.h, line 79 Thread 1 "kwrite" received signal SIGABRT, Aborted. __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228689344) at ./nptl/pthread_kill.c:44 Download failed: Invalid argument. Continuing without source file ./nptl/./nptl/pthread_kill.c. 44 ./nptl/pthread_kill.c: No such file or directory. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 484013] New: When entering heise. into the URL field it is changed to seise. automatically on platform Mobian
https://bugs.kde.org/show_bug.cgi?id=484013 Bug ID: 484013 Summary: When entering heise. into the URL field it is changed to seise. automatically on platform Mobian Classification: Applications Product: angelfish Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: andr...@immerfroehlich.de Target Milestone: --- SUMMARY When entering heise. into the URL field it is changed to seise. automatically on platform Mobian STEPS TO REPRODUCE 1. Open angelfish. 2. Click on the URL field at the bottom of the page. 3. Enter "heise." OBSERVED RESULT The text is automatically changed to "seise." EXPECTED RESULT The text should not be changed automatically. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mobian (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION No additional information given. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407048] Online Accounts, Connections and Settings shoudn't share the same icon
https://bugs.kde.org/show_bug.cgi?id=407048 andreas changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||72ee0c027061737d96ebc49d6ba ||3767ac763935e Status|ASSIGNED|RESOLVED --- Comment #3 from andreas --- Git commit 72ee0c027061737d96ebc49d6ba3767ac763935e by Andreas Kainz. Committed on 17/11/2021 at 23:22. Pushed by andreask into branch 'master'. A +1-0icons/preferences/22/preferences-online-accounts.svg A +1-0icons/preferences/32/preferences-online-accounts.svg https://invent.kde.org/frameworks/breeze-icons/commit/72ee0c027061737d96ebc49d6ba3767ac763935e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443355] Incorrect DPI settings on KDE Plasma when switched GPU
https://bugs.kde.org/show_bug.cgi?id=443355 --- Comment #9 from Andreas --- (In reply to Andreas from comment #6) > Temporary solution > > I created a script > ~/.config/plasma-workspace/env/nvdpi.sh > > and wrote in it > export QT_SCREEN_SCALE_FACTORS=$QT_SCREEN_SCALE_FACTORS"eDP-1-1=2.25" > > eDP-1-1 <- xandr output on NVIDIA > 2.25 <- 225% scaling This solution does not work with dual monitors. So I changed the script ~ / .config / plasma-workspace / env / nvdpi.sh QT_SCREEN_SCALE_FACTORS = "2.25; 2.25" This works on two monitors. Scaling problem when switching GPU only with QT applications, maybe there is a way to fix it? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 437999] VeraCrypt icon
https://bugs.kde.org/show_bug.cgi?id=437999 andreas changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||f365232fc1682a6b8793fabcfc1 ||f8dda97f8a694 Resolution|UPSTREAM|FIXED --- Comment #2 from andreas --- Git commit f365232fc1682a6b8793fabcfc1f8dda97f8a694 by Andreas Kainz. Committed on 23/11/2021 at 22:34. Pushed by andreask into branch 'master'. A +1-0icons/apps/48/veracrypt.svg https://invent.kde.org/frameworks/breeze-icons/commit/f365232fc1682a6b8793fabcfc1f8dda97f8a694 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414213] [konsole] "Scrolling" preference icon
https://bugs.kde.org/show_bug.cgi?id=414213 andreas changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||b6bea1e8c3d24318c8d69ae7893 ||9d54515eb Resolution|--- |FIXED --- Comment #4 from andreas --- Git commit b6bea1e8c3d24318c8d69ae78939d54515eb by Andreas Kainz. Committed on 23/11/2021 at 23:46. Pushed by andreask into branch 'master'. A +162 -0icons/preferences/32/preferences-scroll.svg https://invent.kde.org/frameworks/breeze-icons/commit/b6bea1e8c3d24318c8d69ae78939d54515eb -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414215] [konsole] "Profiles" preference icon
https://bugs.kde.org/show_bug.cgi?id=414215 andreas changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/konsole/commit/ba6abc ||982c43057b9cfb3574bc49d8765 ||e6b7466 Status|ASSIGNED|RESOLVED --- Comment #3 from andreas --- Git commit ba6abc982c43057b9cfb3574bc49d8765e6b7466 by Andreas Kainz. Committed on 23/11/2021 at 23:53. Pushed by andreask into branch 'icons'. Related: bug 414213, bug 414214 M +1-1src/widgets/EditProfileDialog.cpp https://invent.kde.org/utilities/konsole/commit/ba6abc982c43057b9cfb3574bc49d8765e6b7466 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414214] [konsole] "Tabs" and "Tab bar" preference icon(s)
https://bugs.kde.org/show_bug.cgi?id=414214 andreas changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/util ||ities/konsole/commit/ba6abc ||982c43057b9cfb3574bc49d8765 ||e6b7466 --- Comment #1 from andreas --- Git commit ba6abc982c43057b9cfb3574bc49d8765e6b7466 by Andreas Kainz. Committed on 23/11/2021 at 23:53. Pushed by andreask into branch 'icons'. Related: bug 414213, bug 414215 M +1-1src/widgets/EditProfileDialog.cpp https://invent.kde.org/utilities/konsole/commit/ba6abc982c43057b9cfb3574bc49d8765e6b7466 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414213] [konsole] "Scrolling" preference icon
https://bugs.kde.org/show_bug.cgi?id=414213 andreas changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/util |eworks/breeze-icons/commit/ |ities/konsole/commit/ba6abc |b6bea1e8c3d24318c8d69ae7893 |982c43057b9cfb3574bc49d8765 |9d54515eb |e6b7466 --- Comment #5 from andreas --- Git commit ba6abc982c43057b9cfb3574bc49d8765e6b7466 by Andreas Kainz. Committed on 23/11/2021 at 23:53. Pushed by andreask into branch 'icons'. Related: bug 414215, bug 414214 M +1-1src/widgets/EditProfileDialog.cpp https://invent.kde.org/utilities/konsole/commit/ba6abc982c43057b9cfb3574bc49d8765e6b7466 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414215] [konsole] "Profiles" preference icon
https://bugs.kde.org/show_bug.cgi?id=414215 andreas changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/fram |ities/konsole/commit/ba6abc |eworks/breeze-icons/commit/ |982c43057b9cfb3574bc49d8765 |c98c2e6dcdecc12b318cdb65029 |e6b7466 |aff4bf45c5a33 --- Comment #4 from andreas --- Git commit c98c2e6dcdecc12b318cdb65029aff4bf45c5a33 by Andreas Kainz. Committed on 23/11/2021 at 23:51. Pushed by andreask into branch 'master'. A +1-0icons/preferences/32/preferences-tabs.svg https://invent.kde.org/frameworks/breeze-icons/commit/c98c2e6dcdecc12b318cdb65029aff4bf45c5a33 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445494] Opening "Projects TODOs" causes crash
https://bugs.kde.org/show_bug.cgi?id=445494 Andreas changed: What|Removed |Added CC||opendr...@gmail.com --- Comment #5 from Andreas --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445494] Opening "Projects TODOs" causes crash
https://bugs.kde.org/show_bug.cgi?id=445494 --- Comment #6 from Andreas --- Kate 21.08.3 on openSUSE Tumbleweed 20211128. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452158] New: block comment should start with '# '
https://bugs.kde.org/show_bug.cgi?id=452158 Bug ID: 452158 Summary: block comment should start with '# ' Product: kate Version: 21.12.3 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: opendr...@gmail.com Target Milestone: --- Created attachment 147886 --> https://bugs.kde.org/attachment.cgi?id=147886&action=edit Block comment should start with '# ' (E265) SUMMARY When commenting code in Python with ctrl + d, there is no space between the # and the code. LSP shows the following error: Block comment should start with '# ' (E265) Python Recommendations https://peps.python.org/pep-0008/#block-comments Also, if the code is indented, then # is not placed at the beginning of the line and LSP also show an error. Unexpected indentation (comment) (E116) Python Recommendations https://peps.python.org/pep-0008/#indentation Is it possible to fix this? It is very inconvenient to fix it by hand every time. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220330 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.16.15-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452394] New: Kmail friert nach Start ein
https://bugs.kde.org/show_bug.cgi?id=452394 Bug ID: 452394 Summary: Kmail friert nach Start ein Product: kmail2 Version: 5.15.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: bugs@linuxmaker.cloud Target Milestone: --- SUMMARY Hello, yesterday I suddenly had the problem on two Debian systems (Bullseye), which are independent of each other, that Kmail no longer starts properly but freezes constantly and the Kmail process had to be terminated via kill. Running kmail from the console brings up this error message: STEPS TO REPRODUCE kmail Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed org.kde.pim.kmail: setFcc: collection invalid "" org.kde.kitinerary: Cannot find external extractor: "kitinerary-extractor" org.kde.kitinerary: Cannot find external extractor: "kitinerary-extractor" org.kde.kitinerary: Cannot find external extractor: "kitinerary-extractor" org.kde.kitinerary: Cannot find external extractor: "kitinerary-extractor" Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") OBSERVED RESULT Kmail window freezing and unusability. Possibly, however, an e-mail has come in that has thrown the e-mail program out of step. This may have happened due to an "unusual" character string, insufficient range checking for Unicode characters, etc. Unfortunately, this can no longer be traced back. The fact is that everything was working normally yesterday morning and then suddenly from 9 am this problem appeared after reading mails earlier in the morning. INTERIMS RESULT A move from mv ~/.local/share/kmail2 ~/.local/share/kmail2.bak on both machines has ended the spit for now. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux 11 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION No software installation or system upgrades between last functioning and failure occurrence. The client is currently working again with the above solution. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452394] Kmail freezes after launch
https://bugs.kde.org/show_bug.cgi?id=452394 Andreas changed: What|Removed |Added Summary|Kmail friert nach Start ein |Kmail freezes after launch -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452687] New: Space between panel and application in full screen mode
https://bugs.kde.org/show_bug.cgi?id=452687 Bug ID: 452687 Summary: Space between panel and application in full screen mode Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: opendr...@gmail.com Target Milestone: 1.0 Created attachment 148195 --> https://bugs.kde.org/attachment.cgi?id=148195&action=edit Space between panel and application SUMMARY With the release of Plasma 5.24, a space has appeared between the panel and applications, where you can see the desktop wallpaper. STEPS TO REPRODUCE 1. Open KDE Setting in full screen mode OBSERVED RESULT You can see a long line with desktop wallpaper between the panel and the application. EXPECTED RESULT This space between the panel and the application should not be. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.16-default (64-bit) Graphics Platform: X11 Same in openSUSE Tumbleweed with KDE Frameworks 5.92 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452687] Space between panel and application in full screen mode
https://bugs.kde.org/show_bug.cgi?id=452687 --- Comment #1 from Andreas --- I have a UHD display, some users write that they do not see a issue on a FHD display. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 452688] New: At autostart, the Kontact window opens with an offset
https://bugs.kde.org/show_bug.cgi?id=452688 Bug ID: 452688 Summary: At autostart, the Kontact window opens with an offset Product: kontact Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: opendr...@gmail.com Target Milestone: --- Created attachment 148196 --> https://bugs.kde.org/attachment.cgi?id=148196&action=edit Kontact SUMMARY When autostarting or when restoring a previous session, the Kontact window opens with an offset for the first time. After minimizing Kontact to tray, the next time the window opens correctly. STEPS TO REPRODUCE 1. Add Kontact to autorun with --iconify parameter 2. Reboot the system 3. Open Kontact in full screen OBSERVED RESULT The Kontact window will open with a shift down, see screenshot. EXPECTED RESULT The Kontact window should open correctly. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.16-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION UHD Display with 225% scaling -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 452688] At autostart, the Kontact window opens with an offset
https://bugs.kde.org/show_bug.cgi?id=452688 --- Comment #1 from Andreas --- I was told that this problem occurs because the application starts up faster than the panel. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451076] New: Confirming search in VI-Input mode in insert mode creates a spurious linebreak before search result
https://bugs.kde.org/show_bug.cgi?id=451076
Bug ID: 451076
Summary: Confirming search in VI-Input mode in insert mode
creates a spurious linebreak before search result
Product: kate
Version: 21.12.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Vi Input Mode
Assignee: kwrite-bugs-n...@kde.org
Reporter: hoheneg...@web.de
Target Milestone: ---
SUMMARY
When confirming search in VI-Input mode with Enter a spurious linebreak is
inserted before the search result.
That happens
STEPS TO REPRODUCE
1. Enable VI-Input mode (with or without kate shortcuts overriding vim .
2. Put the editor in insert mode ("i") and type some text.
3. Perform a search for entered text selecting "Find" from the menu (not with
"/" since you are still in input mode).
4. Confirm with enter to return to the editor window.
OBSERVED RESULT
Cursor is in editor window after a new linebreak. The search result follows.
EXPECTED RESULT
Cursor is in editor window in front of search result, but no new linebreak has
been created.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon.
ADDITIONAL INFORMATION
None.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 451389] New: Specific key combination for backward word selection not mapped
https://bugs.kde.org/show_bug.cgi?id=451389 Bug ID: 451389 Summary: Specific key combination for backward word selection not mapped Product: kate Version: 21.12.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Vi Input Mode Assignee: kwrite-bugs-n...@kde.org Reporter: hoheneg...@web.de Target Milestone: --- SUMMARY Specific key combination for backward word selection "aw" (a variation of "aw" that works in vim) is not mapped in visual mode. It should be doing the same as "iw". Not sure if there are similar ones. Workaround is to add that mapping in the vi-mode settings. STEPS TO REPRODUCE 1. With kate in vi-input mode, enter visual mode with "v". 2. Type aw. OBSERVED RESULT Nothing. EXPECTED RESULT Previous word should be selected, just like with "iw". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
https://bugs.kde.org/show_bug.cgi?id=401400 Andreas changed: What|Removed |Added CC||hoheneg...@web.de --- Comment #13 from Andreas --- In fact "as" also behaves differently in kate and vim. Perhaps more with the "" modification. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
https://bugs.kde.org/show_bug.cgi?id=401400 --- Comment #14 from Andreas --- Sorry, my previous comment applies to another bug! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451389] Specific key combination for backward word selection not mapped
https://bugs.kde.org/show_bug.cgi?id=451389 --- Comment #1 from Andreas --- In fact "as" also behaves differently in kate and vim. Perhaps more with the "" modification. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 451696] New: Alt+O not working in kmail "Attachment Properties" dialog
https://bugs.kde.org/show_bug.cgi?id=451696 Bug ID: 451696 Summary: Alt+O not working in kmail "Attachment Properties" dialog Product: kmail2 Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: hoheneg...@web.de Target Milestone: --- SUMMARY The shortcut Alt+O for the "Ok" button in English language does not work properly. STEPS TO REPRODUCE 1. Create a new message with composer. 2. Add an attachment to the message. 3. Right click the attachment and choose properties. 4. Place the cursor in one of the text input fields of the "Attachment Properties" dialog. 5. Press the shortcut Alt+O. OBSERVED RESULT The character "o" appears at the cursor location in the text input field. EXPECTED RESULT The "Attachment Properties" dialog is closed and the specified settings are applied as with pressing "Ok" with the mouse. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User ADDITIONAL INFORMATION None. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 451696] Alt+O not working in kmail "Attachment Properties" dialog
https://bugs.kde.org/show_bug.cgi?id=451696 Andreas changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 436931] Update org.fedoraproject.AnacondaInstaller.svg
https://bugs.kde.org/show_bug.cgi?id=436931 andreas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||9e0544474083034eb7ea5520797 ||ac724ddd053ef --- Comment #1 from andreas --- Git commit 9e0544474083034eb7ea5520797ac724ddd053ef by Andreas Kainz. Committed on 26/10/2021 at 22:14. Pushed by andreask into branch 'master'. M +85 -24 icons/apps/48/org.fedoraproject.AnacondaInstaller.svg https://invent.kde.org/frameworks/breeze-icons/commit/9e0544474083034eb7ea5520797ac724ddd053ef -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 174203] Need mail-download-now and mail-download-later icons
https://bugs.kde.org/show_bug.cgi?id=174203 andreas changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||e4acd363fc504e158713c4aca86 ||9bd9595421e50 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from andreas --- Git commit e4acd363fc504e158713c4aca869bd9595421e50 by Andreas Kainz. Committed on 26/10/2021 at 22:25. Pushed by andreask into branch 'master'. A +1-0icons-dark/actions/16/mail-download-later.svg A +1-0icons-dark/actions/16/mail-download-now.svg A +1-0icons-dark/actions/22/mail-download-later.svg A +1-0icons-dark/actions/22/mail-download-now.svg A +1-0icons/actions/16/mail-download-later.svg A +1-0icons/actions/16/mail-download-now.svg A +1-0icons/actions/22/mail-download-later.svg A +1-0icons/actions/22/mail-download-now.svg https://invent.kde.org/frameworks/breeze-icons/commit/e4acd363fc504e158713c4aca869bd9595421e50 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 444548] Missing dark/light icon for GNOME todo
https://bugs.kde.org/show_bug.cgi?id=444548 --- Comment #1 from andreas --- If you could say the icon name, it would be great otherwise I will check. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443502] System tray settings does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=443502 --- Comment #2 from Andreas --- here is output QQmlEngine::setContextForObject(): Object already has a QQmlContext QQmlEngine::setContextForObject(): Object already has a QQmlContext kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling. file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationAppletPage.qml:38:5: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationAppletPage.qml:38:5: QML Loader: Binding loop detected for property "height" qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x8159cb0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x8159cb0) kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x8159cb0) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443355] Incorrect DPI settings on KDE Plasma when switched GPU
https://bugs.kde.org/show_bug.cgi?id=443355 Andreas changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443502] System tray settings does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=443502 Andreas changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443501] Blurred image on Wayland
https://bugs.kde.org/show_bug.cgi?id=443501 Andreas changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- --- Comment #4 from Andreas --- No, Plasma is blurry too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443501] Blurred image on Wayland
https://bugs.kde.org/show_bug.cgi?id=443501 --- Comment #6 from Andreas --- The bug is also present at a scale of 100 and 200%. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443501] Blurred image on Wayland
https://bugs.kde.org/show_bug.cgi?id=443501 --- Comment #8 from Andreas --- Hi, you're right. I took 2 screenshots in X11 and Wayland but couldn't see the difference. The bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443502] System tray settings does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=443502 --- Comment #4 from Andreas --- Meta + arrows keys helped. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444799] New: System tray icons size does not decrease
https://bugs.kde.org/show_bug.cgi?id=444799 Bug ID: 444799 Summary: System tray icons size does not decrease Product: plasmashell Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: opendr...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 143112 --> https://bugs.kde.org/attachment.cgi?id=143112&action=edit system tray setting at "small" SUMMARY In the system tray, if I set the size of the icons to small in the settings, then their size does not decrease, instead, the distance between the icons increases. STEPS TO REPRODUCE 1. Open system tray settings -> General 2. Switch from "scale to panel size" to "small" OBSERVED RESULT icons size does not decrease EXPECTED RESULT the size of the icons should be reduced SOFTWARE/OS VERSIONS Linux: OpenSUSE Tumbleweed KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444799] System tray icons size does not decrease
https://bugs.kde.org/show_bug.cgi?id=444799 Andreas changed: What|Removed |Added CC||opendr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443502] System tray settings does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=443502 Andreas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 445010] New: Network is offline after standby
https://bugs.kde.org/show_bug.cgi?id=445010 Bug ID: 445010 Summary: Network is offline after standby Product: plasma-pk-updates Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: opendr...@gmail.com Target Milestone: --- Created attachment 143234 --> https://bugs.kde.org/attachment.cgi?id=143234&action=edit Network is offline SUMMARY After standby, PackageKit says network is offline. But internet and zypper works without issues. nm-online shows that networkmanager is online. sometimes helps pkcon get-updates I think the update applet started before there was a network connection (WiFi). So it says that the network is offline (it was offline when it checked). STEPS TO REPRODUCE 1. Go to standby 2. Turn on the computer 3. Check for update by applet OBSERVED RESULT Network is offline EXPECTED RESULT It would be nice if the "check for updates" button did not disappear when there is no network or the "check connection" button appeared. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 445010] Network is offline after standby
https://bugs.kde.org/show_bug.cgi?id=445010 Andreas changed: What|Removed |Added CC||opendr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 429737] view-media-playlist icon could stand to be improved
https://bugs.kde.org/show_bug.cgi?id=429737 andreas changed: What|Removed |Added CC||kain...@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from andreas --- icon was updated see https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/159 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 405654] input-keyboard-virtual-on and input-keyboard-virtual-off icons are hard to differenciate
https://bugs.kde.org/show_bug.cgi?id=405654 andreas changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||8faf94f044c5859911dc5734c61 ||5d69c44711e68 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from andreas --- Git commit 8faf94f044c5859911dc5734c615d69c44711e68 by Andreas Kainz. Committed on 14/11/2021 at 20:50. Pushed by andreask into branch 'master'. M +13 -14 icons-dark/status/22/input-keyboard-virtual-off.svg M +14 -15 icons/status/22/input-keyboard-virtual-off.svg https://invent.kde.org/frameworks/breeze-icons/commit/8faf94f044c5859911dc5734c615d69c44711e68 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 372461] Missing RAR inscription in mime icons
https://bugs.kde.org/show_bug.cgi?id=372461 andreas changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit|http://commits.kde.org/oxyg |https://invent.kde.org/fram |en-icons/bfbc27488559dd0aa7 |eworks/breeze-icons/commit/ |c22e7528c0ccf9ea9f6094 |085de1b8b96fb7c03239c53cdc4 ||9c263f015 Resolution|--- |FIXED --- Comment #27 from andreas --- Git commit 085de1b8b96fb7c03239c53cdc49c263f015 by Andreas Kainz. Committed on 14/11/2021 at 21:09. Pushed by andreask into branch 'master'. M +1-1icons/mimetypes/16/application-vnd.rar.svg T +3-1icons/mimetypes/16/application-x-rar.svg M +1-1icons/mimetypes/22/application-vnd.rar.svg T +62 -1icons/mimetypes/22/application-x-rar.svg M +1-1icons/mimetypes/32/application-vnd.rar.svg T +21 -1icons/mimetypes/32/application-x-rar.svg M +1-1icons/mimetypes/64/application-vnd.rar.svg T +113 -1icons/mimetypes/64/application-x-rar.svg https://invent.kde.org/frameworks/breeze-icons/commit/085de1b8b96fb7c03239c53cdc49c263f015 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409022] Disk quota icon is semantically incorrect
https://bugs.kde.org/show_bug.cgi?id=409022 andreas changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||8936f14e15cff18171e73b8ffa6 ||9cce1b339db76 Status|ASSIGNED|RESOLVED --- Comment #10 from andreas --- Git commit 8936f14e15cff18171e73b8ffa69cce1b339db76 by Andreas Kainz. Committed on 14/11/2021 at 21:31. Pushed by andreask into branch 'master'. M +20 -13 icons-dark/status/22/disk-quota-critical.svg M +17 -9icons-dark/status/22/disk-quota-high.svg M +12 -6icons-dark/status/22/disk-quota-low.svg M +14 -8icons-dark/status/22/disk-quota.svg M +20 -13 icons/status/22/disk-quota-critical.svg M +17 -9icons/status/22/disk-quota-high.svg M +12 -6icons/status/22/disk-quota-low.svg M +14 -8icons/status/22/disk-quota.svg https://invent.kde.org/frameworks/breeze-icons/commit/8936f14e15cff18171e73b8ffa69cce1b339db76 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 372461] Missing RAR inscription in mime icons
https://bugs.kde.org/show_bug.cgi?id=372461 andreas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #30 from andreas --- It isn't plan to ad rar or any text to the icon. The icon is to know the file type the color to separate files when you have files with the same type in a folder and the filename show the extension. Breeze was always designed to don't have stuff that is available somewhere else and the file extension is available in the filename. So no rar name will be shown at the rar icon. As the rar icon use the same color than tar files I updated the color so that RAR files stand out. No additional change is planned. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443288] New: Custom folder icons
https://bugs.kde.org/show_bug.cgi?id=443288 Bug ID: 443288 Summary: Custom folder icons Product: Breeze Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: kain...@gmail.com CC: kain...@gmail.com Target Milestone: --- SUMMARY Should I add some specific folder icons like: https://github.com/CleoMenezes/Custom-Adwaita-Folder-Icons I could combine the icons with: https://store.kde.org/p/1160457/ so that you have a lot of specific folders and the colors come from the color scheme. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443288] Custom folder icons
https://bugs.kde.org/show_bug.cgi?id=443288 andreas changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443355] New: Incorrect DPI settings on KDE Plasma when switched GPU
https://bugs.kde.org/show_bug.cgi?id=443355 Bug ID: 443355 Summary: Incorrect DPI settings on KDE Plasma when switched GPU Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: xrandr Assignee: kwin-bugs-n...@kde.org Reporter: opendr...@gmail.com Target Milestone: --- Created attachment 142169 --> https://bugs.kde.org/attachment.cgi?id=142169&action=edit After switching to NVIDIA, Plasma shows 225% scaling, but this is 100% SUMMARY When I change graphics from Intel to NVIDIA or NVIDIA to Intel the scaling is reset to 100%, but the plasma displays the correct scaling of 225%. Same problem https://github.com/Askannz/optimus-manager/issues/208 Similar problem, but "solved" because display is not hidpi https://github.com/Askannz/optimus-manager/issues/67 I also have correct dpi 96 in xorg-nvidia.conf STEPS TO REPRODUCE 1. Set scale 225% on hidpi display 2. Switch GPU from Intel to NVIDIA 3. Switch scale to 200% and save 4. Switch scale back to 225%, save, logout and login. You will get the right scaling 5. Switch GPU from NVIDIA to Intel and you will get the wrong scaling again OBSERVED RESULT Scaling settings are not applied when changing GPU EXPECTED RESULT Scaling should be the same when changing GPUs SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04, KDE Neon, OpenSUSE LEap 15.3 with from Plasma 5.18.6 to 5.22.90 (available in About System) KDE Plasma Version: 5.18.5 to 5.22.90 ADDITIONAL INFORMATION Dell Precision 7530 with UHD Display, Intel UHD P630 + NVIDIA Quadro P3200 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443355] Incorrect DPI settings on KDE Plasma when switched GPU
https://bugs.kde.org/show_bug.cgi?id=443355 --- Comment #1 from Andreas --- Created attachment 142170 --> https://bugs.kde.org/attachment.cgi?id=142170&action=edit After switching to NVIDIA, Plasma shows 225% scaling, but this is 100% -- You are receiving this mail because: You are watching all bug changes.
