heckelson / i3-and-kde-plasma Goto Github PK

Hi,

Asking here as you may have experienced something similar: when I edit panels (the "menu bar" on the top or bottom of the screen, with the system tray etc.), the interface is very buggy, and if I click "Add Widgets" it usually crashes entirely. Any idea what I can do to fix that?

Thanks for the tutorial, other than a few minor quirks I'm really happy with it.

I'm running Fedora 34 on Kde 5.22.4. I followed the instructions in the README, but when I select "Plasma with i3" when logging in, it just runs Kwin. Logging into normal i3-gaps seems to work just fine. What should I try?

I just discovered this and really happy to see it work. Can I follow these instructions to get it working in Pop os KDE?

When using i3, the meta button no longer opens the application menu. Also, meta+1/2/3 etc. doesn't trigger any of the applications on the taskbar. I suspect this is intended, because i3 uses those key commands for its own purposes.

However, i want to keep i3's ability to hold the meta button and clicking to drag and resize windows. Is there anyway i can keep both shortcuts? So on short presses, the application menu is triggered, but on long presses it acts as a mouse modifier?

I disabled the meta+num commands in the config file, as i don't really use workspaces, but I still don't know how to reactivate the plasma shortcuts.

edit: After removing the meta+num shortcuts from the config and restarting my PC, the task bar application shortcuts worked again. Still can't activate application menu with meta though.

I've added the following line to my config
exec --no-startup-id /usr/bin/nm-applet
bar { position top status_command i3status tray_output primary }
but its not working on plasma+i3, while the nm-applet icon shows up on default i3 with the same config file.

also, some tray icons don't show up...

Hi, fantastic guidance and instructions. Really pleased with the result.

I do have one problem which I can't seem to resolve. I've followed your instructions but when I log in to KDE/i3 it seems to hang for about 30 seconds before becoming fully functional. I have loaded two images: one when where it is hanging and the second is when it becomes fully functional.

Rather than using feh I have been using Nitrogen - I have tried disabling Nitrogen but this has no effect. I am also using my own slightly adpated i3 config file which is located in /.config/i3. I was wondering whether, in may case, the plasma-i3.service file should read ExecStart=/david/.config/i3/config rather than ExecStart=/usr/bin/i3 ?

Any thoughts would be much appreciated.

Hi, I just followed your tutorial in order to have i3 on Plasma. I just installed it and everything seems to work just fine, but not the Plasma stock application menu that you can open using the button on Plasma bar.
The first time I open it, it works fine, but after the first time it opens in the center and small, so I'm unable to use it. I attach an image in order to show it to you.
Any ideas?

IE, when logging in, you can choose which session (Plasma or I3) to log into.

all of my notifications are showing up like this power management one is. changing the notification location in KDE settings does nothing. is there a way to fix it? what could be causing it?

This method no longer works in plasma 5.25 (see the duplicates of https://bugs.kde.org/show_bug.cgi?id=439481)

The plasmabar never hides due to inactivity, in turn constantly blocking part of my small screen.

The visibility is set to auto-hide, a fresh KDE installation didn't fix it either.

System is Arch Linux, KDE version is 5.27.9, i3 version is 4.23.
i3+KDE is setup according to Option 2: New XSession.

Is plasmabars auto-hide functionality actually dependent on some feature of KWin?
I iirc could not find any DBus Message instructing plasmabar to hide, in a pure KDE setup.

Any ideas of how I could manually trigger the hide functionality?
I couldn't find plasmabars source code, so I've run out of ideas what else I could try.

I've used this line:

for_window [class="plasmashell" window_type="notification"] border none, move right 700px, move down 450px

Yet even if I get rid of the "move down 450px", my notifications all stack exactly on top of each other, instead of rendering as a set of horizontally aligned, but vertically spread out windows like they do with kwin...

Any suggestions?

There are actually 3 notifications here, but the other 2 are hidden behind this one...

Here you can see a bit more clearly IF the messages that happen to be in back have more content...

Add screenshots please. ;)

After a recent update, the "Desktop — Plasma" window that covers everything is no longer closing. xprop says:

WM_NAME(STRING) = "Desktop @ QRect(0,0 3840x1080) "
_NET_WM_NAME(UTF8_STRING) = "Desktop @ QRect(0,0 3840x1080)  — Plasma"

But neither name in my i3 config file will close the desktop window that covers the screen on log in.

Your instructions helped me dealing with a lot of issues during my time setting up KDE Plasma and i3! Unfortunately, once I close my laptop lid one time after booting, the Plasma task bar disappears completely and does not show up again. Windows that were open on my primary screen are now filling the empty space left by the task bar, so I believe it is either hidden or completely deactivated.

Do you have any idea as to what causes this behavior?

The default indicator of KDE isn't customizable with such a setup. Workspaces don't seem to work properly. When opening Virtual Desktops in Workspace Behavior it displays 'There was an error requesting information from the compositor'.

For now I removed the workspace indicator widget from the panel. Can someone suggest an alternative workspace indicator or a solution for this issue?

