Bug#914956: crashes randomly after 1.0.1 upgrade

Antoine Beaupre anarcat at debian.org
Thu Nov 29 03:11:03 GMT 2018


Package: taffybar
Version: 1.0.0-1
Severity: important

I'm running buster and ever since the 1.0.0 upgrade, I've had trouble
keeping taffybar running, so much so that I'm looking at going back at
xmonad or whatever else would offer me a status bar while this bug is
fixed. Obviously, downgrading would be a huge challenge because of the
complex dependency chain around this package...

I'm not sure what's going on, to be honest. There's been some API
changes, of course, in the new release, so I had to
... er... basically guess my way around those. Here's the patch I had
to make to my config - I have no idea if it's correct, but it made
Haskell happy, so I assume it is:

<#part type="text/x-diff" filename="~/patches/taffybar.hs-1.0.patch" disposition=inline>
<#/part>

Notice how I completely disabled the battery part (I didn't immediately
need it) and the network monitor (which makes the whole thing crash
*faster*).

The symptom is that things generally go well and I have a beautiful
taffybar on top (although the colors have changed and I still need to
figure out how to tweak that). Then, after a delay ranging between few
seconds and a few minutes, it just crashes:

curie:~139$ pkill -f .cache/taffybar/taffybar; taffybar 
Launching custom binary /home/anarcat/.cache/taffybar/taffybar-linux-x86_64

Got error
ErrorEvent {ev_type = 0, ev_display = Display 0x00007f5d84000b70, ev_serialnum = 13, ev_error_code = 3, ev_request_code = 2, ev_minor_code = 0, ev_resourceid = 1072682}
Erreur de segmentation (core dumped)
"pkill -f .cache/taffybar/taffybar; taffybar " took 2 mins

Boom. The kernel tells me:

nov 28 21:57:18 curie kernel: taffybar-linux-[28287] segfault at fffffffffffffff8 ip 0000000000421b75 sp 00007ffe4f0e2630 error 5 in taffybar-linux-x86_64[400000+5f0000] 
nov 28 21:57:18 curie kernel: Code: 06 81 e2 c0 3f 00 00 48 09 ca 0f b7 4a 2e 66 f7 c1 0b 02 0f 85 3c 15 00 00 48 8b 2b 0f b7 52 2a 40 f6 c5 01 0f 85 cb 15 00 00 <8b> 75 f8 83 fe 3e 0f 87 5d 13 00 00 89 f1 48 63 0c 8f 48 01 f9 ff  

gdb tells me it crashes in the garbage collector:

(gdb) bt
#0  0x0000000000421b75 in evacuate1 ()
#1  0x0000000000420edd in scavenge_block1 ()
#2  0x00000000009a6be2 in scavenge_loop1 ()
#3  0x0000000000991bc2 in scavenge_until_all_done ()
#4  0x00000000009924fc in GarbageCollect ()
#5  0x0000000000981cd4 in scheduleDoGC ()
#6  0x00000000009825b0 in schedule ()
#7  0x0000000000983401 in scheduleWaitThread ()
#8  0x0000000000708fb2 in  ()
#9  0x00007f5d9afc3b6d in g_closure_invoke ()
    at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007f5d9afd68f3 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007f5d9afdef43 in g_signal_emit_valist ()
    at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007f5d9afdfecf in g_signal_emit ()
    at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007f5d9b7fe9b2 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#14 0x00007f5d9b5ea1ca in gtk_container_propagate_draw ()
    at /lib/x86_64-linux-gnu/libgtk-3.so.0
#15 0x00007f5d9b5ea29d in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#16 0x00007f5d9b59c604 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#17 0x00007f5d9b5ef32d in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#18 0x00007f5d9b5f4002 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
---Type <return> to continue, or q <return> to quit---
#19 0x00007f5d9b59ee91 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x00007f5d9b7fe854 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#21 0x00007f5d9b5ea1ca in gtk_container_propagate_draw ()
    at /lib/x86_64-linux-gnu/libgtk-3.so.0
