from:"Timo"

https://bugs.kde.org/show_bug.cgi?id=449927

Bug ID: 449927
   Summary: kmail crashes on startup after crashing when switching
folders
   Product: kmail2
   Version: 5.19.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@twilken.net
  Target Milestone: ---

Created attachment 146528
  --> https://bugs.kde.org/attachment.cgi?id=146528&action=edit
kmail startup and debug log

SUMMARY
After looking at emails and switching folders a few times, when switching back
to an inbox, kontact crashes.

I'm not sure, but the crash may have happened when switching to a folder where
the first message was signed using an RSA4096 GPG key, of which I have the
public key stored in KGPG.

Subsequently trying to reopen kontact or kmail crashes with a segfault (see
attached log).


STEPS TO REPRODUCE
1. open kontact/kmail and switch folders a few times, possibly opening a
GPG-signed message
2. kontact/kmail crashes
3. try to reopen kmail
4. kmail keeps segfaulting

OBSERVED RESULT
kmail crashes upon startup, without showing a window. See attached log for
details.

EXPECTED RESULT
kmail starts normally.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel 5.16.8-arch1-1
(available in About System)
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 449891] kmail crashes on startup

https://bugs.kde.org/show_bug.cgi?id=449891

Timo Wilken  changed:

   What|Removed |Added

 CC||kdeb...@twilken.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 449898] "setFcc: collection invalid" after clicking on mail address in e-mail message body

https://bugs.kde.org/show_bug.cgi?id=449898

Timo Wilken  changed:

   What|Removed |Added

 CC||kdeb...@twilken.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 449826] Kmail crashes the moment an encrypted email is selected

https://bugs.kde.org/show_bug.cgi?id=449826

Timo Wilken  changed:

   What|Removed |Added

 CC||kdeb...@twilken.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] New: Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

Bug ID: 468421
   Summary: Discover doesn't show available firmware updates
offered by fwupd
Classification: Applications
   Product: Discover
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: fwupd Backend
  Assignee: plasma-b...@kde.org
  Reporter: timo.g...@gmail.com
CC: aleix...@kde.org, sharma.abhijeet2...@gmail.com
  Target Milestone: ---

SUMMARY
Discover doesn't show any firmware updates available by fwupd.

STEPS TO REPRODUCE
1. Build Discover with the fwupd backend
2. Launch Discover
3. See no updates

OBSERVED RESULT
No updates are being displayed.

EXPECTED RESULT
Available updates correctly being displayed and offered to upgrade.

SOFTWARE/OS VERSIONS
Operating System: Exherbo 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.0 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530

ADDITIONAL INFORMATION
1. Updates are displayed and correctly working via the fwupdmgr cli as well as
within gnome-firmware (43.0) - see additionally attached screenshots.

2. If manually typing "lenovo" in the search box the device is found however
not the update itself as it reports version 0.0.0.1 instead of the 0.0.4.6
firmware update version and the install button doesn't do anything - see
additionally attached screenshots.

3. Discover also reports a general error on launch that it can't be used to do
system upgrades as I've build it only with the fwupd backend (as packagekit
also doesn't support our package manager) however the screenshots I found at
https://pointieststick.com/2018/08/04/this-week-in-usability-productivity-part-30/
also offer the firmware updates labled under the "System Updates" so this error
message isn't quite correct - see additionally attached screenshots.

4. gnome-firmware displays all devices fwupd supports in general with a note
"No Releases Available" to indicate that there are no available updates - but
allows to see all devices supported by fwupd all the time and check their
firmware and other details which I would welcome to see in Discover (or any
other hardware kcm with fwupd support) as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #1 from Timo Gurr  ---
Created attachment 158031
  --> https://bugs.kde.org/attachment.cgi?id=158031&action=edit
discover_1.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #2 from Timo Gurr  ---
Created attachment 158032
  --> https://bugs.kde.org/attachment.cgi?id=158032&action=edit
discover_2.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #3 from Timo Gurr  ---
Created attachment 158033
  --> https://bugs.kde.org/attachment.cgi?id=158033&action=edit
discover_3.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #4 from Timo Gurr  ---
Created attachment 158034
  --> https://bugs.kde.org/attachment.cgi?id=158034&action=edit
discover_4.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #5 from Timo Gurr  ---
Created attachment 158035
  --> https://bugs.kde.org/attachment.cgi?id=158035&action=edit
discover_5.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #6 from Timo Gurr  ---
Created attachment 158036
  --> https://bugs.kde.org/attachment.cgi?id=158036&action=edit
discover_6.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #7 from Timo Gurr  ---
Created attachment 158037
  --> https://bugs.kde.org/attachment.cgi?id=158037&action=edit
discover_manual_01.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #8 from Timo Gurr  ---
Created attachment 158038
  --> https://bugs.kde.org/attachment.cgi?id=158038&action=edit
discover_manual_02.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #9 from Timo Gurr  ---
Created attachment 158039
  --> https://bugs.kde.org/attachment.cgi?id=158039&action=edit
gnome-firmware.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 468421] Discover doesn't show available firmware updates offered by fwupd

https://bugs.kde.org/show_bug.cgi?id=468421

--- Comment #10 from Timo Gurr  ---
$ fwupdmgr get-updates
WARNING: Dieses Paket wurde nicht validiert und könnte nicht richtig
funktionieren.
Geräte mit keinen verfügbaren Firmware-Aktualisierungen: 
 • 1100 MTFDDAK256TBN
 • SSD 860 PRO 256GB
 • System Firmware
 • UEFI dbx
FUJITSU ESPRIMO P757
│
└─ThinkPad Universal USB-C Dock:
  │   Gerätekennung:  8dc9c8149c459498fae30d32e98c8bfedf4390ab
  │   Zusammenfassung:Dock Management Controller Device
  │   Aktuelle Version:   0.0.0.1
  │   Anbieter:   Lenovo (USB:0x17EF)
  │   Installationsdauer: 1 Minute
  │   Seriennummer:   1S40AY0090EUZVR0H51B
  │   GUIDs:  959b1e72-280e-5453-a5eb-d9d5c7674211 ←
USB\VID_17EF&PID_30A9
  │   fa0b1b28-bca0-5577-a670-a7e507f03bda ←
USB\VID_17EF&PID_30A9&REV_3073
  │   Device Flags:   • Aktualisierbar
  │   • System benötigt externe Stromquelle
  │   • Unterstützt auf dem entfernten Server
  │   • Gerät führt Aktualisierungen in Etappen durch
  │   • Das Gerät kann sich nach Fehlern beim Aufspielen
wiederherstellen
  │   • Signierte Nutzdaten
  │ 
  └─ThinkPad Universal:
Neue Version: 0.0.4.6
Remote ID:lvfs
Release ID:   14565
Zusammenfassung:  ThinkPad Universal USB-C Dock Device Firmware
Lizenz:   Proprietär
Größe:1,0 MB
Erstellt: 2022-07-20
Dringlichkeit:Hoch
Anbieter: Lenovo
Dauer:1 Minute
Aktualisierungsmeldung:Updates will complete next time the dock USB
cable is unplugged.  The dock will be unavailable for approximately 1 minute.
Release Flags:• Vertrauenswürdige Metadaten
  • Ist Höherstufung
Beschreibung: 
Device Firmware Version 0.0.4.6

The Docking will LED blinking while deploying FW update.

New Feature support: - Support Universal Dock FW update.

$ fwupdmgr update
WARNING: Dieses Paket wurde nicht validiert und könnte nicht richtig
funktionieren.
Geräte mit keinen verfügbaren Firmware-Aktualisierungen: 
 • 1100 MTFDDAK256TBN
 • SSD 860 PRO 256GB
 • System Firmware
 • UEFI dbx
╔══╗
║ ThinkPad Universal USB-C Dock von 0.0.0.1 auf 0.0.4.6 aktualisieren?
║
╠══╣
║ Device Firmware Version 0.0.4.6 
║
║ 
║
║ The Docking will LED blinking while deploying FW update.
║
║ 
║
║ New Feature support: - Support Universal Dock FW update.
║
║ 
║
║ ThinkPad Universal USB-C Dock und alle angeschlossenen Geräte sind während  
║
║ der Aktualisierung möglicherweise nicht nutzbar.
║
╚══╝
Operation durchführen? [Y|n]: n
Request canceled

$ plasma-discover-update 
QCommandLineParser: option not defined: "feedback"
No updates available, exiting

$ plasma-discover --listbackends
Available backends:
 * fwupd-backend

$ plasma-discover-update --backends fwupd
QCommandLineParser: option not defined: "feedback"
No updates available, exiting

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 481952] Panels are hidden after minimizing Dolphin window

2024-03-02 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=481952

Timo Gurr  changed:

   What|Removed |Added

 CC||timo.g...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 481952] On X11, panels are hidden after minimizing Dolphin window

2024-03-10 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=481952

Timo Gurr  changed:

   What|Removed |Added

 CC|timo.g...@gmail.com |

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480379] New: Changing Address, Name Style, Paper Size or Phone Numbers in Region & Language system settings has no effect.

2024-01-26 Thread Timo Velten

https://bugs.kde.org/show_bug.cgi?id=480379

Bug ID: 480379
Summary: Changing Address, Name Style, Paper Size or Phone
Numbers in Region & Language system settings has no
effect.
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Startup process
Assignee: plasma-b...@kde.org
Reporter: timo.vel...@hotmail.de
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0

