DICOM module not working when used as startup module

Support
1

Hi everyone,

Overnight, the DICOM module has stopped working, see attached screenshot. I am seeing this error, too

Traceback (most recent call last):
File “/Applications/Slicer.app/Contents/lib/Slicer-4.11/qt-scripted-modules/DICOM.py”, line 678, in exit
self.browserWidget.close()
AttributeError: ‘NoneType’ object has no attribute ‘close’

I have updated to the most recent stable build and the behavior is persisting. Interestingly, the behavior is not replicated when Slicer is opened for other users on the same computer.

Any help would be greatly appreciated!

Jamie

Screen Shot 2021-11-03 at 10.34.12 AM
Screen Shot 2021-11-03 at 10.34.12 AM1367×879 84.1 KB

2

İs it possible that you modified your DICOM db location? The location shown in screenshot doesn’t seem right. And i think that setting carries over from versions.

3

Probably something got broken in the settings. These documents should help. If it happens again let us know if you figure out what led to the issue so we can reproduce.

https://slicer.readthedocs.io/en/latest/user_guide/settings.html?highlight=settings#settings-file-location

4

I reset the Application Settings (DICOM module was set as the default module on open) and it works like a charm now! Thank you so much for your speedy solution!

Jamie

5

It’s very possible, I discovered that the behavior resolved when I stopped using DICOM as the default module on open.

6

Setting the DICOM module as startup module can be very useful and I see that currently an error is thrown if you do this. I’ll fix this error tomorrow.

1 Like
7

Great! Thank you very much, it would be very helpful to have the DICOM module as default!

8

The fix will be available in the Slicer Preview Release from tomorrow.