View Single Post
Posts: 915 | Thanked: 3,209 times | Joined on Jan 2011 @ Germany
#2418
Just a brainwave concerning the gconf2 problem that I never encountered so far:

Usually I start Debian applications from within a fully loaded Easy Debian (with LXDE) and not via debbie.
However, today I started Iceweasel via debbie and got this error message:
Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Launch helper exited with unknown return code 1)
Is this the error message that you have in mind when talking about gconf2 problems?
For verification I loaded the original unchanged Easy Debian image and did not get that message so obviously something has changed in the gconf-dbus communication.
I googled a bit and found some posts (also involving hal) that suggest that it might be a permission problem.

Well, I'm certainly not an expert, neither with hal nor with dbus or gconf but as a shot in the dark I started iceweasel via debbie and sudo in my dist-upgraded image:
Code:
debbie sudo iceweasel
And I did not get that error message which I think indicates that in general the communication works fine. So I believe the combination gconf2/Maemo is not broken the way pulseaudio is. I rather think it's a simple permission problem. Can somebody with more knowledge please have a look at this? It could spare us another evil hack on the way to a fully working Squeeze.


Edit:
Oh, btw and totally unrelated: I think adding pipe to .xbindkeysrc would be nice:
Code:
"xvkbd -xsendevent -text '|'"
  Shift + Down
No idea if Shift + Down is the most intuitive combination but it works for me.

Last edited by sulu; 2011-09-15 at 19:45.