On 16-11-09 01:24am, Ruben Astudillo wrote:
> On 08/11/16 16:40, Profpatsch wrote:
> > I stopped using taffybar for that reason, and actually quite like my
> > fullscreen-by-default system as it is now.
>
> How do you know if you have a hogging process then?. Do you have a open
> htop? (I am
Hi,
Does this mean we do have a user session bus now? That’s
one of the features I’ve been longing for for quite a while now.
We have had that for some time but we also now have it socket activated,
where everything should just work as long as you select it:
services.dbus.socketActivated =
On 08/11/16 16:40, Profpatsch wrote:
> I stopped using taffybar for that reason, and actually quite like my
> fullscreen-by-default system as it is now.
How do you know if you have a hogging process then?. Do you have a open
htop? (I am tempted about having a xmonad fullscreen-by-default).
--
On 16-11-05 02:54pm, Nikolay Amiantov wrote:
> Hi Rodney,
>
> On 10/19/2016 01:53 PM, Rodney Lorrimar wrote:
> > My first problem was that Taffybar and xmonad.hs were unable connect to
> > DBus with the following error:
> >
> > connectSession: DBUS_SESSION_BUS_ADDRESS is missing or invalid.
Hi Rodney,
On 10/19/2016 01:53 PM, Rodney Lorrimar wrote:
> My first problem was that Taffybar and xmonad.hs were unable connect to
> DBus with the following error:
>
> connectSession: DBUS_SESSION_BUS_ADDRESS is missing or invalid.
I've pushed a fix to master with a minimal patch that
Hi,
The submitter of #19110 notes that another way to get the user service
to start would be to configure this:
systemd.packages = [ pkgs.gnome3.gnome_terminal ];
The problem is that you either add them to systemd.packages or are
willing to accept global impurity. My guess is that the
On Wed, Oct 19 2016, Rodney Lorrimar wrote:
> My next problem is that gnome-terminal will no longer start:
>
> dbus-daemon[6158]: Activating via systemd: service
> name='org.gnome.Terminal' unit='gnome-terminal-server.service'
> dbus-daemon[6158]: Activation via systemd failed for unit
>
On Wed, Oct 19 2016, Ruben Astudillo wrote:
> On 19/10/16 08:19, Michael Alan Dorman wrote:
>> Rodney Lorrimar writes:
>>>
>>>
On 19/10/16 08:19, Michael Alan Dorman wrote:
> Rodney Lorrimar writes:
>>
>> DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-jp8hFEY1dV,guid=c6e01dc144bda2ae4ca47c84580747a5;unix:abstract=/tmp/dbus-BjlHWWC2xz,guid=3733c1a431ad4cb309cc622a580747a5
>>
>> I'm not quite sure
Rodney Lorrimar writes:
>
> DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-jp8hFEY1dV,guid=c6e01dc144bda2ae4ca47c84580747a5;unix:abstract=/tmp/dbus-BjlHWWC2xz,guid=3733c1a431ad4cb309cc622a580747a5
>
> I'm not quite sure why the dbus socket was unavailable, but my
Hello List,
I've recently had some troubles starting up my gnome3 + XMonad desktop
session.
My first problem was that Taffybar and xmonad.hs were unable connect to
DBus with the following error:
connectSession: DBUS_SESSION_BUS_ADDRESS is missing or invalid.
The value of
11 matches
Mail list logo