Mint-X themes cause GCstar to freeze

[flan_suse]

http://forums.gcstar.org/viewtopic.php?pid=7148#p7148
http://forums.gcstar.org/viewtopic.php?pid=7148
http://forums.gcstar.org/viewtopic.php?id=1817

With the Mint-X or Mint-X-Metal theme, GCstar freezes upon doing certain actions, such as adding a new entry to the collection or using the import tool. It has something to do with the "Controls" of these two GTK themes.

This problem does not occur if another theme is selected.

[Martin Webster (martinwebster)]

I can confirm that GCStar freezes when loading a collection but _not_ with the Mint-X* themes. Running GCStar from the console provides no feedback; the application simply hangs. However, forcing quit displays the following message in the console:

Magic number checking on storable file failed at ../../lib/Storable.pm (autosplit into ../../lib/auto/Storable/fd_retrieve.al) line 398, at /usr/bin/../share/gcstar/lib/GCPlugins.pm line 98

I'm happy to provide more feedback/ debugging information. Please let me know how I can help.

[flan_suse (flansuse)]

Martin, your problem might not be related to this bug. What version of Mint and what version of GCstar? This seems to be a common problem for GCstar 1.6.1 users (maybe even earlier versions) for Linux Mint 10 (or LMDE) using Mint-X-Metal or Mint-X theme.

They _can_ load and open collections with no freezes. The problem arises when they try to _edit_ an item (book, movie, game).

[Martin Webster (martinwebster)]

Adding additional information...

Linux Mint 10 "Julia" 32 bit
GCStar 1.5.0

Problem persistent with Mint-X and Mint-X-Metal themes.

I also created a new collection and GCStar also freeze when loading this. Maybe it's a different bug. However, without much debugging information that's hard to tell. The common theme is the use of Mint-X* themes.

[flan_suse (flansuse)]

Does the problem go away if you go to Appearance > Customize > and choose something else under Controls?

[Martin Webster (martinwebster)]

Yes, changing the controls as described in your post does resolve the problem.