DOOMer / screengrab

Crossplatform tool for fast making screenshots.
http://screengrab.doomer.org/
GNU General Public License v2.0
23 stars 8 forks source link

window close unexpectedly (0.9.96 unstable) #24

Closed bulinancio closed 10 years ago

bulinancio commented 11 years ago

When I build unstable version from this source:

http://screengrab.doomer.org/download/screengrab-0_9_96_/

the window close unexpectedly if you select "Type: Window" and click on "New Screen", if the main window of the app is on the Root window of the desktop screen.

However, this DOES NOT happens if I use the app from the package:

http://screengrab.doomer.org/download/screengrab_0_9_96-ubuntu1_i386/

This is the buggy log from terminal:


QPixmap::scaled: Pixmap is a null pixmap X Error: BadWindow (invalid Window parameter) 3 Major opcode: 15 (X_QueryTree) Resource id: 0x0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 3 (X_GetWindowAttributes) Resource id: 0x0 Not window attributes. X Error: BadAlloc (insufficient resources for operation) 11 Major opcode: 53 (X_CreatePixmap) Resource id: 0x197 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 149 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x140001b X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 55 (X_CreateGC) Resource id: 0x140001b X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x140001b X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x140001b X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x140001b X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 73 (X_GetImage) Resource id: 0x140001b Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted


This is the NON-buggy log from terminal:


QPixmap::scaled: Pixmap is a null pixmap X Error: BadWindow (invalid Window parameter) 3 Major opcode: 15 (X_QueryTree) Resource id: 0x0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 3 (X_GetWindowAttributes) Resource id: 0x0 Not window attributes. QPixmap::scaled: Pixmap is a null pixmap X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 55 (X_CreateGC) Resource id: 0x0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x0 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x0


DOOMer commented 11 years ago

Whatis your distro? What is your desktop environment or window manager? And what is your Qt version? And please give me log of Screngrab building process from sources.

bulinancio commented 11 years ago

Distro: Debian 7.0 (wheezy) Window Manager: FVWM (version 2.6.5) Window Manager: OpenBox + Razorqt (version 0.5.2) Same behavior but if you make DOUBLE clicks on "New Screen" button. Qt version: 4.8.2

Building log for ERR and OUT togheter, using the command:

dpkg-buildpackage -us -uc -rfakeroot -b >build.log 2>&1

see: http://auil.net.br/camille/temp/build.log

Building log for ERR and OUT separated, using the command:

dpkg-buildpackage -us -uc -rfakeroot -b 2>build-err.log >build-out.log

see: http://auil.net.br/camille/temp/build-err.log http://auil.net.br/camille/temp/build-out.log

DOOMer commented 11 years ago

Thanks for your build logs. I will test it in the next few days on the virtual machine in Debian and FVWM in my system (Gentoo) and try to fix.

Perhaps this is a problem on the side of the VM, since I was not able to reproduce this behavior in my KDE.

bulinancio commented 11 years ago

Hi, thanks for your message.

Yes, I agree that this is probably not an application's issue, but rather than a WM and/or system problem.

I guess so, because the problem appears when I build the app from sources in my PC, but do not appears when I use the binary shipped in your Debian package (.deb file).