SUMMARY
Changing Address, Name Style, Paper Size or Phone Numbers in Region & Language
system settings has no effect.

STEPS TO REPRODUCE
1. Change Address, Name Style, Paper Size or Phone Numbers to some value (I
changed them to de_DE).
2. These values (LC_ADDRESS, LC_PAPER, LC_TELEPHONE, LC_MONETARY) are correctly
written into ~/.config/plasma-localerc
3. Logout and log back in

OBSERVED RESULT

Run the locale command to see that the corresponding environment variables
remain unchanged (and in fact, they are not set at all, and the values
displayed by locale are just their inherited values)

EXPECTED RESULT

The environment variables LC_ADDRESS, LC_PAPER, LC_TELEPHONE, LC_MONETARY
should be set to the values specified in ~/.config/plasma-localerc

SOFTWARE/OS VERSIONS
Fedora 39, KDE Plasma Version 5.27.10. I have also observed the same behavior
on KDE Neon last week.

ADDITIONAL INFORMATION

It seems to me that, for whatever reason, plasma only sets those LC_* variables
listed in
https://invent.kde.org/plasma/plasma-workspace/-/blob/7b7e70b2262285dbfc294cc6617f4c0787a61d5c/startkde/startplasma.cpp#L171.
As far as I can tell, this has been the case for a very long time, and
curiously was never changed, even when the options to change LC_ADDRESS, etc
where introduced (see
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1971). So, as
far as I can tell, these have never actually worked at all (?).

In any case, I propose removing the variable lcValues entirely, and to just add
all values of that config file section into the environment. If that is
unacceptable for some reason, I propose adding the missing LC_* values to the
list lcValues.

--
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480379] Changing Address, Name Style, Paper Size or Phone Numbers in Region & Language system settings has no effect.

2024-02-05 Thread Timo Velten

https://bugs.kde.org/show_bug.cgi?id=480379

Timo Velten  changed:

   What|Removed |Added

Version|master  |5.27.10

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 306352] 100% cpu usage when waking up from suspend or switching between x servers, might be caused by kglobalaccel

2022-06-21 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=306352

Timo Gurr  changed:

   What|Removed |Added

 CC||timo.g...@gmail.com

--- Comment #11 from Timo Gurr  ---
(In reply to Robin Bankhead from comment #10)
> I see the same issue with kglobalaccel-5.95.0 in plasma-desktop-5.25.0 on
> Gentoo, when launching the plasma session within TigerVNC server.
> kglobalaccel5 goes straight to 100% and has to be killed (after relaunching
> it behaves normally).
> 
> I do NOT have an ~/.Xmodmap file.

I'm also experiencing this problem *very* often lately and I also do not have
an ~/.Xmodmap file. Every time I login into my plasma session e.g. after a
reboot kglobalaccel goes rogue and consumes 100% CPU of one CPU core and has to
be killed manually. It also happens again after some time on normal desktop
usage, or when not being on the computer at all for a while and comming back I
often find kglobalaccel consuming 100% CPU again. Often I only realize this
because of fan noise as it doesn't negativly affect my desktop usage. I never
had this problem before and didn't change any configuration settings so I
suppose it came with upgrades. However I've also no clue on how to debug this.
It's certainly very annoying. Please let me know if there's any information I
could provide to help finding the root cause.

Operating System: Exherbo
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Kernel Version: 5.18.1 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 458033] New: Failure to build with XSIMD support

https://bugs.kde.org/show_bug.cgi?id=458033

Bug ID: 458033
   Summary: Failure to build with XSIMD support
   Product: krita
   Version: 5.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1.  Try to build with XSIMD

OBSERVED RESULT
Running into compile error (complete build log is attached as file).

[...]
-- Available architectures for xsimd: x86-64
-- Found xsimd: /usr/x86_64-pc-linux-gnu/lib64/cmake/xsimd/xsimdConfig.cmake
(found suitable version "8.1.0", minimum required is "8.1.0") 
[...]
[ 11%] Building CXX object
libs/pigment/CMakeFiles/kritapigment.dir/KoOptimizedCompositeOpFactoryPerArch_AVX.cpp.o
cd /var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/pigment &&
/usr/bin/x86_64-pc-linux-gnu-c++ -DBOOST_ALL_NO_LIB -DHAVE_X11
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS
-DQT_DISABLE_DEPRECATED_BEFORE=0x50900 -DQT_GUI_LIB -DQT_NO_DEBUG
-DQT_NO_SIGNALS_SLOTS_KEYWORDS -DQT_NO_URL_CAST_FROM_STRING -DQT_SQL_LIB
-DQT_STRICT_ITERATORS -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS
-DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB
-DTRANSLATION_DOMAIN=\"krita\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE
-Dkritapigment_EXPORTS -DXSIMD_IMPL=AVX
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/pigment
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/pigment/kritapigment_autogen/include
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/interfaces
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/resources
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/koplugin
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/koplugin
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/store
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/store
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/global
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/global
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/version
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/version
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/resources
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/resources
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/multiarch
-I/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/multiarch
-isystem /usr/x86_64-pc-linux-gnu/include/qt5 -isystem
/usr/x86_64-pc-linux-gnu/include/qt5/QtCore -isystem
/usr/x86_64-pc-linux-gnu/lib/qt5/mkspecs/linux-g++ -isystem
/usr/x86_64-pc-linux-gnu/include/qt5/QtConcurrent -isystem
/usr/x86_64-pc-linux-gnu/include/qt5/QtGui -isystem
/usr/x86_64-pc-linux-gnu/include/qt5/QtWidgets -isystem
/usr/x86_64-pc-linux-gnu/include/qt5/QtXml -isystem
/usr/x86_64-pc-linux-gnu/include/KF5/KI18n -isystem
/usr/x86_64-pc-linux-gnu/include/KF5 -isystem
/usr/x86_64-pc-linux-gnu/include/qt5/QtSql -isystem
/usr/x86_64-pc-linux-gnu/include/OpenEXR -isystem
/usr/x86_64-pc-linux-gnu/include/Imath -isystem
/usr/x86_64-pc-linux-gnu/include/KF5/KConfig -isystem
/usr/x86_64-pc-linux-gnu/include/KF5/KConfigCore -march=native -O2 -pipe
-DNDEBUG -DQT_NO_DEBUG -fno-operator-names -Wall -Wextra -Wcast-align
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self
-Wvla -Wdate-time -Wsuggest-override -Wlogical-op  -fext-numeric-literals
-fexceptions -fPIC -fvisibility=hidden -fvisibility-inlines-hidden
-Wno-suggest-override -Wextra -Wno-class-memaccess -fPIC -std=gnu++14  -Wabi
-fabi-version=0 -fabi-compat-version=0 -ffp-contract=fast -fPIC -mavx -MD -MT
libs/pigment/CMakeFiles/kritapigment.dir/KoOptimizedCompositeOpFactoryPerArch_AVX.cpp.o
-MF
CMakeFiles/kritapigment.dir/KoOptimizedCompositeOpFactoryPerArch_AVX.cpp.o.d -o
CMakeFiles/kritapigment.dir/KoOptimizedCompositeOpFactoryPerArch_AVX.cpp.o -c
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/build/libs/pigment/KoOptimizedCompositeOpFactoryPerArch_AVX.cpp
In file included from
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/global/KisHalfTraits.h:14,
 from
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/KoColorSpaceMaths.h:109,
 from
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoCompositeOpFunctions

[krita] [Bug 458033] Failure to build with XSIMD support

https://bugs.kde.org/show_bug.cgi?id=458033

--- Comment #1 from Timo Gurr  ---
Created attachment 151407
  --> https://bugs.kde.org/attachment.cgi?id=151407&action=edit
krita-5.1.0_build.log

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 458033] Failure to build with XSIMD support

https://bugs.kde.org/show_bug.cgi?id=458033

--- Comment #4 from Timo Gurr  ---
(In reply to amyspark from comment #2)
> Can you check what your compiler returns for the size of `unsigned int`?
Sorry I've no  idea how to do that.

> Alternatively, can you replace the definitions in
> libs\pigment\compositeops\KoStreamedMath.h as follows, and try building
> Krita again? Replace "int" and "unsigned int" for "int32_t" and "uint32_t"
> respectively, in`struct PixelWrapper` and `struct
> PixelWrapper`.

I'm attaching the patch I'm using as krita-5.1.0-xsimd.patch, maybe I did
something wrong, with it applied I get the following error:

/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:176:37:
error: no matching function for call to
'KoRgbaInterleavers<16>::deinterleave(const void*&,
xsimd::batch&, xsimd::batch&, xsimd::avx)'
  176 | return deinterleave(src, a, b, A{});
  |~^~~~
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:131:24:
note: candidate: 'template::value && (sizeof (T) == 4)),
int>::type , typename std::enable_if<(xsimd::batch::size ==
4), int>::type  > static void
KoRgbaInterleavers<16>::deinterleave(const void*, xsimd::batch&,
xsimd::batch&, xsimd::kernel::requires_arch)'
  131 | static inline void deinterleave(const void *src, batch &dst1,
batch &dst2, kernel::requires_arch)
  |^~~~
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:131:24:
note:   template argument deduction/substitution failed:
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:130:120:
error: no type named 'type' in 'struct std::enable_if'
  130 | template = 0, enable_sized_vector_t = 0>
  |
   ^
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:146:24:
note: candidate: 'template::type  > static void
KoRgbaInterleavers<16>::deinterleave(const void*, xsimd::batch&,
xsimd::batch&, xsimd::kernel::requires_arch)'
  146 | static inline void deinterleave(const void *src, batch &a,
batch &b, kernel::requires_arch)
  |^~~~
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:146:24:
note:   template argument deduction/substitution failed:
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:176:37:
note:   cannot convert 'xsimd::avx()' (type 'xsimd::avx') to type
'xsimd::kernel::requires_arch' {aka 'const xsimd::avx2&'}
  176 | return deinterleave(src, a, b, A{});
  |~^~~~
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:174:24:
note: candidate: 'template static void
KoRgbaInterleavers<16>::deinterleave(const void*, xsimd::batch&,
xsimd::batch&)'
  174 | static inline void deinterleave(const void *src, batch &a,
batch &b)
  |^~~~
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:174:24:
note:   template argument deduction/substitution failed:
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:176:37:
error: type/value mismatch at argument 1 in template parameter list for
'template static void
KoRgbaInterleavers<16>::deinterleave(const void*, xsimd::batch&,
xsimd::batch&)'
  176 | return deinterleave(src, a, b, A{});
  |~^~~~
