Krita 5.2 rc1: error at startup

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 =
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 =
doc = ‘Inappropriate argument type.’
eq = <method-wrapper ‘eq’ of TypeError object>
format =
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 =
le = <method-wrapper ‘le’ of TypeError object>
lt = <method-wrapper ‘lt’ of TypeError object>
ne = <method-wrapper ‘ne’ of TypeError object>
new =
reduce =
reduce_ex =
repr = <method-wrapper ‘repr’ of TypeError object>
setattr = <method-wrapper ‘setattr’ of TypeError object>
setstate =
sizeof =
str = <method-wrapper ‘str’ of TypeError object>
subclasshook =
suppress_context = False
traceback =
args = (“addMSecs(self, int): argument 1 has unexpected type ‘float’”,)
with_traceback =

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?

Thanks

Your post would have fit better in the Krita 5.2 Release Candidate topic, then you would have seen immediately where your problem is, and also that it is known as well as not being fixed for now, and also why it is not being fixed for now.

And if you think now, I don’t use Pigment.O, but Imagine Board, both plugins are from @EyeOdin, ergo…

If you install the current stable version, then the plugin will work as expected.

Michelist

@AhabGreybeard, @sooz, @raghukamath, I guess it could be good to move this topic to the Krita 5.2 Release Candidate topic, please decide.

2 Likes

A post was merged into an existing topic: Krita 5.2 Release Candidate is out! Please help us in another round of testing!