Ian

So I tried some other desktops this weekend. The only combination that let me get as far as clearing the history with the edit dialog open was openbox with tint2. Other desktops allow the right-click menu while the dialog is open, but hang almost immediately with any attempt to use the left-click history menu, including with the hotkey. I think trying to grab the focus in the menu popup particularly provokes gtk. So I tried the clear_all command through fifo_cmd. Despite the double-free when saving...

Still playing with this. If I shorten the clipboard entry in the edit dialog, it tends not to crash. Instead, I get messages with garbage such as: Try to add 'loa' ele!null. Free 0x5f04d0787140 '��l�_' If I make the entry in the edit dialog longer, then it seems like it always crashes when I hit OK to save it (after having cleared the history with the edit dialog open).

CLI clipboard submissions dropped

I can get the history menu up from the icon. Might depend on whether you have a generic trayicon or an appindicator, or maybe just luck. The hotkey does tend to lock up the whole application, generally not nice to try working with Gtk while the main loop is blocked by gtk_run_dialog(). The icon isn't a true Gtk widget so you can manage a few simple things, but opening too many menus will make it also lock up. 1. Left click on the icon. 2. Right click or alt-E to get the edit dialog. 3. Left click...

I started with 1.2.1, but can also reproduce with a fresh build. To reproduce, click OK to clear the history, then click OK to save the edited clipboard. Running this many times, I see that it doesn't always crash immediately. Sometimes there is an invalid pointer left and the crash occurs a little later. If I comment in some of the tracing, I see messages like: ele!null. Free 0x60f8973972a0 '' free(): invalid pointer

Icon shows up even when -n option is given

Crash from edit history dialog

Memory leaks in the preferences dialog