|
|
| Reporter | MirceaKitsune | Assigned To | | |
|---|
| Priority | normal | Severity | normal | Reproducibility | sometimes |
|---|
| Status | closed | Resolution | unable to reproduce | |
|---|
| Platform | x64 | OS | Linux openSUSE | OS Version | Release |
|---|
| Product Version | TDM 2.08 | |
|---|
|
|
| Summary | 0005434: Crash when copying to clipboard: IA__gtk_check_menu_item_set_active / GTK_IS_CHECK_MENU_ITEM |
|---|
| Description | Sometimes when copying several entities and / or brushes, by shift-drag selecting them then pressing Control + C, DarkRadiant will crash. I posted the console output in the Additional Information field... it seems to be a bad assertion by IA__gtk_check_menu_item_set_active for GTK_IS_CHECK_MENU_ITEM, could be related to the Linux version exclusively. |
|---|
| Steps To Reproduce | Select a lot of entities and brushes at once and use Ctrl + C to copy them. The crash should occur at that moment. |
|---|
| Additional Information | Gtk-Message: 18:08:13.955: Failed to load module "appmenu-gtk-module"
(darkradiant:5381): Gtk-CRITICAL **: 18:08:14.366: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
(darkradiant:5381): Gtk-CRITICAL **: 18:08:14.366: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
(darkradiant:5381): Gtk-CRITICAL **: 18:08:14.366: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
(darkradiant:5381): Gtk-CRITICAL **: 18:08:14.366: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
(darkradiant:5381): Gtk-CRITICAL **: 18:08:14.366: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
The program 'darkradiant' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 68088 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.) |
|---|
| Tags | Crash, Freeze, gtk |
|---|
|
|
