Public bug reported:
Errors visible in /var/log/Xorg.0.log. You can see the devices get
disconnected once the pen enters the proximity of the screen (hover
cursor). Uploaded example shows:
[15.106] (II) config/udev: Adding input device Wacom HID 516B Finger
(/dev/input/mouse3)
[15.106]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1922529
When reporting bugs in the future please use apport by using 'ubuntu-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lam (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911668
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910405
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910405
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913215
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914224
[Expired for gcc-9 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gcc-9 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914257
Public bug reported:
do-release-upgrade reported a fatal error stating that a bug report
should be filed and to attach /var/log/dist-upgrade/{apt,main}.log
lsb_release -rd reports:
Description: Ubuntu 18.04.5 LTS
Release: Ubuntu 18.04
** Affects: ubuntu
Importance: Undecided
Public bug reported:
Not sure what's going on. The installers for 2020.10 and 2021.04 seem
to come up with a menu I've not seen before. It includes a line for
manufacturers. I'll update the bug with more details later.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
This issue seems to have been resolved in Groovy.
** Also affects: xfwm4 (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: xfwm4 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: xfwm4 (Ubuntu Groovy)
Status: New => Fix Released
**
** Bug watch added: gitlab.xfce.org/xfce/xfwm4/-/issues #372
https://gitlab.xfce.org/xfce/xfwm4/-/issues/372
** Also affects: xfwm4 via
https://gitlab.xfce.org/xfce/xfwm4/-/issues/372
Importance: Unknown
Status: Unknown
** Changed in: xfwm4 (Ubuntu)
Status: New =>
Is this still an issue with recent releases (20.04, 20.10)?
** Changed in: xfwm4 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859836
Title:
Blinking
*** This bug is a duplicate of bug 1864613 ***
https://bugs.launchpad.net/bugs/1864613
** This bug has been marked a duplicate of bug 1864613
xfwm4 very, very slow - leaking something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is this still a problem with recent releases (20.04, 20.10)?
** Changed in: xfwm4 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854511
Title:
desktop not
Is this still a problem in recent releases? (20.04, 20.10)
** Changed in: xfwm4 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853766
Title:
xfwm4
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
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922523
Title:
package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to
install/upgrade: installed
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849493
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849493
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849493
Public bug reported:
After installing Ubuntu 20.04.2 LTS on my ASUS Q325UA, I could not use
the touchpad. I plugged in a mouse and it worked afterwards, but when
another user logged on, the touchpad functionality disappeared.
I followed the guide:
Fix included in 4.15.0.
** Also affects: xfwm4 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: xfwm4 (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Also affects: xfwm4 (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in:
Hello; I am also trying to make this work. I'm get the same Java error,
and trying to run down the comments about 6.1. This is what I see:
(base) cuz@ubuntu:~$ uname -a
Linux ubuntu 5.8.0-48-generic #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
(base)
Fix included in Xfwm4 4.13.2. So this is fixed in Focal and still broken
in Bionic.
** Also affects: xfwm4 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: xfwm4 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: xfwm4 (Ubuntu Bionic)
Is this still an issue in 20.04?
** Changed in: xfwm4 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845874
Title:
Screen blotches/flickering on
Public bug reported:
I am clueless on the cause. It crashed while doing the system setup. I
don't recall what step I was on.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
Uname: Linux 5.8.0-1006-raspi aarch64
Issue disappeared after 4.12.5-1ubuntu1.
** Also affects: xfwm4 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: xfwm4 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: xfwm4 (Ubuntu Focal)
Status: New => Fix Released
** Changed in:
Issue disappeared after 4.12.5-1ubuntu1.
** Also affects: xfwm4 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: xfwm4 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: xfwm4 (Ubuntu Focal)
Status: New => Fix Released
** Changed in:
Issue disappeared after 4.12.5-1ubuntu1.
** Also affects: xfwm4 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: xfwm4 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: xfwm4 (Ubuntu Focal)
Status: New => Fix Released
** Changed in:
All affected releases are EOL. Closing this bug.
** Changed in: xfwm4 (Ubuntu)
Status: New => Fix Released
** Changed in: xfwm4 (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All affected versions are EOL. Closing this bug.
** Changed in: xfwm4 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682676
Title:
/usr/bin/xfwm4:*** Error
Upstream xfwm4 marked WONTFIX.
** Changed in: xfwm4 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054923
Title:
Window raises on click even if set
Sorry guys this private answer should not have been done there. I was
saying to Sylvestre that I could help to propagate some fixes to
upstream.
S.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bonsoir Sylvestre,
Il va falloir que tu m'explique ce que je peux faire de mon côté car
c'est plutôt Clément qui maitrise le build sous Linux (moi c'est sous
macOS, et les problèmes sont disons... différents mais tout aussi
présents). Surtout que là les problèmes principaux sont dus me
@queen8387: Thanks for reporting the bug.
This will be fixed in a few days. I am not sure if there is a workaround
for this.
For now, you can open rhythmbox, and import the songs and play it from
there, rather than from GNOME File manager.
--
You received this bug notification because you are
Public bug reported:
Froze twice on me.
1) Started up OK, selected preferences fine, then froze when I chose
which streaming service and category to listen to.
2) Started up OK, chose one streaming service and station (played fine),
then chose another music category and froze (had to kill -9 it
Seems to be related to https://github.com/systemd/systemd/issues/18677
$ journalctl --unit systemd-rfkill.service -f
-- Journal begins at Sat 2021-04-03 21:08:41 CEST. --
Apr 04 19:18:24 localhost-laptop systemd[1]: Starting Load/Save RF Kill Switch
Status...
Apr 04 19:18:24 localhost-laptop
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921696
Title:
Refer https://gitlab.gnome.org/GNOME/glib/-/issues/1298 as well
** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1884
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1884
** Also affects: rhythmbox via
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1884
Importance:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rhythmbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922267
Title:
Karl would be happy to see you helping ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870813
Title:
Scilab does not start on bionic and focal
To manage notifications about this bug go to:
Public bug reported:
-DESCRIPTION:
I installed and set the OpenVPN server according to the
guide:https://www.cyberciti.biz/faq/howto-setup-openvpn-server-on-ubuntu-linux-14-04-or-16-04-lts/.
However, after stopping all open-VPN services the ssh service is unable to
respond (ssh worked
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 Ubuntu
Bugs, 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work
Still broken on 18.04 LTS and 20.04 LTS. LTS, Karl!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870813
Title:
Scilab does not start on bionic and focal
To manage notifications about this bug go
On 2021-04-02 20:05, Quentin PAGÈS wrote:
> Translated right now here:
> https://l10n.gnome.org/vertimus/desktop-icons/master/po/oc/
I suspect that's for the old desktop-icon project. I don't see the new
"ding" project yet at l10n.gnome.org. Sorry if I mislead you at Ask
Ubuntu.
I'd like to talk
@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.
Exception during installation:
Apr 4 16:34:35 ubuntu plugininstall.py: Traceback (most recent call last):
Apr 4 16:34:35 ubuntu plugininstall.py: File
"/usr/share/ubiquity/plugininstall.py", line 1863, in
Apr 4 16:34:35 ubuntu plugininstall.py: install.run()
Apr 4 16:34:35 ubuntu
Exception during installation:
Apr 4 16:34:35 ubuntu plugininstall.py: Traceback (most recent call last):
Apr 4 16:34:35 ubuntu plugininstall.py: File
"/usr/share/ubiquity/plugininstall.py", line 1863, in
Apr 4 16:34:35 ubuntu plugininstall.py: install.run()
Apr 4 16:34:35 ubuntu
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: casper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
@mohamed
Did you try it? It shouldn't matter where you click.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
To manage
I have also experienced this issue on my Ubuntu 20.04 Installation, and
the only method to resolve is to restart the computer. The method stated
by dmitry does not work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is
@mohamed-badaoui
It works with clicks. The event is BTN_LEFT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
To manage
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922506
Title:
No video during boot process with kernel
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
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
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 Ubuntu
Bugs, which is subscribed
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
I'm going to make a second try with the last Mohamed version :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
To manage
@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
@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
Public bug reported:
~$ bouncy
pygame 1.9.6
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
File "game.py", line 18, in
from map import *
File "/usr/share/games/bouncy/map.py", line 7, in
import euclid, collide, objects,
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS
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
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
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
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
Public bug reported:
See log
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS
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 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
Hi Brian,
I don't think its down to a lack of space - I still have 40GB of storage free
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074746
Title:
package initramfs-tools 0.99ubuntu13
@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 Ubuntu
Bugs, which is
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fonts-noto (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916319
Title:
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 :
Is this still Bug #1820859 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922290
Title:
nautilus crashed with SIGSEGV in update_dbus_opened_locations()
To manage notifications about this bug go
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.
Yes Thanks Mohamed... I've just find it by myself 2 minutes ago !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
To manage
Public bug reported:
To replicate, you must successfully complete a puzzle. When complete,
in bionic version (and as expected) it tells you you're done and offers
to save your score in top 10.In focal version, nothing happens when
you succesfully complete puzzle. Timer doesnt stop, doesn't
For verification I downloaded ubuntu-21.04-beta-desktop-amd64.iso
(Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)) started it in
VirtualBox ("Try Ubuntu") and also experience a crash for the "nautilus
--version" command, see attachment.
** Attachment added: "Screenshot showing the crash"
@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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS
This https://askubuntu.com/a/576342/642027 made me check if I have the
latest BIOS for my motherboard and it turns out I didn't.
I've upgraded my BIOS and the problem with the disk disappeared. Now
suspend+wakeup works as expected.
This issue can be closed now.
--
You received this bug
1 - 100 of 177 matches
Mail list logo
