Home / user-296757

undercat's questions

Martin Hope
undercat
Asked: 2021-02-13 07:27:17 +0800 CST
  • 0

I've recently switched to the Snap version of GIMP (2.10.22) and ran into the following problem.

Whenever I want to open a recent file saved by a different app in Ubuntu, I'm used to clicking "Open file" and then the "Recent" tab. This has been very straightforward and convenient.

However, the Snap version of Gimp does not "see" those files. Likewise, files saved by the Snap version of Gimp aren't perceived as "recent" by the other apps.

This is very inconvenient and I'm wondering whether it's a Snap limitation, or something that could be easily fixed. My OS is Ubuntu 20.04.

snap
Martin Hope
undercat
Asked: 2020-12-22 05:22:08 +0800 CST
  • 0

I'm trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I've also tried:

  • Rebooting — didn't help.
  • Specifying the bus explicitly as 0003 — didn't help.
  • Confirming with evtest that the key codes I'm using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I'm using to remap the keys should be correct, it's got to be an issue with the wrong identifier (though I've quintuple checked it).

Any help will be appreciated.

keyboard systemd udev 20.04 microsoft-keyboard
Martin Hope
undercat
Asked: 2018-08-26 18:17:53 +0800 CST
  • 5

Introduction

I have a source package (downloaded with apt source ...) which I'd like to explore using rtags in a code editor. The standard way of doing this is to dry-run the makefile produced by the build system feeding it to rtags so that it could use those commands for (re)building its contextual source code navigation and auto-completion databases.

Problem

Normally, I would just autogen/autoconf/configure to obtain a makefile and then dry-run the build with make -nk.

However, since I'm working with a Debian package, I need to use the Debian-specific configuration commands with dpkg-buildpackage or dpkg-source in order for the source code navigation to reflect the same build options that were used in the official builds.

I looked through buildpackage's man page but couldn't find any options that would stop the build after the ./configure step, before any actual build commands are executed. While it does have the --build=source(-S) option, it doesn't do what I want: it applies Ubuntu-specific patches and then stops before running automake/configure. This is unacceptable, since I want the automake/configure step to be executed as well.

Question

How can I make dpkg-buildpackage stop AFTER running autogen/automake/configure but BEFORE running make?

The suggested approach should work for the dnsutils source package.

package-management dpkg