Giter VIP home page Giter VIP logo

lxqt-globalkeys's Introduction

LXQt

LXQt is the next generation of LXDE, the Lightweight Desktop Environment. It is the product of the merge between Razor-qt and LXDE-Qt.

About this repository

This is a superproject which contains all LXQt components. After checking out this repo please do the following to initialize git submodules.

git submodule init
git submodule update --remote --rebase

Note: We require git >= 1.8.5

Contributing

If you are interested in helping or joining LXQt, please take a look at our CONTRIBUTING document

Translation

Translations can be done in LXQt-Weblate.

Translation status
Translation status

lxqt-globalkeys's People

Contributors

agaida avatar amoskvin avatar antis81 avatar attuska avatar dglent avatar eltonfabricio10 avatar fat-zer avatar henry-hsieh avatar jleclanche avatar kuzmas avatar luis-pereira avatar lxqtbot avatar micrococo avatar milotype avatar p-bo avatar palinek avatar paulolieuthier avatar pcman avatar philippwiesemann avatar pvanek avatar roxfr avatar scootergrisen avatar selairi avatar ska67 avatar smarquespt avatar sokoloffa avatar stefonarch avatar tsujan avatar welaq avatar zoli111 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

lxqt-globalkeys's Issues

shortcut for main menu: shortcut works only half

in the description of the shortcut-configuration there is as default the windows-key;
the description is there: "Show/hide main menu";
the shortcut shows in fact the main menu, but it does not hide it, so it works half of the description

Expected Behavior

when main menu is visible: by pressing the windows-key should hide the main menu

Current Behavior

when main menu is visible: by pressing the windows-key the main menu is still there

Possible Solution

I think the intention was really: "Show/hide main menu"; but it was not programed till the end;

not only because of the description it should have this do/undo-behavior, but also because it should have the same do/undo-behavior like the mouse:

  • click in the panel on the main-menu-symbol: main menu appears
  • click again in the panel on the main-menu-symbol: main menu disappears

at the moment the main menu can disappear with the esc-key; for people who are used to esc, one could program something like:
if (main menu is visible) then (if esc or windows-key is pressed): hide the main menu

Steps to Reproduce (for bugs)
  1. press the windows-key to let appear the main menu
  2. press again the windows-key to hide the main menu
Context

shortcuts should work like the description

System Information
  • Distribution & Version: Lubuntu 20.10
  • Qt Version: 0.15.0

New release coming?

Is there a new release coming in near future? one of the problems we have we believe it might be solved with b924f8c and is better to have a new release than patch it.

feature request: remove magic numbers in configuration

In the configuration file, shortcuts are appended with a period and a number, indicating its sequence in the list. These numbers change, however, and are ultimately pointless. They further complicate modifying configuration files by hand rather than from the GUI.

Expected Behavior

There's no magic numbers in the configuration file.

Current Behavior

Magic numbers create all sorts of madness.

Possible Solution

Remove the numbers in the configuration file and merely let the code create the enumeration in the GUI based on some default sorting methodology. In this case, where the definitions appeared in the file wouldn't matter.

The one case where it seems to make sense to indicate a difference between shortcuts (perhaps through numbers) is if there are two definitions for the same shortcut. This wouldn't make sense if they were both enabled but one could be enabled and one could be disabled. In this case, it would be good to append a number to the shortcut. There could be logic to check for duplicates and renumber them as needed.

System Information
  • Distribution & Version: Lubuntu 19.10
  • Kernel: 5.0.0
  • Qt Version: 5.12.2
  • liblxqt Version: 0.14.1
  • lxqt-build-tools Version: 0.6.0
  • Package version: 0.14.1

'/etc/lxqt/globalkeyshortcuts.conf' does not work

The shortcuts config 'globalkeyshortcuts.conf' was moved from '/etc/xdg/lxqt' to '/usr/share/lxqt' in 0.14.2.
But should '/etc/lxqt/globalkeyshortcuts.conf' not also work?

For other lxqt components I have defined my global configs under '/etc/lxqt/'.

lxqt-globalkeys: terms

I like to add some questions raised by issue #749. First, thanks for the immediate fix and sorry ... I forgot to mention the platform.

Here's my system info:

Base Distro:    Lubuntu 15.04 (Desktop, 64 bit)
LXQt version:  >0.9 development version from PPA
Hardware:       MacBook 2,1 (second VGA monitor)

