https://bugs.kde.org/show_bug.cgi?id=372932
Bug ID: 372932
Summary: KDEnlive Crash on initial boo
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=422948
Steve changed:
What|Removed |Added
Version|5.20.1 |5.24.0
CC
https://bugs.kde.org/show_bug.cgi?id=422948
Steve changed:
What|Removed |Added
Ever confirmed|1 |0
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=422948
Steve changed:
What|Removed |Added
Version|5.24.0 |5.24.1
--- Comment #89 from Steve ---
Regression and
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: steve@gmail.com
Target Milestone: ---
kstars and EKOS are shut down prematurely
STEPS TO REPRODUCE
1. Leave a capture and guiding job running
2.
3.
OBSERVED RESULT
kstars and EKOS
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #1 from steve ---
This was also reported to the indilib forum:
https://www.indilib.org/forum/ekos/11784-kstars-qsocketnotifier-invalid-socket-error.html
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #3 from steve ---
I'm using a Canon eos700d, eq6 mount and asi120mm guide camera.
The error occurs after taking around 15 to 20 frames (could be more, could be
less).
Socket error, so I thought it maybe the vnc server or client so swi
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #4 from steve ---
There are lots of these in the syslog at the time of the indi disconnection:
usb 3-2: reset high speed USB device number 3 using xhci_hcd
Any pointers?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #6 from steve ---
Hi
Unfortunately, it happens randomly when capturing and/or guiding but always
within an hour of starting the session.
eos700d, eq6, zwo120mm mini
There are lots of these in the syslog. Don't know if it's relate
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #7 from steve ---
Does:
Fix crash on driver restart; a541ab91429cc4f5b1df546fe2a2ce27d10dc900
https://github.com/KDE/kstars/commit/a541ab91429cc4f5b1df546fe2a2ce27d10dc900
Have any bearing upn this?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #9 from steve ---
The issue doesn't occur with 3.5.8, so something which changed between then and
3.5.9?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #11 from steve ---
Can you point me to a method for gir bisect?
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #13 from steve ---
OK
Does this look OK?
steve@E5430:~/Projects/kstars$ git bisect start
steve@E5430:~/Projects/kstars$ git bisect bad
steve@E5430:~/Projects/kstars$ git bisect good
3369e6afa815a6d1e2089f417eade08d69e668a2
Bisecting: 85
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #14 from steve ---
Just seen that it's the name of the commit which git bisect checked out. DUH!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #15 from steve ---
OK. That checkout gave the same error:
[2022-06-08T01:03:56.394 CEST DEBG ][ org.kde.kstars.indi] - ZWO CCD
ASI120MM Mini : "[DEBUG] Upload complete "
[2022-06-08T01:03:56.410
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #17 from steve ---
Yep. OK. I think I've understood.
Here's the next one:
git bisect good
Bisecting: 16 revisions left to test after this (roughly 4 steps)
[3d989ff71a2d1037fdcf0dd6fb2e0aafab144f6d] Fix broken checkbox label a
https://bugs.kde.org/show_bug.cgi?id=455057
Bug ID: 455057
Summary: Exposure blending fails to preview
Product: digikam
Version: 7.6.0
Platform: Other
OS: macOS
Status: REPORTED
Severity: major
P
https://bugs.kde.org/show_bug.cgi?id=455057
--- Comment #1 from Steve ---
Hugin packages downloaded during the installation of DigiKam.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455057
--- Comment #5 from Steve ---
Maik, thanks for confirming the bug and providing an interim solution, i.e.,
use JPG files, albeit they have lower bit depth. Yes the interim solution
worked for me too. When do you estimate digiKam-8.0.0 will be
https://bugs.kde.org/show_bug.cgi?id=455057
--- Comment #6 from Steve ---
Maik, also determined that digicam 7.6.0 works fine with both 8- and 16-bit TIF
images. Using 16-bit TIF is a better work around. My work flow is Nikon Z7 >
Nikon's NX Studio > export 8|16-bit TIF image. T
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #18 from steve ---
For this bisect checkout, the indi server survived but still crashed upon:
[2022-06-11T04:16:40.210 CEST WARN ][ default] -
QSocketNotifier: Invalid socket 76 and type 'Read', disabling.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #19 from steve ---
git bisect bad
b028a6e607f64cb0f7eac284732e5b12c6df366d is the first bad commit
commit b028a6e607f64cb0f7eac284732e5b12c6df366d
Author: Hy Murveit
Date: Tue Apr 12 07:24:03 2022 +
Add Target Distance to the
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #20 from steve ---
log corresponding to bad git bisect here:
https://drive.google.com/file/d/14nhEY_x8oLKdVzk54Mg67o2VUWsqyzCn/view?usp=sharing
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #22 from steve ---
This is the bad commit according to git bisect, not myself.
Please could you help by telling me which is the previous commit you would like
testing?
Thanks.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=454866
steve changed:
What|Removed |Added
Platform|Other |Kubuntu Packages
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #23 from steve ---
OK. Found it in the git log. The previous commit is this one:
3d989ff71a2d1037fdcf0dd6fb2e0aafab144f6d
Will try.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #24 from steve ---
That commit has already proven to be good.
here is the bisect log:
git bisect start
# bad: [ec5c439a01b81aa93fd67abe6fee370e3846a005] For lightbox, we must check
target state since for dark frame it must turned off and
ngrade to older Hugin, wait or fix myself.
It's been a few years since these prior bugs were submitted. What is the
actual status?
Thanks in advance! - Steve
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455226
--- Comment #4 from Steve ---
It appears that version 2019.2.0.b690aa0334b5 built by Niklas Mischkulnig is
available for MacOS.
Steve
> On Jun 13, 2022, at 4:41 PM, Maik Qualmann wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=455226
https://bugs.kde.org/show_bug.cgi?id=455226
--- Comment #5 from Steve ---
Gilles,
I’ve subsequently learned that I can use TIF files (and not JPG) directly with
the Hugin application to make a panorama. So that’s a work around for now.
Sure, be glad to make the bug report as you suggest later
https://bugs.kde.org/show_bug.cgi?id=455226
--- Comment #7 from Steve ---
Maik,
I thought DigiKam 7.6.0 is looking for pto2mk and not Hughin_executor.
Steve
Sent from my Steve's iPad
> On Jun 14, 2022, at 11:39 AM, Maik Qualmann wrote:
>
> https://bugs.kde.org/show_bug
https://bugs.kde.org/show_bug.cgi?id=455226
--- Comment #10 from Steve ---
Maik,
I suspect having run Hugin directly yesturday made some changes in my
computer. Today I was able to run the application but with a couple tweaks. I
also downloaded the most recent version of Hugin
https://bugs.kde.org/show_bug.cgi?id=455226
--- Comment #11 from Steve ---
Created attachment 149707
--> https://bugs.kde.org/attachment.cgi?id=149707&action=edit
attachment-516-1.html
--- Comment #12 from Steve ---
Created attachment 149708
--> https://bugs.kde.org/attachm
https://bugs.kde.org/show_bug.cgi?id=455226
--- Comment #18 from Steve ---
While the DigiKam app starts up and runs via the icon I found that it is the
updated system PATH and use of the terminal cli that enables the Hugin to work
correctly. Have I done something wrong?
Steve
Sent from my
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #25 from steve ---
Hi
Any news on this bug?
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #26 from steve ---
Do you think this may help?
https://www.indilib.org/forum/development/11843-fast-blobs.html
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #27 from steve ---
This is the kstars git built with the latest INDI as requested testing from
here:
https://www.indilib.org/forum/development/11843-fast-blobs.html
It still crashes with the same indi disconnect error.
log:
https
https://bugs.kde.org/show_bug.cgi?id=422088
Steve changed:
What|Removed |Added
CC||sbra...@gmail.com
--- Comment #14 from Steve ---
Same
https://bugs.kde.org/show_bug.cgi?id=422088
Steve changed:
What|Removed |Added
Platform|Archlinux |Flatpak
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=422088
Steve changed:
What|Removed |Added
Ever confirmed|1 |0
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=470184
Bug ID: 470184
Summary: Dual-monitor PC will not refresh secondary desktop
after switching HDMI port in X11
Classification: Plasma
Product: Active Window Control
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #1 from Steve ---
There is a discussion with more detail on LQ here:
https://www.linuxquestions.org/questions/showthread.php?p=6432534&posted=1#post6432534
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #2 from Steve ---
There is more detail in a discussion on LQ here:
https://www.linuxquestions.org/questions/showthread.php?p=6432534&posted=1#post6432534
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #4 from Steve ---
I disagree this is a duplicate of bug 467074. The behavior might be similar but
it is triggered here by a completely different mechanism. That is a
(temporary) hardware disconnection of the secondary monitor - unlike
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #5 from Steve ---
(In reply to Steve from comment #4)
> I disagree this is a duplicate of bug 467074. The behavior might be similar
> but it is triggered here by a completely different mechanism. That is a
> (temporary)
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #16 from Steve ---
FWIW I am including my display configuration. My docking station has 1 display
port and 1 HDMI port. It is the display port that goes to my 4-way HDMI switch
(via a display-port to HDMI adapter) and ultimately monitor #3
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #19 from Steve ---
That would be great detective work LabHamster! I would venture that would be
much appreciated by the Plasma team. That would help them immensely in
tracking down what changed in Plasma. I can say definitively this is not
https://bugs.kde.org/show_bug.cgi?id=467074
Steve changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=478462
Bug ID: 478462
Summary: webkit Element.requestPointerLock() lets pointer move
Classification: Plasma
Product: kwin
Version: 5.27.5
Platform: Debian stable
OS: Linux
St
https://bugs.kde.org/show_bug.cgi?id=478462
--- Comment #1 from steve ---
It affects chromium 119 and 120.0.6099.71,
In 120 it works if your pointerdown event is within about 100px of the edge of
the page (up from 20px)
to try that,
resize that page so the space above the ring is the same as
https://bugs.kde.org/show_bug.cgi?id=478462
--- Comment #2 from steve ---
it is for all pointerlock demos I can find or build, like this one:
https://www.smartjava.org/examples/pointerlock/
here's a video:
https://youtu.be/iK4VljDoVfg
the first drag locked, the second doesn't.
-
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #37 from Steve ---
Happy to try out the 6 RC packages Nate. I'll put a request into the current
release group on LQ to have the packages built and put into /testing.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453965
Bug ID: 453965
Summary: shhowFoto crashed
Product: digikam
Version: 7.6.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity:
https://bugs.kde.org/show_bug.cgi?id=445449
steve changed:
What|Removed |Added
CC||scal...@gmail.com
--- Comment #28 from steve ---
I
https://bugs.kde.org/show_bug.cgi?id=445449
--- Comment #31 from steve ---
(In reply to steve from comment #28)
> I also have this issue with Plasma 5.24.4 on Arch, using the wayland session
> and kernel 5.17.
Edit: I have found the most convenient workaround right now is to logout th
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #28 from steve ---
The qsocketnotifier error and indi disconnect seem to be precipitated after a
Sextract:
[2022-06-20T00:20:42.763 CEST DEBG ][ org.kde.kstars.ekos.guide] - Received
guide frame.
[2022-06-20T00:20:42.763 CEST DEBG
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #29 from steve ---
This is with the latest indi:
commit 3d63e3be5008605ce04621fb796f1a9b32c88a86 (HEAD -> master, origin/master,
origin/HEAD)
Author: Jasem Mutlaq
Date: Sat Jun 18 20:00:15 2022 +0300
Use IDSharedBlobAlloc
https://bugs.kde.org/show_bug.cgi?id=453937
steve changed:
What|Removed |Added
CC||scal...@gmail.com
--- Comment #10 from steve
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #30 from steve ---
Works OK with phd2 which does NOT call sextract.
Tested over 2 sessions of 5 hours guiding with phd2.
logs etc:
https://drive.google.com/drive/folders/1B-OOitN-K5OCmUHoXOgwCXh1Lq3ZPNiG?usp=sharing
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=452032
--- Comment #2 from steve ---
@Maik: Can you elaborate? Where woud a dark color theme be set?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452032
--- Comment #4 from steve ---
Wow! This is very unexpected. On macOS the shortcut to open Preferences is
`cmd,` which opens `Configure`. I wasn't even expected an additional settings
column in the menubar options. Think that is rather uncommon. A
https://bugs.kde.org/show_bug.cgi?id=452032
--- Comment #5 from steve ---
* no edit option: to automatically follow the system *theme default
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453937
--- Comment #13 from steve ---
One quick fix if you need it is to right click on the desktop icons>sort, and
sort the icons in anyway and it will refresh and remove the zombie icons.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #31 from steve ---
Hi everyone
This is fixed by turning off stellarsolver partitioning. The latter is now
default as of kstars 3.6.0
**does this count as RESOLVED?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452032
Bug ID: 452032
Summary: dark mode support on macOS
Product: digikam
Version: 7.6.0
Platform: Other
OS: macOS
Status: REPORTED
Severity: normal
Priority
https://bugs.kde.org/show_bug.cgi?id=453937
--- Comment #14 from steve ---
(In reply to steve from comment #10)
> Plasma 5.25.2, Arch linux and Arco linux, still happening.
Still happening in Plasma 5.25.3, arch and arco linux.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=443680
Bug ID: 443680
Summary: Export to PDF truncates page in landscape
Product: calligrasheets
Version: 3.2.1
Platform: Slackware Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=424935
Bug ID: 424935
Summary: Akonadi crashes/loops importing imap mail box
Product: Akonadi
Version: 5.13.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: grave
https://bugs.kde.org/show_bug.cgi?id=287708
--- Comment #8 from Steve ---
Yes, it's still there...I just tested it with ktorrent 5.2.0.
I right-click to ban a client, switch to another tab, and click on a torrent
with active leechers, and the right-click menu to kick/ban a client is graye
https://bugs.kde.org/show_bug.cgi?id=370448
Steve changed:
What|Removed |Added
CC||ulat...@yahoo.com
--- Comment #5 from Steve
.
-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
PID: 52370 (systemsettings)
UID: 1000 (steve)
GID: 1000 (steve)
Signal: 11 (SEGV)
Timestamp: Wed 2024-01-17 19:12:04 HST (27s ago)
Command Line: /usr/bin/systemsettings
https://bugs.kde.org/show_bug.cgi?id=473866
Steve changed:
What|Removed |Added
Attachment #161779|merkuro off my months and |merkuro off by months and
description|days
https://bugs.kde.org/show_bug.cgi?id=475862
Bug ID: 475862
Summary: software crashes for unknown reasons
Classification: Applications
Product: krita
Version: 5.2.0
Platform: Android
OS: Android 13.x
Status: REPO
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #29 from Steve ---
I just upgraded my kde packages with the hope that this bug would be fixed by
now. My hopes are dashed once again. The behavior still persists with the
following versions in slackware64 (current branch):
Core Desktop
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #28 from Steve ---
This is still an issue in 5.27.7. Although there seems to be new behavior - or
at least I didn't notice there was a timeout dependency before. On my setup I
can now cycle through my 3 other systems (via KVM Switch
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #25 from Steve ---
I can definitively state that in 5.27.5 this is only an issue with Plasma X11.
Wayland and Full Wayland on my Slackware64 distro (Current tree) do not exhibit
this behavior (bug) with Plasma shell - i.e. losing it&#
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #27 from Steve ---
I managed to find an installation image (.iso) from February 6th (2023). This
version of Slackware64 has the following KDE5 versions:
Core Desktop binaries: 5.26.5
Frameworks: 5.102.0
Applications: 22.12.2
I recently
https://bugs.kde.org/show_bug.cgi?id=378172
--- Comment #3 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377590
--- Comment #2 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377979
--- Comment #3 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377982
--- Comment #2 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448070
Bug ID: 448070
Summary: 2.0.18 - television stops working
Product: kaffeine
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: n
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: steve@gmail.com
Target Milestone: ---
Created attachment 129786
--> https://bugs.kde.org/attachment.cgi?id=129786&acti
https://bugs.kde.org/show_bug.cgi?id=423686
--- Comment #1 from steve ---
Created attachment 129787
--> https://bugs.kde.org/attachment.cgi?id=129787&action=edit
This log shows a correct align with the SYNC working.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423686
steve changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=399881
--- Comment #5 from Steve ---
I have upgraded through 4 major versions of kontact since then. Right now my
biggest problem is email I delete suddenly reappears 5 or 10 minutes later. I
suppose its not getting deleted in the imap server and it
https://bugs.kde.org/show_bug.cgi?id=430405
Bug ID: 430405
Summary: Print and Print Assistant Missing From Item Menu
Product: digikam
Version: 7.1.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
S
https://bugs.kde.org/show_bug.cgi?id=429628
Steve changed:
What|Removed |Added
CC||sbp...@protonmail.com
--- Comment #11 from Steve
https://bugs.kde.org/show_bug.cgi?id=492421
Bug ID: 492421
Summary: Brightness slider locked at 21%
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=492421
--- Comment #6 from steve ---
(In reply to steve from comment #5)
> Sorry, I AM thinking it is related to Nightlight.
After a few minutes of turning it back on, the slider sticks again and the
value it was set. Disabling Nightlight has no eff
https://bugs.kde.org/show_bug.cgi?id=492421
--- Comment #5 from steve ---
Sorry, I AM thinking it is related to Nightlight.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492421
--- Comment #8 from steve ---
(In reply to steve from comment #6)
> (In reply to steve from comment #5)
> > Sorry, I AM thinking it is related to Nightlight.
>
> After a few minutes of turning it back on, the slider sticks again and the
https://bugs.kde.org/show_bug.cgi?id=492421
--- Comment #7 from steve ---
(In reply to steve from comment #4)
> It started working again after a restart. Then it just stopped again but I
> am thinking that it is entirely related to something with Nightlight
> because it seems to happe
https://bugs.kde.org/show_bug.cgi?id=492421
--- Comment #4 from steve ---
It started working again after a restart. Then it just stopped again but I am
not thinking that it is entirely related to something with Nightlight because
it seems to happen when it activates. I disabled Nightlight, no
https://bugs.kde.org/show_bug.cgi?id=492421
--- Comment #2 from steve ---
(In reply to paninomaninodesu from comment #1)
> Can you give more information?
> How you try to adjust the brightness, exactly?
> Using the mouse wheel? Dragging the slider with the mouse? Do you use
> func
https://bugs.kde.org/show_bug.cgi?id=492421
--- Comment #10 from steve ---
Sorry, systemctl reboot. I disabled Nightlight also, and the problem hasn't
reoccurred.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377399
--- Comment #4 from Steve ---
I can't reproduce this with the current release. I needed help a long time ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453937
--- Comment #19 from steve ---
(In reply to Nate Graham from comment #18)
> This should be fixed in Plasma 5.27 (aka current git master) as of various
> ports and fixes.
Looking forward to February 2023 then. Recently it seems like it is creatin
https://bugs.kde.org/show_bug.cgi?id=412803
Bug ID: 412803
Summary: Pen Pressure creates blobs/circles along any and every
stroke
Product: krita
Version: 4.2.7
Platform: MS Windows
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=412803
--- Comment #2 from Steve ---
You are correct!
I changed in the settings to Win 8+ ink, restarted Krita, and it was working!
Thanks very much!
Now i can actually check this program out. :)
--
You are receiving this mail because:
You are watching all
1 - 100 of 998 matches
Mail list logo
