search

LBCrion / sfwbar

S* Floating Window Bar
GNU General Public License v3.0
265 stars 17 forks source link

sfwbar core dumped when clicking an item in taskbar group #209

Closed salahoued closed 2 months ago

salahoued commented 2 months ago

I have set my taskbar to group the tasks

group = popup
group cols = 1
group icons = true
group labels = true

lately, sometimes (not every time) when hovering over a group of task the tasks are shown/sorted horizontally like: I'm not sure how to reproduce this issue. +----------+----------+ | task 1 | task 2 | +----------+-----------+

instead of +----------+ | task 1 | +----------+ | task 2 | +-----------+ 20240719_21h33m30s_grim

And when selecting/clicking a task from the group sfwbar core dump.

21:37:34,71 base_widget_get_mirror_parent: assertion 'IS_BASE_WIDGET(self)' failed
Erreur de segmentation (core dumped)
LBCrion commented 2 months ago

Can you please check if these issues still happen with the latest git? These look like #202 and #205.

On Fri, 19 Jul 2024, 21:38 salahoued, @.***> wrote:

I have set my taskbar to group the task

group = popup group cols = 1 group icons = true group labels = true

lately, sometimes when hovering over a group of task the tasks are shown/sorted horizontally like:

+----------+----------+ | task 1 | task 2 | +----------+-----------+

instead of +----------+ | task 1 | +----------+ | task 2 | +-----------+ 20240719_21h33m30s_grim.png (view on web) https://github.com/user-attachments/assets/2579f664-dfa6-478d-be76-4bfdc2b34cd8

And when selecting/clicking in a task from the group sfwbar core dump.

21:37:34,71 base_widget_get_mirror_parent: assertion 'IS_BASE_WIDGET(self)' failed Erreur de segmentation (core dumped)

— Reply to this email directly, view it on GitHub https://github.com/LBCrion/sfwbar/issues/209, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASHPFFFWQFTND22NZXM2FS3ZNF2MTAVCNFSM6AAAAABLFGWTPGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYTSOBRGMZTGMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

salahoued commented 2 months ago

Yes they are the same issues, sorry I didn't check if there are similar issues to mine before writing this.

And this issues no longer happen in the latest git version, it works fine.

Thanks and sorry.