Github messages for voidlinux
 help / color / mirror / Atom feed
From: ProjectMoon <ProjectMoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] KDE X11 should be started with dbus-run-session
Date: Sat, 09 May 2020 01:05:00 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21766@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

New issue by ProjectMoon on void-packages repository

https://github.com/void-linux/void-packages/issues/21766

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  Void 5.4.39_1 x86_64 GenuineIntel uptodate rrFFFFFF
  *output of ``xuname`` (part of xtools)*
* package:  plasma-workspace
  *affected package(s) including the version*

### Expected behavior
When starting Plasma X11 session from SDDM (or another login manager, probably), tray icons and dbus notifications work properly. The `DBUS_SESSION_BUS_ADDRESS` environment variable should be defined.

### Actual behavior
Tray icons do not work consistently, particularly for electron applications. dbus notifications from these applications are not received. `DBUS_SESSION_BUS_ADDRESS` is not defined.

### Steps to reproduce the behavior
Log in with Plasma X11, start an electron app like Riot or Signal. No tray icon or notifications appear. At best, the taskbar icons will light up. Executing `echo $DBUS_SESSION_BUS_ADDRESS` or similar in the terminal will produce no result.

I fixed this by adding `dbus-run-session` at the front of the `Exec=` line of `/usr/share/xsessions/plasma.desktop`. This mimics the setup of `/usr/share/wayland-sessions/plasmawayland.desktop`, and makes the tray icon and notifications work again.


             reply	other threads:[~2020-05-08 23:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 23:05 ProjectMoon [this message]
2020-05-10  1:02 ` ericonr
2020-05-10 13:07 ` ProjectMoon
2020-05-10 22:34 ` ericonr
2020-05-11 17:47 ` furryfixer
2020-05-11 18:10 ` Johnnynator
2020-05-11 18:10 ` Johnnynator
2020-05-11 21:04 ` ProjectMoon
2020-05-12  1:06 ` furryfixer
2020-05-12 11:46 ` furryfixer
2020-05-12 12:11 ` furryfixer
2020-05-20  6:41 ` ericonr
2020-05-20 12:42 ` Johnnynator
2020-05-20 15:02 ` furryfixer
2020-07-17 10:28 ` [ISSUE] [CLOSED] " Johnnynator
2020-07-17 10:28 ` Johnnynator

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21766@inbox.vuxu.org \
    --to=projectmoon@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).