/var/tmp/paludis/build/media-gfx-krita-5.1.0/work/krita-5.1.0/libs/pigment/compositeops/KoRgbaInterleavers.h:176:37:
note:   expected a type, got 'false'

In regards to what tomtomtomreportin...@gmail.com just posted I want to note
that we currently compile our xsimd package with xtl support disabled by
passing -DENABLE_XTL_COMPLEX:BOOL=FALSE since we didn't package
https://github.com/xtensor-stack/xtl yet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 458033] Failure to build with XSIMD support

https://bugs.kde.org/show_bug.cgi?id=458033

--- Comment #5 from Timo Gurr  ---
Created attachment 151414
  --> https://bugs.kde.org/attachment.cgi?id=151414&action=edit
krita-5.1.0-xsimd.patch

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 458033] Failure to build with XSIMD support

https://bugs.kde.org/show_bug.cgi?id=458033

--- Comment #8 from Timo Gurr  ---
(In reply to amyspark from comment #7)
> I'm afraid your compiler is definitely reporting the wrong size for 32-bit
> unsigned integers (not 4 bytes), hence the generic version won't be usable.
> There's nothing we can do on our end, you'll have to upgrade GCC or build
> Krita without SIMD acceleration.
> 
> For this reason, marking as NOT A BUG.

I haven't come across any issues with other packages and since we're a
source-based distribution and compile everything such fundamental issues should
become directly obvious.

Also our GCC version is pretty recent:

# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/x86_64-pc-linux-gnu/libexec/gcc/x86_64-pc-linux-gnu/11.3.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/paludis/build/sys-devel-gcc-11.3.0/work/gcc-11.3.0/configure
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --prefix=/usr/x86_64-pc-linux-gnu
--datarootdir=/usr/share --localstatedir=/var --sysconfdir=/etc
--disable-dependency-tracking --enable-fast-install --enable-serial-configure
--disable-bootstrap --disable-decimal-float --disable-install-libiberty
--disable-libada --disable-libatomic --disable-libcilkrts --disable-libffi
--disable-libgfortran --disable-libgo --disable-libgomp --disable-libitm
--disable-libobjc --disable-liboffloadmic --disable-libquadmath
--disable-libsanitizer --disable-libssp --disable-libstdcxx
--disable-libstdc++-v3 --disable-libvtv --disable-vtable-verify
--disable-multilib --disable-nls --disable-shared --enable-lto --enable-plugin
--enable-plugins --enable-threads --enable-languages=c,c++,fortran,objc,obj-c++
--with-sysroot=
--with-gxx-include-dir=/usr/x86_64-pc-linux-gnu/include/c++/11.3.0 --with-isl
--with-lib-path=/usr/x86_64-pc-linux-gnu/lib
--with-as=/usr/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/bin/as.binutils
--with-ld=/usr/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-ld
--with-system-zlib --with-glibc-version=2.11 --enable-linker-build-id
--with-multilib-list= --disable-libhsail-rt --disable-libphobos
--enable-default-pie --enable-analyzer --without-zstd
--program-transform='s,$,-11,' --enable-cet
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.3.0 (GCC)

and I've also just tried it on another system which was just recently upgraded
to GCC 12 and successfully recompiled every single package installed and can
reproduce the issue there as well.

# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/x86_64-pc-linux-gnu/libexec/gcc/x86_64-pc-linux-gnu/12.1.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/paludis/build/sys-devel-gcc-12.1.0/work/gcc-12.1.0/configure
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --prefix=/usr/x86_64-pc-linux-gnu
--datarootdir=/usr/share --localstatedir=/var --sysconfdir=/etc
--disable-dependency-tracking --enable-fast-install --enable-serial-configure
--disable-bootstrap --disable-decimal-float --disable-install-libiberty
--disable-libada --disable-libatomic --disable-libcilkrts --disable-libffi
--disable-libgfortran --disable-libgo --disable-libgomp --disable-libitm
--disable-libobjc --disable-liboffloadmic --disable-libquadmath
--disable-libsanitizer --disable-libssp --disable-libstdcxx
--disable-libstdc++-v3 --disable-libvtv --disable-vtable-verify
--disable-multilib --disable-nls --disable-shared --enable-lto --enable-plugin
--enable-plugins --enable-threads --enable-languages=c,c++,fortran,objc,obj-c++
--with-sysroot=
--with-gxx-include-dir=/usr/x86_64-pc-linux-gnu/include/c++/12.1.0
--without-isl --with-lib-path=/usr/x86_64-pc-linux-gnu/lib
--with-as=/usr/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/bin/as.binutils
--with-ld=/usr/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-ld
--with-system-zlib --with-glibc-version=2.11 --enable-linker-build-id
--with-multilib-list= --disable-pgo-build --disable-werror --disable-libphobos
--enable-default-pie --enable-analyzer --without-zstd
--program-transform='s,$,-12,' --enable-cet
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.1.0 (GCC)

Both systems are on glibc 2.36 and binutils 2.39 if that might be of any
relevance.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 458033] Failure to build with XSIMD support

2022-08-23 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=458033

--- Comment #10 from Timo Gurr  ---
(In reply to amyspark from comment #9)
> (In reply to Timo Gurr from comment #8)
> > I haven't come across any issues with other packages and since we're a
> > source-based distribution and compile everything such fundamental issues
> > should become directly obvious.
> > 
> > Also our GCC version is pretty recent:
> 
> The RGBA interleavers code that's causing the error checks for 256-bit wide
> vectors (AVX) of 32-bit integers. Your version of GCC is reporting `unsigned
> int` to not be 32-bit in size. I do not know what your distribution is
> doing, but the code is not designed for that circumstance.
> 
> FTR, I compile the code with Clang 14.0.6, GCC 12.1 (MSYS flavours CLANG64
> and UCRT64), and MSVC 17.4 Preview 1. All of them work correctly.

After further investigation and finding the actual problem I'd say this is
clearly an issue on your side regarding the CMake magic you've implemented
doing the wrong thing since if I compile with -march=x86-64 krita builds just
fine with vectorization/xsimd enabled, but it fails when trying to build with
-march=native on the very same machine with nothing else changed. That
shouldn't be the case and I don't consider this an issue with our compiler.
Probably you should be able to reproduce this when trying to compile with
-march=native as well, not sure what the CMake magic does in regards to
different hardware/processor features though and if that may also play a role
here.

For reference, working:
CHOST="x86_64-pc-linux-gnu"
x86_64_pc_linux_gnu_CFLAGS="-march=x86-64 -O2 -pipe"
x86_64_pc_linux_gnu_CXXFLAGS="-march=x86-64 -O2 -pipe"

Failing:
CHOST="x86_64-pc-linux-gnu"
x86_64_pc_linux_gnu_CFLAGS="-march=native -O2 -pipe"
x86_64_pc_linux_gnu_CXXFLAGS="-march=native -O2 -pipe"

/proc/cpuinfo of CPUs tested on:

vendor_id   : GenuineIntel
cpu family  : 6
model   : 94
model name  : Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
stepping: 3
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est
tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi
flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms
invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves
dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear
flush_l1d arch_capabilities

vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
stepping: 4
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm
constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid
tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe
popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm
3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp fsgsbase
tsc_adjust bmi1 avx2 smep bmi2 invpcid avx512f avx512dq rdseed adx smap
clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xsaves arat pku
ospke md_clear flush_l1d arch_capabilities

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 458033] Failure to build with XSIMD support

2022-08-23 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=458033

--- Comment #15 from Timo Gurr  ---
(In reply to amyspark from comment #14)
> If you can test build Krita with the MR above, it'd be great.

Appears to work for me with the changes from the MR.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 442071] New: kwrite/kate: strings in right click menu of the status bar are not localized

2021-09-06 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=442071

Bug ID: 442071
   Summary: kwrite/kate: strings in right click menu of the status
bar are not localized
   Product: kate
   Version: 21.08.1
  Platform: Exherbo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 141331
  --> https://bugs.kde.org/attachment.cgi?id=141331&action=edit
kwrite.png

SUMMARY
Strings in right click menu of the status bar are not localized.

STEPS TO REPRODUCE
1. open kwrite/kate
2. right click on the status bar

OBSERVED RESULT
See "Show line count" & "Show word count" instead of localized strings.

EXPECTED RESULT
See localized strings for "Show line count" & "Show word count".

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
$ locale
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 445276] New: krita segfaults on start after displaying the plash screen

