Bugs and Known Issues - tomboy-notes/tomboy-ng GitHub Wiki

Bugs-and-Known-Issues

This is the tomboy-ng Known Issues and To-Do list for Github Wiki. Its generated from a note in the tomboy-ng doc dir, don't edit the wiki directly.

Bugs

Bug reports and feature requests should be via Github https://github.com/tomboy-notes/tomboy-ng/issues

There is some advice about DIY debugging further down this document.

Known Issues

    • Do not set your notes directory to be on a network share. Please keep your notes on a local disk and use the sync facility to share them with other machines (or even the same multiboot machine).

Specific Things with a Work Around

QT5 versions

Qt5 with earlier Qt5 libraries

Can be a problem on some Linux Desktops. Generally, I don't suggest Qt5 version of tomboy-ng with systems that use Qt5 earlier than 5.15. So, using Ubuntu 20.04 (Qt5 is 5.12) is a risk factor. Setting your Qt theme to 'gtk3' on those early Qt5 systems is asking for trouble. I have not tested on systems with Qt5 between 5.12 and 5.15 so your mileage may vary. By time you get to Qt5 5.15, it all just works !

Dark Theme

Like most Qt applications, the QT5 version does not pick up the Dark Theme from the operating system. You can pass the executable a --dark-theme switch (poor choice) but much better to install qt5ct and set the colour theme you like. You will need to set an environment variable that tells Qt apps (including qt5ct itself) that you are using qt5ct colours, either by adding an environment variable when you start tomboy-ng -

QT_QPA_PLATFORMTHEME=qt5ct tomboy-ng [enter]

Better still, make all your Qt5 app have a nice uniform look. Set that var in either /etc/environment (requires root or, simpler in a .xsessionrc file in your home dir.

cd ; echo "export QT_QPA_PLATFORMTHEME=qt5ct" >> .xsessionrc

And logging out and back in again, the qt5ct command has a nice GUI to let you select your look and feel. But don't set qt5ct to gtk2, messes with highlighting found text.

A similar, simpler and perhaps better approach is to tell the Qt5 app to follow the current (probably gtk2) theme on your system. Similar to above, just set QT_QPA_PLATFORMTHEME=gtk2 instead of the above. You may need to install qt5-style-plugins package package if its not already installed.

Cancelled Bullets - When text is bulleted and then converted back to plaintext, it has a small indent that is not removable. It goes away when next the note is loaded and is not show in printed copy but is annoying! Its an upstream issue and its being worked on.

QT5 versions and Gnome Desktops

It appears that even Qt5 apps can now use XWayland so much of this is unnecessary, leave it here for now, just in case.

Almost all Gnome Desktops now use the Wayland Display Manager instead of X (or XCB). QT5 has a plugin that will manage the connection between a QT5 app and Wayland, typically called qtwayland5, you may find it already installed or need to manually install it yourself. If you run a QT5 app, such as the QT5 version of tomboy-ng, you may see a warning to the effect that its ignoring the request to run under Wayland, if you want it to run under Wayland, do something like -

QT_QPA_PLATFORM=wayland tomboy-ng [enter]

You can do so (if you have qtwayland5 installed) but it seems to make little or no difference and does trigger a couple of warning messages from the QT libraries. So, honestly, don't worry about it.

Calc separator

In the calculator, many countries use the comma instead of a period as a decimal separator. Turns out this could be quite a challenge, my apologies to people from locales where this is an issue. https://forum.lazarus.freepascal.org/index.php/topic,56305.msg418384.html#msg418384

System Tray Issues

Please see https://github.com/tomboy-notes/tomboy-ng/wiki/System-Tray-on-Linux

Long term 'maybe' stuff

These are things I have no immediate plans to fix, but they might be addressed some time in the future if there is some demand from end users.

    • On Linux GTK2 based versions, using the Compose Key approach to entering accented characters results in a bad character also being inserted. This is a known, upstream issue, https://bugs.freepascal.org/view.php?id=38454 . Qt5 versions do not have this problem.
    • Stop house keeping from moving viewport.
    • Restoring cursor position on note load.
    • Dark theme is less than perfect on Windows and unknown on Mac. Windows will not let us set a dark background to buttons, must look at owner draw modes.
    • Lines starting with an '*' should be auto converted to a Bullet.
    • Tabs do not work.
    • Revise controls, at present modelled on Tomboy, we can improve.

Debugging

If you have problems with the application, or wish to make a feature request, please report via the github tomboy-ng issues facility.

If tomboy-ng crashes or does something unexpected, there are a number of command line switches that may reveal whats going on (to either yourself of, if posted to 'issues', the author). Using these command line switches is easy in Linux but Windows or Mac users need to capture the information in a file, see below -

Command Line Switches

    • --dark-theme
    • -l --lang=CCode Force Language, en, es, uk, fr, nl
    • -h --help Show this help message and exit.
    • --version Print version and exit
    • --no-splash Do not show small status/splash window
    • --debug-sync Show debug messages during Sync
    • --debug-index Show debug msgs while indexing notes
    • --debug-spell Show debug messages while spell setup
    • --config-dir=PATH_to_DIR Create or use an alternative config
    • --open-note=PATH_to_NOTE Open indicated note, switch is optional
    • --debug-log=SOME.LOG Direct debug output to SOME.LOG.
    • --import-txt=PATH_to_FILE Import file into Note Repo also -t
    • --import-md=PATH_to_FILE Import file into Note Repo also -m
    • --import-note=PATH_to_NOTE Import file into Note Repo also -n
    • --title-fname Use Filename as title for import txt & md

Capturing to a file

Windows and Mac do not, for this purpose, have a console. But they too can be told to capture this log info to a file using another command line switch or by setting an env variable that specifies a file name. Please ensure you have permission to write to the location specified. For example a linux user would -

   set tomboy-ng_debuglog=c:\%userprofile%\debug.txt

Mac users can do something similar from a terminal :

   open /Applications/tomboy-ng.app --args     "--debug-log=$HOME/tomboy-ng.log"  "--debug-sync"



   Linux users who need a debug log file can also :



   tomboy-ng --debug-sync --debug-log=$HOME/tomboy-ng.log

Windows users should do something like this -

    • Right click the startbutton and select "run". In the field, enter this command line exactly as show (including the inverted commas) -
    • "C:\Program Files\tomboy-ng\tomboy-ng.exe" --debug-index --debug-log=%userprofile%\Desktop\tomboy-log.txt
    • Press enter, tomboy-ng should start up normally. Close it.
    • A file called tomboy-log.txt will have been created on your desktop.

In all cases, you may need to zip that file up to post it on Github. If you do intend to post such a log file to (eg) the Tomboy help system, do please check through it first to ensure there is nothing there you don't want the world to see. It may include things like note Titles for example. Note that a debug file will capture very little data unless of the debug switches is also set.

⚠️ **GitHub.com Fallback** ⚠️