[Bug]: When you start the program, an error message appears.

[pulmuone]

What did you do?

QString::arg: Argument missing: "L1 - 0의 0" , 0

What did you expect to see?

no error

What did you see instead?

QString::arg: Argument missing: "L1 - 0의 0" , 0

DB4S Version

3.13.0-rc1

What OS are you seeing the problem on?

Windows

OS version

Windows 10

Relevant log output

QString::arg: Argument missing: "L1 - 0의 0" , 0

Prevention against duplicate issues

• I have searched for similar issues

[lucydodo]

Hi @pulmuone, Thank you for reporting this. However, I was unable to reproduce the same issue in my enviornment.
Have you installed and run DB4S? or did you download a zip file and run it portably?

[pulmuone]

Hi @pulmuone, Thank you for reporting this. However, I was unable to reproduce the same issue in my enviornment. Have you installed and run DB4S? or did you download a zip file and run it portably?

This is the install file I used.
https://github.com/sqlitebrowser/sqlitebrowser/releases/download/v3.13.x-rc1/DB.Browser.for.SQLite-3.13.0-rc1-win64.msi

[lucydodo]

That's weird because I installed and tested with the same file. Did you try running DB4S from the command line?
Additionally, is it the same if you reset the current DB4S configuration and run it?
You can backup, restore, and reset current configuration in PreferencesDialog.

[justinclift]

As an extra thought, does that dialog pop up right after starting the application, or does it happen in response to something else? (clicking a button or something?)

Am trying to figure out what part of the application might be triggering the start of the problem. 😄

[pulmuone]

As an extra thought, does that dialog pop up right after starting the application, or does it happen in response to something else? (clicking a button or something?)

Am trying to figure out what part of the application might be triggering the start of the problem. 😄

When you start the program, an error message appears immediately.

[justinclift]

Interesting. I wonder if it's something to do with the check for new updates then?

There's a setting to disable that check somewhere in the application Preferences. If you turn that off, does the error still appear?