2021-11-10 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=445276

Bug ID: 445276
   Summary: krita segfaults on start after displaying the plash
screen
   Product: krita
   Version: 4.4.8
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 143410
  --> https://bugs.kde.org/attachment.cgi?id=143410&action=edit
coredump.txt

SUMMARY
Krita crashes right on start just after displaying the splash screen.

STEPS TO REPRODUCE
1.  Compile Krita 4.4.8
2.  Try to run it

OBSERVED RESULT
Segfault

EXPECTED RESULT
No segfault

SOFTWARE/OS VERSIONS
Operating System: Exherbo
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2 (qtbase kde/5.15 branch fixes up to 5.15.2_p254)
Kernel Version: 5.15.1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530

ADDITIONAL INFORMATION
Used CMake options during build:

cmake -DCMAKE_COLOR_MAKEFILE:BOOL=TRUE -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE
-DCMAKE_BUILD_TYPE:STRING=None -DCMAKE_C_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_CXX_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_AR:PATH=x86_64-pc-linux-gnu-ar
-DCMAKE_RANLIB:PATH=x86_64-pc-linux-gnu-ranlib
-DCMAKE_NM:PATH=x86_64-pc-linux-gnu-nm
-DCMAKE_C_COMPILER:PATH=x86_64-pc-linux-gnu-cc
-DCMAKE_CXX_COMPILER:PATH=x86_64-pc-linux-gnu-c++
-DCMAKE_INSTALL_PREFIX:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM:STRING=NEVER
-DCMAKE_SYSTEM_PREFIX_PATH:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_DATAROOTDIR:PATH=/usr/share/
-DBUILD_COVERAGE:BOOL=FALSE -DBUILD_KRITA_QT_DESIGNER_PLUGINS:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_KSeExpr:BOOL=TRUE
-DCRASH_ON_SAFE_ASSERTS:BOOL=FALSE -DENABLE_CPU_THROTTLE:BOOL=FALSE
-DHAVE_BACKTRACE_SUPPORT:BOOL=FALSE -DHAVE_MEMORY_LEAK_TRACKER:BOOL=FALSE
-DHIDE_SAFE_ASSERTS:BOOL=TRUE -DKRITA_ENABLE_BROKEN_TESTS:BOOL=FALSE
-DLIMIT_LONG_TESTS:BOOL=TRUE -DSHARED_LIBS:BOOL=TRUE
-DUSE_LOCK_FREE_HASH_TABLE:BOOL=TRUE -DFOUNDATION_BUILD:BOOL=FALSE
-DENABLE_PYTHON_2:BOOL=FALSE -DKRITA_DEVS:BOOL=FALSE
-DBUILD_SHARED_LIBS:BOOL=TRUE -DKDE_INSTALL_AUTOSTARTDIR=/etc/xdg/autostart
-DKDE_INSTALL_CONFDIR=/etc/xdg -DKDE_INSTALL_DATAROOTDIR:PATH=/usr/share
-DKDE_INSTALL_LIBEXECDIR=libexec -DKDE_INSTALL_SYSCONFDIR=/etc
-DKDE_INSTALL_USE_QT_SYS_PATHS:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_FFTW3:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenColorIO:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_HEIF:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenJPEG:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenEXR:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_Poppler:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonInterp:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonLibrary:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_SIP:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_PyQt5:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_LibRaw:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_Qt5Multimedia:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_TIFF:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Vc:BOOL=TRUE -DBUILD_TESTING:BOOL=FALSE
/var/tmp/paludis/build/media-gfx-krita-4.4.8/work/krita-4.4.8

Attached you'll find, the hopefully useful, coredump.

Kcrash Handler Output Krita 4.4.8:
Application: krita (krita), signal: Segmentation fault
[KCrash Handler]
#4  0x7feeda679a98 in
KisVisualColorSelector::slotSetColorSpace(KoColorSpace const*) () from
/usr/x86_64-pc-linux-gnu/lib/libkritawidgets.so.20
#5  0x7feeda6777a0 in KisVisualColorSelector::slotSetColor(KoColor const&)
() from /usr/x86_64-pc-linux-gnu/lib/libkritawidgets.so.20
#6  0x7feeda680629 in
KisDlgInternalColorSelector::KisDlgInternalColorSelector(QWidget*, KoColor,
KisDlgInternalColorSelector::Config, QString const&,
KoColorDisplayRendererInterface const*) () from
/usr/x86_64-pc-linux-gnu/lib/libkritawidgets.so.20
#7  0x7feedd9d5376 in KoDualColorButton::Private::init(KoDualColorButton*)
() from /usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#8  0x7feedd9d778c in KoDualColorButton::KoDualColorButton(KoColor const&,
KoColor const&, KoColorDisplayRendererInterface const*, QWidget*, QWidget*) ()
from /usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#9  0x7feedd80a4d7 in KisControlFrame::setup(QWidget*) () from
/usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#10 0x7feeddaede39 in KisViewManager::KisViewManager(QWidget*,
KActionCollection*) () from /usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#11 0x7feeddabdaee in KisMainWindow::KisMainWindow(QUuid) () from
/usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#12 0x7feeddac9257 in KisPart::createMainWindow(QUuid) () from
/usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#13 0x7feeddac9bda in KisPart::startBla

[krita] [Bug 445276] krita segfaults on start after displaying the splash screen when a whole log of packages are disabled

2021-11-10 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=445276

--- Comment #2 from Timo Gurr  ---
(In reply to Halla Rempt from comment #1)
> It would be better to build without so many packages disabled... You're
> definitely going to run into trouble. I suspect that this patch will fix the
> issue, but I am not going to create a build like yours to test this out:
> 
> diff --git a/libs/widgets/KisVisualColorSelector.cpp
> b/libs/widgets/KisVisualColorSelector.cpp
> index 8cb62bc2fb..c2f5c5689d 100644
> --- a/libs/widgets/KisVisualColorSelector.cpp
> +++ b/libs/widgets/KisVisualColorSelector.cpp
> @@ -94,8 +94,9 @@ void KisVisualColorSelector::slotSetColorSpace(const
> KoColorSpace *cs)
>  const KoColorSpace *csNew = cs;
>  
>  // PQ color space is not very suitable for selecting colors,
> substitute with linear one
> -if (cs->colorModelId() == RGBAColorModelID &&
> -cs->profile()->uniqueId() ==
> KoColorSpaceRegistry::instance()->p2020PQProfile()->uniqueId()) {
> +if (cs->colorModelId() == RGBAColorModelID
> +&& KoColorSpaceRegistry::instance()->p2020PQProfile() &&
> +cs->profile()->uniqueId() ==
> KoColorSpaceRegistry::instance()->p2020PQProfile()->uniqueId()) {
>  
>  csNew = KoColorSpaceRegistry::instance()->
>  colorSpace(RGBAColorModelID.id(),
> Float32BitsColorDepthID.id(),
> 
> Please check whether this works.

Thanks for the immediate nearly instant help, you're awesome! Sorry that I
couldn't get back to you as fast as you came up with the patch, Krita takes a
while to compile on my machine(s). I can confirm that the patch you've provided
fixes the issue.

I disabled as much as I could for testing purposes, however as Exherbo is a
source-based distribution like Gentoo we offer a few options to enable/disable
optional features on compile-time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 445285] New: krita segfaults on start after displaying the splash screen when a whole log of packages are disabled - part2

2021-11-10 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=445285

Bug ID: 445285
   Summary: krita segfaults on start after displaying the splash
screen when a whole log of packages are disabled -
part2
   Product: krita
   Version: 4.4.8
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 143414
  --> https://bugs.kde.org/attachment.cgi?id=143414&action=edit
coredump.txt

SUMMARY
Krita crashes right on start just after displaying the splash screen.

Followup of https://bugs.kde.org/show_bug.cgi?id=445276 now with additional
enabled options OpenColorIO/OCIO, OpenEXR and Python I run into another
segfault.

STEPS TO REPRODUCE
1.  Compile Krita 4.4.8
2.  Try to run it

OBSERVED RESULT
Segfault

EXPECTED RESULT
No segfault

SOFTWARE/OS VERSIONS
Operating System: Exherbo
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2 (qtbase kde/5.15 branch fixes up to 5.15.2_p254)
Kernel Version: 5.15.1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530

ADDITIONAL INFORMATION
Used CMake options during build:

cmake -DCMAKE_COLOR_MAKEFILE:BOOL=TRUE -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE
-DCMAKE_BUILD_TYPE:STRING=None -DCMAKE_C_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_CXX_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_AR:PATH=x86_64-pc-linux-gnu-ar
-DCMAKE_RANLIB:PATH=x86_64-pc-linux-gnu-ranlib
-DCMAKE_NM:PATH=x86_64-pc-linux-gnu-nm
-DCMAKE_C_COMPILER:PATH=x86_64-pc-linux-gnu-cc
-DCMAKE_CXX_COMPILER:PATH=x86_64-pc-linux-gnu-c++
-DCMAKE_INSTALL_PREFIX:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM:STRING=NEVER
-DCMAKE_SYSTEM_PREFIX_PATH:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_DATAROOTDIR:PATH=/usr/share/
-DBUILD_COVERAGE:BOOL=FALSE -DBUILD_KRITA_QT_DESIGNER_PLUGINS:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_KSeExpr:BOOL=TRUE
-DCRASH_ON_SAFE_ASSERTS:BOOL=FALSE -DENABLE_CPU_THROTTLE:BOOL=FALSE
-DHAVE_BACKTRACE_SUPPORT:BOOL=FALSE -DHAVE_MEMORY_LEAK_TRACKER:BOOL=FALSE
-DHIDE_SAFE_ASSERTS:BOOL=TRUE -DKRITA_ENABLE_BROKEN_TESTS:BOOL=FALSE
-DLIMIT_LONG_TESTS:BOOL=TRUE -DSHARED_LIBS:BOOL=TRUE
-DUSE_LOCK_FREE_HASH_TABLE:BOOL=TRUE -DFOUNDATION_BUILD:BOOL=FALSE
-DENABLE_PYTHON_2:BOOL=FALSE -DKRITA_DEVS:BOOL=FALSE
-DBUILD_SHARED_LIBS:BOOL=TRUE -DKDE_INSTALL_AUTOSTARTDIR=/etc/xdg/autostart
-DKDE_INSTALL_CONFDIR=/etc/xdg -DKDE_INSTALL_DATAROOTDIR:PATH=/usr/share
-DKDE_INSTALL_LIBEXECDIR=libexec -DKDE_INSTALL_SYSCONFDIR=/etc
-DKDE_INSTALL_USE_QT_SYS_PATHS:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_FFTW3:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenColorIO:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_HEIF:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenJPEG:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenEXR:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Poppler:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonInterp:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonLibrary:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_SIP:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PyQt5:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_LibRaw:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_Qt5Multimedia:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_TIFF:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Vc:BOOL=TRUE -DBUILD_TESTING:BOOL=FALSE
/var/tmp/paludis/build/media-gfx-krita-4.4.8/work/krita-4.4.8

Attached you'll find, the hopefully useful, coredump.

Application: krita (krita), signal: Segmentation fault

Kcrash Handler Output Krita 4.4.8:
[KCrash Handler]
#4  0x7f5a0d3d7dd5 in KisSmallColorWidget::Private::generationColorSpace()
() from /usr/x86_64-pc-linux-gnu/lib/kritaplugins/kritasmallcolorselector.so
#5  0x7f5a0d3d4ed0 in void
KisSmallColorWidget::uploadPaletteData<(anonymous
namespace)::FillHPolicy>(KisGLImageWidget*, QSize const&) () from
/usr/x86_64-pc-linux-gnu/lib/kritaplugins/kritasmallcolorselector.so
#6  0x7f5a0d3d6699 in KisSmallColorWidget::KisSmallColorWidget(QWidget*) ()
from /usr/x86_64-pc-linux-gnu/lib/kritaplugins/kritasmallcolorselector.so
#7  0x7f5a0d3d4223 in SmallColorSelectorDock::SmallColorSelectorDock() ()
from /usr/x86_64-pc-linux-gnu/lib/kritaplugins/kritasmallcolorselector.so
#8  0x7f5a0d3d3821 in SmallColorSelectorDockFactory::createDockWidget() ()
from /usr/x86_64-pc-linux-gnu/lib/kritaplugins/kritasmallcolorselector.so
#9  0x7f5a25d54e8e in KisMainWindow::createDockWidget(KoDockFactoryBase*)
() from /usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#10 0x7f5a25d5dd7b in KisMainWindow::KisMainWindow(QUuid) () from
/usr/x86_64-pc-linux-gnu/lib/libkritaui.so.20
#11 0x7f5a25d68f37 in KisPart::createMainWindow(QUuid) () from
/usr/x86_64-pc-linux-gnu/

[krita] [Bug 445285] krita segfaults on start after displaying the splash screen when a whole log of packages are disabled - part2

https://bugs.kde.org/show_bug.cgi?id=445285

--- Comment #2 from Timo Gurr  ---
(In reply to Halla Rempt from comment #1)
> Please try this:
> 
> diff --git a/plugins/dockers/smallcolorselector/kis_small_color_widget.cc
> b/plugins/dockers/smallcolorselector/kis_small_color_widget.cc
> index 99106fa1c1..4b23367cb6 100644
> --- a/plugins/dockers/smallcolorselector/kis_small_color_widget.cc
> +++ b/plugins/dockers/smallcolorselector/kis_small_color_widget.cc
> @@ -72,8 +72,11 @@ struct KisSmallColorWidget::Private {
>  }
>  
>  // PQ color space we deliniearize into linear one
> -if (result && result->colorModelId() == RGBAColorModelID &&
> -result->profile()->uniqueId() ==
> KoColorSpaceRegistry::instance()->p2020PQProfile()->uniqueId()) {
> +if (result
> +&& result->colorModelId() == RGBAColorModelID
> +&& result->profile()
> +&& KoColorSpaceRegistry::instance()->p2020PQProfile()
> +&& result->profile()->uniqueId() ==
> KoColorSpaceRegistry::instance()->p2020PQProfile()->uniqueId()) {
>  
>  result = KoColorSpaceRegistry::instance()->
>  colorSpace(RGBAColorModelID.id(),
> Float32BitsColorDepthID.id(),
> 
> 
> Note that it's easier to figure out where a crash happens if you build with
> the DEBUG cmake build type.

I can confirm that the patch you've provided fixes the issue. Thank you very
much again and also for the hint about the build type, I'll make sure to
compile with Debug (or RelWithDebInfo) next time before I'll report an issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 445329] New: Krita crashes when closing the "Configure Krita" dialogue with the "X" close icon

https://bugs.kde.org/show_bug.cgi?id=445329

Bug ID: 445329
   Summary: Krita crashes when closing the "Configure Krita"
dialogue with the "X" close icon
   Product: krita
   Version: 4.4.8
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 143445
  --> https://bugs.kde.org/attachment.cgi?id=143445&action=edit
coredump.txt

SUMMARY
Krita crashes when closing the "Configure Krita" dialogue with the window
manager decoration "close/X" button instead of the "Cancel" button on the
buttom. The bug doesn't seem to apply to other dialogues closed in the same way
like for example "Open a document" or "configure toolbars" and so on.

STEPS TO REPRODUCE
1.  Compile Krita 4.4.8
2.  Run it
3.  Click "Settings" -> "Configure Krita"
4.  Close that windows via the "X" close button from the window manager
decoration bar next to minmize/maximize

OBSERVED RESULT
Segfault

EXPECTED RESULT
No segfault, behave like when clicking the "Close" button.

SOFTWARE/OS VERSIONS
Operating System: Exherbo
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2 (qtbase kde/5.15 branch fixes up to 5.15.2_p254)
Kernel Version: 5.15.1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530

ADDITIONAL INFORMATION
Used CMake options during build:

cmake -DCMAKE_COLOR_MAKEFILE:BOOL=TRUE -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE
-DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_C_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_CXX_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_AR:PATH=x86_64-pc-linux-gnu-ar
-DCMAKE_RANLIB:PATH=x86_64-pc-linux-gnu-ranlib
-DCMAKE_NM:PATH=x86_64-pc-linux-gnu-nm
-DCMAKE_C_COMPILER:PATH=x86_64-pc-linux-gnu-cc
-DCMAKE_CXX_COMPILER:PATH=x86_64-pc-linux-gnu-c++
-DCMAKE_INSTALL_PREFIX:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM:STRING=NEVER
-DCMAKE_SYSTEM_PREFIX_PATH:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_DATAROOTDIR:PATH=/usr/share/
-DBUILD_COVERAGE:BOOL=FALSE -DBUILD_KRITA_QT_DESIGNER_PLUGINS:BOOL=FALSE
-DBUILD_SHARED_LIBS:BOOL=TRUE -DCMAKE_DISABLE_FIND_PACKAGE_KSeExpr:BOOL=TRUE
-DCRASH_ON_SAFE_ASSERTS:BOOL=FALSE -DENABLE_CPU_THROTTLE:BOOL=FALSE
-DHAVE_BACKTRACE_SUPPORT:BOOL=FALSE -DHAVE_MEMORY_LEAK_TRACKER:BOOL=FALSE
-DHIDE_SAFE_ASSERTS:BOOL=TRUE -DKRITA_ENABLE_BROKEN_TESTS:BOOL=FALSE
-DLIMIT_LONG_TESTS:BOOL=TRUE -DUSE_LOCK_FREE_HASH_TABLE:BOOL=TRUE
-DFOUNDATION_BUILD:BOOL=FALSE -DENABLE_PYTHON_2:BOOL=FALSE
-DKRITA_DEVS:BOOL=FALSE -DBUILD_SHARED_LIBS:BOOL=TRUE
-DKDE_INSTALL_AUTOSTARTDIR=/etc/xdg/autostart -DKDE_INSTALL_CONFDIR=/etc/xdg
-DKDE_INSTALL_DATAROOTDIR:PATH=/usr/share -DKDE_INSTALL_LIBEXECDIR=libexec
-DKDE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_FFTW3:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenColorIO:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_HEIF:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenJPEG:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenEXR:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Poppler:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonInterp:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonLibrary:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_SIP:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PyQt5:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_LibRaw:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Qt5Multimedia:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_TIFF:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Vc:BOOL=TRUE -DBUILD_TESTING:BOOL=FALSE
/var/tmp/paludis/build/media-gfx-krita-4.4.8/work/krita-4.4.8

Attached you'll find, the hopefully useful, coredump.

Application: Krita (krita), signal: Segmentation fault

[KCrash Handler]
#4  0x7f9ab64023a2 in KisImageConfig::setDefaultProofingConfig
(this=this@entry=0x7c198f00, proofingSpace=0x0,
proofingIntent=proofingIntent@entry=3,
blackPointCompensation=blackPointCompensation@entry=true, warningColor=...,
adaptationState=4.6656091129964288e-310, adaptationState@entry=1) at
/var/tmp/paludis/build/media-gfx-krita-4.4.8/work/krita-4.4.8/libs/image/kis_image_config.cpp:512
#5  0x7f9ab72ad323 in KisDlgPreferences::editPreferences
(this=this@entry=0x7f9aa80087d0) at
/var/tmp/paludis/build/media-gfx-krita-4.4.8/work/krita-4.4.8/libs/ui/dialogs/kis_dlg_preferences.cc:1785
#6  0x7f9ab76799f6 in KisMainWindow::slotPreferences (this=0x55e2ec893370)
at
/var/tmp/paludis/build/media-gfx-krita-4.4.8/work/krita-4.4.8/libs/ui/KisMainWindow.cpp:750
#7  0x7f9ab4e9b51d in void doActivate(QObject*, int, void**) () from
/usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#8  0x7f9ab5947a12 in QAction::triggered(bool) () from
/usr/x86_64-pc-linux-gn

[krita] [Bug 445348] New: krita segfaults on start after displaying the splash screen when a whole log of packages are disabled - part3

https://bugs.kde.org/show_bug.cgi?id=445348

Bug ID: 445348
   Summary: krita segfaults on start after displaying the splash
screen when a whole log of packages are disabled -
part3
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 143460
  --> https://bugs.kde.org/attachment.cgi?id=143460&action=edit
coredump.txt

Git master: 382d300c788a3ba68e6bdf3a75fe5ccb5c3454f5

SUMMARY
Krita crashes right on start just after displaying the splash screen. While
4.4.8 works fine with the patches from

https://bugs.kde.org/show_bug.cgi?id=445276
https://bugs.kde.org/show_bug.cgi?id=445285

I experience another segfault on startup with latest git master. Most but not
all of the optional packages are enabled.

STEPS TO REPRODUCE
1.  Compile Krita Git master: 382d300c788a3ba68e6bdf3a75fe5ccb5c3454f5
2.  Try to run it

OBSERVED RESULT
Segfault

EXPECTED RESULT
No segfault

SOFTWARE/OS VERSIONS
Operating System: Exherbo
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2 (qtbase kde/5.15 branch fixes up to 5.15.2_p254)
Kernel Version: 5.15.1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530

ADDITIONAL INFORMATION
Used CMake options during build:

cmake -DCMAKE_COLOR_MAKEFILE:BOOL=TRUE -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE
-DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_C_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_CXX_FLAGS:STRING=-march=native -O2 -pipe
-DCMAKE_AR:PATH=x86_64-pc-linux-gnu-ar
-DCMAKE_RANLIB:PATH=x86_64-pc-linux-gnu-ranlib
-DCMAKE_NM:PATH=x86_64-pc-linux-gnu-nm
-DCMAKE_C_COMPILER:PATH=x86_64-pc-linux-gnu-cc
-DCMAKE_CXX_COMPILER:PATH=x86_64-pc-linux-gnu-c++
-DCMAKE_INSTALL_PREFIX:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM:STRING=NEVER
-DCMAKE_SYSTEM_PREFIX_PATH:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_DATAROOTDIR:PATH=/usr/share/
-DBUILD_COVERAGE:BOOL=FALSE -DBUILD_KRITA_QT_DESIGNER_PLUGINS:BOOL=FALSE
-DBUILD_SHARED_LIBS:BOOL=TRUE -DCMAKE_DISABLE_FIND_PACKAGE_KSeExpr:BOOL=TRUE
-DCRASH_ON_SAFE_ASSERTS:BOOL=FALSE -DENABLE_CPU_THROTTLE:BOOL=FALSE
-DHAVE_BACKTRACE_SUPPORT:BOOL=FALSE -DHAVE_MEMORY_LEAK_TRACKER:BOOL=FALSE
-DHIDE_SAFE_ASSERTS:BOOL=TRUE -DKRITA_ENABLE_BROKEN_TESTS:BOOL=FALSE
-DLIMIT_LONG_TESTS:BOOL=TRUE -DUSE_LOCK_FREE_HASH_TABLE:BOOL=TRUE
-DFOUNDATION_BUILD:BOOL=FALSE -DENABLE_PYTHON_2:BOOL=FALSE
-DKRITA_DEVS:BOOL=FALSE -DCMAKE_DISABLE_FIND_PACKAGE_LibMyPaint:BOOL=TRUE
-DENABLE_BSYMBOLICFUNCTIONS:BOOL=FALSE -DENABLE_UPDATERS:BOOL=FALSE
-DFETCH_TRANSLATIONS:BOOL=FALSE -DINSTALL_BENCHMARKS:BOOL=FALSE
-DBUILD_SHARED_LIBS:BOOL=TRUE -DKDE_INSTALL_AUTOSTARTDIR=/etc/xdg/autostart
-DKDE_INSTALL_CONFDIR=/etc/xdg -DKDE_INSTALL_DATAROOTDIR:PATH=/usr/share
-DKDE_INSTALL_LIBEXECDIR=libexec -DKDE_INSTALL_SYSCONFDIR=/etc
-DKDE_INSTALL_USE_QT_SYS_PATHS:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_FFTW3:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenColorIO:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_HEIF:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenJPEG:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenEXR:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Poppler:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonInterp:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonLibrary:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_SIP:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PyQt5:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_LibRaw:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Qt5Multimedia:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Vc:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_WebP:BOOL=FALSE -DBUILD_TESTING:BOOL=FALSE
/var/tmp/paludis/build/media-gfx-krita-scm/work/krita-scm

Attached you'll find, the hopefully useful, coredump.

Kcrash Handler Output Compile Krita Git master:
382d300c788a3ba68e6bdf3a75fe5ccb5c3454f5:

Application: krita (krita), signal: Segmentation fault

[KCrash Handler]
#4  0x7f71854693f9 in KoColor::toSVG11 (this=this@entry=0x5620a3ac7668,
profileList=profileList@entry=0x7ffcc60585f8) at
/var/tmp/paludis/build/media-gfx-krita-scm/work/krita-scm/libs/pigment/KoColor.cpp:413
#5  0x7f718562bf21 in KoStopGradient::saveSvgGradient (this=) at
/var/tmp/paludis/build/media-gfx-krita-scm/work/krita-scm/libs/pigment/resources/KoStopGradient.cpp:599
#6  0x7f7185631569 in KoStopGradient::saveToDevice (this=0x5620a3ac7480,
dev=) at
/var/tmp/paludis/build/media-gfx-krita-scm/work/krita-scm/libs/pigment/resources/KoStopGradient.cpp:630
#7  0x7f71876c6a9e in KisMemoryStorage::addResource (this=,
resourceType=..., resource=...) at
/var/tmp/paludis/

[krita] [Bug 445329] Krita crashes when closing the "Configure Krita" dialogue with the "X" close icon

https://bugs.kde.org/show_bug.cgi?id=445329

--- Comment #2 from Timo Gurr  ---
Created attachment 143466
  --> https://bugs.kde.org/attachment.cgi?id=143466&action=edit
krita_segfault.png

Attaching screenshot to illustrate / make clear which button I'm referring to.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 445329] Krita crashes when closing the "Configure Krita" dialogue with the "X" close icon

2021-11-12 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=445329

--- Comment #5 from Timo Gurr  ---
(In reply to Halla Rempt from comment #4)
> This only happens because of an unusual combination of present and absent
> dependencies, it won't happen in a supported build.

Can you please give any details? The only optional external dependencies
disabled in this build appear to be KSeExpr & Vc. Will you still look into it
considering krita offers the options? I don't consider this a major issue
though like the crashes on startup I experienced before that you've fixed in no
time and allowed us update our package to the latest stable version, thanks
again for that! Thanks for any help & information!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 306352] 100% cpu usage when waking up from suspend or switching between x servers, might be caused by kglobalaccel

2022-07-21 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=306352

Timo Gurr  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #12 from Timo Gurr  ---
*** This bug has been confirmed by popular vote. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 431218] mail viewer loads external fonts even with external refs disabled

2021-02-03 Thread Timo Weingärtner

https://bugs.kde.org/show_bug.cgi?id=431218

--- Comment #3 from Timo Weingärtner  ---
I sent you a test case in private mail.

When reading your patch and the surrounding code it looks like only some
(images, now also fonts) request types are blacklisted. What about external
style sheets or other types that might grow in HTML-land? Are there any
external requests you think should be allowed?

Regarding URL schemes: why is file:// allowed? I could think of some social
engineering attacks that might work by including files from the victims
computer. I would read "external request" as external to the e-mail in
question.

To me the function could be as simple as:

8<8<
bool
LoadExternalReferencesUrlInterceptor::interceptRequest(QWebEngineUrlRequestInfo
&info)
{
if (mAllowLoadExternalReference) {
return false;
}

const QString scheme = info.requestUrl().scheme();
if (scheme == QLatin1String("data")
|| scheme == QLatin1String("cid")) {
return false;
}

return true;
}
8<8<

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 431218] mail viewer loads external fonts even with external refs disabled

2021-02-04 Thread Timo Weingärtner

https://bugs.kde.org/show_bug.cgi?id=431218

--- Comment #5 from Timo Weingärtner  ---
Why should an email be able to load images from my home directory?

What is the use case for loading images from file:// ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)

2021-08-10 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=439040

--- Comment #6 from Timo Gurr  ---
(In reply to Manuel Geißer from comment #5)
> *output
> If `qtbase_de.qm` is missing, then we may have found the cause.

Indeed! Huge thanks for that very insightful hint. Now I was just wondering
that I couldn't find any translation sources included in the qtbase source
tarball at all and just found out it's shipped in a separate tarball/package
"qttranslations" which solves my problem with the missing files and of course
also the inital problem I had. Again thanks and sorry for the noise, I'll see
that I can add a suggestion/recommendation on qttranslations to our qtbase
package to make things more obvious.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)

2021-08-10 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=439040

--- Comment #7 from Timo Gurr  ---
FYI: The same problem/solution exists on Fedora, might have to verify with a
complete fresh installation, but on an else localized KDE Plasma desktop
pre-installed via the "KDE Spin" the "qt5-qtranslations" package was missing
there as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[i18n] [Bug 440943] New: plasma-pa: translation discrepancy of string microphone

2021-08-13 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=440943

Bug ID: 440943
   Summary: plasma-pa: translation discrepancy of string
microphone
   Product: i18n
   Version: unspecified
  Platform: Exherbo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: de
  Assignee: kde-i18n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 140700
  --> https://bugs.kde.org/attachment.cgi?id=140700&action=edit
plasma-pa.png

SUMMARY

In the same popup dialog there's "Mikrophon" and "Mikrofon", see attached
screenshot.

It's probably
https://websvn.kde.org/trunk/l10n-kf5/de/messages/plasma-pa/kcm_pulseaudio.po?view=markup

314 #: qml/microphoneindicator.cpp:132 qml/microphoneindicator.cpp:134
315 #, kde-format
316 msgid "Microphone"
317 msgstr "Mikrophon"

STEPS TO REPRODUCE
1. Have an application using the microphone so the taskbar symbol is displayed
2. Hover the taskbar symbol with the mouse cursor
3. Read text in the popup dialog

OBSERVED RESULT

Outdated "Mikrophon"


EXPECTED RESULT

"Mikrofon" you see everywhere these days and is already used in KDE Plasma
everywhere else as well.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ki18n] [Bug 439040] New: Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)

