more on antialiasing problem

[Aaron Solochek]

I have some more information regarding my problem with anti aliasing and
digikam.  The problem, to remind people, is that no text renders at all:

http://www.aberrant.org/~aarons/no_text.png

This problem exists with nearly every font I have installed.  The only
font I don't see the problem with is Terminus, and I think that's
because it doesn't actually do antialiasing for it.  If I turn off
antialiasing and reopen digikam or shotfoto, the text shows up fine.

I see this behavior on 3 systems now.  All three are debian, two
unstable, one unstable/testing.  They are all running X.org, and both
kde and gnome apps.  Two systems are running digikam 0.8.0-0beta2-1, and
the other is running 0.7.4-5.

What could digikam be doing that other kde applications aren't wrt
fonts?  I thought at that level all kde applications used the same
libraries.  This is a very frustrating problem because I love digikam
and had started organizing everything with it before this problem popped up.

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

[Tom Albers-2]

Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
> I have some more information regarding my problem with anti aliasing and
> digikam.  The problem, to remind people, is that no text renders at all:
>
> http://www.aberrant.org/~aarons/no_text.png

This does not seem digiKam related to me, this is just a default file open
window. Are you using KDE? Do other applications suffer from the same
problem?

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

[Gerhard Kulzer]

Am Mittwoch, 16. November 2005 18.43 schrieb Tom Albers:

> Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
> > I have some more information regarding my problem with anti aliasing and
> > digikam.  The problem, to remind people, is that no text renders at all:
> >
> > http://www.aberrant.org/~aarons/no_text.png
>
> This does not seem digiKam related to me, this is just a default file open
> window. Are you using KDE? Do other applications suffer from the same
> problem?
>
> Toma

Why don't you regenerate your fonts like that:
  # dpkg-reconfigure -plow fontconfig
  # fc-cache -vf

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

[Aaron Solochek]

Tom Albers wrote:

> Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
>
>>I have some more information regarding my problem with anti aliasing and
>>digikam.  The problem, to remind people, is that no text renders at all:
>>
>>http://www.aberrant.org/~aarons/no_text.png
>
>
> This does not seem digiKam related to me, this is just a default file open
> window. Are you using KDE? Do other applications suffer from the same
> problem?
>

I am using KDE to various extents on these other computers.  Generally
I'm using a gnome/kde hybrid, but some machines launch a kde-session,
others a gnome-session.  In all cases I use lots of other kde
applications, such as the kdepim suite and konqueror.  digiKam and
showFoto are the only two applications I see this problem.

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

[Aaron Solochek]

Gerhard Kulzer wrote:

> Am Mittwoch, 16. November 2005 18.43 schrieb Tom Albers:
>
>>Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
>>
>>>I have some more information regarding my problem with anti aliasing and
>>>digikam.  The problem, to remind people, is that no text renders at all:
>>>
>>>http://www.aberrant.org/~aarons/no_text.png
>>
>>This does not seem digiKam related to me, this is just a default file open
>>window. Are you using KDE? Do other applications suffer from the same
>>problem?
>>
>>Toma
>
>
> Why don't you regenerate your fonts like that:
>   # dpkg-reconfigure -plow fontconfig
>   # fc-cache -vf
>

I tried that.  Should any of my answers to those questions make a
difference?  The questions are whether or not to enable truetype or
native fonts, enable bitmapped fonts, and whether or not to always do
sub-pixel rendering.

-Aaron

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

Op woensdag 16 november 2005 20:09, schreef Aaron Solochek:

> Tom Albers wrote:
> > Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
> >>I have some more information regarding my problem with anti aliasing and
> >>digikam.  The problem, to remind people, is that no text renders at all:
> >>
> >>http://www.aberrant.org/~aarons/no_text.png
> >
> > This does not seem digiKam related to me, this is just a default file
> > open window. Are you using KDE? Do other applications suffer from the
> > same problem?
>
> I am using KDE to various extents on these other computers.  Generally
> I'm using a gnome/kde hybrid, but some machines launch a kde-session,
> others a gnome-session.  In all cases I use lots of other kde
> applications, such as the kdepim suite and konqueror.  digiKam and
> showFoto are the only two applications I see this problem.

We are not doing something with a file->open dialog this is a simple kde class
we use, even if we want we have no influence on it.

