Are you using the Pigment.O plugin? If you are, the developer @EyeOdin said in this post to uninstall the plugin before updating to Krita 5.2 as the new python version breaks the plugin and there hasenāt been a bug fix for it yet. The creator also stated all bug reports pertaining to that will be ignored.
Last month I got a new PC, and I installed the beta of 5.2 on it. I made a backup of my resources folder and Kritarc file. I placed those back on my new PC and Krita works fine, with all my settings intact.
Except I get an error at each startup:
An exception occurred while running the script.
TypeError: addMSecs(self, int): argument 1 has unexpected type 'float'
TypeError
Python 3.10.7: C:\Program Files\Krita (x64)\bin\krita.exe
Wed Sep 20 11:21:14 2023
A problem occurred in a Python script. Here is the sequence of
function calls leading up to the error, in the order they occurred.
C:\Program Files\Krita (x64)\lib\krita-python-libs\krita\dockwidgetfactory.py in createDockWidget(self=<krita.dockwidgetfactory.DockWidgetFactory object>)
14 super(DockWidgetFactory, self).__init__(_id, _dockPosition)
15 self.klass = _klass
16
17 def createDockWidget(self):
18 return self.klass()
self = <krita.dockwidgetfactory.DockWidgetFactory object>
self.klass = <class 'imagine_board.imagine_board_docker.ImagineBoard_Docker'>
C:\Users\Gremr\AppData\Roaming\krita\pykrita\imagine_board\imagine_board_docker.py in __init__(self=<imagine_board.imagine_board_docker.ImagineBoard_Docker object>)
96 self.Style()
97 self.Extension()
98 self.Settings()
99
100 def Variables(self):
self = <imagine_board.imagine_board_docker.ImagineBoard_Docker object>
self.Settings = <bound method ImagineBoard_Docker.Settings of <i...imagine_board_docker.ImagineBoard_Docker object>>
C:\Users\Gremr\AppData\Roaming\krita\pykrita\imagine_board\imagine_board_docker.py in Settings(self=<imagine_board.imagine_board_docker.ImagineBoard_Docker object>)
420 Krita.instance().writeSetting("Imagine Board", "slideshow_time", str(1000) )
421 else:
422 tempo = QTime(0,0,0).addMSecs(float(ms))
423 self.dialog.menu_slideshow_time.setTime(tempo)
424 # Grid U
tempo undefined
global QTime = <class 'PyQt5.QtCore.QTime'>
).addMSecs = <built-in function addMSecs>
builtinfloat = <class 'float'>
ms = '1000'
TypeError: addMSecs(self, int): argument 1 has unexpected type 'float'
__cause__ = None
__class__ = <class 'TypeError'>
__context__ = None
__delattr__ = <method-wrapper '__delattr__' of TypeError object>
__dict__ = {}
__dir__ = <built-in method __dir__ of TypeError object>
__doc__ = 'Inappropriate argument type.'
__eq__ = <method-wrapper '__eq__' of TypeError object>
__format__ = <built-in method __format__ of TypeError object>
__ge__ = <method-wrapper '__ge__' of TypeError object>
__getattribute__ = <method-wrapper '__getattribute__' of TypeError object>
__gt__ = <method-wrapper '__gt__' of TypeError object>
__hash__ = <method-wrapper '__hash__' of TypeError object>
__init__ = <method-wrapper '__init__' of TypeError object>
__init_subclass__ = <built-in method __init_subclass__ of type object>
__le__ = <method-wrapper '__le__' of TypeError object>
__lt__ = <method-wrapper '__lt__' of TypeError object>
__ne__ = <method-wrapper '__ne__' of TypeError object>
__new__ = <built-in method __new__ of type object>
__reduce__ = <built-in method __reduce__ of TypeError object>
__reduce_ex__ = <built-in method __reduce_ex__ of TypeError object>
__repr__ = <method-wrapper '__repr__' of TypeError object>
__setattr__ = <method-wrapper '__setattr__' of TypeError object>
__setstate__ = <built-in method __setstate__ of TypeError object>
__sizeof__ = <built-in method __sizeof__ of TypeError object>
__str__ = <method-wrapper '__str__' of TypeError object>
__subclasshook__ = <built-in method __subclasshook__ of type object>
__suppress_context__ = False
__traceback__ = <traceback object>
args = ("addMSecs(self, int): argument 1 has unexpected type 'float'",)
with_traceback = <built-in method with_traceback of TypeError object>
The above is a description of an error in a Python program. Here is
the original traceback:
Traceback (most recent call last):
File "C:\Program Files\Krita (x64)\lib\krita-python-libs\krita\dockwidgetfactory.py", line 18, in createDockWidget
return self.klass()
File "C:\Users\Gremr\AppData\Roaming\krita\pykrita\imagine_board\imagine_board_docker.py", line 98, in __init__
self.Settings()
File "C:\Users\Gremr\AppData\Roaming\krita\pykrita\imagine_board\imagine_board_docker.py", line 422, in Settings
tempo = QTime(0,0,0).addMSecs(float(ms))
TypeError: addMSecs(self, int): argument 1 has unexpected type 'float'
I have no extra scripts installed, but I did have some on my old machine, but I canāt remember which ones.
I did rename Kritarc, and Krita started up with no errors. So my guess is there is something in the Kritarc file that tries to look for a script.
I have no idea what to look for, and I would prefer to not have to set up Krita again.
Is there a way to fix this without reverting to the default Kritarc?
The errorās being caused by the Imagine Board plugin needing to be updated for 5.2. You can disable the plugin from Preferences->Python Plugin Manager.
(The setting to change in kritarc would be
[python]
enable_imagine_board=true
, to false.)
When you copied your resource folder, you also copied your plugins. Theyāre in the pykrita subfolder.
There was a post that indicated that the API was changed in 5.2 and it broke some plugins, so I removed all the plugins I installed in my pykrita folder and kept the ones that are already in Krita.
It seems 5.2 wont be pushed for android as that bug was halting all other platforms version. Which sucks but its really getting difficult to debug partly because devs dont have that kind of device and logs are not showing much
The problem is none of the developers have been able to reproduce that issue. That makes it very, very difficult to figure out whatās causing it and how to fix it, as itās seemingly random and device/setup specific, with no useful information in the crashlog.
Until someone can pinpoint the cause, by figuring out how changing user fixes it, or throwing a debugger at it, or bisecting it, itās unlikely to be fixed, unfortunately. And until someone has any idea how to fix it, making the release wait on a fix wouldnāt accomplish much.
Was so excited to be using the 5.2 Release Candidate and was loving that it hadnāt crashed on me for several daysā¦until just recently.
Now Iām afraid it just randomly crashes. I could be in the middle of drawing, changing settings, staring at a layer and it will crash.
Tried clearing cache, clearing entire data, uninstalling completely and reinstallingā¦several times, and it seems to actually get worse instead of better.
On Galaxy Tab s9 Ultra.
Iām gonna be one sad panda if the android version doesnāt get released at the same time as the other OSās. I was getting so excited using this with all the updates.
Im using Huion Kamvas 22 plus stylus and Krita rc2 portable from zip [also the latest nightly] , whenever i start it my stylus doesnt register on all dockers, menu bars etcā¦ but works on the canvas and the tablet tester. mouse works fine there too.
I also tested with all plugins off just to be sure its not any plugins messing up. Will try again this afternoon.
i tested and opened my 5.1.5 krita and it works fine there.
This is kind of the gist, developers dont have a device with the said issue and we as a user are not able to help enough to do an RCA.
The new user stability is a shocker which could mean something is clashing with krita in regular user which should be unlikely because all apps on android are container based
The render animation does not remember the last render settings. Every time I open it, it defaults to render as mkv, and if I need to render as gif multiple times, I have to change to render as gif multiple times.
I have the same pen display and no problems here with the stylus. But Iām still on RC1. Are you using the latest Huion driver? Maybe try the device diagnosis feature of the driver?
still not working in RC2, now im suspecting maybe its the windows update that happened after my pc boot up yesterday after it shutdown due to power outage.
weird that its only on RC2, current nightly happening. Other wise pen is ok on the canvas and table tester but just canāt seem to work on the dockers and menus.
Sorry Iām confusing myself. I have RC2 installed and my pen display/stylus is working normally. I experienced problems with toolbars and dockers in the beta releases. It seemed that they had addressed some of that with the latest RC2. The stuff Iām seeing now is clearly program related. I mentioned it earlier up the list but the Tool Options docker is missing completely. I understand theyāre working on itā¦
Couple minor things about the Welcome/Opening screen. I like where itās going. Butā¦
That begging for money advert at the topā¦ of course you should donate, but if weāre already donating on a monthly basis can that be removed please?
The latest project tilesā¦ when you click on one, the one you want to open, they all get highlighted. Thatās been going on since before 5.2
There used to be a ādrag image hereā notification box in that same area. Yes you can still drag images into the middle section but itās confusing to newbies. It was to me when I first opened the beta ver.
