lnav icon indicating copy to clipboard operation
lnav copied to clipboard

SQL error when opening log files with lnav

Open kourosh7 opened this issue 3 months ago • 4 comments

lnav version lnav 0.13.2

Describe the bug When opening certain log files I get this error:

 SQL error: near "7": syntax error                                                                                                                                                                                                                                                  
;7;rgb:0000/afaf/afaf\

If I backspace through that ;7;rgb:0000/afaf/afaf\ text then the error goes away and the log shows fine

To Reproduce I don't always see the problem. But I'll attach a log file I see the problem with.

f6a.log

This is my environment:

$ cat /etc/os-release 
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
$ uname -a
Linux kourosh 6.5.0-1023-oem #24-Ubuntu SMP PREEMPT_DYNAMIC Tue May  7 14:26:31 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Is it the same issue as https://github.com/tstack/lnav/issues/1518 ?

kourosh7 avatar Oct 21 '25 22:10 kourosh7

What terminal are you using?

tstack avatar Oct 21 '25 23:10 tstack

GNOME Terminal Version 3.44.0 for GNOME 42

kourosh7 avatar Oct 22 '25 15:10 kourosh7

This happens when there is some issue with handling escape codes from the terminal. Sometimes it's a timing-related thing, which looks like the case here. I have a similar Ubuntu install I test with and haven't seen this issue yet, but I'll keep trying to replicate.

tstack avatar Oct 22 '25 21:10 tstack

Same lnav version and very similar issue. Using konsole 25.04.3 I was seeing errors like SQL error: near "$y": syntax error. In my case, the problem appears to be with Zellij running locally or through ssh. I casually upgraded Zellij from 0.41.X to 0.43.1 and the problem is gone. I confirmed going back to 0.41 and the problem appeared again. The changelog for Zellij announces improvements in asynchronous processing and general performance, so maybe that was it.

pandiloko avatar Nov 07 '25 10:11 pandiloko