--- Comment #21 from Guido Falsi <[hidden email]> ---
(In reply to Marko Cupać from comment #19)
> Another crash, newly installed system, no chromium and droid fonts
> installed, visiting link in firefox crashes panel:
> https://www.discogs.com/%E6%88%90%E9%BE%8D- > %E4%B8%80%E5%80%8B%E5%A5%BD%E4%BA%BA-Mr-Nice-Guy-
> I gues I can easily workaround by installing droid fonts but still, this
> shouldn't happen, right?
I saw this just now.
If visiting a link from firefox causes the crash it's an interaction from
I suspect a panel plugin triggering this. Maybe the one listing window titles
is being confused by the title of the page. It's quite probable the problem
shows up only if using a specific locale.
The fonts you're using can be missing some language specific glyph, for
If I'm right this is not easy to reproduce for someone using a different locale
and font set.
Unluckily the gdb output you posted is not very useful, missing the whole
Before grabbing and posting the gdb output you should give it the "bt" command
and grabbing the output of that too.
Obviously gdb output can be made much more useful by having debug symbols in
binaries, but it's not always strictly needed.
... but only when I have "Window Buttons" enabled.
I don't have x11-fonts/droid-fonts-ttf installed, I have never been installing
it as a prime-origin, I guess it used to be chromium's dependency but not
So, I would say the crash happens when I open web page containing "east asian"
characters (political correctness police, please don't be too harsh on me if I
said something forbidden :D), in both Firefox and Chromium, when Window Buttons
are presented in panel.
--- Comment #23 from Guido Falsi <[hidden email]> ---
(In reply to Marko Cupać from comment #22)
> I think you're onto something about plugin crashing the panel, "Window
> Buttons" being the problematic one.
> I am on 11.2-RELEASE now. Opening the following link in Chromium crashes the
> https://blog.goo.ne.jp/nhh0/m/201404/2 >
> ... but only when I have "Window Buttons" enabled.
Here using the C default locale that URL is not causing a crash.
But maybe I have some other font satisfying the requirement whole you are
missing some font and that could be the cause of the crash. It should not crash
obviously, that's a bug, but we need to identify it.
> I don't have x11-fonts/droid-fonts-ttf installed, I have never been
> installing it as a prime-origin, I guess it used to be chromium's dependency
> but not anymore.
> So, I would say the crash happens when I open web page containing "east
> asian" characters (political correctness police, please don't be too harsh
> on me if I said something forbidden :D), in both Firefox and Chromium, when
> Window Buttons are presented in panel.
> Here's my locale:
> pacija@efreet:~ % locale
> Would it be helpful to debuggers to remove custom locale and see if the
> problem persists?
If you could test setting the default ("C") locale or an en_US locale and test
again it could be useful to understand if the locale is the cause or some
If using the C locale it crashes anyway I'd rule out the locale setting and
start looking at installed font as the real cause.
--- Comment #25 from Guido Falsi <[hidden email]> ---
(In reply to Marko Cupać from comment #24)
> (In reply to Guido Falsi from comment #23)
> Of course, I checked each time if changes were applied with `locale' and
> they were.
> Thank you once again for looking into it. The bug doesn't bother me much as
> it happens so rarely, still it would be nice to have it solved for the sake
> of software improvement.
From what I see it's a font problem. The panel plugin seems to be crashing when
it, for some reason, can't find the correct glyph, but could also be a problem
in downstream libraries.
At least we now know the encoding isn't the main cause.
It will be necessary to work with upstream to solve this, since I don't know
the details of X11 fonts management.
You should file a bug report in the XFCE bugzilla instance , and reference
it here, so they are informed and help us.
--- Comment #29 from Guido Falsi <[hidden email]> ---
(In reply to Marko Cupać from comment #28)
> (In reply to Guido Falsi from comment #27)
> Hi Guido,
> thank you for your effort. I can live with this bug as crash happens so
> rarely. I'm a bit disappointed that XFCE devs closed it as "FIXED", while it
> is still present in stable production version.
Unluckily I can't force them to act on this, I can only try to prod them in
> Should I leave this open? Or close with "Works as intended" or "Rejected"?
The problem actually exists and is confirmed, so closing it is not correct.
Let's leave this open, A solution could be found in the future.