Why does my application close when I click it in the Fluxbox Iconbar(?)?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












This is really about finding the correct setting. When I click on an icon on the iconbar (the part of the toolbar that holds active window tabs? I'm not even sure I know the correct terms for the parts of the window manager) if it does not have the focus, it gets the focus (no problem so far), but if it already has the focus it closes the window. I'd love to change this behavior.



If I click here stackexchange will close:
enter image description here



EDIT: This behavior happens on my desktop but not on my laptop. While there are many differences between the two installs, whatever the problem is it's not inherent to all flux installs. Also there is nothing in the logs (I thought that maybe it's a bug or missing package problem on my machine).



EDIT2: @filipe-brandenburger had the right idea but not the correct file. I painfully disabled files and rebooted, checked , and repeated the process until I found the problem line in my .fluxbox/init file. Specifically there is a line



session.screen0.iconbar.mode: static groups (minimized=no) (Workspace)


which when commented out solves my problem. However, I would still like to understand what this line intends to do as it's not clear to me why this causes my windows to close in that way.



EDIT3: Changing the line to



session.screen0.iconbar.mode: Workspace


as outlined as one of the valid options solves the problem. If someone comes along to explain what happened I'll add some bounty.







share|improve this question


















  • 1




    Do you mean close? Or minimize?
    – JdeBP
    Mar 15 at 21:45










  • Yup, I really mean close.
    – user1794469
    Mar 16 at 14:39










  • Did you try to rename (or delete) ~/.fluxbox to have a fresh start?
    – mviereck
    Mar 21 at 15:39






  • 1




    @mviereck that does seem to fix it so it seems like a misconfiguration or a setting and not a bug; just need to find which one.
    – user1794469
    Mar 21 at 20:58














up vote
0
down vote

favorite












This is really about finding the correct setting. When I click on an icon on the iconbar (the part of the toolbar that holds active window tabs? I'm not even sure I know the correct terms for the parts of the window manager) if it does not have the focus, it gets the focus (no problem so far), but if it already has the focus it closes the window. I'd love to change this behavior.



If I click here stackexchange will close:
enter image description here



EDIT: This behavior happens on my desktop but not on my laptop. While there are many differences between the two installs, whatever the problem is it's not inherent to all flux installs. Also there is nothing in the logs (I thought that maybe it's a bug or missing package problem on my machine).



EDIT2: @filipe-brandenburger had the right idea but not the correct file. I painfully disabled files and rebooted, checked , and repeated the process until I found the problem line in my .fluxbox/init file. Specifically there is a line



session.screen0.iconbar.mode: static groups (minimized=no) (Workspace)


which when commented out solves my problem. However, I would still like to understand what this line intends to do as it's not clear to me why this causes my windows to close in that way.



EDIT3: Changing the line to



session.screen0.iconbar.mode: Workspace


as outlined as one of the valid options solves the problem. If someone comes along to explain what happened I'll add some bounty.







share|improve this question


















  • 1




    Do you mean close? Or minimize?
    – JdeBP
    Mar 15 at 21:45










  • Yup, I really mean close.
    – user1794469
    Mar 16 at 14:39










  • Did you try to rename (or delete) ~/.fluxbox to have a fresh start?
    – mviereck
    Mar 21 at 15:39






  • 1




    @mviereck that does seem to fix it so it seems like a misconfiguration or a setting and not a bug; just need to find which one.
    – user1794469
    Mar 21 at 20:58












up vote
0
down vote

favorite









up vote
0
down vote

favorite











This is really about finding the correct setting. When I click on an icon on the iconbar (the part of the toolbar that holds active window tabs? I'm not even sure I know the correct terms for the parts of the window manager) if it does not have the focus, it gets the focus (no problem so far), but if it already has the focus it closes the window. I'd love to change this behavior.



If I click here stackexchange will close:
enter image description here



EDIT: This behavior happens on my desktop but not on my laptop. While there are many differences between the two installs, whatever the problem is it's not inherent to all flux installs. Also there is nothing in the logs (I thought that maybe it's a bug or missing package problem on my machine).



EDIT2: @filipe-brandenburger had the right idea but not the correct file. I painfully disabled files and rebooted, checked , and repeated the process until I found the problem line in my .fluxbox/init file. Specifically there is a line



session.screen0.iconbar.mode: static groups (minimized=no) (Workspace)


which when commented out solves my problem. However, I would still like to understand what this line intends to do as it's not clear to me why this causes my windows to close in that way.



EDIT3: Changing the line to



session.screen0.iconbar.mode: Workspace


as outlined as one of the valid options solves the problem. If someone comes along to explain what happened I'll add some bounty.







share|improve this question














This is really about finding the correct setting. When I click on an icon on the iconbar (the part of the toolbar that holds active window tabs? I'm not even sure I know the correct terms for the parts of the window manager) if it does not have the focus, it gets the focus (no problem so far), but if it already has the focus it closes the window. I'd love to change this behavior.



If I click here stackexchange will close:
enter image description here



EDIT: This behavior happens on my desktop but not on my laptop. While there are many differences between the two installs, whatever the problem is it's not inherent to all flux installs. Also there is nothing in the logs (I thought that maybe it's a bug or missing package problem on my machine).



EDIT2: @filipe-brandenburger had the right idea but not the correct file. I painfully disabled files and rebooted, checked , and repeated the process until I found the problem line in my .fluxbox/init file. Specifically there is a line



session.screen0.iconbar.mode: static groups (minimized=no) (Workspace)


which when commented out solves my problem. However, I would still like to understand what this line intends to do as it's not clear to me why this causes my windows to close in that way.



EDIT3: Changing the line to



