gdk_drawing_context_get_cairo_context: assertion 'GDK_IS_DRAWING_CONTEXT (context)' failed Segmentation fault

Bug #1871781 reported by ZuLu
56
This bug affects 12 people
Affects Status Importance Assigned to Milestone
pgadmin3 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Every time I select a database and then go to SQL query tool, I get a segmentation fault.

pgadmin3
Debug: Adding duplicate image handler for 'PNG file'
(pgadmin3:10182): Gdk-CRITICAL **: 10:56:30.191: The window 0x5575b2343400 already has a drawing context. You cannot call gdk_window_begin_draw_frame() without calling gdk_window_end_draw_frame() first.

(pgadmin3:10182): Gdk-CRITICAL **: 10:56:30.191: gdk_drawing_context_get_cairo_context: assertion 'GDK_IS_DRAWING_CONTEXT (context)' failed
Segmentation fault

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pgadmin3 1.22.2-6build1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 9 10:55:29 2020
InstallationDate: Installed on 2019-03-31 (374 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: pgadmin3
UpgradeStatus: Upgraded to focal on 2020-04-04 (4 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2020-04-04T23:30:01.380007

Revision history for this message
ZuLu (nenominal) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pgadmin3 (Ubuntu):
status: New → Confirmed
Revision history for this message
Georgy Silkly (rekgrpth) wrote :

I fixed it (and other bugs found) in my fork https://github.com/RekGRpth/pgadmin3

Revision history for this message
Ryan Grange (ryantg) wrote :

Bug is still present in 20.04.4.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.