[Ubuntu-x-swat] [Bug 2002869] [NEW] "ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Public bug reported:
Ubuntu: 22.10
xkb-data: 2.35.1-1
keyboard layout: jp106
I enable a xkb option "ctrl:swapcaps" and often use shift+ctrl modifier
key combinations like shift+ctrl+T.
Expected:
Both pressing [shift]+[capslock] and [capslock]+[shift] should work as
shift+ctrl modifier.
What happened:
[capslock]+[shift] works as expected, but [shift]+[capslock] still works
as shift+capslock.
This behavior is very confusing and annoying to me.
Workaround:
The problem can be avoided by editing /usr/share/X11/xkb/symbols/ctrl as
follows.
--- ctrl.orig 2022-02-09 02:13:55.0 +0900
+++ ctrl2023-01-14 18:57:15.589534502 +0900
@@ -14,7 +14,7 @@
// Swap the functions of the CapsLock key and the left Ctrl key.
partial modifier_keys
xkb_symbols "swapcaps" {
-replace key { [ Control_L ] };
+replace key { [ Control_L, Control_L ] };
replace key { [ Caps_Lock ] };
modifier_map Control { };
modifier_map Lock { };
** Affects: xkeyboard-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/2002869
Title:
"ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2002869/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpText
Thanks, Daniel. I reported my Blender issue in Blender bug tracker. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpText
My own build of Blender that OSL support is enabled crashes on startup in Virtualbox. Attached a backtrace. ** Attachment added: blender_OSL_in_virtualbox_crash.txt https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/927168/+attachment/3431061/+files/blender_OSL_in_virtualbox_crash.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 950963] [NEW] nvidia-graphics-drivers needs to provide separate packages such as libcuda1
Public bug reported: Ubuntu 12.04 nvidia-graphics-drivers 295.20-0ubuntu1 In Ubuntu, nvidia-graphics-drivers package provides only nvidia-current and nvidia-current-dev, while the Debian's package provides many separated deb packages as follows: libcuda1 libcuda1-dev libcuda1-ia32 libgl1-nvidia-alternatives libgl1-nvidia-alternatives-ia32 libgl1-nvidia-glx libgl1-nvidia-glx-ia32 libglx-nvidia-alternatives libnvidia-compiler libnvidia-compiler-ia32 libnvidia-compiler1 libnvidia-compiler1-ia32 nvidia-glx nvidia-glx-dev nvidia-glx-ia32 nvidia-kernel-dkms nvidia-kernel-source nvidia-libopencl1 nvidia-libopencl1-dev nvidia-libopencl1-ia32 nvidia-libvdpau-dev nvidia-libvdpau1 nvidia-libvdpau1-ia32 nvidia-opencl-common nvidia-opencl-icd nvidia-opencl-icd-ia32 nvidia-smi nvidia-vdpau-driver nvidia-vdpau-driver-ia32 So, some packages imported from Debian cannot be built or not installable unless their dependencies are modified. For example, nvidia-cuda-toolkit is failed to build because of missing libcuda1. See https://launchpad.net/ubuntu/+source/nvidia-cuda- toolkit/4.0.17-3/+build/3079987 . I think the separate packages should be provided as in Debian and nvidia-current and nvidia-current-dev should be changed to meta packages which depend on those separate packages. ** Affects: nvidia-cuda-toolkit (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-cuda-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/950963 Title: nvidia-graphics-drivers needs to provide separate packages such as libcuda1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/950963/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 587288] Re: ld cannot find -lcuda, when compiling cuda programs
This problem can be solved by putting .profile file the following line: export LIBRARY_PATH=/usr/lib/nvidia-current I think creating /etc/profile.d/nvidia-current.sh file containing the above is good idea. This file provides the system-wide setting. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/587288 Title: ld cannot find -lcuda, when compiling cuda programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/587288/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 587288] Re: ld cannot find -lcuda, when compiling cuda programs
Probably, export LIBRARY_PATH=/usr/lib/nvidia-current:$LIBRARY_PATH is better than my previous code in comment #6. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/587288 Title: ld cannot find -lcuda, when compiling cuda programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/587288/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
