Ticket #2510 (closed bug: fixed)

Opened 3 years ago

Last modified 3 years ago

Basic statistics tool crashes qgis/throws an error on PostGIS layers

Reported by: dr Owned by: cfarmer
Priority: critical: causes crash or data corruption Milestone: Version 1.5.0
Component: Python plugins and bindings Version: Trunk
Keywords: Cc: dr, gislab, alexbruy
Platform Version: Platform: All
Must Fix for Release: Yes Awaiting user input: no

Description

Basic statistic tool doesn't work on PostGIS layers.
 http://gis-lab.info/share/DR/basic-statistics-postgis.png

Change History

Changed 3 years ago by borysiasty

  • owner changed from borysiasty to cfarmer

Changed 3 years ago by lutra

  • must_fix changed from No to Yes

On linux the terminal message is 

Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
Warning: QPixmap: It is not safe to use pixmaps outside the GUI thread
<unknown>: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0

Changed 3 years ago by cfarmer

  • status changed from new to closed
  • resolution set to fixed

This should be fixed in r13028. Tested here with several PostGIS layers and now everything runs fine. Please test and reopen if necessary. If problem persists, please consider providing access to a test PostGIS database, for testing.

-Carson

Note: See TracTickets for help on using tickets.