[Bug 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
** Changed in: network-manager (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] Re: Netplan generates the wrong YAML value when setting activation-mode=off
** Description changed:
- When setting activation-mode=off, netplan generates the incorrect value
- in the YAML file (activation-mode: false), causing it to fail due to
- incorrect syntax.
+ When setting activation-mode=off on Ubuntu 20.04/Ubuntu Core 20, netplan
+ generates the incorrect value in the YAML file (activation-mode: false),
+ causing it to fail due to incorrect syntax.
$ sudo netplan set ethernets.eth0.activation-mode=off
Traceback (most recent call last):
- File "/usr/sbin/netplan", line 23, in
- netplan.main()
- File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
- self.run_command()
- File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
- self.func()
- File "/usr/share/netplan/netplan/cli/commands/set.py", line 55, in run
- self.run_command()
- File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
- self.func()
- File "/usr/share/netplan/netplan/cli/commands/set.py", line 126, in
command_set
- self.write_file(subtree, hint + '.yaml', self.root_dir)
- File "/usr/share/netplan/netplan/cli/commands/set.py", line 193, in
write_file
- libnetplan.netplan_parse(tmpp)
- File "/usr/share/netplan/netplan/libnetplan.py", line 64, in netplan_parse
- raise Exception(err.contents.message.decode('utf-8'))
+ File "/usr/sbin/netplan", line 23, in
+ netplan.main()
+ File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
+ self.run_command()
+ File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
+ self.func()
+ File "/usr/share/netplan/netplan/cli/commands/set.py", line 55, in run
+ self.run_command()
+ File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
+ self.func()
+ File "/usr/share/netplan/netplan/cli/commands/set.py", line 126, in
command_set
+ self.write_file(subtree, hint + '.yaml', self.root_dir)
+ File "/usr/share/netplan/netplan/cli/commands/set.py", line 193, in
write_file
+ libnetplan.netplan_parse(tmpp)
+ File "/usr/share/netplan/netplan/libnetplan.py", line 64, in netplan_parse
+ raise Exception(err.contents.message.decode('utf-8'))
Exception: /tmp/netplan-set_o73ewgp4/etc/netplan/50-cloud-init.yaml:4:24:
Error in network definition: Value of 'activation-mode' needs to be 'manual' or
'off'
- activation-mode: false
-^
+ activation-mode: false
+ ^
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975678
Title:
Netplan generates the wrong YAML value when setting activation-
mode=off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975678] [NEW] Netplan generates the wrong YAML value when setting activation-mode=off
Public bug reported:
When setting activation-mode=off on Ubuntu 20.04/Ubuntu Core 20, netplan
generates the incorrect value in the YAML file (activation-mode: false),
causing it to fail due to incorrect syntax.
$ sudo netplan set ethernets.eth0.activation-mode=off
Traceback (most recent call last):
File "/usr/sbin/netplan", line 23, in
netplan.main()
File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
self.func()
File "/usr/share/netplan/netplan/cli/commands/set.py", line 55, in run
self.run_command()
File "/usr/share/netplan/netplan/cli/utils.py", line 247, in run_command
self.func()
File "/usr/share/netplan/netplan/cli/commands/set.py", line 126, in
command_set
self.write_file(subtree, hint + '.yaml', self.root_dir)
File "/usr/share/netplan/netplan/cli/commands/set.py", line 193, in write_file
libnetplan.netplan_parse(tmpp)
File "/usr/share/netplan/netplan/libnetplan.py", line 64, in netplan_parse
raise Exception(err.contents.message.decode('utf-8'))
Exception: /tmp/netplan-set_o73ewgp4/etc/netplan/50-cloud-init.yaml:4:24: Error
in network definition: Value of 'activation-mode' needs to be 'manual' or 'off'
activation-mode: false
^
** Affects: netplan.io (Ubuntu)
Importance: Medium
Status: Triaged
** Affects: netplan.io (Ubuntu Focal)
Importance: Medium
Status: Triaged
** Affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: netplan.io (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: netplan.io (Ubuntu Kinetic)
Importance: Medium
Status: Triaged
** Tags: rls-ff-incoming rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975678
Title:
Netplan generates the wrong YAML value when setting activation-
mode=off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975678/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
Hi @seb128, Sorry I haven't yet had the chance to test it with GNOME, but I can confirm that it works if I manually add the connection with nmcli, without adding any particular arguments: nmcli c add type wifi ssid "" It does seem to indeed be an issue with plasma-nm. Cheers, Isaac -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
This seems to be related to OWE (https://en.wikipedia.org/wiki/Opportunistic_Wireless_Encryption). If I disable this in the router, then I can connect without any issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
I've attached the journalctl output. I'm running Kubuntu with plasma-nm 5.24.2-0ubuntu1. I haven't provided a certificate or any authentication details, and the security is set to none in the settings. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+attachment/5567059/+files/log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964100] [NEW] Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
Public bug reported: I'm trying to connect to an open (i.e. no ecryption) WLAN with network- manager 1.36.0-1ubuntu2 on 22.04 but it's failing with the following error message (after selecting the network from the network-manager applet prompt): Mär 08 10:50:04 Isaac-Laptop NetworkManager[31754]: [1646733004.4425] audit: op="connection-add-activate" pid=12122 uid=1000 result="fail" reason="802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it" I haven't changed any of the default settings for network-manager and this network worked on 20.04. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959477] Re: USB dies, GUI hangs after plugging in Brother DS-740D scanner
This seems to be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849 The dmesg output is the same as mine when the host controller stops working: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/comments/13 Are you using the 5.13 HWE kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959477 Title: USB dies, GUI hangs after plugging in Brother DS-740D scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
This problem seems to occur very randomly for me on 20.04 with the 5.13 HWE kernel (5.13.0-27-generic). Here's the relevant dmesg from after the problem occurs: [1.751416] wacom 0003:056A:00EC.0002: hidraw0: USB HID v1.10 Mouse [Tablet ISD-V4] on usb-:00:1d.0-1.8/input0 [6.738809] usb 3-3: device descriptor read/8, error -110 [6.846682] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [ 12.114819] usb 3-3: device descriptor read/8, error -110 [ 12.358687] usb 2-4: new full-speed USB device number 3 using xhci_hcd [ 12.508071] usb 2-4: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [ 12.508086] usb 2-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 12.598690] usb 2-3.2: new high-speed USB device number 4 using xhci_hcd [ 12.711168] usb 2-3.2: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.00 [ 12.711184] usb 2-3.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 12.711190] usb 2-3.2: Product: USB 2.0 Hub [MTT] [ 12.712162] hub 2-3.2:1.0: USB hub found [ 12.712243] hub 2-3.2:1.0: 4 ports detected [ 23.002688] xhci_hcd :00:14.0: Abort failed to stop command ring: -110 [ 23.002707] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [ 23.002744] xhci_hcd :00:14.0: HC died; cleaning up [ 23.002767] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 23.002771] clocksource: 'acpi_pm' wd_now: af831a wd_last: a565c0 mask: ff [ 23.002775] clocksource: 'tsc' cs_now: 10bdde5e61 cs_last: e237c090a mask: [ 23.002778] tsc: Marking TSC unstable due to clocksource watchdog [ 23.002791] xhci_hcd :00:14.0: Timeout while waiting for setup device command [ 23.002798] xhci_hcd :00:14.0: Error while assigning device slot ID [ 23.002801] xhci_hcd :00:14.0: Max number of devices this xHCI host supports is 32. [ 23.002805] usb 2-3.2-port1: couldn't allocate usb_device [ 23.003022] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 23.003024] sched_clock: Marking unstable (23002093033, 928871)<-(23061485899, -58464196) [ 23.003286] clocksource: Checking clocksource tsc synchronization from CPU 2. [ 23.003348] clocksource: Switched to clocksource acpi_pm [ 23.418688] usb 3-3: device not accepting address 3, error -108 [ 23.418792] usb usb3-port3: attempt power cycle [ 23.418799] usb usb3-port3: failed to disable port power [ 23.418804] usb usb3-port3: couldn't allocate usb_device [ 23.418855] usb usb2-port5: couldn't allocate usb_device [ 23.418902] usb 2-3: USB disconnect, device number 2 [ 23.418909] usb 2-3.2: USB disconnect, device number 4 [ 23.419931] usb 2-4: USB disconnect, device number 3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878920] Re: Default KDE browser cannot be changed, "Apply" button is disabled
I can confirm what @anatoly.borodin reported is still the case: when the file BrowserApplication is set to does not exist the setting cannot be changed. Removing the line allowed me to set the application again in the system settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878920 Title: Default KDE browser cannot be changed, "Apply" button is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1878920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902038] [NEW] GNU Radio .xml block files not compatible with GNU Radio 3.8 on Ubuntu 20.04
Public bug reported: This packages installs .xml files into the /usr/share/gnuradio/grc/blocks directory, which are not compatible with GNU Radio 3.8 (the version installed on Ubuntu 20.04). GNU Radio 3.8 requires the new .yml block files, which are available in the upgrade-3.8 branch from the gr-iio upstream repository. ** Affects: gr-iio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902038 Title: GNU Radio .xml block files not compatible with GNU Radio 3.8 on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gr-iio/+bug/1902038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
