Sorry, it was of course 24.04 I were testing. 24.04 beta and the preview
image was also of 24.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875062
Title:
[20.04] Keyboard layout changes during
I've just tested this, and can confirm that there is a bug regarding
keyboard layout in 22.04 beta. As this time the error also appears when
you select the keyboard initially it could a new error.
I also have a preview image of 22.04 dated mars 27th that does not have
the error, even after updated
The ascii flow didn't turn out well. Attaching a PNG that hopefully is
better.
** Attachment added: "3 ways of selecting the language"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+attachment/5561938/+files/Selection%20language%20flow.drawio.png
--
You received this bug n
I've done some more testing on the daily images from today and
yesterday. In one sequence I'm able to get correct keyboard throughout
the installation. I've tried to illustrate it with this ASCII flow-chart
Welcome --(NOR)-+
||
(ENG) TRY? --- YES --+
||
The installation process is at the point where I'm creating user, that
is entering username and password. Noticed that typing Norwegian
characters in name field produces unwanted result.
** Attachment added: "syslog while installing"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875
Hi I just tried install of jammy-desktop-amd64.iso (download yesterday) and ran
into the keybord issue straight away. So I can provide some info:
'locale'
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-
I ran into this today. My system has packagekit 1.2.2-2ubuntu3, so it
does not look like it is related to bug 1943189.
Since this computer currently is used for testing, I'm in no hurry to
install the NVIDIA drivers so I can do some further testing, if needed.
--
You received this bug notificati
I have just tested 20.10 and 20.04.02.
For 20.10 it's OK
For 20.04.02 the bug is still present.
These tests were done on both VMware 16.1 and VirtualBox 6.1 both of
those on same Ubuntu 20.04.02 host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I've conducted a test for some ISO's that I've got:
* Groovy from 8th Oct 2020
* 20.04.01
* 20.10
* Hirsute from 17th Jan 2021
The last three were downloaded 17th Jan.
All versions had correct keyboard layout where one could test the keyboard.
Likewise all installs had correct layout after insta
I've checked with Norwegian keyboard and settings as I originally did.
And I did not experience the problem described earlier.
I've tested both UTF-8 characters and keyboard layout.
So this appears to be solved.
Good woork!
/dag
--
You received this bug notification because you are a member o
I've tried groovy-desktop-amd64 downloaded yesterday (July 3rd).
Attempt 1
---
- Did you boot under BIOS or UEFI?
BIOS
- If BIOS, did you select the keyboard from the bootloader (purple screen)?
Not sure what screen this should b
I would also need an ISO to start with.
Den 25.06.2020 18:55, skrev Gunnar Hjalmarsson:
> On 2020-06-25 18:24, Brian Murray wrote:
>> There is an updated version of ubiquity (20.04.15.1) in the
>> -proposed pocket which may address this issue. Could you please test
>> it?
> How would you go about
** Summary changed:
- Incorrect keyboard layout for selecting username and password during install
of 20.04
+ [20.04] Keyboard layout not enabled immediately during installation when
typing username/password
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
During a fresh install of Ubuntu 20.04, selecting Norwegian keyboard is
provided and keys are responding correctly at that stage. But later when
entering user information the keyboard setting is wrong.
It looks like it have fallen back to English keyboard-layout.
I failed to
Public bug reported:
Did a first time upgrade of an 17.10.1 installation on a PC with encrypted
disk, and I did
sudo apt update
sudo apt upgrade
PC was rebooted after install.
I had problems connecting to internett during install and the
instructions to enter EFI I was not able to complete.
Ad
Complains about changes in /etc/mysql/mysql.conf.d/mysqld.cnf
Upgrading from 17.04 to 17.10 gave this error. Error also present in during the
upgrade process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I finally got to check the status of this on Ubuntu 17.04. Same computer but
upgraded ubuntu.
Print from LibreOffice gave this in log (dmesg):
[491184.232027] audit: type=1400 audit(1496903835.766:41): apparmor="DENIED"
operation="capable" profile="/usr/sbin/cupsd" pid=21237 comm="lpd"
capabilit
Meanwhile I've upgraded the computer to 17.04, but I have not checked
the presence of the bug after the upgrade. I will check tomorrow when I
get access to the computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
This was raised from the C308 printer, which I just had installed. The
C650 was the old printer that we got, and I _think_ printing was working
on that machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
Printing is enabled when doing sudo aa-complain cupsd
Here is an extract of /var/log/syslog:
Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/lib/cups
Just tested a new upstream kernel:
# uname -a
Linux dag-XPS-13 3.17.0-031700rc5-generic #201409142135 SMP Mon Sep 15 01:36:30
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Bug still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just tested a new upstream kernel:
> uname -a
>Linux dag-XPS-13 3.17.0-031700rc3-generic #201408312235 SMP Mon Sep 1 02:36:10
>UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Bug still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just tested new upstream kernel:
>uname -a
>Linux dag-XPS-13 3.16.1-031601-generic #201408140014 SMP Thu Aug 14 04:15:26
>UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Bug still exists.
3.5.0-40 still works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Just tested with:
dag@dag-XPS-13:~$ uname -a
Linux dag-XPS-13 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:36:11 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
dag@dag-XPS-13:~$
Bug still exists.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete
Public bug reported:
At one point suspending the computer stopped working. It just goes back
on right away. Monitor goes black a short while but comes back on after
2-3 sec. I'm running Ubuntu 14.04 and I've tested some earlier kernels
that I've got. The latetes that I have where suspend works is
25 matches
Mail list logo