2021-06-22 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=439040

Bug ID: 439040
   Summary: Some strings in right click menus of input fields are
not localized (Undo/Redo/Cut/Copy/Paste/Delete)
   Product: frameworks-ki18n
   Version: 5.83.0
  Platform: Exherbo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: caslav.i...@gmx.net
  Reporter: timo.g...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 139596
  --> https://bugs.kde.org/attachment.cgi?id=139596&action=edit
kfind.png

SUMMARY
I hope I chose the right component. Some strings in right click menus of input
fields are not localized, like e.g. Undo/Redo/Cut/Copy/Paste/Delete. See
attached screenshots.


STEPS TO REPRODUCE (kfind)
1. open kfind
2. right click any text input field

STEPS TO REPRODUCE (dolphin)
1. right click a file to rename it and see proper translated strings
2. right click in the highlighted input where you can type the filename and see
untranslated strings


EXPECTED RESULT
Have everything properly localized.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I can also reproduce this behaviour on a current up-to-date Fedora 34 KDE
Plasma Session so this is not exclusive to Exherbo Linux.

Everything else is properly localized, so I assume no user configuration error
on my side.

$ locale
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

Plasma is also setup with the proper non-english localization via
systemsettings kcm.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)

2021-06-22 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=439040

--- Comment #1 from Timo Gurr  ---
Created attachment 139597
  --> https://bugs.kde.org/attachment.cgi?id=139597&action=edit
