pkgsrc-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
pkg/50294: dbus + xfce/mate creates timeouts and cannot connect
>Number: 50294
>Category: pkg
>Synopsis: dbus + xfce/mate creates timeouts and cannot connect
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: pkg-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Oct 02 07:50:00 +0000 2015
>Originator: Petr Topiarz
>Release: 6.1.5 release amd64 and 7RC3 amd64
>Organization:
on my own
>Environment:
NetBSD mybsd.openunix.eu 6.1.5 NetBSD 6.1.5 (GENERIC) amd64
>Description:
Mate (from wip) or XFCE4 - certain actions which need dbus hang at start when dbus is started (from rc.conf). This problem persists in 2014Q4 2015Q1 2015Q2 and stable but in my old laptop installation (2014Q2 + netbsd 6.1.3) everything worked well. I tried to fix it with my ip record in /etc/hosts which changed the behaviour bud did not fix it.
What happens is that parts of the desktop like panels start two minutes after desktop starts and terminal or caja/thunar have delays when launching, even terminal hangs, and it is not possible to launch a logout dialogue.
It can partly be solved by starting the desktops with ck-launch and without dbus running, but then some elements of the desktop like pulseaudio or power management refuse to work at all.
I think this is serious because it makes NetBSD as desktop fairly unusable, which is a shame considering that other parts of the system work very reliably.
>How-To-Repeat:
Install full NETBSD 6.1.5 amd distro.
Install stable pkgsrc (and wip for mate).
Compile mate or xfce.
add a line to your rc.conf:
"dbus=YES"
add a line to your .xinitrc:
"exec startxfce4 --with-ck-launch # starts XFCE"
or
"exec dbus-launch --exit-with-session mate-session #starts MATE"
(optionally add your hostname and ip to /etc/hosts)
run startx and you will see immediatelly
>Fix:
Partial fix:
insert a line in your rc.conf:
"dbus=NO"
I even tried to compile xfce or mate against older dbus (1.8.6) but the problem persists.
Home |
Main Index |
Thread Index |
Old Index