#22 0x00007f5d9b5ea29d in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#23 0x00007f5d9b59c604 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#24 0x00007f5d9b5ef32d in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#25 0x00007f5d9b5f4002 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#26 0x00007f5d9b59ee91 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#27 0x00007f5d9b7fe854 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#28 0x00007f5d9b5ea1ca in gtk_container_propagate_draw ()
    at /lib/x86_64-linux-gnu/libgtk-3.so.0
#29 0x00007f5d9b5ea29d in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#30 0x00007f5d9b80cba2 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#31 0x00007f5d9b7fe854 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#32 0x00007f5d9b807878 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#33 0x00007f5d9b6b70a9 in gtk_main_do_event ()
    at /lib/x86_64-linux-gnu/libgtk-3.so.0
#34 0x00007f5d9b3b82a5 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#35 0x00007f5d9b3c87d6 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#36 0x00007f5d9b3c9946 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#37 0x00007f5d9b3c9b04 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#38 0x00007f5d9afc3b6d in g_closure_invoke ()
---Type <return> to continue, or q <return> to quit---
    at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#39 0x00007f5d9afd68f3 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#40 0x00007f5d9afdf882 in g_signal_emit_valist ()
    at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#41 0x00007f5d9afdfecf in g_signal_emit ()
    at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#42 0x00007f5d9b3c18cd in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#43 0x00007f5d9b3acac8 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#44 0x00007f5d9aee4573 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#45 0x00007f5d9aee3ae8 in g_main_context_dispatch ()
    at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#46 0x00007f5d9aee3ed8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#47 0x00007f5d9aee41d2 in g_main_loop_run ()
    at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#48 0x00007f5d9b6b6295 in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#49 0x000000000042fe3c in taffybarzm1zi0zi0zmD624yHXkS8H5uGgJmxK9Qw_SystemziTaffybar_defaultTaffybar18_info ()
#50 0x0000000000000000 in  ()

... which is... er... a little surprising.

To trigger the bug faster, i can swap to the next desktop real fast in
i3 ("workspace next/prev") but just waiting for a while also seems to
trigger the bug.

As I mentioned, enabling the network monitor makes the whole thing crash
much faster, just a few seconds.

Here's my full taffybar config.

<#part type="text/x-haskell" filename="~/.config/taffybar/taffybar.hs" disposition=inline>
<#/part>

I wish I could be more helpful... but that's what I got! I'll be glad to
help diagnose this further as I'm excited to make use of the new
features that taffybar has to offer! :)

Cheers,

A.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages taffybar depends on:
ii  libasound2           1.1.7-1+b1
ii  libatk1.0-0          2.30.0-1
ii  libatomic1           8.2.0-9
ii  libc6                2.27-8
ii  libcairo-gobject2    1.16.0-1
ii  libcairo2            1.16.0-1
ii  libffi6              3.2.1-8
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglib2.0-0         2.58.1-2
ii  libgmp10             2:6.1.2+dfsg-3
ii  libgtk-3-0           3.24.1-2
ii  libpango-1.0-0       1.42.4-4
ii  libpangocairo-1.0-0  1.42.4-4
ii  libx11-6             2:1.6.7-1
ii  libxext6             2:1.3.3-1+b2
ii  libxft2              2.3.2-2
ii  libxinerama1         2:1.1.4-1
ii  libxml2              2.9.4+dfsg1-7+b2
ii  libxrandr2           2:1.5.1-1
ii  libxss1              1:1.2.3-1
ii  zlib1g               1:1.2.11.dfsg-1

Versions of packages taffybar recommends:
ii  libghc-taffybar-dev  1.0.0-1
pn  libghc-taffybar-doc  <none>

taffybar suggests no packages.

-- debconf-show failed



More information about the Pkg-haskell-maintainers mailing list