dolphin.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 435516] New: PGP PUBLIC KEY BLOCK silently removed from view

2021-04-08 Thread Timo Weingärtner

https://bugs.kde.org/show_bug.cgi?id=435516

Bug ID: 435516
   Summary: PGP PUBLIC KEY BLOCK silently removed from view
   Product: kmail2
   Version: 5.15.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: t...@tiwe.de
  Target Milestone: ---

Created attachment 137436
  --> https://bugs.kde.org/attachment.cgi?id=137436&action=edit
example mail

SUMMARY

PGP PUBLIC KEY BLOCK is silently removed from mail view.
When viewing a text-only mail I don't expect anything to be removed.
What else is removed from mail bodies? What can be hidden from a recipient
using kmail, even in signed mails?

STEPS TO REPRODUCE
1. view example mail (attached)

OBSERVED RESULT

no public key displayed, neither inline nor as an attachment

EXPECTED RESULT

public key block shown inline ready to be copied

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 474665] New: gwenview weird behaviour under wayland session with global scaling >100% active

https://bugs.kde.org/show_bug.cgi?id=474665

Bug ID: 474665
   Summary: gwenview weird behaviour under wayland session with
global scaling >100% active
Classification: Applications
   Product: gwenview
   Version: 23.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 161701
  --> https://bugs.kde.org/attachment.cgi?id=161701&action=edit
gwenview_wayland.png

SUMMARY
Under wayland when global scaling is active (in my case 125%) the default view
doesn't zoom to a reasonable size and trying to zoom to original size doesn't
seem to work at all.

STEPS TO REPRODUCE
1. Log into a wayland session
2. Set global scaling to e.g. 125%
3. Observe issues

OBSERVED RESULT
* default zoom doesn't fill in the whole application window
* trying to zoom to original size doesn't do anything

EXPECTED RESULT
* work like intended and behave like under X11 with global scaling active
* work like on wayland when global scaling is not active / 100%

SOFTWARE/OS VERSIONS

Operating System: Exherbo 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.3 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION
Please see attached screenshots.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 474665] gwenview weird behaviour under wayland session with global scaling >100% active

https://bugs.kde.org/show_bug.cgi?id=474665

--- Comment #1 from Timo Gurr  ---
Created attachment 161702
  --> https://bugs.kde.org/attachment.cgi?id=161702&action=edit
gwenview_x11.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 474665] gwenview weird behaviour under wayland session with global scaling >100% active

https://bugs.kde.org/show_bug.cgi?id=474665

--- Comment #2 from Timo Gurr  ---
Created attachment 161703
  --> https://bugs.kde.org/attachment.cgi?id=161703&action=edit
gwenview_x11_zoom_original_size.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 474666] New: On a wayland session fonts look horrible when global scaling is active

https://bugs.kde.org/show_bug.cgi?id=474666

Bug ID: 474666
   Summary: On a wayland session fonts look horrible when global
scaling is active
Classification: Plasma
   Product: kwin
   Version: 5.27.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 161704
  --> https://bugs.kde.org/attachment.cgi?id=161704&action=edit
display_settings_wayland.png

SUMMARY
I hope I picked the right component and kwin is actually doing the global
scaling, if not please move this bug to the respective component as I have no
idea of the actual technical implementation, thank in advance.

When logging in to a wayland session and setting the global scaling to 125%
like I do on X11 the fonts look horrible compared to X11. 

STEPS TO REPRODUCE
1. Have a 2k monitor
2. Log into a wayland session
3. Set global scaling to 125%

OBSERVED RESULT
Fonts look horrible like eroded or frayed compared to X11. Also the font
spacing is different, like can be seen on the last item of the menu on the left
side "Über dieses System" where the spacing between Üb<->er is too narrow and
not consistent between the letters.

EXPECTED RESULT
Font looking "normal" sharp and crisp and easily readable like on a X11 session
with global scaling set to 125%.

SOFTWARE/OS VERSIONS

Operating System: Exherbo 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.3 (64-bit)
Graphics Platform: Wayland / X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION
Attaching screenshots to illustrate the problem, while they might look ok on
the first look try comparing them and you probably see the difference, it might
not look that bad but compared to X11 it really hurts the eyes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 474666] On a wayland session fonts look horrible when global scaling is active

https://bugs.kde.org/show_bug.cgi?id=474666

--- Comment #1 from Timo Gurr  ---
Created attachment 161705
  --> https://bugs.kde.org/attachment.cgi?id=161705&action=edit
display_settings_x11.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 474666] On a wayland session fonts look horrible when global scaling is active

https://bugs.kde.org/show_bug.cgi?id=474666

--- Comment #2 from Timo Gurr  ---
Created attachment 161706
  --> https://bugs.kde.org/attachment.cgi?id=161706&action=edit
system_settings_wayland.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 474666] On a wayland session fonts look horrible when global scaling is active

https://bugs.kde.org/show_bug.cgi?id=474666

--- Comment #3 from Timo Gurr  ---
Created attachment 161707
  --> https://bugs.kde.org/attachment.cgi?id=161707&action=edit
system_settings_x11.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 474666] On a wayland session fonts look horrible when global scaling is active

2023-09-20 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=474666

