Hello Christoph,
On 29/03/13 19:44 +0100, Christoph Wickert wrote:
Am Donnerstag, den 28.03.2013, 22:11 +0100 schrieb Jan Pokorný:
>
> first, wanted to point out that Blueman's OBEX access does not work
> out of the box but a tweak like [1] is necessary (natural choice
> is probably to use pcmanfm as the last step).
That script shouldn't be necessary, you should just need gvfs-obexftp.
should have added more details:
- "Command to start an obex ftp browser" was originally set to
something like "nautilus obex://%d"
- nautilus is not installed by default in my LXDE installation
- I want to avoid dependencies like gnome-desktop3 :)
> Dunno if this can be automated easily and if LXDE and the like
spins
> are playing games with dconf et al. in before-the-fact manner
> (read: kickstart). Or does this warrant for a new "Soft-dependencies
> workarounds" section under LXDE in Fedora wiki [2]?
I'm afraid I cannot follow you. What does dconf have to do with this? As
per spins guidelines, we should not touch other packages.
I believe this setting is Blueman frontend is in GTK2 so would
expect the configuration items like "Command to start an obex ftp
server" are persisted in a native config format. I may be wrong.
In Xfce, is there any other user-friendly and straightforward
way to access mobile phone via bluetooth + OBEX? If not, is
nautilus an integral part of this environment? This may be
quite rare scenario, but still deserving to work out-of-the-box,
IMHO.
And why soft-dependencies? rpm doesn't have such a thing.
With soft-dependency, I meant a dependency arising from default
configuration and not captured anywhere else, yet one has to
tweak/workaround it (or have an automation do it for her) to get
the functionality working. A list of such recipes for LXDE might
be handy(?).
> Second, doing a cleanup on my virtual LXDE stack I realized the
issue
> with notification-daemon not being automatically run in fresh
> install [3] of LXDE spin unfortunately persists till F18.
> Is it just my installation images (AFAIK official ones)?
When I boot the F18 LXDE spin in KVM, notification-daemon is running.
It's started through /etc/xdg/lxsession/LXDE/autostart.
Yes, it was working for me too, IIRC. Problem is with installed
version.
Install and in the desktop session under standard user, run
$ notify-send test # -> nothing happens
$ ps aux | grep notification # -> no line other than the grep cmd
> Side-question: I am using LXDE for more than a year now, am I
> qualified for LXDE SIG membership? :)
Sure. Frankly speaking the SIG only exists in the wiki these days. Most
people are either no longer using Fedora or LXDE - including myself. In
the past I was running LXDE and Xfce, but now that I'm busy with other
projects I decided to focus on Xfce. And help is welcome - may it be
writing documentation, or package maintenance.
Have read about your decline from LXDE, but I don't feel like running
solo. Co-maintenance might work if you want to outsource some effort
(or there is another interested soul around).
--
Jan