Bug 1313422 - firefox creates $HOME/Desktop folder at launch indiscriminately
Summary: firefox creates $HOME/Desktop folder at launch indiscriminately
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 15:18 UTC by Fabio Valentini
Modified: 2019-05-28 06:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 20:18:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 922719 0 None None None 2019-05-28 06:01:13 UTC

Description Fabio Valentini 2016-03-01 15:18:59 UTC
Launching firefox always causes it to create the "$HOME/Desktop" folder (even when XDG_DESKTOP_DIR is set to something else).

Setting the system to a locale that translates "Desktop" to another string might also cause this, but I have not tested it.

Comment 1 Fabio Valentini 2016-11-11 08:39:40 UTC
This still happens even on fedora 25.

Comment 2 Fedora End Of Life 2017-11-16 18:37:33 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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 Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fabio Valentini 2017-11-16 21:56:50 UTC
This still happens on fedora 27.

Comment 4 Ben Cotton 2018-11-27 18:12:36 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 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 Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fabio Valentini 2018-11-27 20:20:09 UTC
Still present in current firefox on fedora (see also still open upstream bug).

Comment 6 Christian Stadelmann 2019-05-08 20:18:36 UTC
I cannot reproduce this issue any more. Please tell me if you can.

Comment 7 Fabio Valentini 2019-05-28 06:01:54 UTC
It looks like it has been fixed in the meantime. Thanks for checking!


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