Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43544 - [dex] Unable to start vboxclient.desktop: 'ascii' codec can't decode byte
Attached to Project:
Community Packages
Opened by Alain Kalker (ackalker) - Thursday, 22 January 2015, 23:17 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 17 February 2015, 00:13 GMT
Opened by Alain Kalker (ackalker) - Thursday, 22 January 2015, 23:17 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 17 February 2015, 00:13 GMT
|
DetailsDescription:
On a freshly installed Arch Linux system running in a VM, I'm unable to get dex to autostart the Virtualbox client using its autostart desktop file. Running dex manually in dry-run mode, I get the following message: $ dex -dv /etc/xdg/autostart/vboxclient.desktop Dry run, nothing is executed. 'ascii' codec can't decode byte 0xc5 in position 247: ordinal not in range(128) dex has no problem reading other desktop files, for instance: $ dex -dv /usr/share/applications/urxvt.desktop Dry run, nothing is executed. Autostart file: /usr/share/applications/urxvt.desktop Executing command: urxvt On another system (which has many more (Python) packages installed, dex loads the desktop file (and runs the Virtualbox client) without problems, so I'm suspecting some kind of missing package dependency. Additional info: * package version(s) dex 0.7-1 * config and/or log files etc. Steps to reproduce: - Start out with a freshly installed or pacstrap'ped system - Use dex with the attached .desktop file: `dex -dv vboxclient.desktop` 
vboxclient.desktop
(0.4 KiB)
|
This task depends upon
Closed by Sébastien Luttringer (seblu)
Tuesday, 17 February 2015, 00:13 GMT
Reason for closing: Upstream
Additional comments about closing: Reopen, when you upstream provide a patch
Tuesday, 17 February 2015, 00:13 GMT
Reason for closing: Upstream
Additional comments about closing: Reopen, when you upstream provide a patch
Comment by Alain Kalker (ackalker) -
Thursday, 22 January 2015, 23:21 GMT
Perhaps this is yet another of those lovely locale / UTF8 problems: the desktop file probably contains some UTF8 text, while the problematic VM runs with C locale (actually, no locales generated or specified at all). The system where dex runs without problems has locale setup for en_US.utf8 .
Comment by Sébastien Luttringer (seblu) -
Sunday, 25 January 2015, 19:51 GMT
Please report your issue upstream, that's linked to python and its ascii/unicode handling.
Comment by Alain Kalker (ackalker) -
Monday, 26 January 2015, 04:34 GMT
Okay, I will do that when I have some spare time.