When talking about the terms, my first question always is: Where can I find them? Is there a text file or something to look them up quickly?

Firing a dpkg --list lxqt* reveals the following info:

||/ Name                  Version         Architektur     Beschreibung
+++-=====================-===============-===============-===============================================
ii  lxqt-about            0.8.0+bzr39+201 amd64           lxqt-about
ii  lxqt-admin            0.9.0+bzr44+201 amd64           lxqt-admin
ii  lxqt-common           0.9.1.0.0+bzr11 all             lxqt-common
ii  lxqt-config           0.9.0.0.0+bzr30 amd64           lxqt-config
ii  lxqt-globalkeys       0.9.0+bzr151+20 amd64           lxqt-globalkeys
ii  lxqt-leave            0.9.0.0.1+bzr24 amd64           lxqt-leave
rc  lxqt-lightdm-greeter  0.0.1+bzr63+201 amd64           lxqt-lightdm-greeter
ii  lxqt-notificationd    0.9.0.0.0+bzr12 amd64           lxqt-notificationd
ii  lxqt-openssh-askpass  0.9.0+bzr29+201 amd64           lxqt-openssh-askpass
rc  lxqt-panel            0.8.0.0.2+bzr66 amd64           lxqt-panel
ii  lxqt-policykit        0.9.0+bzr33+201 amd64           lxqt-policykit
ii  lxqt-powermanagement  0.9.0+bzr148+20 amd64           lxqt-powermanagement
ii  lxqt-qtplugin         0.9.0+bzr29+201 amd64           lxqt-qtplugin
ii  lxqt-runner           0.9.0+bzr149+20 amd64           lxqt-runner
ii  lxqt-session          0.9.0.0.1+bzr24 amd64           lxqt-session

IMHO the package name lxqt-globalkeys makes as a good term.

Usually I run these settings via the command lxqt-config (usually via menu action - no terminal involved).

Browsing through Cleaning the terms up here would definitely help:

  • The terminal call is currently lxqt-config-globalkeyshortcuts -> should be lxqt-config-globalkeys.
  • The dialog's title bar reads Global Actions Manager. Suggestion: According to (all?) other lxqt-config dialog's it could show LXQt - Global Keys (or LXQt - Global Keyboard Shortcuts). Screenshot:
    lxqt-config-globalkeys
  • Running lxqt-config, the overview shows this (in German l10n):
    lxqt-config-globalkeys-marked

That's all locations I found so far. Would highly appreciate, if the term becomes more unified.

disabled global actions are still blocking after a new lxqt session

I disabled all CTRL+F## keys in the manager, I don't need them.
But after any reboot the CTRL+F5 doesn't behave how it should - though, all CTRL+F## keys are still disabled.
If I enable and disable CTRL+F5 in the manager, everything is fine again until the next reboot.

Expected Behavior

CTRL+F5 should be applied to the browser, doing a whole cache-refresh.

Current Behavior

CTRL+F5 is not applied to the browser, instead does "kind" of nothing, firefox behaves like CTRL+F5 is enabled.
But on CTRL+2 or CTRL+1 nothing happens, no desktop switch.

Possible Solution

--

Steps to Reproduce (for bugs)
  1. start your lxqt session
  2. start firefox, open any website
  3. press CTRL+F5 in order to reload the cache
  4. it should reload the whole website, but it doesn't
Context

I use µMatrix and I need to refresh the cache if I allow a frame.
If there is any website error because of blocked cookies, CTRL+F5 also helps often.

System Information
  • Distribution & Version: EndeavourOS Linux x86_64 (based on ArchLinux)
  • Kernel: 5.7.11.a-1-hardened
  • Qt Version: 5.15.0
  • liblxqt Version: 0.15.1-1
  • lxqt-build-tools Version: -- (stable version atm)
  • Package version: lxqt-globalkeys 0.15.0-1
  • windows manager: openbox

the button "Remove" should be deactivated when a marked shortcut can't be removed

in the Global-Actions-Manager-window:
the button "Remove" should be deactivated instead of activated when a marked shortcut can't be removed from the list

Expected Behavior

the button "Remove" should be deactivated when a marked shortcut can't be removed from the list

Current Behavior

the button "Remove" is still activated when a marked shortcut can't be removed from the list

Possible Solution

the button "Remove" should be deactivated when a marked shortcut can't be removed from the list

