[digikam] [Bug 469740] SVG lable icons are not displayed anymore
https://bugs.kde.org/show_bug.cgi?id=469740 --- Comment #5 from Frédéric Virot --- Thanks a lot! Very fast answer & fix! Best Regards Fred -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469740] New: SVG lable icons are not displayed anymore
https://bugs.kde.org/show_bug.cgi?id=469740 Bug ID: 469740 Summary: SVG lable icons are not displayed anymore Classification: Applications Product: digikam Version: 8.0.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: frede...@virot.fr Target Milestone: --- Created attachment 158937 --> https://bugs.kde.org/attachment.cgi?id=158937=edit issue screen shot It is possible to to select an SVG file as the icon of an image tag. It has been so for quite a while. The Tags view used to display them correctly. It is not the case anymore. Instead of the actual chosen icon, a standard "no file" icon (?) is displayed. In my case, I get a monochrome "no parking sign" icon instead. STEPS TO REPRODUCE 1. Select an image in the album view 2. Select the "Captions" --> "Tags" view in the right pannel (it probably works alike in the left pannel) 3. If there is no existing tag, right-click and select "New tag". If a tag already exists, right-click on it and select "Properties" 4. In the dialog box that appear, click the button next to the "Icon: " text 5. In the "Select Icon" dialog, click the "Browse" button: 6. From the file selection modal dialog select any svg file and click "Open" 7. Confirm/Accept all open dialogs OBSERVED RESULT The chosen svg icon is not displayed as expected. EXPECTED RESULT The chosen svg icon is displayed as it was the case in earlier (6.x for sure, 7.x I do not know for sure). SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I only report this issue now, but it has been around for many a month now, maybe a year or slightly more. Before that issue occured, I used to favor SVG icons for my labels (I used them extensively) and it worked very well. It stopped to work somewhere in the 7.x series (not sure) . This issue does not seem to be linked to Ticket 422900. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396855] KDE System Configuration: Selecting SDDM in frequently used configuration modules resulted in a crash of systemsettings5
https://bugs.kde.org/show_bug.cgi?id=396855 Frédéric Virot changed: What|Removed |Added Summary|KDE System Configuration: |KDE System Configuration: |Selecting SDDM in |Selecting SDDM in |frequently used |frequently used |configuration modules |configuration modules ||resulted in a crash of ||systemsettings5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396855] New: KDE System Configuration: Selecting SDDM in frequently used configuration modules
https://bugs.kde.org/show_bug.cgi?id=396855 Bug ID: 396855 Summary: KDE System Configuration: Selecting SDDM in frequently used configuration modules Product: systemsettings Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: frede...@virot.fr Target Milestone: --- Application: systemsettings5 (5.13.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.9-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I opened the systemsettings5 application from the "K" menu. Then I selected "Login Screen (SDDM)" from the "Frequently used:" pane. And the application immediately crashed. I restarted right after and could do exactly the same thing without crash. Multiple times. This behaviour occured on a freshly installed ArchLinux system, right after the machine was rebooted followng a software update in which the kernel was updated. output of uname -a after crash: Linux lerins 4.17.9-1-ARCH #1 SMP PREEMPT Sun Jul 22 20:23:36 UTC 2018 x86_64 GNU/Linux The machine had been updated on a daily basis before this issue occured and rebooted right after the kernel update. After the reboot, a regular user session was entered using KDE as DM and systemsettings5 was among the first applications to be used. -- Backtrace: Application: Configuration du système (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f51cf7f4840 (LWP 1162))] Thread 9 (Thread 0x7f5181ce2700 (LWP 1174)): #0 0x7f51cae2fea9 in poll () at /usr/lib/libc.so.6 #1 0x7f51c40ae523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f51c40ae63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f51cb74c054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f51cb6f794c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f51cb540a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f51c92389c9 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f51cb54ab45 in () at /usr/lib/libQt5Core.so.5 #8 0x7f51c6713075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f51cae3a53f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f51909d8700 (LWP 1172)): #0 0x7f51cae2b934 in read () at /usr/lib/libc.so.6 #1 0x7f51c40f3ed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f51c40adff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f51c40ae4c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f51c40ae63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f51cb74c054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f51cb6f794c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f51cb540a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f51c92389c9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f51cb54ab45 in () at /usr/lib/libQt5Core.so.5 #10 0x7f51c6713075 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f51cae3a53f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f51913e8700 (LWP 1171)): #0 0x7f51cae2b934 in read () at /usr/lib/libc.so.6 #1 0x7f51c40f3ed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f51c40adff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f51c40ae4c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f51c40ae8e2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7f5192368348 in () at /usr/lib/libgio-2.0.so.0 #6 0x7f51c40d6a2a in () at /usr/lib/libglib-2.0.so.0 #7 0x7f51c6713075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f51cae3a53f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f5191be9700 (LWP 1170)): #0 0x7f51cae2fea9 in poll () at /usr/lib/libc.so.6 #1 0x7f51c40ae523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f51c40ae63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f51c40ae692 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f51c40d6a2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f51c6713075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f51cae3a53f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f519a3c4700 (LWP 1169)): #0 0x7f51c40f52d9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f51c40ada55 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f51c40ae44e in () at /usr/lib/libglib-2.0.so.0 #3 0x7f51c40ae63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f51cb74c054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f51cb6f794c in
