Community Packages

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!
Tasklist

FS#46576 - [blueman] Unable to start blueman-manager

Attached to Project: Community Packages
Opened by Ng Oon-Ee (ngoonee) - Tuesday, 06 October 2015, 02:59 GMT
Last edited by Balló György (City-busz) - Tuesday, 17 November 2015, 18:58 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Balló György (City-busz)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Running blueman-manager gives the traceback below

Additional info:
* package version(s)
blueman-2.0-5
* config and/or log files etc.


Traceback (most recent call last):
File "/usr/bin/blueman-manager", line 279, in <module>
Blueman()
File "/usr/bin/blueman-manager", line 54, in __init__
self.Builder.add_from_file(UI_PATH + "/manager-main.ui")
GLib.Error: g-file-error-quark: Failed to open file '../data/ui/manager-main.ui': No such file or directory (4)
This task depends upon

Closed by  Balló György (City-busz)
Tuesday, 17 November 2015, 18:58 GMT
Reason for closing:  Upstream
Comment by Balló György (City-busz) - Friday, 06 November 2015, 10:24 GMT
I can't reproduce this problem. Please report to upstream: https://github.com/blueman-project/blueman/issues
Comment by Ng Oon-Ee (ngoonee) - Saturday, 07 November 2015, 01:19 GMT
Submitted upstream as https://github.com/blueman-project/blueman/issues/387

Found the issue as well, which explains why you can't reproduce. My /home has both an 'apps' folder and a 'data' folder, and one of their imports checks for ../apps and ../data to modify some path constants...
Comment by Balló György (City-busz) - Tuesday, 17 November 2015, 18:57 GMT
Thanks. I will apply the fix after it's committed into git master by upstream.

Loading...