When working in a multi-monitor setup, the notifications always pop up it the "main" workspace, the one the KDE panel is in.

However, doing so steals focus from the current workspace

For example let's say you are writing an email in the workspace 2, and you have your browser opened in the workspace 1, which is the main workspace. Then a notification pops up and forces the focus on the workspace 1. Even if you kill the window with an i3 command, the focus is on the workspace 1 so that if you keep on typing, the text will be actually written on the url bar of the browser

Are you having this same issue?
Do you have a workaround?

I noticed many integrations of i3 and plasma like mine and this point in this walkthrough video have white boxes instead of apps like below:

On hovering:
The right visuable ones are the ones I pined.

It looks like you got folders for apps. That's really cool and I wonder how to do it! Thaks!

Greetings,
I was wondering if their is any documented steps for removing i3 from KDE?

Hi Alexander,

Thank you for posting your config!

However, this bindsym doesn't work for me:

bindsym $mod+Shift+e exec --no-startup-id qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout -1 -1 -1

If I execute this command in the terminal:

qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout -1 -1 -1

I get this error:

Cannot find 'org.kde.KSMServerInterface.logout' in object /KSMServer at org.kde.ksmserver

I tried under Kubuntu 19.04 with i3 4.16.1 and Kubuntu 20.04 with 4.17.1.

Did you find a workaround?

Lucas

As mentioned, there is a big window on startup, which is the Plasma desktop. I'm just wondering, is is possible to use xwinwrap to make this window stay on back instead of just killing it and using other applications for desktop (like feh) since by doing so we'll have access to desktop widgets?

Hi, I love using i3 when I'm getting dirty and productive.
but I also have a touch screen monitor I use when I'm lounging and consuming media.

I was hoping to easily be able to swap between these two window managers so I can customize the experience depending on whether I have touch capabilities.

I had hoped I might be able to run a bash script to kill i3 and start Kwin and maybe fiddle with a couple other settings if needed.
But I recognize I might have to create a totally different session where I logout of KDE+i3 and login to KDE+Kwin.

Can anyone point me in the right direction. I was a front end developer a decade ago with some linux experience trying to get back in it so I'm not a novice but need a little direction..

How might I go about making this work?
Any input would be stellar. Thank you

Hello,

Been using a Plasma-i3 configuration for a long time now with a configuration from this repo and I love it. I wanted to make a few comments to update the instructions a little bit with respect to picom.

1. the default configuration is now located at /etc/xdg/picom.conf instead of /etc/xdg/picom.conf.example

2. Dual-kawase blur is now included in extra/picom rather than just picom-git in AUR, and no longer requires using --experimental-backends (Here is my startup line for picom: exec_always --no-startup-id picom -bc --no-fading-openclose --backend glx --blur-method dual_kawase --config $HOME/.config/picom.conf)

Man page for picom can be found here.
I'm running picom 11.2-1 from extra/picom

Hello,
I followed your guide to install i3wm with kde on arch linux.

I can't really describe what's the issue but it look like plasma desktop is part of the tiling app and fill only half of the screen?

Here's a oneliner on how I installed everything: $ sudo pacman -Syu && sudo pacman -S i3 feh i3-dmenu-desktop morc_menu wmctrl

I followed the steps and with the installation of packages I had a "problem" with the one-line command.
When I execute this I receive the message:
error: target not found: i3-dmenu-desktop

An image trying just this package:

I just resolved it, avoiding the installation of "i3-dmenu-desktop" and everything worked well.

Hey, I'd like have the i3 tiling windows capable of going in front of the kde panel when I increase their size, how can I do this? (maybe change the properties of the kde panel in some way?)

I'm running KDE Plasma on arch, with i3 as window manager.

Besides the known limitations (including the buggy widget selector), a black square is visible on the top left of my screen. It disappears if I kill xembedsniproxy but then I don't see the icons in the system tray.
I am wondering if I am the only one this issue (which could be related to some other parameter), or if that's something other people observed too. I deleted all cache and config files related to KDE / Plasma, without success.

Packages versions:
plasma-desktop 5.23.3-1
plasma-framework 5.87.0-1
plasma-integration 5.23.3-1
plasma-workspace 5.23.3-1

Kernel: 6.6.1-arch1-1
Theme: [Plasma], Breeze [GTK2/3]
plasmashell 5.27.9
i3 version 4.23 (2023-10-29) © 2009 Michael Stapelberg and contributors
CPU: AMD Ryzen 7 PRO 5850U with Radeon Graphics (16) @ 4.507GHz
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series

Whenever I connect or disconnect an external display the active window is getting forced to floating mode. I'm experiencing this with a minimal i3 configuration with only the needed Plasma-related settings:

exec --no-startup-id picom -fb

# Generals
hide_edge_borders both
default_border pixel 1
default_floating_border pixel 3
smart_borders on
focus_follows_mouse yes
# Switch to urgent workspace when clicking notification
focus_on_window_activation focus
gaps inner 10px

