On 25.02.2023 23:00, Hendrik Jäger wrote:
So I start bspwm by running `startx` at boot and had `exec bspwm` as the WM
launch command
This might be the crucial point: I’m guessing you are using ~/.xinitrc?
If you can reproduce the issue with ~/.xinitrc, could you test whether it also
occurs
Hi Prescott
> It's been a while but luckily I've kept all my config changes in a git repo!
Thank you for your quick response and being able to dig this up!
> >How do you select to start bspwm: via a menu in your DM, after logging into
> >your DM, from your ~/.xsession, ~/.xinitrc, etc.?
>
I’m thinking your (dbus) environment is not initialized correctly when
starting your X-session. How do you start it?
Do you use some Display Manager, like xdm, gdm, etc.?
How do you select to start bspwm: via a menu in your DM, after logging into
your DM, from your ~/.xsession, ~/.xinitrc, etc.?
Hi Prescott
Do you still have this issue?
> I just realized the issue, although it doesn't seem to be related to
> flameshot directly. The program runs as a D-BUS service, and for some reason
> the DISPLAY environment variable isn't being set.
This sounds like this bug needs to be reassigned
Package: flameshot
Version: 0.5.1+git20180601-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Upgraded to testing from stable for help in bugs finding and for
some newer packages I needed from Buster.
I originally used my sxhkd keybinding "flameshot gui -p
5 matches
Mail list logo
