[krita] [Bug 363110] Insecure download for pre-built Krita (especially the beta version)
https://bugs.kde.org/show_bug.cgi?id=363110 --- Comment #5 from Vitaly "_Vi" Shukela <vi0...@gmail.com> --- One more idea: include magnet links. A file downloaded from magnet link (obtained securely, of course) should be secure. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363110] New: Insecure download for pre-built Krita (especially the beta version)
https://bugs.kde.org/show_bug.cgi?id=363110 Bug ID: 363110 Summary: Insecure download for pre-built Krita (especially the beta version) Product: krita Version: unspecified Platform: unspecified URL: https://krita.org/download/krita-desktop/ OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: vi0...@gmail.com For example, I see "Linux Bleeding Edge Appimage Download" for downloading a user-executable file by HTTP. No HTTPS, no signatures, not even sha1sum. The same for Windows binaries. Reproducible: Always Steps to Reproduce: 1. Go to Krita download site 2. Download Krita 3. Attempt to verity if the downloaded file is corrupted Actual Results: No way to verify if the downloaded file is genuine Expected Results: There is published checksum or there is detached signature file. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363110] Insecure download for pre-built Krita (especially the beta version)
https://bugs.kde.org/show_bug.cgi?id=363110 --- Comment #2 from Vitaly "_Vi" Shukela <vi0...@gmail.com> --- Then links to those mirrorlists should be visible on download page, like this: * Linux Bleeding Edge Appimage Download (mirros and checksums) * Linux Bleeding Edge Appimage Download (legacy distros) (mirros and checksums) Also your link to mirrorlist is HTTP (not HTTPS). It means checksums may be also faked. Changing the link to https makes 404. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368971] Wrong/missing icons in Tool Options for Multiline Text tool when editing text
https://bugs.kde.org/show_bug.cgi?id=368971 --- Comment #1 from Vitaly "_Vi" Shukela <vi0...@gmail.com> --- Created attachment 101154 --> https://bugs.kde.org/attachment.cgi?id=101154=edit Broken icons screenshot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368973] New: "Group layers" operation should be more clever about compositing mode.
https://bugs.kde.org/show_bug.cgi?id=368973
Bug ID: 368973
Summary: "Group layers" operation should be more clever about
compositing mode.
Product: krita
Version: 3.0.1
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Layer Stack
Assignee: krita-bugs-n...@kde.org
Reporter: vi0...@gmail.com
When one use "Group layers", it create a new layer with compositing mode
"Normal". This does not mix well with "Wavelet decompose" feature.
I suggest "Group layers" to look at compositing mode of the parts being
grouped, e.g. just copy the first groupee's mode.
Reproducible: Always
Steps to Reproduce:
1. Open some image or create it and paint someting there
2. Image->Wavelet decompose
3. Select scale layers, say, from "Scale 2" to "Scale 4"
4. Press Ctrl+G ("Quick layer group")
Actual Results:
Image changes, "Scale 5" and "Residual" no loger in effect. Compositing mode
for newly created group layer is "Normal".
Expected Results:
No effect on resulting imag. Compositing mode for newly created group layer is
"Grain Merge", like of "Scale 2".
Workaround: manually set the mode to "Grain Merge" in layer properties.
With appearance of the "Wavelet decompose" filter, non-Normal layers might
become more commonplace and user might run into problem even without knowing
about layer compositing modes.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 368973] "Group layers" operation should be more clever about compositing mode.
https://bugs.kde.org/show_bug.cgi?id=368973 --- Comment #2 from Vitaly "_Vi" Shukela <vi0...@gmail.com> --- Then maybe grouping layers with different compositing modes should give a warning and/or set passthough? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368971] New: Wrong/missing icons in Tool Options for Multiline Text tool when editing text
https://bugs.kde.org/show_bug.cgi?id=368971 Bug ID: 368971 Summary: Wrong/missing icons in Tool Options for Multiline Text tool when editing text Product: krita Version: 3.0.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: vi0...@gmail.com See the screenshot. Reproducible: Always Steps to Reproduce: 1. Open Krita 3.0.1 from app bundle, create/open a file 2. Activate multiline text tool, choose a rectangle for text 3. Observe broken "Tool Options" icons Actual Results: Most icons are missing. The sole visible icon is "Decrease indent" Expected Results: There are icons for all actions, like with other tools. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368973] "Group layers" operation should be more clever about compositing mode.
https://bugs.kde.org/show_bug.cgi?id=368973 --- Comment #4 from Vitaly "_Vi" Shukela <vi0...@gmail.com> --- Shall there be at least a warning when grouping "Grain Merge" layers? "Wavelet decompose" is easier to find in the menu than layer blending modes, so users may trigger and use it without fully understanding what it actually does. Another idea: Extend "Wavelet decompose" window to contain a piece of help, not just the sole "Wavelet scales" input parameter. This help can at least point users to look more about blending modes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374852] New: Auto-save triggers transform application, abandoning manually entered anchor points.
https://bugs.kde.org/show_bug.cgi?id=374852 Bug ID: 374852 Summary: Auto-save triggers transform application, abandoning manually entered anchor points. Product: krita Version: 3.1.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: transform Assignee: krita-bugs-n...@kde.org Reporter: vi0...@gmail.com Target Milestone: --- Steps to reproduce: 1. Start Krita. Assuming auto-save is enabled (default); 2. Open some image 3. Select all 4. "Transform layer or selection" (Ctrl+T) 5. Tool options -> Warp 6. Tool options -> Anchor points -> Draw 7. Begin carefully placing and adjusting points Expected: The transform applies when I select other tool or press "Apply" button. Actual: Half-way though by anchor points adjustment, the filter applies spontaneously, abandoning all my points. Can't go back and resume moving anchor points. When this happens, I see saving progress flashing though status bar. Workaround: Settings->Configure Krita-> General -> Misc -> uncheck "Autosave every", then apply the transform, then check it again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394179] New: Error message about missing/unconfigured qt-gmic is not helpful enough.
https://bugs.kde.org/show_bug.cgi?id=394179 Bug ID: 394179 Summary: Error message about missing/unconfigured qt-gmic is not helpful enough. Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: vi0...@gmail.com Target Milestone: --- Created attachment 112604 --> https://bugs.kde.org/attachment.cgi?id=112604=edit A low-effort untested patch that edits the message (no translations) The error message should contain some call to action. Additionally, "G'Mic-Qt Integration" settings page should also hint to look at downloadable AppImage at Krita site (https://download.kde.org/stable/krita/4.0.1/gmic_krita_qt-x86_64.appimage), not just point to GMic's site. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394179] Error message about missing/unconfigured qt-gmic is not helpful enough.
https://bugs.kde.org/show_bug.cgi?id=394179 --- Comment #1 from Vitaly "_Vi" Shukela <vi0...@gmail.com> --- Created attachment 112605 --> https://bugs.kde.org/attachment.cgi?id=112605=edit A low-effort change to "G'Mic-Qt integration" settings page to hint about AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454236] New: Crash when using a clip that was changed on the filesystem.
https://bugs.kde.org/show_bug.cgi?id=454236 Bug ID: 454236 Summary: Crash when using a clip that was changed on the filesystem. Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: vi0...@gmail.com Target Milestone: --- Encounted a crash: ... ::: REGISTERING CLIP TO BIN: :: REGISTRATION 35 ptr count 8 qml: loaded clip: 3143 , ID: 35 , index: 0 , TYPE: Video qml: loaded clip with Astream: -1 terminate called after throwing an instance of 'std::out_of_range' what(): _Map_base::at [1]+ Aborted /opt/kdenlive-master-208-linux-64-gcc.AppImage when re-adding a video clip from bin to timeline where the clip was repeatedly changed on filesystem. The video got replaced by one-second video, then back to original length. I saw the clip's segment shrink to 1 second in the timeline, but after deleting and attempting to re-add it Kdenlive crashed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454236] Crash when using a clip that was changed on the filesystem.
https://bugs.kde.org/show_bug.cgi?id=454236 --- Comment #1 from Vitaly "_Vi" Shukela --- After Kdenlive restart it offered to recover session. Repeating the actions in the recovered session worked properly. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451817] Render fails instantly 21.12.3 on Linux Mint kdenlive-21.12.3-x86_64.AppImage
https://bugs.kde.org/show_bug.cgi?id=451817 --- Comment #8 from Vitaly "_Vi" Shukela --- @emohr Tried kdenlive-master-208-linux-64-gcc.AppImage: rendering now works out of the box: `/tmp/.mount_kdenliNUbyI1/usr/bin/melt` is working. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416139] Crash on startup running Kdenlive without pulseaudio
https://bugs.kde.org/show_bug.cgi?id=416139 Vitaly "_Vi" Shukela changed: What|Removed |Added CC||vi0...@gmail.com --- Comment #5 from Vitaly "_Vi" Shukela --- kdenlive-master-208-linux-64-gcc.AppImage or /opt/kdenlive-22.04.0-1-x86_x64.AppImage crash when I try to start after "chmod -x /usr/bin/pulseaudio". Sometimes it shows "Could not initialize preview" before crashing, sometimes main window only briefly blinks. I see in dmesg: [1367303.177761] SDLHotplugALSA[3978]: segfault at 0 ip 7fa010cdc5fe sp 7f9fd49f6c10 error 4 in libSDL2-2.0.so.0[7fa010c1f000+12a000] [1367303.177803] Code: 68 67 fa ff 48 85 db 75 e3 48 83 c4 78 31 c0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 90 48 c7 44 24 68 00 00 00 00 4c 8b 44 24 60 <49> 8b 38 48 85 ff 0f 84 df 04 00 00 48 c7 44 24 18 00 00 00 00 45 [1368115.019694] AppRun.wrapped[6297]: segfault at 0 ip 7fdb859c31e0 sp 7ffe4564ffd8 error 4 in libmlt++-7.so.7[7fdb859a6000+29000] [1368115.019719] Code: 54 24 08 48 89 34 24 ff d0 48 8b 54 24 08 48 8b 34 24 48 83 c4 18 48 89 c7 e9 cc 89 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 07 48 8d 0d d6 f8 ff ff 48 8b 40 10 48 39 c8 75 0d 48 8b 7f With /usr/bin/pulseaudio enabled it starts successfully from one user account but crashes from another one (before even displaying a message about preview pane being unavailable). Typically the crash happens after second instance of the following console messages: ALSA lib /home/appimage/Craft/BC/linux-64-gcc/build/libs/libasound2/work/alsa-lib-1.2.5.1/src/conf.c:4499:(snd_config_update_r) Cannot access file /home/appimage/Craft/BC/linux-64-gcc/share/alsa/alsa.conf (it crashes instead of outputting "no alsa devices available") Workaround: explicitly and manually start PulseAudio for that user: `pulseaudio --daemonize=false --exit-idle-time=-1 --disallow-exit=true`. Kdenlive then starts properly. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451817] Render fails instantly 21.12.3 on Linux Mint kdenlive-21.12.3-x86_64.AppImage
https://bugs.kde.org/show_bug.cgi?id=451817 Vitaly "_Vi" Shukela changed: What|Removed |Added CC||vi0...@gmail.com --- Comment #3 from Vitaly "_Vi" Shukela --- Still reproducible for kdenlive-22.04.0-1-x86_x64.AppImage: Rendering of /home/vi/Videos/untitled.mp4 crashed /tmp/.mount_kdenlihBl3HV/usr/bin/melt: symbol lookup error: /tmp/.mount_kdenlihBl3HV/usr/lib/ladspa/alias_1407.so: undefined symbol: libintl_bindtextdomain -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451817] Render fails instantly 21.12.3 on Linux Mint kdenlive-21.12.3-x86_64.AppImage
https://bugs.kde.org/show_bug.cgi?id=451817 --- Comment #4 from Vitaly "_Vi" Shukela --- Workaroud: save render script (mlt) from GUI, install "melt" package in distro, then render the video from CLI using /usr/bin/melt outside AppImage. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339605] vgpreload_helgrind-arm-linux.so is not linked to libc.so and can't find sched_yield, pthread_self and so on
https://bugs.kde.org/show_bug.cgi?id=339605 --- Comment #8 from Vitaly "_Vi" Shukela --- If there will be more similar problems, I'll probably open another issue. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339605] vgpreload_helgrind-arm-linux.so is not linked to libc.so and can't find sched_yield, pthread_self and so on
https://bugs.kde.org/show_bug.cgi?id=339605 --- Comment #6 from Vitaly "_Vi" Shukela --- > Is your application linked with libpthread and does it run correctly on its > own? I don't remember which application it was, but probably it worked correctly (apart from bugs to be debugged using valgrind), and according to my previous comment it also worked in Valgrind (but other tool). It was 8 years ago, so many things both in Android, Valgrind and toolchains for building apps could have changed. -- You are receiving this mail because: You are watching all bug changes.