Steps to Reproduce (for bugs)
  1. open the Global-Actions-Manager-window
  2. mark a shortcut that can't be removed from the list, like for example "Show/hide main menu": the button "Remove" is still activated
Context

if the button "Remove" is still activated when a marked shortcut can't be removed from the list, and if then a user is pressing the "Remove"-button, but nothing happens, the user could think that there is a mistake in the software

System Information
  • Distribution & Version: Lubuntu 20.10
  • Qt Version: 0.15.0

lxqt-globalkeys-config-version.cmake wrong package version

cmake problems when mixing lxqt-globalkeys 0.14.2 with lxqt 0.14.1 packages..
Found be building lxqt-runner 0.14.1

CMake Error at /usr/local/share/cmake/Modules/CMakeFindDependencyMacro.cmake:47 (find_package):
  Could not find a configuration file for package "lxqt-globalkeys" that is
  compatible with requested version "0.14.2".

  The following configuration files were considered but not accepted:

    /usr/local/share/cmake/lxqt-globalkeys/lxqt-globalkeys-config.cmake, version: 0.14.1

Call Stack (most recent call first):
  /usr/local/share/cmake/lxqt-globalkeys-ui/lxqt-globalkeys-ui-config.cmake:43 (find_dependency)
  CMakeLists.txt:39 (find_package)

Fix is

--- CMakeLists.txt.orig
+++ CMakeLists.txt
@@ -72,7 +72,7 @@ configure_package_config_file(
 #************************************************
 write_basic_package_version_file(
     "${CMAKE_BINARY_DIR}/${LXQT_GLOBALKEYS_CMAKE_NAME}-config-version.cmake"
-    VERSION ${LXQT_VERSION}
+    VERSION ${LXQT_GLOBALKEYS_VERSION}
     COMPATIBILITY AnyNewerVersion
 )

Brightness shortcut keys change contrast/gamma, not brightness.

I apologize if this is not the right place to bring this up. I am using Lubuntu 20.04 LTS.

The Shortcut application is bound to lxqt-config-brightness instead of some variation of lxqt-backlight_backend.

The first command changes the gamma/contrast, not the brightness. The second one changes the brightness (at least as I understand it in this context).

Possible Solution

Binding the correct command in the shortcuts application should be able to address this but there are two issues. With that:

  1. lxqt-backlight_backend requires root permissions, but you can use pkexec lxqt-backlight_backend --inc[--dec].
  2. Neither of these seems to work if bound from the shortcut app. I tried enclosing the command in quotes but it wasn't saved with quotes in globalkeyshortcuts.conf. I couldn't manually save that in the file either.

I also tried creating an alias for the command and assigning that to the shortcut, but that doesn't work either.

All the lxqt-backlight_backend based solutions work from the terminal, but can't get the shortcuts to work.

The Brightness Settings application does the right thing.

Steps to Reproduce (for bugs)

Fire up the "Global Actions Manager" (the shortcuts app) and use brightness up shortcut to see the contrast changing. This is not what happens if you increase the brightness using the brightness application.

Context

This is a very basic feature and a major regression coming from LXDE. This feature is used (by me) multiple times a day and there is no clear way to set up the shortcut.

System Information
  • Distribution & Version: Lubuntu 20.04 LTS.
  • Kernel: 5.4.0-26.
  • Qt Version: 5.12.8
  • liblxqt Version: 0.14.1
  • lxqt-build-tools Version: Unsure
  • Package version: Unsure

I'd be more than happy to help! Apologies if I'm missing something obvious somewhere.

in the Global-Actions-Manager-window: checkbox: double-click versus one click

in the Global-Actions-Manager-window:
at the moment shortcuts can be deactivated in the list of shortcuts by double-click on the checkbox;
the checkbox is exactly the same checkbox like in the properties of the shortcut;
but in the properties only one click on the checkbox is enough to deactivate the shortcut;
that is a contradiction: 2 different behavior for a checkbox;
checkbox should have exactly the same behavior

Expected Behavior

in the Global-Actions-Manager-window:
one click to activate/deactivate the checkbox (like the checkbox in the properties of the shortcut, what can be reached for example by double-click on the description of one shortcut)

Current Behavior

in the Global-Actions-Manager-window:
double-click is necessary to activate/deactivate the checkbox

Possible Solution

I think it is necessary to add a column on the right side of the checkbox;
in this column there should be only the id-number

the reason:

  • checkbox: 1x click for activate/deactivate
  • rest of the row, like the id-number: double-click for showing the properties

in other words:
instead of 1 cell with checkbox and id-number, there should be
2 cells, so one cell only for the checkbox, and one cell only for the id-number,
because of 2 different behavior

Steps to Reproduce (for bugs)
  1. open Global-Actions-Manager-window
  2. click on the checkbox 1x
Context

checkbox should have exactly the same behavior

System Information
  • Distribution & Version: Lubuntu 20.10
  • Qt Version: 0.15.0

Super_L "Show/hide main menu" binding blocks WM keybinds using Win key

When I enable the Super_L "Show/hide main menu" binding in lxqt-globalkeys, my Openbox keybindings that use the Win key as a modifier such as W-Right to tile a window right no longer work.

Possible Solution

I realize that as LXQT now considers itself WM agnostic it is not responsible for WM incompatibilities, I'd just like some guidance as to the most appropriate place to fix this if it can be fixed.

Steps to Reproduce (for bugs)
  1. Make a keybind in the Openbox rc.xml such as W-e to run pcmanfm-qt.
  2. Enable Super_L for "Show/hide main menu" in lxqt-globalkeys.
  3. Try to use the Openbox W-e keybinding, it won't work.
Context

I'd like to be able to use the Super_L keybinding, as I'm used to it from things like Windows and KDE, without it interfering with Openbox. I could probably just move some of my Openbox keybindings to lxqt-globalkeys instead, although I'm not sure how I'd make it do things like tiling keybindings.

System Information
  • Distribution & Version: Gentoo unstable, systemd profile
  • Kernel: 5.19.0-rc6-x86_64+
  • Qt Version: 5.15.5
  • liblxqt Version: 1.1.0
  • lxqt-build-tools Version: 0.11.0
  • Package version: lxqt-globalkeys 1.1.0

duplicated entries in shortcuts conf

Expected Behavior

each keyboard shortcut should be unique in config

Current Behavior

it isn't

Possible Solution

fix ti

Steps to Reproduce (for bugs)

provide the same key in /usr/share conf. etc/xdg and $HOME/.config - maybe with different numbers

Context


^^^ i really don't like it 😎

Possible related to: #125

Imho the command/key combination should be unique, i have nothing against

ctrl a and ctrl b doing the same thing - might be legit, but i don't want to see

11 ctrl a action foo
12 crtl a action foo
13 crtl a action foo

System Information

latest git

Exporting shortcuts

I'd like to save my shortcuts but I can't find the location of the config file for lxqt-config-globalkeyshortcuts.
A button "export" would be nice too... :-)

