search

phase1geo / Outliner

Outlining application for elementary OS
GNU General Public License v3.0
56 stars 6 forks source link

Old behavior (crash at Ctrl-arrow movement in row) #59

Open jaslar opened 3 years ago

jaslar commented 3 years ago

I downloaded the development branch today, and saw cool stuff there (split row, Focus). But when I cloned it, it crashed in ways I thought you'd fixed (crashed when I used mostly ctrl-arrow to navigate within a row). Then I saw that the Master branch was several commits ahead, so downloaded that, too. But it too has the old behavior. Did the bug creep back in?

phase1geo commented 3 years ago

I haven't made any changes to that area of code. I'm unable to reproduce the problem on my end. Is there any chance that you could record a short screencast of the issue and make sure that the terminal output is displayed after the application crashes?

jaslar commented 3 years ago

I downloaded a screen cast program to try to capture it. In a row, I can move forward and back by character, to the beginning and end of the row. But the instant I try the Ctrl-arrow (left or right), the program just closes, and the screen cast with it. It wouldn't show you anything but the screen winking out. Where/how can I find the terminal output?

jaslar commented 3 years ago

Screen record from 2020-10-27 13 43 38

Where do I find the log file for errors?

phase1geo commented 3 years ago

If you start Outliner from the terminal:

After the application crashes, the Terminal application should have some sort of output displayed within it. This was the error information I was referring to.

I'm assuming that in the video, after you jumped to the end of the line, you attempted to do a Control-Left to move backwards by a word?

phase1geo commented 3 years ago

I'm attempting to try exactly what you are doing in the video and I am unable to get the application to crash. I can seemingly move the cursor around using all sorts of keyboard shortcuts (including Control-left/right) without any issues. Ugh.

jaslar commented 3 years ago

Yes, that's right. I jumped to the end of the line, then did a Control-Left. I did the terminal launch (cool trick!), and got this:

$ com.github.phase1geo.outliner Segmentation fault

Not much to go on. I wonder if I somehow set up a configuration file with all my attempts to install the latest version. I admit that I'm new to git.

