** Description changed:
Running 21.04, updated daily.
Since updating the linux-firmware package yesterday, the Wireless card
does not work with current kernel (5.11.0-13).
The error message is as follows:
Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout
** Description changed:
[Impact]
On mlx5 device, When creating geneve tunnel in a Virtual Function and
setting it up error are logged in kernel buffer.
[test case]
using two setups connected back to back
on both sides create vf's
$ echo 1 >
And yes, it is not the perfect solution. For all readers, before
installation you must know that sometimes, backspace key is holding even
if you release the key and it erase all you are typing... That's why it
is better to activate it only if it is needed. We made a huge progress
last days and I'm
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1909005
Title:
Ubuntu does not resume (wake up) from suspend
Status in
@mohamed : Please could you help me to remove the toggle ON/OFF from the
numpad ? I prefer activate it only with F8 because sometimes it switch
on despite I don't want. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I confirm your workaround is working fine with the Asus UX431F model, Linux
5.4.0-70-generic
I used the default script ux433_touchpad_numpad.py.
Thank you for your hard work!
Le sam. 3 avr. 2021 à 17:20, Badaoui Mohamed <1810...@bugs.launchpad.net> a
écrit :
> @amattana your package is
Public bug reported:
[Impact]
On mlx5 device, When creating geneve tunnel in a Virtual Function and
setting it up error are logged in kernel buffer.
[test case]
using two setups connected back to back
on both sides create vf's
$ echo 1 > /sys/class/net/ens5f0/device/sriov_numvfs
add ip-es to
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1922472
and then change the status of the bug to 'Confirmed'.
If, due to the
Seems that the steps to fixing this issue are:
1) Turn on bluetooth in GNOME (has no effect)
2) Then: sudo systemctl restart bluetooth
And then it works
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Renaming file iwlwifi-ty-a0-gf-a0.pnvm to iwlwifi-ty-a0-gf-a0.pnvm.old
located on /lib/firmware/ is enough to make it work as-is on current
kernel.
If there are any tests needed to help troubleshoot this for good, please
let me know.
--
You received this bug notification because you are a
@Magella just clean your previous installation with the right command.
For you, I think it is something like:
sudo systemctl stop M433IA_touchpad_numpad
sudo systemctl disable M433IA_touchpad_numpad
sudo rm -rf /lib/systemd/system/M433IA_touchpad_numpad.service
sudo rm -rf
@magellan
You need to ensure that you have uninstalled previous version, else if
you have the 2 scripts running at the same time, one would conflict with
another
Mohamed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've just update install.sh to take into account qwerty keyboard.
You can re run sudo ./install.sh and it should be fine.
else you have to find and replace all KEY_KEY_APOSTROPHE by KEY_5
Normally the % symbol is on the 5 key ?
Mohamed
--
You received this bug notification because you are a
Thanks for the feedback.
Normally it s already working.
The install.sh does all what you mentioned and copy the python modified script
in folder /usr/bin
Check the result inside /usr/bin/asus_touchpad_numpad.py
Thanks,
Mohamed.
--
You received this bug notification because you are a member
I'm sorry, but I dont' understand this bug report. Maybe you can
explain what you did, what you expected to happen and what happened
instead.
FWIW, turbostat exists just fine in focal.
$ dpkg -S /usr/bin/turbostat
linux-tools-common: /usr/bin/turbostat
--
You received this bug notification
Cool. I can't believe that my notebook is working so fine now...
In line 73 of install.sh we can list the model UX363EA as a option,
after M433IA.
Thanks for your time and patience.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
@Santiago
I just remove the mention of models because I think there is no need to precise
a list of working models, as it depends mainly on the numpad layout and not
really on the asus model.
@Pilot6
Currently there is 2 ways to light up the numpad (F8 and top right corner).
Using the touchpad
I'm going to make a second try with the last Mohamed version :-(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status
@mohamed-badaoui
I think they have the click feature. The event is BTN_LEFT. I tested it
and it works. I think it is a good idea to use it for turning it on. I
don't know how it works in Windows.
--
You received this bug notification because you are a member of Kernel
Packages, which is
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1922506
Title:
No video during boot process
@Magellan I forgot to precise you that I removed the sub folder for your
version. All scripts are in the root directory:
https://github.com/mohamed-badaoui/ux433-touchpad-numpad
So run sudo ./install.sh from this directory (not the old sub
directory).
Mohamed.
--
You received this bug
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1922494
and then change the status of the bug to 'Confirmed'.
If, due to the
Thanks Mohamed.
I have tested your suggestion, but don't worked for me. Maybe I'm not
doing it right. I have a qwerty keyboard, Spanish distribution.
I have replaced line 99:
dev.enable(EV_KEY.KEY_APOSTROPHE)
by:
dev.enable(EV_KEY.KEY_5)
And line 234
value = EV_KEY.KEY_APOSTROPHE
by:
value
Ohhh!!
Understood now :D
Around line 249 I introduced a typo :(
Now it is fixed and working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't
Ok cool ^^
workaround tested and works fine for these asus versions:
- UX433 (without extra symbols)
- UX431F (without extra symbols)
- UX434FA (with % and = symbols)
- UX363EA (with % and = symbols)
https://github.com/mohamed-badaoui/ux433-touchpad-numpad
Mohamed
--
You received this bug
Great. You can introduce in the install.sh a option for ZenBook
UX363EA_UX363EA. And a new .py file to this notebook.
If you do this I test it to check that it's ok.
For touchpad_numpad_m433ia.py I have edited the lines 9 and 10, fixing
the interface to turn ON/OFF. Because my touchpar interface
asus zenbook UX434FA
Hello everyone I have my fully functional digital keyboard thanks to
mohamed.
https://github.com/mohamed-badaoui/ux433-touchpad-numpad
Many thanks Mohamed!!!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
So for the moment that workaround has been tested and works fine for
these asus versions:
- UX433 (without extra symbols)
- UX431F (without extra symbols)
- UX434FA (with % and = symbols)
https://github.com/mohamed-badaoui/ux433-touchpad-numpad
Mohamed
--
You received this bug notification
@Magellan
the code part you would like to disable, is around line 130, that one :
if e.matches(EV_KEY.BTN_TOOL_FINGER) and e.value == 0:
# Check if numlock was hit #
if (x > 0.95 * maxx) and (y < 0.05 * maxy):
finger=0
if not
Hi Santiago,
You ve got an Qwerty keyboard.
You have to replace APOSTROPHE by KEY_5 (APOSTROPHE works for azerty keyboard)
Mohamed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@magellan
The current version is not really different than the older.
I let you compare the 2 versions. You ll see that it is barely a reorder of
code part to manage correctly the events.
Mohamed.
--
You received this bug notification because you are a member of Kernel
Packages, which is
@mohamed-badaoui
I confirm the script works for X412DA laptop.
I have a small suggestion. Change touchpad actions from taps to clicks.
That will solve the problem with accidentally turning it on, etc. At
least the toggle button.
--
You received this bug notification because you are a member of
@Pilot
If we use the click to enable the numpad, that means that a user who
want to do a simple click with his touchpad would in fact turn on his
numpad?
Mohamed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For thus interrested, here is a mod version with only F8 to activate the
numpad and no detection above the first line. The mohamed version
capture 7,8,9 and / even if we click above the numbers. On this numpad
there is a blank area above with 2 icons on the up corners. On the left
for adjusting
Hi Magellan,
I fixed the backspace repetition error.
I also added in the installer the auto-detection of ic2 adapter. So no need to
manually modify anymore the number inside the python script.
@Cedric Your issue is due to a bad detection of your touchpad device.
Can you give us the results of
If someone has already installed the previous version, before re-running
.install.sh, you have to clean old installation with following commands:
sudo systemctl stop ux433_touchpad_numpad
sudo systemctl disable ux433_touchpad_numpad
sudo rm -rf /lib/systemd/system/ux433_touchpad_numpad.service
@Mohamed : Could you just tell me how to remove the toggle area on the
numpad in your code ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't
Yes Thanks Mohamed... I've just find it by myself 2 minutes ago !
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Just testing the script for ZenBook UX363EA_UX363EA, with ubuntu 20.04.
The available script named touchpad_numpad_m433ia.py works for me with a
minor fix, as I can describe:
1) install.sh script detects the correct interface of the numeric pad:
# bash install.sh
Testing interface i2c-1 :
@magellan
I can confirm that for me is working like a charm without any bug by
now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in
Ok Mohamed you're the best. But about the top right corner, is it still
activated ? Because on my computer, sometimes, if I just pass my hand
over to type text, it light up. You add auto-detection, this is magic
but how about my azerty keyboard ? Do I need to make changes ?
--
You received this
Sorry but it's completely buggy for me. The numpad type numbers alone
and erase them alone after. Looks like some key is still pressed... In
my version I resize the ignore area to fit my numpad so when I put my
fingers above the number on the first line it is not detected. Now it is
no more the
There's no other script, all was removed (files et services). My last
version was the most stable. I just need to remove the toggle area on
the numpad but don't understand how.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
[impact]
Add Support for flow counters offset for bulk counters on kernel side.
Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on
user space side only with these 3 rdma-core patches from v27.0
3956cf74 mlx5: Add support for bulk flow counters
Because your last update does not work on my computer, I still have one
last problem with mine and the backspace. I don't know how you managed
to solve the problem in your last update because as it is not usable for
me, I didn't investigate... but for me, we must avoid key repetition for
all area.
Nobody else have problem with their numpad ? All is working like a charm
without any bug ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work
Ok... I'm the "Calimero" Boy. On M433IA, even if I don't press
anything,when I'm using Firefox, it comes back to previous pages like I
press backspace. There is a problem with this key ! If only I known how
to eliminate key repetition, I think lot of problems will disappear.
--
You received this
Public bug reported:
Kubuntu beta 21.04 installed on disk, upgraded from Kubuntu 20.10. After
booting with kernel 5.11 (linux-image-5.11.0-13) if I will reboot the system,
or shutdown and boot again external monitor (connected via displayport) is not
waking up until SDDM is loaded - screen is
** Description changed:
- Kubuntu beta 21.04 installed on disk, upgraded from Kubuntu 20.10. After
booting with kernel 5.11 (linux-image-5.11.0-13) if I will reboot the system,
or shutdown and boot again external monitor (connected via displayport) is not
waking up until SDDM is loaded -
@mohamed-badaoui
It works with clicks. The event is BTN_LEFT.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status
@Pilot6
Oh ok my bad.
On Asus Ux433 the click is possible only on the bottom part of the touchpad.
So it could not work for the first keys row.
Mohamed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
otherwise what we could try is activation by a longer tap of the upper right
corner.
For example for 2 seconds. I think It might be possible but I don't know if
that would be a good solution.
Mohamed.
--
You received this bug notification because you are a member of Kernel
Packages, which is
@Pilot6
As far as I know, on Windows it works the same way just by touching the top
right corner.
And I agree it s not the best user experience solution.
That's why at the beginning I searched a keyboard combination with no
conflict to enable it and I went for F8.
But F8 is sometimes used by
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1922523
Title:
package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to
Public bug reported:
Upon startup after a routine software update, my desktop was limited to
640×480 resolution, making the desktop UI unusable. Switching graphics
drivers didn't help.
Downgrading the kernel from linux-image-5.11.0-7612-generic to linux-
image-5.8.0-7642-generic via Grub after
Ok I tried it, it seems workable solution.
If I correctly understood, you suggest to listen on the click event
(instead of the tap event) of the top right corner to turn on and enable
the numpad?
Personally I m not a huge fan, certainly because on UX433 model, the
click is a little hard, above
@mohamed
Tested for ZenBook UX363EA. I can confirm that is working very fine.
Just executed the script and voilá!!
1234567590.+-*/=%
Perfect.
Thanks very much.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@mohamed
Yes, it is a little "hard" to click, I also never use it while normally
using the touchpad. But in this case it seems perfect. it prevents
accidentally enabling the numpad, etc. I completely switched to clicking
and it seems good. You can post this solution for testing by other
people.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-gcp (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
No, it doesn't mean that simple clicking will disable the touchpad. We
match the area and the click. If you replace BTN_TOOL_FINGER with
BTN_LEFT, you'll see it. Some small changes will be needed to polish.
--
You received this bug notification because you are a member of Kernel
Packages, which
@mohamed
Did you try it? It shouldn't matter where you click.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status
Also this can be quite easily be added to Linux kernel. But it needs
some testing for different models.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
68 matches
Mail list logo