feature request: improved restart handling

It would be nice if there were options to restart and/or reconfigure a running daemon.

Expected Behavior

It's easy to restart lxqt-globalkeysd.

Current Behavior

It's not easy to restart lxqt-globalkeysd.

Possible Solution

With Openbox, for example, you can run openbox --restart to stop the current daemon and start a new one or you can run openbox --reconfigure after having edited the configuration files to get the running daemon to use them. Alternately, sending SIGHUP or SIGUSR might work.

Context

The primary issue is that in order to ensure the daemon is run in the same fashion, one would have to research how the daemon was run in the first place and to replicate it, rather than the above suggestions which would work universally for everyone and could be documented in the man page.

System Information
  • Distribution & Version: Lubuntu 19.10
  • Kernel: 5.0.0
  • Qt Version: 5.12.2
  • liblxqt Version: 0.14.1
  • lxqt-build-tools Version: 0.6.0
  • Package version: 0.14.1

shortcuts going through panel

I noticed that shortcuts like opening pcmanfm-qt etc directly go to the apps.
while shortcuts for opening applications menu goes like /panel/mainmenu/show_hide

The conflict I see is if someone removes the default panel and adds a new panel with say, only mainmenu and clock in it,
the shortcut set for mainmenu (super_L in case of lubuntu) doesn't work.
reason, it is set to /panel/mainmenu/show_hide
which refers to mainmenu on earlier panel.
In this case, user is likely to go to shortcuts editor(lxqt-config-globalkeyshortcuts) and check the settings. But only to find that the super_l key has show/hide main menu in description and set to /panel/mainmenu/show_hide
Note: He will see that this entry is in italics as compared to other entries(which are working, eg pcmanfm-qt)
Since user doesn't know about how things work, he/she is still gonna say that shortcut keys is broken.
But it is not, he needs to right click on application menu of new panel, select configure, and set shortcut to super_l which by default is set to alt+F1
Now after doing that, if one goes and checks the shortcut settings, one can see that there are two entries for Super_L :

  1. set to /panel/mainmenu/show_hide
  2. set to /panel/mainmenu2/show_hide
    Note: Earlier one is still in italics but both entries are in bold now.
