Bug 238277 - preferences dialog crashes KOrganizer when PT Sans is used as general KDE font
Summary: preferences dialog crashes KOrganizer when PT Sans is used as general KDE font
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-20 10:30 UTC by Sergei Kasaurov
Modified: 2010-06-09 21:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The log file of "valgrind korganizer --nofork &> log.txt" (947 bytes, text/plain)
2010-05-22 19:29 UTC, Sergei Kasaurov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergei Kasaurov 2010-05-20 10:30:47 UTC
Version:            (using KDE 4.4.3)
OS:                Linux
Installed from:    Ubuntu Packages

I've been using free public PT Sans font by ParaType (http://www.paratype.com/public/) for six months and all was OK. I haven't tried to use KOrganizer so far. But when I open it and then tried to open it's preferences dialog my KOrganizer crashed with segmentation fault. This bug reproduces every time I open KOrganizer preferences dialog.

Trying to find the cause of this crash I found that it is using PT Sans as general KDE font.

I created a new user account from scratch that have default DejaVu KDE fonts. No crash. Then I installed PT Sans as user font and chose it as a general KDE font (other kinds of fonts don't affect on that bug). Opening KOrganizer preferences dialog crashed the application.

I'm at Kubuntu Lucid Lynx 10.04, KDE 4.4.3.
Comment 1 Sergio Martins 2010-05-22 14:52:56 UTC
Please post a valgrind report.

Just run valgrind korganizer --nofork &> log.txt

and attach the log.txt file after it crashed
Comment 2 Sergei Kasaurov 2010-05-22 19:29:03 UTC
Created attachment 43805 [details]
The log file of "valgrind korganizer --nofork &> log.txt"
Comment 3 Sergei Kasaurov 2010-06-03 14:14:34 UTC
Can anybody confirm this bug?
Comment 4 Sergei Kasaurov 2010-06-09 21:41:12 UTC
The bug is fixed in KDE 4.5 beta2 (sorry, could not try beta1).