View Issue Details

IDProjectCategoryView StatusLast Update
0005434The Dark ModDesign/Codingpublic09.12.2022 05:28
ReporterMirceaKitsune Assigned To 
PrioritynormalSeveritynormalReproducibilitysometimes
Status closedResolutionunable to reproduce 
Platformx64OSLinux openSUSEOS VersionRelease
Product VersionTDM 2.08 
Summary0005434: Crash when copying to clipboard: IA__gtk_check_menu_item_set_active / GTK_IS_CHECK_MENU_ITEM
DescriptionSometimes 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 ReproduceSelect a lot of entities and brushes at once and use Ctrl + C to copy them. The crash should occur at that moment.
Additional InformationGtk-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.)
TagsCrash, Freeze, gtk

Activities

MirceaKitsune

MirceaKitsune

29.11.2020 16:17

reporter   ~0013046

Please move this to the DarkRadiant project: For some reason Mantis changed the active project on me while I was posting this, despite clicking the report button with DR selected... it got posted into the TheDarkMod project instead. I tried to edit the issue but I can't change the project of the issue any more.
nbohr1more

nbohr1more

09.12.2022 05:28

developer   ~0015532

Please create a new tracker if this can be reproduced in the latest DarkRadiant. This issue was reported before many substantial GUI changes

Issue History

Date Modified Username Field Change
29.11.2020 16:14 MirceaKitsune New Issue
29.11.2020 16:14 MirceaKitsune Tag Attached: Crash
29.11.2020 16:14 MirceaKitsune Tag Attached: Freeze
29.11.2020 16:14 MirceaKitsune Tag Attached: gtk
29.11.2020 16:17 MirceaKitsune Note Added: 0013046
09.12.2022 05:27 nbohr1more Status new => closed
09.12.2022 05:27 nbohr1more Resolution open => unable to reproduce
09.12.2022 05:28 nbohr1more Note Added: 0015532