On 5/13/19 12:51 PM, Edgar Pettijohn wrote:
> On May 13, 2019 2:58 AM, shadrock uhuru <niyal...@gmail.com> wrote:
>>
>>
>> On 5/13/19 1:35 AM, shadrock uhuru wrote:
>>> hi everyone
>>> since upgrading to 6.5 my i3bar no longer works.
>>> i have not changed the configuration in any way
>>> when i run the i3status command manually in a terminal the bar is not
>>> displayed but the correct infomation that would be on the i3bar is
>>> echoed to the terminal.
>>> the message on the right hand of the i3bar is
>>> error: status_command not found or is missing a library dependency
>>> (exit 127)
>>> the left hand side of the bar is functioning correctly
>>> the following is from the i3 log file.
>>>
>>> grep i3bar 'i3log-2019-05-12-0-41-37'
>>>
>>> 05/12/19 00:41:40 - config_parser.c:parse_config:267 - CONFIG(line
>>> 152): # Start i3bar to display a workspace bar (plus the system
>>> information i3status
>>> 05/12/19 00:41:41 - Starting bar process: i3bar --bar_id=bar-0
>>> --socket="/tmp/i3-shadrock.Q7Rfx2/ipc-socket.80799"
>>> 05/12/19 00:41:41 - executing: i3bar --bar_id=bar-0
>>> --socket="/tmp/i3-shadrock.Q7Rfx2/ipc-socket.80799"
>>> 05/12/19 00:41:41 - WM_CLASS changed to i3bar (instance), i3bar (class)
>>> 05/12/19 00:41:41 - WM_NAME changed to "i3bar for output LVDS-1"
>>> 05/12/19 00:41:41 - Checking window 0x00e00003 (class i3bar)
>>> 05/12/19 00:41:41 - Checking window 0x00e00003 (class i3bar)
>>> [/usr/obj/ports/i3-4.16.1/i3-4.16.1/../i3-4.16.1/i3bar/src/child.c:468]
>>> ERROR: Child (pid: 72679) unexpectedly exited with status 127
>>>
>>>
>> how do i debug for a missing library ?
>> shadrock
>>
> LD_DEBUG=1
thanks
found the problem by enabling logging for i3
i had my i3 config file at ~/.i3 instead of at ~/.config/i3 which had an
old i3 config file ,
after copying everything from ~i3 to ~/config/i3 and restarting i3 all
is working again.
shadrock
