Bug 4576 - Dragging and dropping an image file from Firefox to the KDE desktop and setting it as a wallpaper (after setting "different widgets per desktop").
Summary: Dragging and dropping an image file from Firefox to the KDE desktop and setti...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL: http://www.shlomifish.org/Files/files...
Whiteboard:
Keywords: NEEDINFO, Triaged
Depends on:
Blocks:
 
Reported: 2012-02-18 19:33 CET by Shlomi Fish
Modified: 2016-12-28 18:58 CET (History)
2 users (show)

See Also:
Source RPM: kdebase4-workspace-4.8.0-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Shlomi Fish 2012-02-18 19:33:13 CET
Description of problem:

When dragging and dropping an image from Firefox to the KDE desktop and setting it as wallpaper (which requires unlocking the widgets and also setting sytemsettings -> "Workspace Behavior" -> "Virtual Desktops" -> "Different widgets  for each desktop") from an http:// address (such as the image in the URL - http://www.shlomifish.org/Files/files/images/Self/shlomif-st-bernard.jpg which is public domain/CC-Zero and was taken by me), then the screen become black.

This is also happens in a new user. This is a long-standing problem in Mageia and annma from #kde said it doesn't happen to her on openSUSE (with KDE compiled from sources I believe).

Version-Release number of selected component (if applicable):

Mageia Linux 2/Cauldron.

How reproducible:

Always.

Steps to Reproduce:
1. Create a new user.
2. Start KDE from the virtual console.
3. sytemsettings -> "Workspace Behavior" -> "Virtual Desktops" -> tick "Different widgets  for each desktop" and apply.
4. Unlock the widgets. (right click on the panel and say "Unlock widgets").
5. Start Firefox in the URL http://www.shlomifish.org/Files/files/images/Self/shlomif-st-bernard.jpg .
6. Preferably follow http://cybernetnews.com/helpful-tip-disable-drag-drop-images-in-firefox/ .
7. Drag and drop the image to the desktop.
8. Select "Wallpaper -> Image".
Comment 1 Shlomi Fish 2012-02-18 19:38:08 CET
Just checked and it also happens with Google Chromium.
Comment 2 Marja Van Waes 2012-05-26 13:05:44 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 3 Shlomi Fish 2012-05-27 08:14:41 CEST
I was able to reproduce this bug on Mageia 2.

Regards,

-- Shlomi Fish

Keywords: NEEDINFO => (none)
Version: Cauldron => 2

Comment 4 Samuel Verschelde 2013-09-05 14:41:22 CEST
I reproduced it too and got the black screen (without step 6., don't know why it would be needed)

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => nicolas.lecureuil

Comment 5 Manuel Hiebel 2013-10-22 12:21:04 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 6 Manuel Hiebel 2013-11-23 16:16:34 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 7 Shlomi Fish 2013-11-23 17:39:09 CET
This still happens with Mageia Cauldron (what will become Mageia 4), only this time the bug has a somewhat different symptom: the first image I try to put on the background does nothing, no matter how many times I try to drag and drop and "Set as Wallpaper" it, but the second image I try to drag and drop causes a black screen again. So I'm going to reopen this bug.

One such image can be:

http://www.shlomifish.org/Files/files/images/abs-x+2-abs-x+1.png

Regards,

-- Shlomi Fish

Status: RESOLVED => REOPENED
Version: 2 => Cauldron
Resolution: OLD => (none)

Comment 8 Samuel Verschelde 2015-04-23 14:15:15 CEST
Hi Shlomi. Does this still happen in latest cauldron?

Keywords: (none) => NEEDINFO
Status: REOPENED => NEW

Comment 9 Shlomi Fish 2015-04-23 15:41:12 CEST
(In reply to Samuel VERSCHELDE from comment #8)
> Hi Shlomi. Does this still happen in latest cauldron?

Yes, it does - it still happens.
Samuel Verschelde 2016-08-25 16:24:59 CEST

Assignee: mageia => kde

Comment 10 Nicolas Lécureuil 2016-12-28 18:53:53 CET
is this still valid with current cauldron ?

CC: (none) => mageia

Comment 11 Nicolas Lécureuil 2016-12-28 18:57:34 CET
i can't reproduce here
Comment 12 Nicolas Lécureuil 2016-12-28 18:58:02 CET
Please reopen if this is still valid for you on current cauldron

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME


Note You need to log in before you can comment on or make changes to this bug.