-
-
Notifications
You must be signed in to change notification settings - Fork 703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
polybar segfaults (segfault at 10 ip 00007f71861f3570 sp 00007f714affc298 error 4 in libfontconfig.so.1.11.1[7f71861da000+23000]) #1435
Comments
Could you try to remove the |
I've played with it and it started to work when I removed the |
Alright... |
Really strange that fc produces a segfault for that. Can you try to run the segfaulting config with EDIT: Please also post the output of |
Oh and it seems like we already had an issue for this: #1337. |
|
Just as I thought. We will need to check if |
If FcNameParse returns NULL FcDefaultSubstitute segfaults We log and throw an error here because the signal emitter swallows all exceptions so if that exception was thrown, the bar would stop rendering without any indication as to why. Fixes polybar#1435
If FcNameParse returns NULL FcDefaultSubstitute segfaults We log and throw an error here because the signal emitter swallows all exceptions so if that exception was thrown, the bar would stop rendering without any indication as to why. Fixes #1435
If FcNameParse returns NULL FcDefaultSubstitute segfaults We log and throw an error here because the signal emitter swallows all exceptions so if that exception was thrown, the bar would stop rendering without any indication as to why. Fixes polybar#1435
### Breaking Changes: None ### Changelog **New Config Options** The following config options were added In the `[settings]` section: * `pseudo-transparency` In `internal/cpu`: * `ramp-coreload-spacing`, spacing between elements in `<ramp-coreload>` elements * `%percentage-sum%` in `label`. Shows sum of all percentages In `custom/script`: * `double-click-left` * `double-click-middle` * `double-click-right` In `internal/pulseaudio`: * `interval`, volume increase and decrease steps in percentage points In `internal/memory`: * `bar-swap-used` * `bar-swap-free` * `ramp-swap-used` * `ramp-swap-free` **Deprecations** * `tray-transparent` in the bar section is no longer used. The tray now always uses pseudo-transparency **Features** * volume: adjustable volume steps (#1364), see #1361 * memory: Add progress bars and ramps for swap (#1325) * render: pseudo-transparency (always used in the tray) (#595) * cpu: * Configurable spacing in between coreloads (#1472), see #1389 * Non-normalized cpu load (#1517), see #1516 * script: Double click actions (#1442) * net: Support for bridge interfaces (#1528), see #1522 * token: zero pad tokens when min-width value starts with a `0` (#1341), see #1332 **Fixes** * config: Use font patterns detected on system in sample config (#1350) * net: Disconnected module when SSID is only an emoji (#1371), see #1367 * tray: Tray overlapping with bar (#1392), see #591 * build: Several build errors (#1395, #1454, #1470, polybar/xpp#12, #1493), see #1447, #1469, #750, #1492 * mpd: format-online-prefix not working (#1402), see #1399 * font: Crash for some font-patterns (#1451), see #1435 * script: * Only `%counter%` or `%pid%` token usable, never both (#1456) * click actions with colons in them (#1457), see #984 * renderer: Bar locks up when xorg composite extension is disabled (#1430), see #1425
Describe the issue
Was running ubuntu 18.04 and polybar was running with the same config fine. Today upgraded to ubuntu 18.10 and recompiled polybar and it segfaults.
Version of libfontconfig:
Version: 2.13.0-5ubuntu3
Expected behavior:
It should not segfault.
Actual behavior:
It segfaults.
To Reproduce
A minimal but complete config with which the problem occurs:
I guess it has to do something with fonts and version of libfontconfig:
font-0 = Hack:pixelsize=10:weight=bold;2
font-1 = Hack:pixelsize=32;2
font-2 = "Font Awesome:pixelsize=12;2"
font-3 = Unifont:size=9;2
List any other steps needed to reproduce the issue besides starting polybar with the config you posted above.
Polybar Log
polybar main
warn: No monitor specified, using "HDMI-1"
Segmentation fault (core dumped)
GDB:
Environment:
bspwm 0.9.5
polybar -vvv
:polybar 3.2.1
Features: -alsa +curl -i3 +mpd +network +pulseaudio +xkeyboard
X extensions: +randr (+monitors) -render -damage -sync -composite +xkb +xrm +xcursor
Build type: Debug
Compiler: /usr/bin/c++
Compiler flags: -Wall -Wextra -Werror -Wno-noexcept-type -O2 -pedantic -pedantic-errors
Linker flags:
The text was updated successfully, but these errors were encountered: