Bug 15358 - LXQt: XDG data dir seems to be ~/.local/sharelxqt instead of ~/.local/share/lxqt
Summary: LXQt: XDG data dir seems to be ~/.local/sharelxqt instead of ~/.local/share/lxqt
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Florian Hubold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-25 12:20 CET by Rémi Verschelde
Modified: 2015-03-05 21:18 CET (History)
1 user (show)

See Also:
Source RPM: lxqt-about-0.9.0-1.mga5
CVE:
Status comment:


Attachments
Screenshot that shows the wrong translations directory in lxqt-about (34.80 KB, image/png)
2015-02-25 12:23 CET, Rémi Verschelde
Details

Description Rémi Verschelde 2015-02-25 12:20:13 CET
lxqt-about shows that its translation directory is:

  ~/.local/sharelxqt/translations

This might be a simple typo in lxqt-about, or might be the symptom of a bigger issue where XDG_DATA_DIR is not parsed properly and all local LXQt data will end up in ~/.local/sharelxqt instead of ~/.local/share/lxqt.

Reproducible: 

Steps to Reproduce:
Comment 1 Rémi Verschelde 2015-02-25 12:23:17 CET
Created attachment 5946 [details]
Screenshot that shows the wrong translations directory in lxqt-about
Comment 2 Florian Hubold 2015-02-25 22:05:19 CET
Thanks for the hint, will investigate.

Status: NEW => ASSIGNED
CC: (none) => doktor5000

Comment 3 Florian Hubold 2015-02-28 19:36:38 CET
Reproduced, and opened https://github.com/lxde/lxqt/issues/518

See Also: (none) => https://github.com/lxde/lxqt/issues/518

Comment 4 Florian Hubold 2015-03-03 23:15:27 CET
Seems to be fixed by https://github.com/lxde/libqtxdg/commit/5058cd61611a712ed11ba6e998e9444e041b5d43

Already commited, will test and ask for freeze push.
Comment 5 Florian Hubold 2015-03-05 21:18:28 CET
After libqtxdg update lxqt-about now shows


Translations
/usr/share/lxqt/translations
/usr/local/share/lxqt/translations

So marking as resolved, just asked for freeze push.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


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