Bug 329138 - Convert to B&W hangs when moving editor window to other screen
Summary: Convert to B&W hangs when moving editor window to other screen
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Editor-BlackWhite (show other bugs)
Version: 3.5.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-22 21:25 UTC by Daniel Bauer
Modified: 2020-08-26 03:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.11.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Bauer 2013-12-22 21:25:01 UTC
When I open an editor window on one screen, use "colors->black and white" and then  drag the window on my other screen (without applying the filter, just letting it there), the b-w-converter gets irresponsive: a watch-incon replaces the mouse-pointer, the mouse-over-switch between before/after (color/b-w) does not work anymore. It doesn't freeze (I can close the window), but it does not work neither.

Reproducible: Always

Steps to Reproduce:
1. open editor from album with click 
2. choose from menu: colors->black and white (set behaviour so that moving the mouse into the settings bar changes image to preview)
3. drag editor window to the other screen (it does not matter from which to which, error occurs in both directions)
Actual Results:  
Before/After view does not work anymore, only the original color image is shown. The mouse-ponter shows "wait" (watch icon)

Expected Results:  
Should act just the same as on both screens, so than window can be moved from one to the other at any time (for me: useful to compare contrasts/color on two different screens)

This problem occurs only since I updated to 3.5 (last version before was 3.2)

Opensuse 12.3
KDE  4.10.5
Nvidia GeForce GTX 460
Screen 1: Samsung 1920x1080
Screen 2: Eizo 1920x1200
in "twinview" mode

I don't know if it happens in other tools as well...
Comment 1 caulier.gilles 2013-12-23 06:47:41 UTC
I use multiscreen here too, and i cannot reproduce the problem.

Do you use color managed view ?  If yes, which LCMS version is used by digiKam ? Look in help/components info dialog for details.

Gilles Caulier
Comment 2 Daniel Bauer 2013-12-23 17:26:28 UTC
No, I have color management deactivated in digikam.
I just found out that this probably occurs in all tools unter the menu item "colors" (I tried "Farbabgleich" [ctrl-B] and "Gradation" [shift-ctrl-C].
The behaviour is rather weird:
- for example in "Gradation" I can still move the red line in the histogram, but it does not produce any effect
- if I close the editor window and reopen it, the mouse-pointer still shows the wait-icon, but now moving the histogram-line produces effect
- the wait-mouse-pointer remains after closing the editor window until I completely close digikam
- even though the wait-pointer is there I can use digikam normally, once closed the editor window that caused the problem, but it's cinfusing ans so I always have to restart dk.

Please note: this only happens when I use one of the mentioned tools, without applying the effect and move the window in this "open state". Moving the editor window without an open toll does NOT produce the problem.
Comment 3 caulier.gilles 2014-08-29 15:22:32 UTC
Daniel,

Still reproducible using last digiKam 4.2.0 ?

Gilles Caulier
Comment 4 Daniel Bauer 2014-08-29 15:44:13 UTC
Am 29.08.2014 17:22, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=329138
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Summary|convert to b-w hangs when   |Convert to B&W hangs when
>                     |moving editor window to     |moving editor window to
>                     |other screen                |other screen
>
> --- Comment #3 from Gilles Caulier <caulier.gilles@gmail.com> ---
> Daniel,
>
> Still reproducible using last digiKam 4.2.0 ?
>
> Gilles Caulier
>


Hi Gilles,

sorry I cannot test it. I was on a 4.x version (don't know which) but it 
had too many bugs and so now I am with version 3.2 ...

kind regards

Daniel
Comment 5 caulier.gilles 2015-05-11 13:38:08 UTC
Daniel,

It still valid using last digiKam  4.9.0 ?

Gilles Caulier
Comment 6 Daniel Bauer 2015-05-12 08:15:00 UTC
Hi Gilles,

I am using 4.6.0 on OpenSuse 13.2, KDE 4.14 now. This problem does NOT exist anymore here :-)

Daniel