Bug#753809: ginkgocadx: will not display studies
Hi Karsten, thanks for your continuous attempts to help fixing this bug. I have uploaded a new upstream version yesterday to experimental. May be you can give it a try and see whether the issue might be fixed? Thanks for your patience Andreas. On Mon, Jan 12, 2015 at 12:10:59PM +0100, Karsten Hilbert wrote: On Mon, Jan 12, 2015 at 11:39:47AM +0100, Karsten Hilbert wrote: Attached find a DICOM file which, for me, shows the problem and the TRACE log of Ginkgo CADx reading that file. Here's a much better log, voided of all unnecessary clutter. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 2015/01/12 12:08:54.645 [2910259456] INFO Core - Starting Ginkgo CADx 3.7.0.1465.37 32 bits 2015/01/12 12:08:57.307 [2910259456] DEBUG WindowAttributes - Client area X: 0, 1366 Y: 0, 768 2015/01/12 12:08:57.307 [2910259456] DEBUG WindowAttributes - 2015/01/12 12:08:59.106 [2910259456] TRACE SmartRetrieve - SmartRetrieveController has been disabled ... -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
On Mon, Jan 12, 2015 at 11:39:47AM +0100, Karsten Hilbert wrote: Attached find a DICOM file which, for me, shows the problem and the TRACE log of Ginkgo CADx reading that file. Here's a much better log, voided of all unnecessary clutter. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 2015/01/12 12:08:54.645 [2910259456] INFO Core - Starting Ginkgo CADx 3.7.0.1465.37 32 bits 2015/01/12 12:08:57.307 [2910259456] DEBUG WindowAttributes - Client area X: 0, 1366 Y: 0, 768 2015/01/12 12:08:57.307 [2910259456] DEBUG WindowAttributes - 2015/01/12 12:08:59.106 [2910259456] TRACE SmartRetrieve - SmartRetrieveController has been disabled 2015/01/12 12:09:09.987 [2910259456] DEBUG WindowAttributes - Client area X: 0, 1366 Y: 0, 768 2015/01/12 12:09:09.987 [2910259456] DEBUG WindowAttributes - 2015/01/12 12:09:10.288 [2910259456] TRACE ControladorCarga - Se invoca el iniciar pipeline de la vista 2015/01/12 12:09:10.289 [2910259456] INFO Core/HL7 - HL7-Sender wurde gestartet 2015/01/12 12:09:15.809 [2910259456] DEBUG dcmtk.dcmdata - DcmItem::checkTransferSyntax() TransferSyntax=Little Endian Explicit 2015/01/12 12:09:15.809 [2910259456] TRACE dcmtk.dcmdata - DcmMetaInfo::checkAndReadPreamble() Preamble = 0x 2015/01/12 12:09:15.809 [2910259456] TRACE dcmtk.dcmdata - DcmMetaInfo::checkAndReadPreamble() TransferSyntax=Little Endian Explicit 2015/01/12 12:09:15.811 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,) VR=UL at beginning inserted 2015/01/12 12:09:15.812 [2910259456] TRACE dcmtk.dcmdata - DcmMetaInfo::readGroupLength() Group Length of File Meta Header = 228 2015/01/12 12:09:15.812 [2910259456] TRACE dcmtk.dcmdata - DcmMetaInfo::readGroupLength() returns error = Normal 2015/01/12 12:09:15.812 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0001) VR=OB inserted 2015/01/12 12:09:15.812 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0002) VR=UI inserted 2015/01/12 12:09:15.812 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0003) VR=UI inserted 2015/01/12 12:09:15.812 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0010) VR=UI inserted 2015/01/12 12:09:15.813 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0012) VR=UI inserted 2015/01/12 12:09:15.813 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0013) VR=SH inserted 2015/01/12 12:09:15.813 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0016) VR=AE inserted 2015/01/12 12:09:15.813 [2910259456] TRACE dcmtk.dcmdata - DcmItem::searchSubFromHere() Element (0002,0010) found 2015/01/12 12:09:15.813 [2910259456] TRACE dcmtk.dcmdata - DcmFileFormat::lookForXfer() TransferSyntax=Little Endian Implicit in MetaInfo 2015/01/12 12:09:15.813 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0002,0003) VR=UI at beginning inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,) VR=UL inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0005) VR=CS inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0008) VR=CS inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0016) VR=UI inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0018) VR=UI inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0020) VR=DA inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0021) VR=DA inserted 2015/01/12 12:09:15.814 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0022) VR=DA inserted 2015/01/12 12:09:15.815 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0023) VR=DA inserted 2015/01/12 12:09:15.815 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0030) VR=TM inserted 2015/01/12 12:09:15.815 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0031) VR=TM inserted 2015/01/12 12:09:15.815 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0032) VR=TM inserted 2015/01/12 12:09:15.815 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0033) VR=TM inserted 2015/01/12 12:09:15.815 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0050) VR=SH inserted 2015/01/12 12:09:15.816 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0060) VR=CS inserted 2015/01/12 12:09:15.816 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0070) VR=LO inserted 2015/01/12 12:09:15.816 [2910259456] TRACE dcmtk.dcmdata - DcmItem::insert() Element (0008,0080) VR=LO inserted 2015/01/12 12:09:15.816 [2910259456] TRACE dcmtk.dcmdata -
Bug#753809: Re: Bug#753809: ginkgocadx: will not display studies
On Tue, Dec 16, 2014 at 10:08 PM, Karsten Hilbert karsten.hilb...@gmx.net wrote: On Wed, Nov 26, 2014 at 11:40:02PM +0100, Karsten Hilbert wrote: Is there any news regarding this bug ? It is rather serious: Because of this bug Ginkgo CADx is rather useless for serious clinical care on Debian. I admit I feel helpless about this issue. However, if you think that this issue is serious than you should tag the bug that way to make more people aware of it. The consequence would be that ginkgocadx will not be released with Jessie if it will not be fixed. I keep upstream in CC (Carlos, feel free to read the whole story here [1]). Here is the only technical information in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753809#15 [...] We found many issues in GDCM 2.x which is provided with debian bundled ITK version. [...] AFAIR ITK/GDCM upstream has been fairly reluctant to apply patches. [...] What exactly do you expect from me ? Please stop CCing me on FUDs. I've happily applied patch for better integration of current ITK and GDCM see recent changelog, so stop saying things like fairly reluctant, or at least include the context. As for the so-called many issues in GDCM 2.x, please include actual details to reproduce them. Mathieu, what do you expect me to do other than the following ? 1) supply a detailed explanation of how to reproduce the problem I did. Did you try to reproduce the problem ? Let's summarize it (as I see it). You found a bug in A (ginkgocadx), which uses B (ITK) which in turns uses C (GDCM). Upstream for A says: this is not our fault it is somewhere in B or C. I believe somewhere in between A or B there is a missing link to report *exactly* what is wrong with C. You've gently reported a bug report for A, they confirmed this is a bug, and even confirmed the bug is somewhere in B or C. I am not going to re-do the above work, because I've never used A, and upstream for A was very precise in saying that the bug was in B or C. In summary yes I expect a bug report for C to be somewhat minimalist, but don't ask me to use A - B - C to dig a bug somewhere in A. The chain as I see it is that either someone from A or B is capable of reporting a reduced test case for C. -M -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
Hi Mathieu, On Wed, Dec 17, 2014 at 09:05:34AM +0100, Mathieu Malaterre wrote: I am not going to re-do the above work, because I've never used A, To explain why I CCed you in the first place: I simply kept those people I consider competent to solve a problem concerning medical imaging in the row. I personally fixed bugs in 100 packages I never used and I was simply hoping that our team is strong enough to solve serious issues even if the actual team member does not see a direct connection to the own work. I did not wanted to imply that the problem is caused by one of the packages you are usually maintaining and feel responsible for. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: Re: Bug#753809: ginkgocadx: will not display studies
Hello Mathieu, thanks for continuing to have a useful discussion. You found a bug in A (ginkgocadx), That is correct - in a way. I found a bug when using A on Debian. I then went upstream and used their static binary of A compiled for Debian. That binary worked. This meant that the bug lies in the Debian variant of A. Nevertheless I reported the bug to A-upstream because just because it doesn't happen in upstream doesn't mean it doesn't _exist_ in upstream. which uses B (ITK) which in turns uses C (GDCM). Upstream for A says: this is not our fault it is somewhere in B or C. I agree with you here. I would assume upstream decided that they don't want to afford searching for a bug in a non-upstream variant of their code. Good or bad -- it is their decision. I believe somewhere in between A or B there is a missing link to report *exactly* what is wrong with C. You are correct. That missing link would probably be me because I am a user who wants to use A but in conjunction with a version of B and/or C which A-upstream doesn't directly support. However, I lack the skills to nail the problem myself. Therefore I went A-upstream and asked for details. I then reported what I got as a response. I agree this response would be a lot more helpful if A-upstream pointed out the exact issues they had with in-Debian B and/or C. In summary yes I expect a bug report for C to be somewhat minimalist, but don't ask me to use A - B - C to dig a bug somewhere in A. The chain as I see it is that either someone from A or B is capable of reporting a reduced test case for C. So, in effect, A (or me equipped with information gotten from A) should report a bug against B (ITK). Then B (or me, equipped with information gotten from B) would report a bug against C (GDCM). Or else A would provide information on the exact problem against C in which case B can be skipped. Now, since A doesn't seem to afford the resources to help us find bugs in our use of their code I guess we are stuck. In short: Debian doesn't have a DICOM viewer suitable for clinical care. Which is a great pity. BTW: I do acknowledge that Dmitry has at least tried to reproduce the problem. BTWBTW: I also know that all of you guys volunteer your time. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
Hi Karsten, On Wed, Nov 26, 2014 at 11:40:02PM +0100, Karsten Hilbert wrote: Is there any news regarding this bug ? It is rather serious: Because of this bug Ginkgo CADx is rather useless for serious clinical care on Debian. I admit I feel helpless about this issue. However, if you think that this issue is serious than you should tag the bug that way to make more people aware of it. The consequence would be that ginkgocadx will not be released with Jessie if it will not be fixed. I keep upstream in CC (Carlos, feel free to read the whole story here [1]). Kind regards Andreas. [1] https://bugs.debian.org/753809 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
On Tue, Dec 16, 2014 at 11:48 AM, Andreas Tille andr...@an3as.eu wrote: Hi Karsten, On Wed, Nov 26, 2014 at 11:40:02PM +0100, Karsten Hilbert wrote: Is there any news regarding this bug ? It is rather serious: Because of this bug Ginkgo CADx is rather useless for serious clinical care on Debian. I admit I feel helpless about this issue. However, if you think that this issue is serious than you should tag the bug that way to make more people aware of it. The consequence would be that ginkgocadx will not be released with Jessie if it will not be fixed. I keep upstream in CC (Carlos, feel free to read the whole story here [1]). Here is the only technical information in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753809#15 [...] We found many issues in GDCM 2.x which is provided with debian bundled ITK version. [...] AFAIR ITK/GDCM upstream has been fairly reluctant to apply patches. [...] What exactly do you expect from me ? Please stop CCing me on FUDs. I've happily applied patch for better integration of current ITK and GDCM see recent changelog, so stop saying things like fairly reluctant, or at least include the context. As for the so-called many issues in GDCM 2.x, please include actual details to reproduce them. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: Aw: Re: Bug#753809: ginkgocadx: will not display studies
On Wed, Nov 26, 2014 at 11:40:02PM +0100, Karsten Hilbert wrote: Is there any news regarding this bug ? It is rather serious: Because of this bug Ginkgo CADx is rather useless for serious clinical care on Debian. I admit I feel helpless about this issue. However, if you think that this issue is serious than you should tag the bug that way to make more people aware of it. The consequence would be that ginkgocadx will not be released with Jessie if it will not be fixed. I keep upstream in CC (Carlos, feel free to read the whole story here [1]). Here is the only technical information in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753809#15 [...] We found many issues in GDCM 2.x which is provided with debian bundled ITK version. [...] AFAIR ITK/GDCM upstream has been fairly reluctant to apply patches. [...] What exactly do you expect from me ? Please stop CCing me on FUDs. I've happily applied patch for better integration of current ITK and GDCM see recent changelog, so stop saying things like fairly reluctant, or at least include the context. As for the so-called many issues in GDCM 2.x, please include actual details to reproduce them. Mathieu, what do you expect me to do other than the following ? 1) supply a detailed explanation of how to reproduce the problem I did. Did you try to reproduce the problem ? 2) contact upstream I did. 3) relay upstreams response I did. 3) test upstream code I did. It worked. 4) test other software to try to isolate the problem I did. Aeskulap worked. So it doesn't seem to be Orthanc. 5) ping every once in a while to reconfirm the problem and ask for status I did. I lack the skillset to dig into the code. Would you like me to stop providing problem reports to the level of detail I can manage ? For what it is worth: This problem certainly IS serious but I have refrained from marking the report as such because I humbly accept the possibility that the severity may somehow be constrained to my system or setup or whatnot and that the package might work for other people (after all, it does display some instances of studies when loaded from CD-ROM for the first time). Hence I don't think it warrants tagging as serious such as to facilitate exclusion from next Debian/Stable. Have you tried to reproduce the problem ? If so, did you succeed or fail to reproduce it ? If you failed to reproduce it what other information do you need ? Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
Is there any news regarding this bug ? It is rather serious: Because of this bug Ginkgo CADx is rather useless for serious clinical care on Debian. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
On Sun, Sep 21, 2014 at 10:41:54AM +1000, Dmitry Smirnov wrote: Could you please help me to reproduce this problem? I can successfully open bunch of dicom files I have as well as anything from Ginkgo cloud. I'm not as familiar with ginkgocadx interface as you are so I will need a detailed how-to instructions what to do to hit the problem. No problem. It only seems to appear when using a DICOM server (say, Orthanc). This is my workflow to reproduce the problem: - open Ginkgo - open a DICOM (.dcm) file which has not been viewed in Ginkgo before - Ginkgo will happily display this file - in Ginkgo upload the file to the DICOM server At this stage, other DICOM viewers (say, Aeskulap) will happily retrieve the file from the DICOM server _and_ gladly display it. - in Gingko remove the file from the viewing history - in Ginkgo query the DICOM server for the study (the DICOM file) you just uploaded - in Ginkgo download the DICOM file from the DICOM server - Ginkgo now fails to create a thumbnail and also fails to display the DICOM file after download despite having properly displayed it before Note that it IS possible to download the very same file from the very same DICOM server and properly display it using _another_ DICOM viewer (say, Aeskulap). In other words, the failure does NOT depend on the DICOM server. I also tried the following: - at the filesystem level copy the downloaded-and-failing-to-display DICOM file to another directory - in Ginkgo remove the failing file from the history - in Ginkgo open the copied file (which previously failed after the download) as if it was a new file - Ginkgo _still_ fails to display the file This means, that something permanent is being done to the file when Ginkgo first downloads it from the DICOM server. Note that other DICOM viewers (Aeskulap) gladly display the copy (which, again, still fails in Ginkgo). _Very_ strange. And frustrating :-) Karsten -- GPG key ID E4071346 @ gpg-keyserver.de E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: Aw: Re: Bug#753809: ginkgocadx: will not display studies
Hi ! Ginkgo CADx 3.6.1 does not display a whole range of studies which it did display before. I just uploaded 3.7.0.1465.37 to unstable so it would be nice if you could try it to check if this problem is fixed. As far as I can test it seems to be working. Please confirm. I will install and report back tonight. Thanks to everyone involved, Olly, Dmitry, Carlos ! Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
On Sat, Sep 20, 2014 at 03:09:19PM +1000, Dmitry Smirnov wrote: Ginkgo CADx 3.6.1 does not display a whole range of studies which it did display before. I just uploaded 3.7.0.1465.37 to unstable so it would be nice if you could try it to check if this problem is fixed. As far as I can test it seems to be working. Please confirm. Unfortunately, GinkgoCADx still does not display any studies. Attached find a log created by opening a DICOM file from the history which had been downloaded from the DICOM server and which DID display in Ginkgo CADx before it was uploaded. It still does display in, say, Aeskulap :-( Karsten -- GPG key ID E4071346 @ gpg-keyserver.de E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
On Sat, Sep 20, 2014 at 08:11:39PM +0200, Karsten Hilbert wrote: Ginkgo CADx 3.6.1 does not display a whole range of studies which it did display before. I just uploaded 3.7.0.1465.37 to unstable so it would be nice if you could try it to check if this problem is fixed. As far as I can test it seems to be working. Please confirm. Unfortunately, GinkgoCADx still does not display any studies. Attached find a log created by opening a DICOM file from the history which had been downloaded from the DICOM server and which DID display in Ginkgo CADx before it was uploaded. It still does display in, say, Aeskulap :-( That is to say that in Aeskulup it both displays when a) downloaded from the same DICOM server as Ginkgo did b) grabbed from the Ginkgo DICOM directory after _Ginkgo_ downloaded the file That pretty much proves that the problem neither lies with the DICOM server nor with the _retrieval/storage only_ done by Ginkgo. Karsten -- GPG key ID E4071346 @ gpg-keyserver.de E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
Hi Karsten, Could you please help me to reproduce this problem? I can successfully open bunch of dicom files I have as well as anything from Ginkgo cloud. I'm not as familiar with ginkgocadx interface as you are so I will need a detailed how-to instructions what to do to hit the problem. Thank you. -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Bug#753809: ginkgocadx: will not display studies
Dear Karsten, On Sat, 5 Jul 2014 12:51:12 Karsten Hilbert wrote: Ginkgo CADx 3.6.1 does not display a whole range of studies which it did display before. I just uploaded 3.7.0.1465.37 to unstable so it would be nice if you could try it to check if this problem is fixed. As far as I can test it seems to be working. Please confirm. Thank you. -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B --- What can be asserted without proof can be dismissed without proof. -- Christopher Hitchens, 2004 signature.asc Description: This is a digitally signed message part.
Bug#753809: ginkgocadx: will not display studies
Package: ginkgocadx Version: 3.6.1.1367.34+dfsg-1 Severity: important Ginkgo CADx 3.6.1 does not display a whole range of studies which it did display before. Upstream tells me this is a problem with GDCM/ITK not being patched on Debian (as opposed to upstream's internal version which works fine) so I am putting this bug here so we don't forget. The severity lies in patients sitting at my desk wanting to know about their imaging results. Karsten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ginkgocadx depends on: ii libc6 2.19-4 ii libcairo2 1.12.16-2 ii libcurl3-gnutls 7.37.0-1+b1 ii libdcmtk2 3.6.0-15+b1 ii libgcc1 1:4.9.0-7 ii libgl1-mesa-glx [libgl1] 10.2.1-2 ii libgtk2.0-0 2.24.24-1 ii libinsighttoolkit3.20 3.20.1+git20120521-5 ii libjsoncpp0 0.6.0~rc2-3 ii libsqlite3-0 3.8.5-2 ii libssl1.0.0 1.0.1h-3 ii libstdc++64.9.0-7 ii libvtk5.8 5.8.0-17.3 ii libwxbase3.0-03.0.1-2 ii libwxgtk3.0-0 3.0.1-2 ginkgocadx recommends no packages. ginkgocadx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: Potential problem with GDCM/ITK (Was: Bug#753809: ginkgocadx: will not display studies)
Hi Karsten, could you please quote the full upstream mail about the GDCM/ITK issue? It would make more sense to apply the patch to GDCM/ITK upstream if it is needed / helpful to display a whole range of studies. Moreover it would be helpful to provide some example study which shows the problem. Perhaps you could upload an anonymised test case to some place? Kind regards Andreas. On Sat, Jul 05, 2014 at 12:51:12PM +0200, Karsten Hilbert wrote: Package: ginkgocadx Version: 3.6.1.1367.34+dfsg-1 Severity: important Ginkgo CADx 3.6.1 does not display a whole range of studies which it did display before. Upstream tells me this is a problem with GDCM/ITK not being patched on Debian (as opposed to upstream's internal version which works fine) so I am putting this bug here so we don't forget. The severity lies in patients sitting at my desk wanting to know about their imaging results. Karsten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ginkgocadx depends on: ii libc6 2.19-4 ii libcairo2 1.12.16-2 ii libcurl3-gnutls 7.37.0-1+b1 ii libdcmtk2 3.6.0-15+b1 ii libgcc1 1:4.9.0-7 ii libgl1-mesa-glx [libgl1] 10.2.1-2 ii libgtk2.0-0 2.24.24-1 ii libinsighttoolkit3.20 3.20.1+git20120521-5 ii libjsoncpp0 0.6.0~rc2-3 ii libsqlite3-0 3.8.5-2 ii libssl1.0.0 1.0.1h-3 ii libstdc++64.9.0-7 ii libvtk5.8 5.8.0-17.3 ii libwxbase3.0-03.0.1-2 ii libwxgtk3.0-0 3.0.1-2 ginkgocadx recommends no packages. ginkgocadx suggests no packages. -- no debconf information ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: Potential problem with GDCM/ITK (Was: Bug#753809: ginkgocadx: will not display studies)
On Sat, Jul 05, 2014 at 05:32:32PM +0200, Andreas Tille wrote: could you please quote the full upstream mail about the GDCM/ITK issue? Sure: Date: Fri, 4 Jul 2014 23:28:02 +0200 From: Carlos Barrales Ruiz carlos.barra...@metaemotion.com To: Karsten Hilbert karsten.hilb...@gmx.net Subject: Re: assert() failed Hi, Karsten. ... Regarding the study in your other mails… the error seems to occur internally, in the pixel data reading stage which is performed by the irk version of GDCM. We found many issues in GDCM 2.x which is provided with debian bundled ITK version. Please, try to open the study with our compiled ginkgo cadx 3.7.0, just to discard the problem is there. ... Thank you. Best regards. -- Carlos Barrales Ruiz carlos.barra...@metaemotion.com [+34] 983 108 494 MetaEmotion Edificio CTTA. Módulos 119-122. Paseo de Belén, nº9. E47011. Valladolid. Spain. www.metaemotion.com But that won't help :-) I would think Matthieu (sp?) knows more. It would make more sense to apply the patch to GDCM/ITK upstream if it is needed / helpful to display a whole range of studies. AFAIR ITK/GDCM upstream has been fairly reluctant to apply patches. Karsten -- GPG key ID E4071346 @ gpg-keyserver.de E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