# Select which programs to open in floating mode by default
for_window [window_role="pop-up"] floating enable
for_window [window_role="bubble"] floating enable
for_window [window_role="task_dialog"] floating enable
for_window [window_role="Preferences"] floating enable
for_window [window_role="About"] floating enable
for_window [window_type="dialog"] floating enable
for_window [window_type="menu"] floating enable
for_window [window_role="Organizer"] floating enable
for_window [window_role="page-info"] floating enable
for_window [window_role="toolbox"] floating enable
for_window [window_role="webconsole"] floating enable
for_window [instance="__scratchpad"] floating enable

exec --no-startup-id /usr/lib/pam_kwallet_init
exec --no-startup-id wmctrl -c Plasma
for_window [title="Desktop @ QRect.*"] kill; floating enable; border none
for_window [class="ksplash"] kill
for_window [class="Plasma"] floating enable, border none
for_window [title="plasma-desktop"] floating enable, border none
for_window [title="win7"] floating enable, border none
for_window [class="yakuake"] floating enable;
for_window [class="lattedock"] floating enable;
for_window [class="kruler"] floating enable; border none
for_window [class="krunner"] floating enable, border none
for_window [class="Kmix"] floating enable, border none
for_window [class="Klipper"] floating enable, border none
for_window [class="kscreen_osd_service"] floating enable, move position center
for_window [class="tastenbrett"] floating enable, move position center
for_window [class="Plasmoidviewer"] floating enable, border none
for_window [class="(?i)*nextcloud*"] floating disable
for_window [class="systemsettings"] floating enable, move position center
for_window [class="kcalc"] floating enable, move position center
for_window [class="plasma.emojier"] floating enable
for_window [class="plasmashell"] floating enable
for_window [class="plasmashell" window_type="notification"] floating enable, border none, move position center
no_focus [class="plasmashell" window_type="notification"]

bindsym XF86AudioRaiseVolume exec --no-startup-id qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "increase_volume"
bindsym XF86AudioLowerVolume exec --no-startup-id qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "decrease_volume"
bindsym XF86AudioMute exec --no-startup-id qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "mute"
bindsym XF86AudioMicMute exec --no-startup-id qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "mic_mute"

Could someone maybe try to reproduce this and if anything trying to solve with me the issue? Even helping debug this a bit deeper would mean a lot since I'm relative new to KDE/i3 and not fully aware where to look at exactly.

My computer updated to Plasma 6 last night and I noticed a few things so far.

1. Plasma now defaults to Wayland over X11. I've been on X11, so I had to check that as I log in.

2. Some keyboard shortcuts aren't working. Not sure how widespread that issue is, but I know Meta+Shift+E isn't working anymore. I'll test more when I get home tonight, I updated before going to bed and didn't have the chance then. EDIT: Forgot to mention that I can press the physical power button on my PC to bring up the sleep/reboot/shutdown menu instead, but none of the options will work. It just goes back to the desktop.

Hey, thank you for making this guide, really helpful.
The notifications are a little bit off, sometimes they go at the top (the position I have set for them in KDE) and sometimes they go at the bottom (Please see the following image)

On startup

Configs

i3: https://raw.githubusercontent.com/Mistreaper/personalcfg/main/i3/config
Picom: https://github.com/Mistreaper/personalcfg/blob/main/picom/picom.conf

After $mod+shift+r, the problem stops, but feh wallpaper still blurred.

Thank you for making this guide, really wonderful and I'm honestly impressed by my new setup.
One of the bars in this setup is hidden and can be shown by the MOD key (bottom bar in image) but and that is fine. Problem is that there is a 2nd bar (the bar just above the 'hidden' bar in the above image) which is not hiding. Please help me hiding that bar too. It is showing above of my KDE panel like this:

title

Small mistake in the Readme. plasma-kwin_x11.target does not exist. plasma-kwin_x11.servixe does and is what should be masked.

I'm on Kubuntu 20.04 LTS. I use my laptop connected to an external monitor via HDMI (with dongle type-c to HDMI).

After the laptop goes to sleep because of inactivity and I "wake it up", suddenly there is a black screen with just the KDE screen where I have to put the password.
It takes a long time before I can manage to write the password because the system seems to not get input nor from the track-pad, nor from the keyboard, neither from a cabled mouse.

Then, when I manage to log in, basic i3 "starting screen", even though I have a wallpaper and bumblebee-status, plus the keyboard doesn't work, just the trackpad and mouse. I litteraly cannot do anything from there.

Do you have any ideas on how to solve this?

Hi
As the title suggests i'm having issues with config file but cannot find where is the error. when i log in to plasma-i3 session it displays the error message with the options 'show errors' and 'edit config file' but i can't choose one.
In addition when i create the config file using $ i3-config-wizard it shows me the following message:
i3: Could not connect to i3 on socket "/tmp/i3-ipc.sock": No such file or directory
is that a problem actually? Is it linked to the config file error? (notice that the config file is created and it is in the correct folder)

Then, i've noticed that the plasma-i3.desktop file has an exclamation mark, differently from the plasma.desktop one as you can see in the screenshot

is that a problem too?

thanks in advance!