--- Comment #6 from Timo Gurr  ---
(In reply to Zamundaaa from comment #4)
> You need to log out and log in again before Qt renders correctly with
> changed scaling. This is fixed in Plasma 6

I did logout and back in before taking the screenshots, actually I even
restarted the whole machine after every change.

(In reply to Nate Graham from comment #5)
> I appreciate you taking screenshots that are pixel-for-pixel identical onX11
> vs Wayland except for the text. That was very helpful.
> 
> In a nutshell, fractional scaling on Qt5 Wayland is less than ideal compared
> to X11. It's already fixed in Qt 6, though.

Thanks for the clarification, I guess I'll have to wait until February then for
the KDE Plasma version based on Qt6 to arrive to be able to switch from a X11
to a Wayland session. I read your wayland articles and finally got an amd gpu
together with a new 2k monitor so I thought I could do the switch right away.
I'm glad to hear that it is already fixed for the Qt6 based KDE Plasma, looking
very much forward to it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 306352] 100% cpu usage when waking up from suspend or switching between x servers, might be caused by kglobalaccel

2023-09-25 Thread Timo Gurr

https://bugs.kde.org/show_bug.cgi?id=306352

--- Comment #26 from Timo Gurr  ---
While certainly not a fix by any means I want to share a workaround because I
found myself ever so often not noticing that the cpu spike again kicked in
until I wondered why my machine is loud again and revving up the fans. I
installed monit and dropped a configuration file in /etc/monit.d/ which
monitors the process kglobalaccel5 and restarts it under my user session when
two consecutive checks find the kglobalaccel5 process running with higher cpu
usage than usual/normal:

/etc/monit.d/kglobalaccel5

check process kglobalaccel5
matching "kglobalaccel5"
start program = "/usr/bin/systemctl --machine tgurr@.host --user start
plasma-kglobalaccel.service"
stop program = "/usr/bin/systemctl --machine tgurr@.host --user stop
plasma-kglobalaccel.service"
restart program = "/usr/host/bin/systemctl --machine tgurr@.host --user
restart plasma-kglobalaccel.service"
if cpu usage > 10% for 2 cycles then restart

You may have to adjust the systemctl path and the user of course and it only
works for one user this way. For me this means I don't have to manually care
about monitoring the process anymore and not having to issue the restart
command after every single login all the time.

journal entries should look something along the line like:

Sep 25 20:25:05 exherbo monit[2412]: 'kglobalaccel5' process is running with
pid 2457
Sep 25 20:25:05 exherbo monit[2412]: 'kglobalaccel5' cpu usage of 32.7% matches
resource limit [cpu usage > 10.0%]
Sep 25 20:25:34 exherbo monit[2412]: 'kglobalaccel5' cpu usage of 33.9% matches
resource limit [cpu usage > 10.0%]
Sep 25 20:25:34 exherbo monit[2412]: 'kglobalaccel5' trying to restart
Sep 25 20:25:34 exherbo monit[2412]: 'kglobalaccel5' restart:
'/usr/bin/systemctl --machine tgurr@.host --user restart
plasma-kglobalaccel.service'

Hope it may be useful for someone else as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 475562] New: krita segfaults on start after displaying the splash screen

https://bugs.kde.org/show_bug.cgi?id=475562

Bug ID: 475562
   Summary: krita segfaults on start after displaying the splash
screen
Classification: Applications
   Product: krita
   Version: 5.2.0
  Platform: Exherbo
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: timo.g...@gmail.com
  Target Milestone: ---

Created attachment 162272
  --> https://bugs.kde.org/attachment.cgi?id=162272&action=edit
krita-20231013-132223.kcrash

SUMMARY
Krita crashes right on start just after displaying the splash screen. 

STEPS TO REPRODUCE
1.  Compile Krita 5.2.0
2.  Try to run it

OBSERVED RESULT
Segfault

EXPECTED RESULT
No segfault

SOFTWARE/OS VERSIONS
Operating System: Exherbo 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.5 (64-bit)
Graphics Platform: X11
Processors: 12 × 12th Gen Intel® Core™ i5-12500
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 770

ADDITIONAL INFORMATION
Used CMake options during build

cmake -DCMAKE_BUILD_TYPE:STRING=None -DCMAKE_C_FLAGS:STRING=-march=native -O2
-pipe -DNDEBUG -DQT_NO_DEBUG -DCMAKE_CXX_FLAGS:STRING=-march=native -O2 -pipe
-DNDEBUG -DQT_NO_DEBUG -DCMAKE_AR:PATH=x86_64-pc-linux-gnu-ar
-DCMAKE_RANLIB:PATH=x86_64-pc-linux-gnu-ranlib
-DCMAKE_NM:PATH=x86_64-pc-linux-gnu-nm
-DCMAKE_C_COMPILER:PATH=x86_64-pc-linux-gnu-cc
-DCMAKE_CXX_COMPILER:PATH=x86_64-pc-linux-gnu-c++
-DCMAKE_INSTALL_PREFIX:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM:STRING=NEVER
-DCMAKE_SYSTEM_PREFIX_PATH:PATH=/usr/x86_64-pc-linux-gnu
-DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_DATAROOTDIR:PATH=/usr/share/
-DBUILD_COVERAGE:BOOL=FALSE -DBUILD_KRITA_QT_DESIGNER_PLUGINS:BOOL=FALSE
-DBUILD_SHARED_LIBS:BOOL=TRUE -DCMAKE_DISABLE_FIND_PACKAGE_KSeExpr:BOOL=TRUE
-DCMAKE_DISABLE_FIND_PACKAGE_LibMyPaint:BOOL=TRUE
-DCRASH_ON_SAFE_ASSERTS:BOOL=FALSE -DDISABLE_PO_INSTALLATION:BOOL=FALSE
-DENABLE_BSYMBOLICFUNCTIONS:BOOL=FALSE -DENABLE_CPU_THROTTLE:BOOL=FALSE
-DENABLE_UPDATERS:BOOL=FALSE -DHAVE_BACKTRACE_SUPPORT:BOOL=FALSE
-DHAVE_MEMORY_LEAK_TRACKER:BOOL=FALSE -DHIDE_SAFE_ASSERTS:BOOL=TRUE
-DINSTALL_BENCHMARKS:BOOL=FALSE -DKRITA_ENABLE_BROKEN_TESTS:BOOL=FALSE
-DKRITA_ENABLE_PCH:BOOL=TRUE -DLIMIT_LONG_TESTS:BOOL=TRUE
-DUSE_EXTERNAL_RAQM:BOOL=FALSE -DUSE_LOCK_FREE_HASH_TABLE:BOOL=TRUE
-DFOUNDATION_BUILD:BOOL=FALSE -DKRITA_DEVS:BOOL=FALSE
-DBUILD_SHARED_LIBS:BOOL=TRUE -DKDE_INSTALL_AUTOSTARTDIR=/etc/xdg/autostart
-DKDE_INSTALL_CONFDIR=/etc/xdg -DKDE_INSTALL_DATAROOTDIR:PATH=/usr/share
-DKDE_INSTALL_LIBEXECDIR=libexec -DKDE_INSTALL_SYSCONFDIR=/etc
-DKDE_INSTALL_USE_QT_SYS_PATHS:BOOL=TRUE -DQT_MAJOR_VERSION=5
-DCMAKE_DISABLE_FIND_PACKAGE_FFTW3:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenColorIO:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_HEIF:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenJPEG:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_JPEGXL:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_OpenEXR:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Poppler:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_libjpeg-turbo:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PythonLibrary:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_SIP:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_PyQt5:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_KF5KDcraw:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_Mlt7:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_SDL2:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_xsimd:BOOL=FALSE
-DCMAKE_DISABLE_FIND_PACKAGE_WebP:BOOL=FALSE -DBUILD_TESTING:BOOL=FALSE
/var/tmp/paludis/build/media-gfx-krita-5.2.0/work/krita-5.2.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 475562] krita segfaults on start after displaying the splash screen

https://bugs.kde.org/show_bug.cgi?id=475562

--- Comment #1 from Timo Gurr  ---
Created attachment 162273
  --> https://bugs.kde.org/attachment.cgi?id=162273&action=edit
krita-5.2.0-coredump.txt

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 475562] krita segfaults on start after displaying the splash screen

https://bugs.kde.org/show_bug.cgi?id=475562

--- Comment #3 from Timo Gurr  ---
Only one krita present on the system. Exherbo is a source-based distribution
like Gentoo.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 475562] krita segfaults on start after displaying the splash screen

https://bugs.kde.org/show_bug.cgi?id=475562

--- Comment #5 from Timo Gurr  ---
Thanks for your comments. Just for reference this pretty much happens to us
with every new krita version and usually the problems in the past have not
really been on our side:

https://bugs.kde.org/show_bug.cgi?id=445276
https://bugs.kde.org/show_bug.cgi?id=445285
https://bugs.kde.org/show_bug.cgi?id=445329
https://bugs.kde.org/show_bug.cgi?id=447597

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 475562] krita segfaults on start after displaying the splash screen

https://bugs.kde.org/show_bug.cgi?id=475562

--- Comment #7 from Timo Gurr  ---
(In reply to Halla Rempt from comment #6)
> I know... But even so, there isn't much testing we can do, since it doesn't
> happen elsewhere. The only guess I can make is that this patch might help,
> but I cannot test it:
> 
> diff --git a/libs/widgets/KisVisualColorModel.cpp
> b/libs/widgets/KisVisualColorModel.cpp
> index 943eb0a93a..d9d6206031 100644
> --- a/libs/widgets/KisVisualColorModel.cpp
> +++ b/libs/widgets/KisVisualColorModel.cpp
> @@ -78,6 +78,8 @@ void KisVisualColorModel::slotSetColor(const KoColor &c)
>  
>  void KisVisualColorModel::slotSetColorSpace(const KoColorSpace *cs)
>  {
> +if (!cs) return;
> +
>  if (!m_d->currentCS || *m_d->currentCS != *cs) {
>  const KoColorSpace *csNew = cs;

Thanks for helping to get this resolved. I'm afraid it still segfaults right
away with the patch applied, the kcrash looks basically identical, attaching it
anyways.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 475562] krita segfaults on start after displaying the splash screen