Does this provide any clues?

  1. It used to work really well, no problems with these very important Ctrl-left/right keys. I had built it from the development branch.
  2. I deleted the Outliner folder created by the git command (sudo git clone https://github.com/phase1geo/Outliner.gitcom.github.phase1geo.outliner & ./app install (maybe sudo ./app install), I don't remember). Then I had the old problem.
  3. I deleted that folder again, switched to the master branch, repeated the git commands. Same problem.
  4. I deleted the Outliner folder again, went to AppCenter to remove and reinstall. No change.

Usually, when something goes wrong, it's me!

Sorry for the hassle. But I have grown to quite like this program, and miss it!

phase1geo commented 3 years ago

Let's try this instead. When you are in the terminal, do the following:

This is going to compile and start the application within the debug environment. You will see a 'gdb' prompt, type 'run' to run the application. Use the application to cause the crash. When the crash occurs, go back to the Terminal and enter the command 'where'. The resulting output is going to be a stack trace of the failure. Add that output to this bug report. This should hopefully provide me the information that I need to get down to the bottom of what is going on.

Let me know if you have any issues with the above instructions.

phase1geo commented 3 years ago

BTW, if the application crashes on startup, you will still be able to type 'where' to get a stack trace of that problem (it may differ from the Control-left/right crash), but if you include that stack trace output, I'll let you know what to do to move past that problem.

jaslar commented 3 years ago

Here's the output:

$ ./app debug The Meson build system Version: 0.49.2 Source dir: /home/jlarue/Outliner Build dir: /home/jlarue/Outliner/build Build type: native build Project name: com.github.phase1geo.outliner Project version: 1.4.0 Native C compiler: cc (gcc 7.5.0 "cc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0") Native Vala compiler: valac (valac 0.40.24) Build machine cpu family: x86_64 Build machine cpu: x86_64 Found pkg-config: /usr/bin/pkg-config (0.29.1) Configuring config.h using configuration Dependency gtk+-3.0 found: YES 3.22.30 Library m found: YES Library markdown found: YES Dependency gobject-2.0 found: YES 2.56.4 Dependency glib-2.0 found: YES 2.56.4 Dependency cairo found: YES 1.15.10 Dependency gee-0.8 found: YES 0.20.2 Dependency granite found: YES 5.5.0 Dependency gtk+-3.0 found: YES (cached) Dependency libxml-2.0 found: YES 2.9.4 Dependency webkit2gtk-4.0 found: YES 2.28.4 Program meson/post_install.py found: YES (/home/jlarue/Outliner/meson/post_install.py) Build targets in project: 11 Found ninja-1.8.2 at /usr/bin/ninja [1/75] Generating outliner-resources_h with a custom command. XMLLINT not set and xmllint not found in path; skipping xml preprocessing. [2/75] Generating outliner-resources_c with a custom command. XMLLINT not set and xmllint not found in path; skipping xml preprocessing. [6/75] Compiling Vala source ../src/exports/ExportH...Utils.vala ../tests/assert.vala ../tests/test.vala. ../src/TextParser.vala:49.72-49.75: warning: copying delegates is not supported ../src/TextParser.vala:28.5-28.26: warning: copying delegates is not supported Compilation succeeded - 2 warning(s) [75/75] Linking target com.github.phase1geo.outliner. ./app: line 81: gdb: command not found jlarue@elemac:~/Outliner$

On Tue, Oct 27, 2020 at 10:40 PM Trevor Williams notifications@github.com wrote:

BTW, if the application crashes on startup, you will still be able to type 'where' to get a stack trace of that problem (it may differ from the Control-left/right crash), but if you include that stack trace output, I'll let you know what to do to move past that problem.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phase1geo/Outliner/issues/59#issuecomment-717690826, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMDL7NF67JXGB3NFRTXB26DSM6OFJANCNFSM4S6Q577Q .

-- James LaRue

Mobile: 720-530-4294 Website and Blog: jlarue.com Twitter: @jaslar

phase1geo commented 3 years ago

Looks like you don’t have the gdb debugger installed on your system. I think ‘sudo apt install gdb’ will do this for you, but I’m not completely sure. Once you get gdb installed, try the app debug steps again.

jaslar commented 3 years ago

I was able to install gdb. Results:

$ ./app debug The Meson build system Version: 0.49.2 Source dir: /home/jlarue/Outliner Build dir: /home/jlarue/Outliner/build Build type: native build Project name: com.github.phase1geo.outliner Project version: 1.4.0 Native C compiler: cc (gcc 7.5.0 "cc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0") Native Vala compiler: valac (valac 0.40.24) Build machine cpu family: x86_64 Build machine cpu: x86_64 Found pkg-config: /usr/bin/pkg-config (0.29.1) Configuring config.h using configuration Dependency gtk+-3.0 found: YES 3.22.30 Library m found: YES Library markdown found: YES Dependency gobject-2.0 found: YES 2.56.4 Dependency glib-2.0 found: YES 2.56.4 Dependency cairo found: YES 1.15.10 Dependency gee-0.8 found: YES 0.20.2 Dependency granite found: YES 5.5.0 Dependency gtk+-3.0 found: YES (cached) Dependency libxml-2.0 found: YES 2.9.4 Dependency webkit2gtk-4.0 found: YES 2.28.4 Program meson/post_install.py found: YES (/home/jlarue/Outliner/meson/post_install.py) Build targets in project: 11 Found ninja-1.8.2 at /usr/bin/ninja [1/75] Generating outliner-resources_h with a custom command. XMLLINT not set and xmllint not found in path; skipping xml preprocessing. [2/75] Generating outliner-resources_c with a custom command. XMLLINT not set and xmllint not found in path; skipping xml preprocessing. [6/75] Compiling Vala source ../src/exports/ExportH...Utils.vala ../tests/assert.vala ../tests/test.vala. ../src/TextParser.vala:49.72-49.75: warning: copying delegates is not supported ../src/TextParser.vala:28.5-28.26: warning: copying delegates is not supported Compilation succeeded - 2 warning(s) [75/75] Linking target com.github.phase1geo.outliner. GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./com.github.phase1geo.outliner...done.

phase1geo commented 3 years ago

After that last line of output do you get a gdb prompt? If so, type ‘run’ to start running the application.

jaslar commented 3 years ago

OK. The program launched. It worked perfectly, no control-arrow problems at all. I exited, went back to the gdb command, and guessed quit.

(gdb) run Starting program: /home/jlarue/Outliner/build/com.github.phase1geo.outliner [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe7e5b700 (LWP 24683)] [New Thread 0x7fffe765a700 (LWP 24684)] [New Thread 0x7fffe63cf700 (LWP 24685)] [New Thread 0x7fffe5243700 (LWP 24700)] [Thread 0x7fffe5243700 (LWP 24700) exited] [New Thread 0x7fffe5243700 (LWP 24702)] [Thread 0x7fffe5243700 (LWP 24702) exited] [Thread 0x7fffe63cf700 (LWP 24685) exited] [Thread 0x7fffe7e5b700 (LWP 24683) exited] [Thread 0x7ffff7fbca80 (LWP 24679) exited] [Inferior 1 (process 24679) exited normally] (gdb) quit jlarue@elemac:~/Outliner$

On Wed, Oct 28, 2020 at 4:00 PM Trevor Williams notifications@github.com wrote:

After that last line of output do you get a gdb prompt? If so, type ‘run’ to start running the application.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phase1geo/Outliner/issues/59#issuecomment-718233415, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMDL7NCOPVQT7GWSUDBAMR3SNCIADANCNFSM4S6Q577Q .

-- James LaRue

Mobile: 720-530-4294 Website and Blog: jlarue.com Twitter: @jaslar

phase1geo commented 3 years ago

Crud. Does the application behave badly again when you run it without gdb? Like if you just run './app run' in the prompt?

jaslar commented 3 years ago

No, when I ./app run everything works great. I suppose that's a work around.

After exiting normally, I get,

Directory already configured.

Just run your build command (e.g. ninja) and Meson will regenerate as necessary. If ninja fails, run "ninja reconfigure" or "meson --reconfigure" to force Meson to regenerate.

If build failures persist, run "meson setup --wipe" to rebuild from scratch using the same options as passed when configuring the build. To change option values, run "meson configure" instead. ninja: no work to do.

Does that suggest a way forward?

On Wed, Oct 28, 2020 at 9:13 PM Trevor Williams notifications@github.com wrote:

Crud. Does the application behave badly again when you run it without gdb? Like if you just run './app run' in the prompt?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phase1geo/Outliner/issues/59#issuecomment-718331871, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMDL7NBK4A3RG2WOH7G6ADLSNDMVNANCNFSM4S6Q577Q .

-- James LaRue

Mobile: 720-530-4294 Website and Blog: jlarue.com Twitter: @jaslar

phase1geo commented 3 years ago

I think if you do an './app install' from the command-line, things should be working for you when launching the application from the desktop.

jaslar commented 3 years ago

And you are correct. I don't understand what's changed exactly, but yet, I'm working again. Thank you.

On Sun, Nov 1, 2020 at 8:04 AM Trevor Williams notifications@github.com wrote:

I think if you do an './app install' from the command-line, things should be working for you when launching the application from the desktop.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phase1geo/Outliner/issues/59#issuecomment-720102395, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMDL7NGB5AMAIABSTBA2L4TSNV2JPANCNFSM4S6Q577Q .

-- James LaRue

Mobile: 720-530-4294 Website and Blog: jlarue.com Twitter: @jaslar

phase1geo commented 3 years ago

To be honest, I'm not exactly sure why the self-built executable is working but the AppCenter one is not. This should at least get things working for you until I can figure out what the issue is.

jaslar commented 3 years ago

Thanks, Trevor. I greatly appreciate your attention to this always more useful product.

On Sun, Nov 1, 2020 at 10:17 PM Trevor Williams notifications@github.com wrote:

To be honest, I'm not exactly sure why the self-built executable is working but the AppCenter one is not. This should at least get things working for you until I can figure out what the issue is.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phase1geo/Outliner/issues/59#issuecomment-720241257, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMDL7NGT7RXXVA7ZPGLPJATSNY6G7ANCNFSM4S6Q577Q .

-- James LaRue

Mobile: 720-530-4294 Website and Blog: jlarue.com Twitter: @jaslar

dagelf commented 3 years ago

If I hold Ctrl-up and move past the top item with expanded subnodes, and then ctrl-Down, into the former top item's expanded subnodes, then collapsing and expanding some subnodes the spacing doesn't collapse but just goes blank. I'm still trying to figure out when exactly this happens. The problem seems to disappear for good sequentially expanding everything. This is with the current git version.