i3wm: Fn key causes certain apps to crash (Manjaro on ThinkPad E570)
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Running i3wm on a Lenovo Thinkpad E570. Everything else typically works just fine. However, pressing the Fn
key instantly kills Firefox (if open), all tray icons, and dunst. Some notes:
- There is nothing in my
.config/i3/config
that relates to XF86WakeUp (whichFn
maps to, for some reason). - This problem does not occur when using KDE (i.e. this problem seems related to i3wm, not Xorg/Wayland).
- Once this crash has happened, these apps can be reopened and are then no longer affected.
- I've also had issues with opening some apps such as Dolphin, which shows the following error when opened in a terminal:
"Session bus not foundnTo circumvent this problem try the following command (with Linux and bash)nexport $(dbus-launch)"
- I can then use
export $(dbus-launch)
to run it from the terminal, but it only applies to the terminal session; running this command from dbar also has no effect. Could this be a related problem? This only happens after the crash.
Any and all insight into strange i3 or dbus behavior is greatly appreciated.
manjaro i3 d-bus thinkpad
add a comment |Â
up vote
0
down vote
favorite
Running i3wm on a Lenovo Thinkpad E570. Everything else typically works just fine. However, pressing the Fn
key instantly kills Firefox (if open), all tray icons, and dunst. Some notes:
- There is nothing in my
.config/i3/config
that relates to XF86WakeUp (whichFn
maps to, for some reason). - This problem does not occur when using KDE (i.e. this problem seems related to i3wm, not Xorg/Wayland).
- Once this crash has happened, these apps can be reopened and are then no longer affected.
- I've also had issues with opening some apps such as Dolphin, which shows the following error when opened in a terminal:
"Session bus not foundnTo circumvent this problem try the following command (with Linux and bash)nexport $(dbus-launch)"
- I can then use
export $(dbus-launch)
to run it from the terminal, but it only applies to the terminal session; running this command from dbar also has no effect. Could this be a related problem? This only happens after the crash.
Any and all insight into strange i3 or dbus behavior is greatly appreciated.
manjaro i3 d-bus thinkpad
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Running i3wm on a Lenovo Thinkpad E570. Everything else typically works just fine. However, pressing the Fn
key instantly kills Firefox (if open), all tray icons, and dunst. Some notes:
- There is nothing in my
.config/i3/config
that relates to XF86WakeUp (whichFn
maps to, for some reason). - This problem does not occur when using KDE (i.e. this problem seems related to i3wm, not Xorg/Wayland).
- Once this crash has happened, these apps can be reopened and are then no longer affected.
- I've also had issues with opening some apps such as Dolphin, which shows the following error when opened in a terminal:
"Session bus not foundnTo circumvent this problem try the following command (with Linux and bash)nexport $(dbus-launch)"
- I can then use
export $(dbus-launch)
to run it from the terminal, but it only applies to the terminal session; running this command from dbar also has no effect. Could this be a related problem? This only happens after the crash.
Any and all insight into strange i3 or dbus behavior is greatly appreciated.
manjaro i3 d-bus thinkpad
Running i3wm on a Lenovo Thinkpad E570. Everything else typically works just fine. However, pressing the Fn
key instantly kills Firefox (if open), all tray icons, and dunst. Some notes:
- There is nothing in my
.config/i3/config
that relates to XF86WakeUp (whichFn
maps to, for some reason). - This problem does not occur when using KDE (i.e. this problem seems related to i3wm, not Xorg/Wayland).
- Once this crash has happened, these apps can be reopened and are then no longer affected.
- I've also had issues with opening some apps such as Dolphin, which shows the following error when opened in a terminal:
"Session bus not foundnTo circumvent this problem try the following command (with Linux and bash)nexport $(dbus-launch)"
- I can then use
export $(dbus-launch)
to run it from the terminal, but it only applies to the terminal session; running this command from dbar also has no effect. Could this be a related problem? This only happens after the crash.
Any and all insight into strange i3 or dbus behavior is greatly appreciated.
manjaro i3 d-bus thinkpad
manjaro i3 d-bus thinkpad
asked 23 mins ago
brilliantlyInsane
1063
1063
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
I looked to see if there were any alternative or supplementary dbus
packages, and found dbus-x11
in Manjaro's core
repository. Upon installing that (which replaced the normal dbus
package), both the crashing error and the problem with Dolphin are no longer occurring.
As such, I'm inclined to believe that I simply had the wrong version of dbus
installed! Problem solved. :)
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I looked to see if there were any alternative or supplementary dbus
packages, and found dbus-x11
in Manjaro's core
repository. Upon installing that (which replaced the normal dbus
package), both the crashing error and the problem with Dolphin are no longer occurring.
As such, I'm inclined to believe that I simply had the wrong version of dbus
installed! Problem solved. :)
add a comment |Â
up vote
0
down vote
I looked to see if there were any alternative or supplementary dbus
packages, and found dbus-x11
in Manjaro's core
repository. Upon installing that (which replaced the normal dbus
package), both the crashing error and the problem with Dolphin are no longer occurring.
As such, I'm inclined to believe that I simply had the wrong version of dbus
installed! Problem solved. :)
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I looked to see if there were any alternative or supplementary dbus
packages, and found dbus-x11
in Manjaro's core
repository. Upon installing that (which replaced the normal dbus
package), both the crashing error and the problem with Dolphin are no longer occurring.
As such, I'm inclined to believe that I simply had the wrong version of dbus
installed! Problem solved. :)
I looked to see if there were any alternative or supplementary dbus
packages, and found dbus-x11
in Manjaro's core
repository. Upon installing that (which replaced the normal dbus
package), both the crashing error and the problem with Dolphin are no longer occurring.
As such, I'm inclined to believe that I simply had the wrong version of dbus
installed! Problem solved. :)
answered 15 mins ago
brilliantlyInsane
1063
1063
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f476953%2fi3wm-fn-key-causes-certain-apps-to-crash-manjaro-on-thinkpad-e570%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password