Philip-Scott / Notes-up

Markdown notes editor & manager
GNU General Public License v2.0
621 stars 47 forks source link

Closes unexpectedly after edit and double click on the name of a note. (Flatpak build) #280

Open fabriciojardim opened 6 years ago

fabriciojardim commented 6 years ago

Tested on Ubuntu 18.04 and Mint 18.3 (both installed from Flathub).

Steps to reproduce:

  1. Edit a note.
  2. Double click on the name of the note you just edited.
  3. Instead of toggle markdown preview the app closes.
Philip-Scott commented 6 years ago

Mind sharing the terminal output? Also try to install the app manually instead of using flatpak to see if you can also get it to crash

fabriciojardim commented 6 years ago

Hi, I copied this information from my terminal after launch the app from there and reproducing the bug, not sure if this is the output you mentioned:

[INFO 14:06:44.617062] Application.vala:154: Notes-Up version: 1.3
[INFO 14:06:44.617093] Application.vala:156: Kernel version: 4.15.0-23-generic

Tried to install from the ppa on ubuntu 18.04 and got an error:

E: The repository 'http://ppa.launchpad.net/philip.scott/notes-up/ubuntu bionic Release' does not have a Release file.

Anyway I imagined that by manually install you mean that I build it by myself to test. Will see if I can figure out how to do that.

Thanks for the response and for developing the app!

Philip-Scott commented 6 years ago

That output you sent is just the normal output.... does it only say that when it crashes?

You might need to compile it by yourself to check what's going on. I'll be running a build over at that PPA you added, but not sure everything will work and i don't really have the time to check atm to test things.

fabriciojardim commented 6 years ago

Yes. Thats the only output I got. Will do the compilation latter. As I have no practice with it I want to do it when I have time to pay attention.

ChristopherNugent commented 6 years ago
[INFO 20:10:04.593570] Application.vala:154: Notes-Up version: 1.3
[INFO 20:10:04.593609] Application.vala:156: Kernel version: 4.15.0-33-generic
[WARNING 20:10:04.608686] Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-C91BgcGKuO: Connection refused

** (WebKitWebProcess:12005): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-C91BgcGKuO: Connection refused
[FATAL 20:10:58.660716] enchant_dict_check: assertion 'len' failed
[FATAL 20:11:03.125433] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:12.657655] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:15.127662] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:26.159448] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:26.463350] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:27.325258] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:28.335833] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:29.896170] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:30.177992] enchant_dict_check: assertion 'len' failed
[FATAL 20:12:30.363993] enchant_dict_check: assertion 'len' failed
[FATAL 20:14:52.965461] [GLib-GIO] g_file_get_basename: assertion 'G_IS_FILE (file)' failed
[FATAL 20:14:52.965536] [GLib] g_utf8_strdown: assertion 'str != NULL' failed
[FATAL 20:14:52.965587] [GLib] g_str_has_suffix: assertion 'str != NULL' failed
[FATAL 20:14:52.965652] [GLib-GIO] g_file_get_path: assertion 'G_IS_FILE (file)' failed
[FATAL 20:14:52.965685] [GLib-GIO] g_file_new_for_path: assertion 'path != NULL' failed
[FATAL 10:17:32.844025] enchant_dict_check: assertion 'len' failed
[FATAL 10:17:33.142112] enchant_dict_check: assertion 'len' failed
[FATAL 10:18:21.048981] enchant_dict_check: assertion 'len' failed
[FATAL 10:18:21.312793] enchant_dict_check: assertion 'len' failed
Segmentation fault (core dumped)

Terminal output from the crash

Philip-Scott commented 6 years ago

What text do you guys use to make it crash? Mind sending a video? :) I still can't reproduce it :/

ChristopherNugent commented 6 years ago

Not sure. I'll start logging console output to see if that reveals anything. Is there flag that enables a more verbose console output?

Philip-Scott commented 6 years ago

There's a -d to show debug info, but i don't think it will be useful. But can also run it with gdb to get a stack trace of where exactly does it crash :)