Open
Bug 318110
Opened 20 years ago
Updated 3 years ago
Dragging and drop icon to GNOME desktop creates invalid .desktop file
Categories
(Firefox :: General, defect)
Tracking
()
NEW
People
(Reporter: hidenosuke, Unassigned)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051129 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051129 Firefox/1.6a1
Dragging and drop an icon on the location bar to GNOME desktop
creates invalid .desktop file.
Reproducible: Always
Steps to Reproduce:
1.Open http://www.mozilla.gr.jp/
2.Drag and drop icon on the location bar to GNOME desktop
3.
Actual Results:
Invalid .desktop file is created.
Expected Results:
Correct .desktop file is create.
Epiphany browser doesn't have this problme.
Reporter | ||
Comment 1•20 years ago
|
||
Reporter | ||
Comment 2•20 years ago
|
||
Reporter | ||
Comment 3•20 years ago
|
||
My environment is Debian GNU/Linux unstable.
GNOME 2.12 and locale is ja_JP.eucJP.
Updated•20 years ago
|
Version: unspecified → Trunk
Reporter | ||
Comment 4•20 years ago
|
||
SeaMonkey has also this problem.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060217 SeaMonkey/1.5a
Sorry, I don't know which product is suitable.
Reporter | ||
Comment 5•19 years ago
|
||
This doesn't happen with UTF-8 environment.
I think EUC-JP to UTF-8 conversion has the problem.
![]() |
||
Comment 6•14 years ago
|
||
Not a shell integration bug (e.g. protocol registration, default browser check, save as wallpaper). Moving over to General for further triage
Component: Shell Integration → General
QA Contact: shell.integration → general
Coming from the duplicate.
I don't think it's Gnome specific.
( Ubuntu Budgie in my example )
The duplicate provides more info.
Title of the thread here is a bit misleading
and did not pop out when I searched around words such as :
drag / drop / .desktop / shortcut
It's an old bug, 15 years ago.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•