[Users] [Bug 4563] New: Crash on copying and pasting from Filtering Log

[noreply at thewildbeast.co.uk]

https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4563

            Bug ID: 4563
           Summary: Crash on copying and pasting from Filtering Log
           Product: Claws Mail (GTK 2)
           Version: 3.17.8
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: Tools
          Assignee: users at lists.claws-mail.org
          Reporter: thewildbeast.reg at kjpetrie.co.uk

Frequently I find Claws Mail crashes on attempting to copy and paste the
Filtering log text into another application, such as a text editor.
Unfortunately, the crash also clears the log so it is not possible to repeat
the exercise or to recover the information I intended to search.

I want to paste it into a text editor so I can search it for the message
concerned to find out why it wasn't filtered as expected.

Steps to reproduce:

1. enable the Filtering log,
2. Fetch Mail
3. Open the filtering log
4. Select all and copy
5. Open another application (eg kwrite)
6. Paste into the other application

Expected result:

The log text will appear in the other application and Claws Mail will be
unaffected.

Actual Result:

Claws Mail usually disappears instantly, either on the copy or on the paste.
(Why on the paste? it shouldn't even receive any input at that point as it's
not the application in focus.) Nothing is pasted into the other application and
a new blank entry has been added to the clipboard.
On reopening Claws Mail and checking the filtering log, this is also now empty.

Running from a terminal produced:

$ claws-mail &
[1] 30378
$ Gtk-Message: 11:23:50.341: (for origin information, set GTK_DEBUG): failed to
retrieve property `gtk-primary-button-warps-slider' of type `gboolean' from rc
file value "((GString*) 0x2755680)" of type `gboolean'

------then, on copying...
The program 'claws-mail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 50612 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

-- 
You are receiving this mail because:
You are the assignee for the bug.