! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
xfce4-screenshooter black screen with region selection on dual screens
Status:
RESOLVED: INVALID
Product:
Xfce4-screenshooter
Component:
General

Comments

Description Tcll5850 2017-10-31 14:36:27 CET
When selecting a region, the screen is supposed to darken, but instead it goes completely black.
I can see the cursor, but I can't see what I'm selecting or what's selected.

it captures the region properly, I just can't see what I'm selecting.

I'm running a dual monitor setup with my primary monitor on a GT 430 pcie, and my secondary monitor on a legacy 6150SE nForce 430 onboard.

Xorg is configured with xinerama across both monitors.
Comment 1 Andre Miranda editbugs 2018-01-04 04:41:41 CET
Can you reproduce with xfce4-screenshooter-1.9.1?
What if you disable xfwm4's compositing[1]?

1 - https://docs.xfce.org/xfce/xfwm4/wmtweaks#compositor
Comment 2 Tcll5850 2018-01-04 13:23:08 CET
so apparently version 1.8.2 is still the latest that's available in the package repository

thank you for telling me about compositing, the thought never occurred to me, but it made perfect sense as to the cause of the issue.
after disabling it and restarting, yes I can select screen regions now.

although I wouldn't call that a legit fix... only a workaround...
so I've downloaded 1.9.1, gimme a moment to install that and I'll reply back if that fixes the compositing side or even breaks with disabled compositing.
Comment 3 Tcll5850 2018-01-04 13:57:34 CET
yeah, as expected, I can't compile crap to save my life

first issue trying to build the src:
configure: error: Your intltool is too old.  You need intltool 0.35.0 or later.

did:
$ sudo apt-get install --reinstall intltool

and ran again with this BS:
*** The required package libxfce4panel-2.0 was not found on your system.
*** Please install libxfce4panel-2.0 (atleast version 4.12.0) or adjust
*** the PKG_CONFIG_PATH environment variable if you
*** installed the package in a nonstandard prefix so that
*** pkg-config is able to find it.

so whatever, I'll just deal with the workaround for now wait for a precompiled binary in a .deb package and install that
F this noise.

unless it's just because I'm using 16.04.3, which has been giving me non-stop trouble with many things not working as they should be.

anyways, thanks again for the workaround :)
Comment 4 Andre Miranda editbugs 2019-05-19 19:51:14 CEST
Closing since OP couldn't test the latest version, please file a new bug if this is still an issue.

Bug #13965

Reported by:
Tcll5850
Reported on: 2017-10-31
Last modified on: 2019-05-19

People

Assignee:
Jérôme Guelfucci
CC List:
1 user

Version

Attachments

Additional information