I can only suggest to try with a new kde-session with a brand new user, but
whatever the outcome is, I can not help you, it is a system installation
error, not a digiKam one, else we would have had similar reports.

Tom

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

[Aaron Solochek]

Tom Albers wrote:

> Op woensdag 16 november 2005 20:09, schreef Aaron Solochek:
>
>>Tom Albers wrote:
>>
>>>Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
>>>
>>>>I have some more information regarding my problem with anti aliasing and
>>>>digikam.  The problem, to remind people, is that no text renders at all:
>>>>
>>>>http://www.aberrant.org/~aarons/no_text.png
>>>
>>>This does not seem digiKam related to me, this is just a default file
>>>open window. Are you using KDE? Do other applications suffer from the
>>>same problem?
>>
>>I am using KDE to various extents on these other computers.  Generally
>>I'm using a gnome/kde hybrid, but some machines launch a kde-session,
>>others a gnome-session.  In all cases I use lots of other kde
>>applications, such as the kdepim suite and konqueror.  digiKam and
>>showFoto are the only two applications I see this problem.
>
>
> We are not doing something with a file->open dialog this is a simple kde class
> we use, even if we want we have no influence on it.
>
> I can only suggest to try with a new kde-session with a brand new user, but
> whatever the outcome is, I can not help you, it is a system installation
> error, not a digiKam one, else we would have had similar reports.
>
> Tom

Well, I created a brand new user, logged in with a kde session, turned
on anti-aliasing, and had the same problem.

In case it wasn't obvious from my earlier posts, it is not simply the
file open dialog that has no text.  There is no text on any of the
showfoto or digiKam widgets, just the underlines for the keyboard
shortcuts.  If it is a system installation error, it is one that only
manifests itself with digiKam.  Every other kde application works fine.

My theory is that there is some odd initilization parameter that digikam
uses that triggers this.  I have been messing with the digikam source to
try to track down the problem, but debugging the gui is beyond my
expertise.

-Aaron

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

[Gilles Caulier]

Le Mercredi 16 Novembre 2005 22:36, Aaron Solochek a écrit :

> Tom Albers wrote:
> > Op woensdag 16 november 2005 20:09, schreef Aaron Solochek:
> >>Tom Albers wrote:
> >>>Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
> >>>>I have some more information regarding my problem with anti aliasing
> >>>> and digikam.  The problem, to remind people, is that no text renders
> >>>> at all:
> >>>>
> >>>>http://www.aberrant.org/~aarons/no_text.png
> >>>
> >>>This does not seem digiKam related to me, this is just a default file
> >>>open window. Are you using KDE? Do other applications suffer from the
> >>>same problem?
> >>
> >>I am using KDE to various extents on these other computers.  Generally
> >>I'm using a gnome/kde hybrid, but some machines launch a kde-session,
> >>others a gnome-session.  In all cases I use lots of other kde
> >>applications, such as the kdepim suite and konqueror.  digiKam and
> >>showFoto are the only two applications I see this problem.
> >
> > We are not doing something with a file->open dialog this is a simple kde
> > class we use, even if we want we have no influence on it.
> >
> > I can only suggest to try with a new kde-session with a brand new user,
> > but whatever the outcome is, I can not help you, it is a system
> > installation error, not a digiKam one, else we would have had similar
> > reports.
> >
> > Tom
>
> Well, I created a brand new user, logged in with a kde session, turned
> on anti-aliasing, and had the same problem.
>
> In case it wasn't obvious from my earlier posts, it is not simply the
> file open dialog that has no text.  There is no text on any of the
> showfoto or digiKam widgets, just the underlines for the keyboard
> shortcuts.  If it is a system installation error, it is one that only
> manifests itself with digiKam.  Every other kde application works fine.
>
> My theory is that there is some odd initilization parameter that digikam
> uses that triggers this.  I have been messing with the digikam source to
> try to track down the problem, but debugging the gui is beyond my
> expertise.
>
> -Aaron

Witch language you use ? English or another one ? Please trying in English
using KDE control pannel...

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

[Gerhard Kulzer]

Am Mittwoch, 16. November 2005 20.12 schrieb Aaron Solochek:

> Gerhard Kulzer wrote:
> > Am Mittwoch, 16. November 2005 18.43 schrieb Tom Albers:
> >>Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
> >>>I have some more information regarding my problem with anti aliasing and
> >>>digikam.  The problem, to remind people, is that no text renders at all:
> >>>
> >>>http://www.aberrant.org/~aarons/no_text.png
> >>
> >>This does not seem digiKam related to me, this is just a default file
> >> open window. Are you using KDE? Do other applications suffer from the
> >> same problem?
> >>
> >>Toma
> >
> > Why don't you regenerate your fonts like that:
> >   # dpkg-reconfigure -plow fontconfig
> >   # fc-cache -vf
>
> I tried that.  Should any of my answers to those questions make a
> difference?  The questions are whether or not to enable truetype or
> native fonts, enable bitmapped fonts, and whether or not to always do
> sub-pixel rendering.
>

No, your answers should make not the difference you're looking for.

See if all libraries are correctly loaded with:
# ldd /usr/bin/digikam

and for X error in
# less ~/.xsession-errors

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

[Aaron Solochek]

Gerhard Kulzer wrote:

> Am Mittwoch, 16. November 2005 20.12 schrieb Aaron Solochek:
>
>>Gerhard Kulzer wrote:
>>
>>>Am Mittwoch, 16. November 2005 18.43 schrieb Tom Albers:
>>>
>>>>Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
>>>>
>>>>>I have some more information regarding my problem with anti aliasing and
>>>>>digikam.  The problem, to remind people, is that no text renders at all:
>>>>>
>>>>>http://www.aberrant.org/~aarons/no_text.png
>>>>
>>>>This does not seem digiKam related to me, this is just a default file
>>>>open window. Are you using KDE? Do other applications suffer from the
>>>>same problem?
>>>>
>>>>Toma
>>>
>>>Why don't you regenerate your fonts like that:
>>>  # dpkg-reconfigure -plow fontconfig
>>>  # fc-cache -vf
>>
>>I tried that.  Should any of my answers to those questions make a
>>difference?  The questions are whether or not to enable truetype or
>>native fonts, enable bitmapped fonts, and whether or not to always do
>>sub-pixel rendering.
>>
>
> No, your answers should make not the difference you're looking for.
>
> See if all libraries are correctly loaded with:
> # ldd /usr/bin/digikam

/usr/bin/digikam:
        linux-gate.so.1 =>  (0xffffe000)
        libdigikam.so.0 => /usr/lib/libdigikam.so.0 (0xb7ce8000)
        libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb7c98000)
        libkabc.so.1 => /usr/lib/libkabc.so.1 (0xb7be8000)
        libvcard.so.0 => /usr/lib/libvcard.so.0 (0xb7bc5000)
        libkresources.so.1 => /usr/lib/libkresources.so.1 (0xb7ba3000)
        libkipi.so.0 => /usr/lib/libkipi.so.0 (0xb7b6f000)
        libkutils.so.1 => /usr/lib/libkutils.so.1 (0xb7b0f000)
        libtiff.so.4 => /usr/lib/libtiff.so.4 (0xb7abd000)
        libkdeprint.so.4 => /usr/lib/libkdeprint.so.4 (0xb79f4000)
        libkparts.so.2 => /usr/lib/libkparts.so.2 (0xb79b3000)
        libkio.so.4 => /usr/lib/libkio.so.4 (0xb76a4000)
        libkdesu.so.4 => /usr/lib/libkdesu.so.4 (0xb768e000)
        libkwalletclient.so.1 => /usr/lib/libkwalletclient.so.1 (0xb767e000)
        libfam.so.0 => /usr/lib/libfam.so.0 (0xb7676000)
        libImlib2.so.1 => /usr/lib/libImlib2.so.1 (0xb7612000)
        libkexif.so.1 => /usr/lib/libkexif.so.1 (0xb75fd000)
        libkdeui.so.4 => /usr/lib/libkdeui.so.4 (0xb7346000)
        libkdecore.so.4 => /usr/lib/libkdecore.so.4 (0xb7126000)
        libDCOP.so.4 => /usr/lib/libDCOP.so.4 (0xb70f5000)
        libresolv.so.2 => /lib/tls/libresolv.so.2 (0xb70e2000)
        libutil.so.1 => /lib/tls/libutil.so.1 (0xb70de000)
        libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0xb70c8000)
        libidn.so.11 => /usr/lib/libidn.so.11 (0xb7098000)
        libkdefx.so.4 => /usr/lib/libkdefx.so.4 (0xb706b000)
        libqt-mt.so.3 => /usr/lib/libqt-mt.so.3 (0xb6889000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb686b000)
        libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0xb6863000)
        libaudio.so.2 => /usr/lib/libaudio.so.2 (0xb684e000)
        libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0xb67ff000)
        libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0xb67fa000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb67f1000)
        libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0xb67ee000)
        libXft.so.2 => /usr/lib/libXft.so.2 (0xb67db000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb676e000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb673f000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb6719000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb6705000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0xb66f7000)
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0xb66ee000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0xb66d7000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb66c5000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb66bc000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xb65f1000)
        libgphoto2.so.2 => /usr/lib/libgphoto2.so.2 (0xb6578000)
        libexif.so.12 => /usr/lib/libexif.so.12 (0xb6559000)
        libgphoto2_port.so.0 => /usr/lib/libgphoto2_port.so.0 (0xb6552000)
        libdl.so.2 => /lib/tls/libdl.so.2 (0xb654e000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb6473000)
        libm.so.6 => /lib/tls/libm.so.6 (0xb644e000)
        libc.so.6 => /lib/tls/libc.so.6 (0xb6316000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb630b000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb62ea000)
        /lib/ld-linux.so.2 (0xb7f19000)