Expected Behavior

Ideally a user expects if mainmenu is set to open via a particular key combination, it should work even if the mainmenu is present on panel other than default one. Coz he sees that he has set it in shortcut settings.

Current Behavior

Mainmenu is set to combination "x"
if mainmenu is removed and created again(on same/ different panel),
the earlier key combination "x" doesn't work

Note: same is observed for panel/desktopswitch , panel/taskbar/

Possible Solution

No idea yet. Still reading the cpp manual.
Instead if creating two entries as above, either the earlier entry should be modified coz it's obselete now. OR any key combination once set for particular function(opening menu/switching apps) should do that irrespective of panel's settings. (shortcuts shouldn't go through /panel)

Steps to Reproduce
  1. Set mainmenu to open on pressing super_l (do this using shortcuts editor)(another combination can also be used)
  2. check if it works.
  3. now remove the mainmenu from panel
  4. now add it again, on same place
  5. press the combination you set in step 1.
  6. Doesn't work
  7. go to shortcut settings and notice that the line for that shortcut which you set is in italics
  8. right click on the menu and select configure, see that it is set to alt+f1
  9. set it to same combinantion as in step 1.
  10. open shortcut settings again, see that there are two entries for the combination
    as mentioned above. Earlier one is still in italics but both entries are in bold now.
Context

seems like shortcuts are set according to panel and associated modules
while ideally they should be set according to "keys"
explaination:
looks like super key is set to launch /panel/mainmenu i.e it is set according to panel applet
but ideally panel applet should be set to open on pressing super key.

i.e instead of two entries in shortcut settings, the earlier entry should hav been modified to /panel/mainmenu2

System Information
  • Distribution & Version: Lubuntu 19.10 daily build
  • Kernel: 5.2.0-15-generic
  • Qt Version: 0.14.1
  • liblxqt Version: 0.14.1
  • Package version: 0.14.1

Add a default lxqt-globalkeys.conf in lxqt-common

I need to add some key shortcuts by default.

Some of them help to solve problems with screen brightness. These shortcuts are:

  • Increase screen brightness
  • Decrease screen brightness

I would like to add another shortcut too:

  • Ctl + Alt + T to open Terminal.
    This shortcut is set by default in other desktops.

Maybe the simplest way to add those shortcuts is writing a new config file in lxqt-common. This file would be lxqt-common/config/lxqt-globalkeys.conf.

I can do it by myself.

What do you think?

lxqt-globalkeys seems to handle quotation marks improperly

I'm not sure if I'm in the right place for lxqt-globalkeys bugs - if not, please point me in the right direction.

Expected Behavior

I want to use lxqt-globalkeys to take screenshots using scrot.
I'm trying to add a shortcut using lxqt-config-globalkeyshortcuts to execute a command, for example:
scrot '%Y-%m-%d_%Hh%Mm%Ss.png' -e 'mv $f ~/Pictures/screenshots/'
I'd expect the exact command to be executed, as if I had typed it into a shell.

Current Behavior

Edit: I think you can skip this section and see Steps to Reproduce for a tl;dr

There seem to be problems with sanitising the command input field in lxqt-config-globalkeyshortcuts.

If I add a shortcut to execute this command:
scrot '%Y-%m-%d_%Hh%Mm%Ss.png' -e 'mv $f ~/Pictures/screenshots/'
pressing the defined shortcut will result in this error being printed in the shell where I started lxqt-globalkeysd (not sure what happens when the daemon is started automatically):
giblib error: Saving to file 2017-10-23_16h11m53s.png' -e 'mv ~/Pictures/screenshots/ failed

This seems to indicate that something funky happens to the outer set of quotes. I can replicate the error by typing the following scrot command in a terminal (note the outer double quotes):
scrot "%Y-%m-%d_%Hh%Mm%Ss.png' -e 'mv $f ~/Pictures/screenshots/"

It gets even weirder if I try to use the same command with double quotes, like this:
scrot "%Y-%m-%d_%Hh%Mm%Ss.png" -e "mv $f ~/Pictures/screenshots/"
The command will instead by saved like this:
scrot '%Y-%m-%d_%Hh%Mm%Ss.png" -e "mv $f ~/Pictures/screenshots/'
Note the single quotes.

If I try to save it with all single quotes escaped, like this:
scrot \'%Y-%m-%d_%Hh%Mm%Ss.png\' -e \'mv $f ~/Pictures/screenshots/\'
The window for shortcut input closes, but no entry is added to the list of shortcuts. No error is printed to the console, and nothing happens when I press the key I defined.

The same thing happens if I only escape the outer quotes, like this:
scrot \'%Y-%m-%d_%Hh%Mm%Ss.png' -e 'mv $f ~/Pictures/screenshots/\'

If I only escape the inner set of quotes, like this:
scrot '%Y-%m-%d_%Hh%Mm%Ss.png\' -e \'mv $f ~/Pictures/screenshots/'
The command is displayed in the list just like I typed it (including \' for the inner quotes), but the error message again looks like this:
giblib error: Saving to file 2017-10-23_16h25m50s.png' -e 'mv ~/Pictures/screenshots/ failed

Steps to Reproduce
Case 1: Escaped single quotes
  1. Launch lxqt-config-globalkeyshortcuts
  2. Click Add ...
  3. Define a shortcut key, enter some description, click radio button for "Command"
  4. Enter this into the command field: echo \'asdf\'
  5. Click OK.
    -> The window will close, but no shortcut is added to the list.

lxqt-scrot

Case 2: Non-Escaped single quotes
  1. Run steps 1-5 as before, but enter the following command: echo \'asdf\'
    -> The entry will appear in the list, but without the quotation marks
    singlequotes
Case 2: Nested single quotes
  1. Run steps 1-5 as before, but enter the following command: echo 'asdf'; echo 'foo'
    -> The command will appear in the list exactly as it was entered
    nestedquotes
  2. Press the shortcut defined before
    -> Only the first echo command will run, with the following output: asdf'; echo 'foo
System Information
  • Distribution & Version: Debian GNU/Linux 9 (stretch)
  • Kernel: Linux 4.9.51-1 amd64
  • Package version: lxqt-globalkeys/stable 0.11.1-1 amd64
  • Display manager: gdm3
  • Window manager: awesome 4.0

No way to remove global shortcuts

There's no way to remove the shortcuts that aren't defined by the user -- let's call them "global" -- at best, they can be disabled.

The code should allow the removal of any kind of shortcut, IMO.

Enabling of a disabled shortcut does not take effect without a daemon restart

Expected Behavior

When I enable an existing but disabled shortcut, I expect it to work.

Current Behavior

When a disabled shortcut is enabled, a daemon restart is needed for it to work.

Possible Solution

Will make a PR.

Steps to Reproduce (for bugs)
  1. Enable a disabled shortcut or disable a working shortcut and enable it again.
  2. Press the keys of that shortcut.

Then nothing will happen until you restart lxqt-globalkeysd.

Context

I found this bug while fixing #173.

System Information
  • Latest git LXQt.

bug: keyboard input ignored

Expected Behavior

Normal operation

Current Behavior

This happened twice today, unknown cause, where keyboard becomes mostly non-responsive (cannot alt-tab, cannot type into open windows, none of the shortcuts handled by lxqt work) except for ctrl+alt+F2 which let me switch to a text console and troubleshoot this issue.

Possible Solution

From another console, 'kill -SIGQUIT" on the lxqt-globalkeysd PID, causes it to be respawned and normal operation restored. [EDIT - on a third occurence, it was 'lxqt-panel' that needed to be killed - will try to confirm this next time]

Steps to Reproduce (for bugs)
  1. use system normally
  2. sorry, that's all I have...
Context

started occuring after recent system update , however no lxqt or openbox packages were updated (only kernel and other seemingly unrelated pkgs)

System Information
  • Distribution & Version: archlinux
  • Kernel: 6.7.6
  • Qt Version: 5.15.12
  • liblxqt Version: 1.4.0-1
  • lxqt-build-tools Version: -
  • Package version: 1.4.0-1

Meta + backslash shortcut won't survive a reboot.

Hello everybody and thanks for the great job you’re doing on this DE!

I'm trying to set up a shortcut where pressing Meta+backslash brings out featherpad (but I also tried kcalc just to check, and it would behave the same way)
I do manage to assign this shortcut through lxqt-globalkeys, which works properly until I reboot. after the reboot, it won't work anymore: the shortcut doesn't load anything. Meta+u, for example, works perfectly, only Meta+backslash won't survive a reboot even though it still appears among lxqt-globalkeys shortcuts (and not in bold)
Meta+backslash also works smoothly when I set it through openbox

I'm using Lubuntu 19.04 with all the latest updates

Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
System Information
  • Distribution & Version:
  • Kernel:
  • Qt Version:
  • liblxqt Version:
  • lxqt-build-tools Version:
  • Package version:

dbus method parameters

I have been trying to make a keypress in lxqt call a dbus method.
This functionality exists, however it is not clear if, or where static method parameters can be passed to the called method.

We need a new release because of the CMakeLists-Bug

Current release make the builds of lxqt-panel and -runner FTBFS

Expected Behavior

panel and runner should build :)

Possible Solution

make a new point release - the chance is to hight that we wreck the builds of certain distributions

New Release

Hii.
Do you plan to have a new release soon? About using xdg-hierarchy if no config file is given. It would be great if you could provide a release. We won't have to patch it for lubuntu then. It actually affects a high priority task on our end so I wanted to know if new release was upcoming.

Thanks!

Shortcuts Ignored After Upgrade

Expected Behavior

After upgrading lxqt shortcut keys are expected to work as before

Current Behavior

Upgrading lxqt, in particular lxqt-globalkeys (0.17.0-1 -> 1.0.0-1), shortcut keys ceased working. Further, configuration tool "Global Actions Manager" is empty/does not list shortcuts although file $HOME/.config/lxqt/globalkeyshortcuts.conf still exists and has proper content. Adding new shortcuts in config tool is also not working because all buttons are disabled. globalkeyshortcuts.conf has rw entitlements for user, group and others.

Possible Solution

Running out of ideas...

Steps to Reproduce (for bugs)
  1. User shortcut keys as before upgrade
  2. No action is taking place
Context

Trying to start apps as configured in globalkeyshosrtcuts.conf

System Information
  • Distribution & Version: ArchLinux
  • Kernel: 5.15.7-arch1-1 #1 SMP PREEMPT Wed, 08 Dec 2021 14:33:16 +0000 x86_64 GNU/Linux
  • Qt Version:
  • liblxqt Version: 1.0.0-1
  • lxqt-build-tools Version:
  • Package version:

Unlock valid shortcuts

The UI doesn't allow for certain valid shortcuts (e.g. I have mapped Meta-E to xdg-open /home/<user>). This likely will hit quite a number of systems since 0.17 deactivates lxqt-openbox.conf - forcing users to manually "reconfigure" openbox and LXQt shortcuts.

LXQt should solve that during upgrade (0.17.1 package maybe?). E.g. rename an existing ~/.config/openbox/lxqt-openbox.xml to …/rc.xml when upgrading.

Expected Behavior

User can define shortcuts for any key combination.

Current Behavior

Some shortcuts including the Meta key cannot be registered via UI (dialog with 10s countdouwn). They do work however, so for example adding this to the config helps:

[Meta%2BE.26]
Comment=File Manager
Enabled=true
Exec=xdg-open, /home/<USER-NAME>

💡 Don't forget to replace sequence number (26 here) and with local settings!

Steps to Reproduce (for bugs)

Try to register a Meta-E shortcut via lxqt-globalkeys UI.

Context

Desktop environment

System Information

Affects any LXQt 0.17 setup

Register shortcuts under wayland

Expected Behavior

We can use lxqt-globalkeysd under wayland

Possible Solution

Also for other global shortcut systems to work with KWin it’s needed to port them to use KGlobalAccel internally when running in a Plasma/Wayland session (that’s also a good idea for X11 sessions as KGlobalAccel can provide additional features like checking whether the key is already taken by another process).

  • Wrapper for writing to different compositors configs (workaround)

feature request: filter shortcuts

Expected Behavior

A possibility to filter the list by the fields "shortcut", "description" and "info".

Current Behavior

Not implemented

Possible Solution

Add a text field where a contained string can be entered.

Steps to Reproduce (for bugs)

n.a.

Context

Improve usability

System Information
  • Package version: 0.17

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.