#943: wxpython gui hangs after switching to cairo display driver
------------------------------------------+---------------------------------
 Reporter:  epatton                       |       Owner:  grass-dev@…           
   
     Type:  defect                        |      Status:  new                   
   
 Priority:  critical                      |   Milestone:  6.4.3                 
   
Component:  wxGUI                         |     Version:  svn-develbranch6      
   
 Keywords:  cairo, driver, gui, wxpython  |    Platform:  Linux                 
   
      Cpu:  All                           |  
------------------------------------------+---------------------------------
Changes (by hamish):

  * priority:  normal => critical
  * component:  Display => wxGUI
  * milestone:  6.5.0 => 6.4.3


Comment:

 ok, seems like two bugs,

 [debian/squeeze on amd64, testing in both relbr64 and devbr6, cairo 1.10]

 with GRASS_PNG_READ as in the example in comment:1, d.mon still crashes
 with,
 {{{
 G643svn> export GRASS_PNGFILE=map.bmp
 G643svn> export GRASS_PNG_READ=TRUE
 G643svn> d.mon -L
 *** glibc detected *** status: free(): invalid pointer:
 ...
 G643svn> echo $?
 1
 }}}
 (as above)

 If I `touch map.bmp` first then d.mon runs ok.
 So it either needs to test if the file exists and exit with an error, or
 test if it exists and skip trying to read it, or create it if it's
 missing. (maybe d.mon shouldn't be creating it..)

 ---

 in the wxGUI preferences, after changing the Map Display -> Display driver
 to "cairo" I get this error in the command console:

 {{{
 Settings applied to current session but not saved
 ERROR: Rendering failed. Details: File </tmp/tmpsF0WNE.ppm>
 not found
 }}}

 however, there is an empty file in /tmp/ called `tmpsF0WNE`.  (no .ppm)


 ?,
 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/943#comment:9>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to