>
> and for X error in
> # less ~/.xsession-errors

I have a whole ton of mime errors in there, so I'm going to have to
clear those up before I can get any useful info.  I'll work on that.

Thanks.

-Aaron

>
> Gerhard
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>
> !DSPAM:437c1f9995517844616463!
>

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

[Aaron Solochek]

Gilles Caulier wrote:

> Le Mercredi 16 Novembre 2005 22:36, Aaron Solochek a écrit :
>
>>Tom Albers wrote:
>>
>>>Op woensdag 16 november 2005 20:09, schreef Aaron Solochek:
>>>
>>>>Tom Albers wrote:
>>>>
>>>>>Op woensdag 16 november 2005 03:02, schreef Aaron Solochek:
>>>>>
>>>>>>I have some more information regarding my problem with anti aliasing
>>>>>>and digikam.  The problem, to remind people, is that no text renders
>>>>>>at all:
>>>>>>
>>>>>>http://www.aberrant.org/~aarons/no_text.png
>>>>>
>>>>>This does not seem digiKam related to me, this is just a default file
>>>>>open window. Are you using KDE? Do other applications suffer from the
>>>>>same problem?
>>>>
>>>>I am using KDE to various extents on these other computers.  Generally
>>>>I'm using a gnome/kde hybrid, but some machines launch a kde-session,
>>>>others a gnome-session.  In all cases I use lots of other kde
>>>>applications, such as the kdepim suite and konqueror.  digiKam and
>>>>showFoto are the only two applications I see this problem.
>>>
>>>We are not doing something with a file->open dialog this is a simple kde
>>>class we use, even if we want we have no influence on it.
>>>
>>>I can only suggest to try with a new kde-session with a brand new user,
>>>but whatever the outcome is, I can not help you, it is a system
>>>installation error, not a digiKam one, else we would have had similar
>>>reports.
>>>
>>>Tom
>>
>>Well, I created a brand new user, logged in with a kde session, turned
>>on anti-aliasing, and had the same problem.
>>
>>In case it wasn't obvious from my earlier posts, it is not simply the
>>file open dialog that has no text.  There is no text on any of the
>>showfoto or digiKam widgets, just the underlines for the keyboard
>>shortcuts.  If it is a system installation error, it is one that only
>>manifests itself with digiKam.  Every other kde application works fine.
>>
>>My theory is that there is some odd initilization parameter that digikam
>>uses that triggers this.  I have been messing with the digikam source to
>>try to track down the problem, but debugging the gui is beyond my
>>expertise.
>>
>>-Aaron
>
>
> Witch language you use ? English or another one ? Please trying in English
> using KDE control pannel...

The one language installed is "US English"

-Aaron

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