[02:30] <afterThought> Ok, I'm missing something. I've looked over at least a dozen posts on how to create a desktop shortcut that opens qterminal and runs a command, but I can't figure it out. Is someone willing to lend a hand?
[02:31] <afterThought> I created a .desktop file with the command, but when I double click it nothing happens. Even if I make it an executable or if I do Terminal=true
[02:32] <afterThought> The only thing I came close to doing was creating a hidden .sh file in my home directory and having the .desktop file invoke that...but it opens in xterm
[02:38] <afterThought> Nevermind, I got it, qterminal -e "script.sh"
[02:39] <afterThought> Thanks all!
[14:07] <solerution> not sure if this is the correct channel, but I'll give it a try. In 20.04.3, is there any reason that lxsession and lxsession-default-apps are not installed? Does it conflict with something else?
[14:45] <kc2bez> solerution: Those are old lxde packages. Lubuntu uses LXQt now. 
[14:56] <solerution> kc2bez, ok, this makes sense. I asked because when I enable the openbox menu on right click (desktop preferences -> advanced -> show menus provided by WM when desktop is clicked), the menu that shows  up, requires the lxsession-default-apps. 
[14:57] <solerution> what would a recommended way to recreate this menu / or make it be in accordance with the "normal" working menu?
[14:57] <solerution> * ... be ?
[15:00] <kc2bez> I forgot that was still available in 20.04. Upstream LXQt disabled the WM menus in later versions so I don't think there is a solution. 
[15:06] <solerution> aha ok, I see, thanks though :)
[15:07] <solerution> but I guess it would still be possible if I manually create an openbox menu file by hand to just add working shortcuts
[15:08] <solerution> unless there is another issue deeper that maybe prevents a process to start (?)
[15:17] <kc2bez> Creating the menus manually should work I think. 
[15:25] <solerution> cool, thanks
 Maybe this is a basic linux question, and forgive me if it is, but after performing an apt update && upgrade, should a system be rebooted if there are only package updates/upgrades?
 Normally not
[16:28] <oerheks> heysoundude, if the file /var/run/reboot-required exists, then yes >>  cat /var/run/reboot-required ## would show: *** System restart required ***
[16:28] <oerheks> some packages are as important as the kernel
 Ok, I generally do reboot anyway after seeing “big stuff” update/upgrade, I was just wondering if it’s necessary for everything every time.
 Thanks folks
[16:31] <oerheks> use the gui tool to update, it shows if reboot is necessary
 The gui tool should trigger if there are updates. It doesn’t always.
 LWQt would match "Light Weight Qt" and "Lightweigt Wayland Qt" 😁 (re @lubuntu_bot: (irc) <guiverc> The X in LXQt is Xorg; but Wayland is known - https://github.com/lxqt/lxqt/issues/10)