Is this KIO error significant/important?

[Chris Green]

When I start digikam from a terminal window I see the following at the
end of the start up messages:-

    digikam: ImagePlugin_Core plugin loaded
    digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
    digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg : JPEG file identified
    kio (KIOConnection): ERROR: Could not write data
    digikam: Found JPEGLossless plugin
    digikam: Transforming with option 0 5
    digikam: No EXIF information found.

Is that kio error significant or important?

--
Chris Green ([hidden email])
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 06 December 2006 11:36, [hidden email] wrote:

> When I start digikam from a terminal window I see the following at the
> end of the start up messages:-
>
>     digikam: ImagePlugin_Core plugin loaded
>     digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
>     digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg : JPEG
> file identified kio (KIOConnection): ERROR: Could not write data
>     digikam: Found JPEGLossless plugin
>     digikam: Transforming with option 0 5
>     digikam: No EXIF information found.
>
> Is that kio error significant or important?

yes. try RC2 or current implementation from svn. it's fixed.

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Chris Green]

On Wed, Dec 06, 2006 at 11:32:26AM +0100, Gilles Caulier wrote:

> On Wednesday 06 December 2006 11:36, [hidden email] wrote:
> > When I start digikam from a terminal window I see the following at the
> > end of the start up messages:-
> >
> >     digikam: ImagePlugin_Core plugin loaded
> >     digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
> >     digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg : JPEG
> > file identified kio (KIOConnection): ERROR: Could not write data
> >     digikam: Found JPEGLossless plugin
> >     digikam: Transforming with option 0 5
> >     digikam: No EXIF information found.
> >
> > Is that kio error significant or important?
>
> yes. try RC2 or current implementation from svn. it's fixed.
>

OK, thanks, I've got RC2 installed now, and I'm still getting the
message:-

    KIPI (loading): Loaded RawConverter
    KIPI (loading): KIPI::PluginLoader: Loaded plugin RawConverter
    digikam: ImagePlugin_Core plugin loaded
    digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
    digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg : JPEG file identified
    kio (KIOConnection): ERROR: Could not write data

I haven't installed the Kipi plugins 1.3 beta yet (see other thread),
would this be relevant?  I'm also running this across an ssh
connection from a (very) remote machine, i.e. digikam is a machine at
home and I'm doing all this from work, might that affect things if the
X permissions aren't exactly right?

--
Chris Green ([hidden email])
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 06 December 2006 12:41, [hidden email] wrote:

> On Wed, Dec 06, 2006 at 11:32:26AM +0100, Gilles Caulier wrote:
> > On Wednesday 06 December 2006 11:36, [hidden email] wrote:
> > > When I start digikam from a terminal window I see the following at the
> > > end of the start up messages:-
> > >
> > >     digikam: ImagePlugin_Core plugin loaded
> > >     digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
> > >     digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg :
> > > JPEG file identified kio (KIOConnection): ERROR: Could not write data
> > > digikam: Found JPEGLossless plugin
> > >     digikam: Transforming with option 0 5
> > >     digikam: No EXIF information found.
> > >
> > > Is that kio error significant or important?
> >
> > yes. try RC2 or current implementation from svn. it's fixed.
>
> OK, thanks, I've got RC2 installed now, and I'm still getting the
> message:-
>
>     KIPI (loading): Loaded RawConverter
>     KIPI (loading): KIPI::PluginLoader: Loaded plugin RawConverter
>     digikam: ImagePlugin_Core plugin loaded
>     digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
>     digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg : JPEG
> file identified kio (KIOConnection): ERROR: Could not write data
>
> I haven't installed the Kipi plugins 1.3 beta yet (see other thread),
> would this be relevant?  

no

> I'm also running this across an ssh
> connection from a (very) remote machine, i.e. digikam is a machine at
> home and I'm doing all this from work, might that affect things if the
> X permissions aren't exactly right?

hum, not sure.

in local, run '#tail -f ~/.xsession-errors" and restart digiKam and look if
any error messages appears.

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Chris Green]

On Wed, Dec 06, 2006 at 12:41:10PM +0100, Gilles Caulier wrote:

> > OK, thanks, I've got RC2 installed now, and I'm still getting the
> > message:-
> >
> >     KIPI (loading): Loaded RawConverter
> >     KIPI (loading): KIPI::PluginLoader: Loaded plugin RawConverter
> >     digikam: ImagePlugin_Core plugin loaded
> >     digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
> >     digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg : JPEG
> > file identified kio (KIOConnection): ERROR: Could not write data
> >
> > I haven't installed the Kipi plugins 1.3 beta yet (see other thread),
> > would this be relevant?  
>
> no
>
> > I'm also running this across an ssh
> > connection from a (very) remote machine, i.e. digikam is a machine at
> > home and I'm doing all this from work, might that affect things if the
> > X permissions aren't exactly right?
>
> hum, not sure.
>
> in local, run '#tail -f ~/.xsession-errors" and restart digiKam and look if
> any error messages appears.
>

No X errors I'm afraid, still getting:-

    kio (KIOConnection): ERROR: Could not write data

Digikam version reports correctly:-

    server$ digikam -v
    Qt: 3.3.6
    KDE: 3.5.4
    digiKam: 0.9.0-rc2

--
Chris Green ([hidden email])
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 06 December 2006 13:42, [hidden email] wrote:

> On Wed, Dec 06, 2006 at 12:41:10PM +0100, Gilles Caulier wrote:
> > > OK, thanks, I've got RC2 installed now, and I'm still getting the
> > > message:-
> > >
> > >     KIPI (loading): Loaded RawConverter
> > >     KIPI (loading): KIPI::PluginLoader: Loaded plugin RawConverter
> > >     digikam: ImagePlugin_Core plugin loaded
> > >     digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
> > >     digikam: /home/chris/Pictures/dtest/Evelyn/Thailand/aps054.jpg :
> > > JPEG file identified kio (KIOConnection): ERROR: Could not write data
> > >
> > > I haven't installed the Kipi plugins 1.3 beta yet (see other thread),
> > > would this be relevant?
> >
> > no
> >
> > > I'm also running this across an ssh
> > > connection from a (very) remote machine, i.e. digikam is a machine at
> > > home and I'm doing all this from work, might that affect things if the
> > > X permissions aren't exactly right?
> >
> > hum, not sure.
> >
> > in local, run '#tail -f ~/.xsession-errors" and restart digiKam and look
> > if any error messages appears.
>
> No X errors I'm afraid, still getting:-
>
>     kio (KIOConnection): ERROR: Could not write data
>
> Digikam version reports correctly:-
>
>     server$ digikam -v
>     Qt: 3.3.6
>     KDE: 3.5.4
>     digiKam: 0.9.0-rc2

strange. I have fixed a huge memory leak duing of wrong management of picture
preview mode (F3 in album view). Before to fix it, i have this error message.

This error message can be also reported by another part of KDE. To be sure, go
to an album, select the first item, press F3 and change current picture to
show using mouse wheel or PageUp/PageDown keys. If digikam crash after to
view some pictures, something is wrong.

But i will be suprised if it crash. i have tested indeep this part using
valgrind and now the memory leak is fixed.

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Chris Green]

On Wed, Dec 06, 2006 at 01:42:25PM +0100, Gilles Caulier wrote:

> > > in local, run '#tail -f ~/.xsession-errors" and restart digiKam and look
> > > if any error messages appears.
> >
> > No X errors I'm afraid, still getting:-
> >
> >     kio (KIOConnection): ERROR: Could not write data
> >
> > Digikam version reports correctly:-
> >
> >     server$ digikam -v
> >     Qt: 3.3.6
> >     KDE: 3.5.4
> >     digiKam: 0.9.0-rc2
>
> strange. I have fixed a huge memory leak duing of wrong management of picture
> preview mode (F3 in album view). Before to fix it, i have this error message.
>
> This error message can be also reported by another part of KDE. To be sure, go
> to an album, select the first item, press F3 and change current picture to
> show using mouse wheel or PageUp/PageDown keys. If digikam crash after to
> view some pictures, something is wrong.
>

That will have to wait until I get home this evening, I doubt very
much if F3 is mapped across correctly nor the other keys, not to
mention that it would be impossibly slow!

It's amazing it works at all really, I'm running Kea/X (X server) on a
PC displaying a Sun Solaris CDE desktop.  I then ssh from a Sun
terminal window to my home system and run Digikam using the ssh
connection as the 'pipe'.


> But i will be suprised if it crash. i have tested indeep this part using
> valgrind and now the memory leak is fixed.
>
I will try and remember to check it when I get home and report what
happens.