session.screen0.iconbar.mode: Workspace


as outlined as one of the valid options solves the problem. If someone comes along to explain what happened I'll add some bounty.









share|improve this question













share|improve this question




share|improve this question








edited Mar 22 at 14:47

























asked Mar 15 at 18:33









user1794469

1,3061621




1,3061621







  • 1




    Do you mean close? Or minimize?
    – JdeBP
    Mar 15 at 21:45










  • Yup, I really mean close.
    – user1794469
    Mar 16 at 14:39










  • Did you try to rename (or delete) ~/.fluxbox to have a fresh start?
    – mviereck
    Mar 21 at 15:39






  • 1




    @mviereck that does seem to fix it so it seems like a misconfiguration or a setting and not a bug; just need to find which one.
    – user1794469
    Mar 21 at 20:58












  • 1




    Do you mean close? Or minimize?
    – JdeBP
    Mar 15 at 21:45










  • Yup, I really mean close.
    – user1794469
    Mar 16 at 14:39










  • Did you try to rename (or delete) ~/.fluxbox to have a fresh start?
    – mviereck
    Mar 21 at 15:39






  • 1




    @mviereck that does seem to fix it so it seems like a misconfiguration or a setting and not a bug; just need to find which one.
    – user1794469
    Mar 21 at 20:58







1




1




Do you mean close? Or minimize?
– JdeBP
Mar 15 at 21:45




Do you mean close? Or minimize?
– JdeBP
Mar 15 at 21:45












Yup, I really mean close.
– user1794469
Mar 16 at 14:39




Yup, I really mean close.
– user1794469
Mar 16 at 14:39












Did you try to rename (or delete) ~/.fluxbox to have a fresh start?
– mviereck
Mar 21 at 15:39




Did you try to rename (or delete) ~/.fluxbox to have a fresh start?
– mviereck
Mar 21 at 15:39




1




1




@mviereck that does seem to fix it so it seems like a misconfiguration or a setting and not a bug; just need to find which one.
– user1794469
Mar 21 at 20:58




@mviereck that does seem to fix it so it seems like a misconfiguration or a setting and not a bug; just need to find which one.
– user1794469
Mar 21 at 20:58










1 Answer
1






active

oldest

votes

















up vote
0
down vote



+50










The mouse settings are configured in your ~/.fluxbox/keys



Mouse button clicks map to "keys" named such as Mouse1, Mouse2, Mouse3, etc. for left-click, right-click, middle-click and so on.



There are also modifiers such as OnToolbar, OnTitlebar or OnTab for when you click one of those elements. (Looks like OnTab might be the one you want?)



So take a look at your ~/.fluxbox/keys and see if you find an event for OnTab Mouse1 that looks suspicious...



Considering you have one machine that works and one that doesn't, comparing those two might give you a hint of what might be wrong...



I hope this helps!






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f430456%2fwhy-does-my-application-close-when-i-click-it-in-the-fluxbox-iconbar%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote



    +50










    The mouse settings are configured in your ~/.fluxbox/keys



    Mouse button clicks map to "keys" named such as Mouse1, Mouse2, Mouse3, etc. for left-click, right-click, middle-click and so on.



    There are also modifiers such as OnToolbar, OnTitlebar or OnTab for when you click one of those elements. (Looks like OnTab might be the one you want?)



    So take a look at your ~/.fluxbox/keys and see if you find an event for OnTab Mouse1 that looks suspicious...



    Considering you have one machine that works and one that doesn't, comparing those two might give you a hint of what might be wrong...



    I hope this helps!






    share|improve this answer
























      up vote
      0
      down vote



      +50










      The mouse settings are configured in your ~/.fluxbox/keys



      Mouse button clicks map to "keys" named such as Mouse1, Mouse2, Mouse3, etc. for left-click, right-click, middle-click and so on.



      There are also modifiers such as OnToolbar, OnTitlebar or OnTab for when you click one of those elements. (Looks like OnTab might be the one you want?)



      So take a look at your ~/.fluxbox/keys and see if you find an event for OnTab Mouse1 that looks suspicious...



      Considering you have one machine that works and one that doesn't, comparing those two might give you a hint of what might be wrong...



      I hope this helps!






      share|improve this answer






















        up vote
        0
        down vote



        +50







        up vote
        0
        down vote



        +50




        +50




        The mouse settings are configured in your ~/.fluxbox/keys



        Mouse button clicks map to "keys" named such as Mouse1, Mouse2, Mouse3, etc. for left-click, right-click, middle-click and so on.



        There are also modifiers such as OnToolbar, OnTitlebar or OnTab for when you click one of those elements. (Looks like OnTab might be the one you want?)



        So take a look at your ~/.fluxbox/keys and see if you find an event for OnTab Mouse1 that looks suspicious...



        Considering you have one machine that works and one that doesn't, comparing those two might give you a hint of what might be wrong...



        I hope this helps!






        share|improve this answer












        The mouse settings are configured in your ~/.fluxbox/keys



        Mouse button clicks map to "keys" named such as Mouse1, Mouse2, Mouse3, etc. for left-click, right-click, middle-click and so on.



        There are also modifiers such as OnToolbar, OnTitlebar or OnTab for when you click one of those elements. (Looks like OnTab might be the one you want?)



        So take a look at your ~/.fluxbox/keys and see if you find an event for OnTab Mouse1 that looks suspicious...



        Considering you have one machine that works and one that doesn't, comparing those two might give you a hint of what might be wrong...



        I hope this helps!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 22 at 4:55









        Filipe Brandenburger

        3,467621




        3,467621






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f430456%2fwhy-does-my-application-close-when-i-click-it-in-the-fluxbox-iconbar%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?