Opera crashing with “opera: error while reading system fonts”

Opera crashing with “opera: error while reading system fonts”

When trying to launch >=opera-12.00.1467 (same for opera-next) I get

opera: error while reading system fonts
opera [crash logging]: CRASH!!
/usr/lib64/opera-next/opera-next got signal SIGSEGV at address 0000009B89E0

Log was created here:
/var/tmp/opera-20120804213826
zsh: killed     opera-next
(zyx-desktop:zyx:~) % opera: error while reading system fonts

/var/tmp/opera-20120804213826/crash.log is here: http://bpaste.net/show/38487/
/var/tmp/opera-20120804213826/gpu_info.txt is empty.

Additionally opera creates the following files in ~/.opera-next:

• lock (empty)
• upgrade.log (empty)
• tmp (directory, empty)
• operaprefs.ini
  

  Opera Preferences version 2.1
  ; Do not edit this file while Opera is running
  ; This file is stored in UTF-8 encoding
  
  [State]
  Detected Country Code=RU
  Active Country Code=RU
  Active Region=cis
  Active Default Language=ru
  

stat tells that all these files were modified in one second.

Note: I had exactly the same result for a release when there was opera-11.64.1403 ebuild in the portage tree in addition to opera-12.00.1467, I just don’t want to update (for obvious reasons), thus speaking about opera-next here.

^_^

I got a similar problem with Opera 12.01.

Try running 'opera -debugfont' and posting the results here, it might give more information about the fonts failing. Opera needs fontconfig to look up font data.

I had the same problem with opera 12.00 on 64bit SuSe SLED11.2. In my case the solution was to change the locale settings from "C" to "de_DE.UTF-8", or more precisely by setting the LC_CTYPE environment variable to "de_DE.UTF-8".

Originally posted by AVL:

Try running 'opera -debugfont' and posting the results here, it might give more information about the fonts failing. Opera needs fontconfig to look up font data.

Way too large for posting it here: http://bpaste.net/show/38699/. Needed to run under strace or valgrind (seems to output nothing useful) to get the full output or it got truncated.

Here is the strace: http://bpaste.net/show/38697/
(obtained via

strace -f -o >(wgetpaste) opera-next -debugfont

. For some unknown reason when running under strace opera-next complains that there is another opera-next instance running. Does not do so when running in the shell or under valgrind.

Can you find the 'NanumGothicCoding' font? fc-list might help you here. Try if Opera starts if you move that fond out of the way, so that fontconfig doesn't know it's there.

Originally posted by AVL:

Can you find the 'NanumGothicCoding' font? fc-list might help you here. Try if Opera starts if you move that fond out of the way, so that fontconfig doesn't know it's there.

Opera starts normally if I rename the files with the font so that new filename contains only ASCII characters. Original names are the following

$'\246'$'\254'$'\246'$'\253'$'\246'$'\335'$'\301'$'\261'-+$'\301'$'\250'-Bold.ttf
$'\246'$'\254'$'\246'$'\253'$'\246'$'\335'$'\301'$'\261'-+$'\301'$'\250'.ttf

($'\246' means character with 0xF6 byte, not literal $'\246'). Changelog for the ebuild says

Added hack to avoid installation of files in cp949 encoding, bug 322041,
thank Alexander Bezrukov for report.

and in fact it is fixed after I updated to a masked version, but I still don’t think segfault is the proper way of handling this problem.

Thanks for pointing to fc-list.

Originally posted by ZyXI:

and in fact it is fixed after I updated to a masked version, but I still don’t think segfault is the proper way of handling this problem.Thanks for pointing to fc-list.

Glad it helped! You should file a bug for it and attach the font file (with the broken file name) so that Opera can look into it.

Originally posted by AVL:

Originally posted by ZyXI:

and in fact it is fixed after I updated to a masked version, but I still don’t think segfault is the proper way of handling this problem.Thanks for pointing to fc-list.

Glad it helped! You should file a bug for it and attach the font file (with the broken file name) so that Opera can look into it.

I guess I should just email to DSK-366555@bugs.opera.com with this file attached, problematic name and a link to this thread. Filing a bug report was the first thing I did when encountered this problem.

Yes, that should be the right thing to do.

Look out for a fix for DSK-369031, your bug was marked as a duplicate of that one.