--
Chris Green ([hidden email])
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 06 December 2006 13:59, [hidden email] wrote:
> That will have to wait until I get home this evening, I doubt very
> much if F3 is mapped across correctly nor the other keys, not to
> mention that it would be impossibly slow!

Well use Image/View option from main menu instead

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Chris Green]

On Wed, Dec 06, 2006 at 01:57:20PM +0100, Gilles Caulier wrote:
> On Wednesday 06 December 2006 13:59, [hidden email] wrote:
> > That will have to wait until I get home this evening, I doubt very
> > much if F3 is mapped across correctly nor the other keys, not to
> > mention that it would be impossibly slow!
>
> Well use Image/View option from main menu instead
>
Most odd, I went to the Image menu before the first picture had
actually displayed and, this time, I didn't get the error message.
I can't really exercise it much though going through an album because
it takes tens of seconds to update the display each time anything
changes, let alone displaying a different picture.

I will give it a good work out when I get home.

--
Chris Green ([hidden email])
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Chris Green]

On Wed, Dec 06, 2006 at 01:35:42PM +0000, [hidden email] wrote:

> On Wed, Dec 06, 2006 at 01:57:20PM +0100, Gilles Caulier wrote:
> > On Wednesday 06 December 2006 13:59, [hidden email] wrote:
> > > That will have to wait until I get home this evening, I doubt very
> > > much if F3 is mapped across correctly nor the other keys, not to
> > > mention that it would be impossibly slow!
> >
> > Well use Image/View option from main menu instead
> >
> Most odd, I went to the Image menu before the first picture had
> actually displayed and, this time, I didn't get the error message.
> I can't really exercise it much though going through an album because
> it takes tens of seconds to update the display each time anything
> changes, let alone displaying a different picture.
>
> I will give it a good work out when I get home.
>

.... and the result is that if I PgUp/PgDn slowly there are no errors
but if I PgUp/PgDn faster than the pictures are redisplayed (i.e. I do
it when there's still the watchface displayed) I get errors like the
following:-

    kio (KIOConnection): ERROR: Could not write data
    kio (KIOConnection): ERROR: Could not write data
    kio (KIOConnection): ERROR: Could not write data
    kio_digikampreview: WARNING: Failed to attach to shared memory segment 8224775
    kio (KIOConnection): ERROR: Could not write data
    kio_digikampreview: WARNING: Failed to attach to shared memory segment 8257544
    kio (KIOConnection): ERROR: Could not write data
    kio_digikampreview: WARNING: Failed to attach to shared memory segment 8323080



--
Chris Green ([hidden email])
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 06 December 2006 19:46, [hidden email] wrote:

> On Wed, Dec 06, 2006 at 01:35:42PM +0000, [hidden email] wrote:
> > On Wed, Dec 06, 2006 at 01:57:20PM +0100, Gilles Caulier wrote:
> > > On Wednesday 06 December 2006 13:59, [hidden email] wrote:
> > > > That will have to wait until I get home this evening, I doubt very
> > > > much if F3 is mapped across correctly nor the other keys, not to
> > > > mention that it would be impossibly slow!
> > >
> > > Well use Image/View option from main menu instead
> >
> > Most odd, I went to the Image menu before the first picture had
> > actually displayed and, this time, I didn't get the error message.
> > I can't really exercise it much though going through an album because
> > it takes tens of seconds to update the display each time anything
> > changes, let alone displaying a different picture.
> >
> > I will give it a good work out when I get home.
>
> .... and the result is that if I PgUp/PgDn slowly there are no errors
> but if I PgUp/PgDn faster than the pictures are redisplayed (i.e. I do
> it when there's still the watchface displayed) I get errors like the
> following:-
>
>     kio (KIOConnection): ERROR: Could not write data
>     kio (KIOConnection): ERROR: Could not write data
>     kio (KIOConnection): ERROR: Could not write data
>     kio_digikampreview: WARNING: Failed to attach to shared memory segment
> 8224775 kio (KIOConnection): ERROR: Could not write data
>     kio_digikampreview: WARNING: Failed to attach to shared memory segment
> 8257544 kio (KIOConnection): ERROR: Could not write data
>     kio_digikampreview: WARNING: Failed to attach to shared memory segment
> 8323080

ok thanks. I will investiguate in this KIO slave.

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users