[Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
For 5.8, we will backport the real solution from linux-next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904827] [NEW] Can't mark 'ubuntu-desktop' for upgrade (E:Ошибка: pkgProblemResolver::Resolve привёл к появлению сломанных пакетов. Это может быть вызвано зафиксированными пакетами
Public bug reported: Can't mark 'ubuntu-desktop' for upgrade (E:Ошибка: pkgProblemResolver::Resolve привёл к появлению сломанных пакетов. Это может быть вызвано зафиксированными пакетами ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18 Uname: Linux 4.15.0-125-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 10:59:19 2020 InstallationDate: Installed on 2018-12-05 (714 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-19 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904827 Title: Can't mark 'ubuntu-desktop' for upgrade (E:Ошибка: pkgProblemResolver::Resolve привёл к появлению сломанных пакетов. Это может быть вызвано зафиксированными пакетами To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1904827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904823] Missing required logs.
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 1904823 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904823 Title: device-mapper: btree spine: node_check failed: csum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904819] Re: gnome-shell uses 100% cpu when screen blanked
Thanks for the bug report. Your system log is certainly full of a lot of messages so it's easy to believe you might have high CPU too. But I can't tell what part of gnome-shell they came from. Since so many bugs are caused by extensions, and nobody else is reporting this issue, the first thing we need to check is all: 'alternate-...@gnome-shell-extensions.gcampax.github.com', 'dash-to- d...@micxgx.gmail.com', 'screenshot-window-sizer@gnome-shell- extensions.gcampax.github.com', 'gsconn...@andyholmes.github.io' Please uninstall or just disable all of them in the Extensions app, then log out and log in again. Does the problem still occur? If so then it might be this: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3098 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3098 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3098 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: performance ** Tags added: regression-release ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3098 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904819 Title: gnome-shell uses 100% cpu when screen blanked To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1904819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713775] Re: [USB-Audio - Logitech BRIO, recording] fails on suspend/resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (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/1713775 Title: [USB-Audio - Logitech BRIO, recording] fails on suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1713775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904823] [NEW] device-mapper: btree spine: node_check failed: csum
Public bug reported: While I have found previous reports of this check failing, they are all resolved years ago. So I guess this is something for upstream. device-mapper: btree spine: node_check failed: csum 544691913 != wanted 1983069109 [ cut here ] kernel BUG at drivers/md/persistent-data/dm-btree-spine.c:34! invalid opcode: [#1] SMP PTI CPU: 42 PID: 2175930 Comm: kworker/42:1 Not tainted 5.4.0-51-generic #56-Ubuntu Hardware name: Quanta Cloud Technology Inc. QuantaGrid D52B-1U/S5B-MB (LBG-1G), BIOS 3B17.Q302 08/12/2020 Workqueue: dm_bufio_cache work_fn [dm_bufio] RIP: 0010:node_prepare_for_write+0x61/0x70 [dm_persistent_data] Code: 01 00 48 89 43 08 e8 1e 9f ff ff ba 00 10 00 00 4c 89 e6 4c 89 f7 89 03 e8 1c fe ff ff 85 c0 75 09 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 RSP: 0018:98b9f539fd08 EFLAGS: 00010286 RAX: ffac RBX: 8bce38b4f000 RCX: RDX: RSI: 8bc580e978c8 RDI: 8bc580e978c8 RBP: 98b9f539fd28 R08: 8bc580e978c8 R09: 00c80001 R10: 0095 R11: 6b300095 R12: 8bc451e18d20 R13: 1000 R14: c0416550 R15: 8bc451e18d20 FS: () GS:8bc580e8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f1204062010 CR3: 007ef02da004 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: ? le64_inc+0x20/0x20 [dm_persistent_data] dm_block_manager_write_callback+0x42/0x50 [dm_persistent_data] submit_io+0x1ad/0x230 [dm_bufio] __flush_write_list+0x81/0xc0 [dm_bufio] work_fn+0x1c8/0x1f0 [dm_bufio] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 Modules linked in: dm_snapshot vhost_net vhost tap ip6table_raw tcp_diag udp_diag inet_diag overlay veth dummy bridge nf_tables netconsole sch_ingress vxlan ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout openvswitch nsh nf_conncount ip6table_filter ip6_tables xt_CT iptable_raw iptable_mangle intel_rapl_msr intel_rapl_common xt_set xt_tcpudp isst_if_common skx_edac xt_state nfit xt_conntrack x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul ghash_clmulni_intel iptable_filter aesni_intel ipmi_ssif bpfilter kvm_intel crypto_simd cryptd glue_helper rapl kvm intel_cstate drm_vram_helper ttm drm_kms_helper i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt ioatdma ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid ip_set_hash_net ip_set nfnetlink sch_fq_codel nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tcp_htcp 8021q garp mrp stp llc bonding drm ip_tables x_tables autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c raid10 raid1 crc32_pclmul ixgbe xfrm_algo dca mdio nvme nvme_core ahci i2c_i801 lpc_ich libahci wmi ---[ end trace 7e896cfa4fcf1285 ]--- RIP: 0010:node_prepare_for_write+0x61/0x70 [dm_persistent_data] Code: 01 00 48 89 43 08 e8 1e 9f ff ff ba 00 10 00 00 4c 89 e6 4c 89 f7 89 03 e8 1c fe ff ff 85 c0 75 09 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 RSP: 0018:98b9f539fd08 EFLAGS: 00010286 RAX: ffac RBX: 8bce38b4f000 RCX: RDX: RSI: 8bc580e978c8 RDI: 8bc580e978c8 RBP: 98b9f539fd28 R08: 8bc580e978c8 R09: 00c80001 R10: 0095 R11: 6b300095 R12: 8bc451e18d20 R13: 1000 R14: c0416550 R15: 8bc451e18d20 FS: () GS:8bc580e8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f1204062010 CR3: 007ef02da004 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 [ cut here ] ** Affects: linux (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/1904823 Title: device-mapper: btree spine: node_check failed: csum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903524] Re: System state with 'space' in name prevent update-grub to create menu entries in grub.cfg
** Description changed:
+ [Impact]
+ Some characters are not supported in snapshot names by either zfs, grub or
init. As a consequence a system cannot be reverted to a snapshot created with
such characters, and the system fails to boot with various errors.
+
+ This patch forces the name of snapshot created with zsysctl to the
+ following characters: a-z, A-Z, 0-9, _, -, .
+
+ Space is not unsupported by ZFS and would be perfectly correct to create
+ a snapshot with a space in it. However it creates issues in GRUB when it
+ generates the boot command line due to the way it quotes the argument
+ root= by adding a double before root which is then wrongly interpreted
+ by init. It also creates issues in init which uses for loop to read the
+ command line and splits it on spaces, and in the middle of the root
+ argument while it should be a single argument. Fixing space handling in
+ GRUB and init is really intrusive and beyond the scope of this bug so we
+ decided to prevent spaces too in snapshot names.
+
[Test Case]
1. Boot a system with zsys without the patch
* Positive test *
2. Create a system snapshot with a valid character. Valid characters are
"a-z", "A-Z", "0-9", "_", "-", "." Name must not start by . or -
=> Verify that the snapshot is created successfully
3. Reboot to the grub menu and in the history menu select the snapshot you
just created.
=> Verify that the system boot to the reverted state of the snapshot
* Negative test 1*
4. Create a snapshot with an invalid character.
=> Verify that the creation fails with an error message listing the invalid
character/s
* Negative test 2*
5. Create a snapshot that starts with '-'
=> Verify that the snapshot cannot be created.
* Negative test 3*
5. Create a snapshot names '.' or '..'
=> Verify that the snapshot cannot be created.
+
+ [Regression potential]
+ If filtering is not done properly the patch can either:
+ 1. prevent supported characters to be used in snapshot names but snapshots
can still be created and names generated by auto snapshots are supported.
+ 2. allow unsupported characters to be used in snapshot names. In this case we
are back to current situation.
+
+ The patch is covered by several tests in the included test suite.
+
[Original Description]
From https://github.com/ubuntu/zsys/issues/169
Describe the bug
I did create few days ago a System state with a 'space' in the name :
"pool/ROOT/ubuntu_u7dn3s@Stable Plex"
server:~$ zsysctl show
Name: rpool/ROOT/ubuntu_u7dn3s
ZSys: true
Last Used: current
History:
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_ceqh6a
Created on: 2020-10-16 06:49:59
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_ahzb7l
Created on: 2020-10-15 06:40:13
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_a00j2k
Created on: 2020-10-08 06:46:34
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_b7t6lj
Created on: 2020-10-07 06:20:00
- Name: rpool/ROOT/ubuntu_u7dn3s@Stable Plex
Created on: 2020-10-03 19:18:18
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_a81mbp
Created on: 2020-10-03 17:58:19
(truncated)...
I found myself in the impossibility to boot the server few days after as the
Grub menu had only the UEFI entry in it. No more entries for current kernel or
zsys history.
server:~$ cat /boot/grub/grub.cfg
...(truncated)
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
(truncated)...
After chrooting into the server, I tried to rebuild the menu with update-grub
and got a weird error message on ignoring datasets:
server:~$ update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_25bi0j
Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_25bi0j
Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_25bi0j
Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_25bi0j
...(truncated)...
Found initrd image: initrd.img-5.4.0-42-generic in
rpool/ROOT/ubuntu_u7dn3s@autozsys_a81mbp
Warning: Failed to find a valid directory 'etc' for dataset
'rpool/ROOT/ubuntu_u7dn3s@Stable'. Ignoring
Warning: Ignoring rpool/ROOT/ubuntu_u7dn3s@Stable
filesystem 'Plex' cannot be mounted, unable to open the dataset
Adding boot
[Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
I don't know. This is none Realtek AMP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi @E (mantsje), Just try one of the patches mentioned here (e.g. #179). My touchpad also was making click events when moving fingers on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault
r10-4054 failed with during RTL pass: reload /root/qemu-5.0/fpu/softfloat.c: In function ‘sf_canonicalize’: /root/qemu-5.0/fpu/softfloat.c:670:1: internal compiler error: Segmentation fault 670 | } | ^ 0x4b7443 crash_signal ../../gcc/gcc/toplev.c:326 0x66b7c7 thumb2_legitimate_address_p ../../gcc/gcc/config/arm/arm.c:8242 0x66bc31 arm_legitimate_address_p(machine_mode, rtx_def*, bool) ../../gcc/gcc/config/arm/arm.c:8657 0x458667 memory_address_addr_space_p(machine_mode, rtx_def*, unsigned char) ../../gcc/gcc/recog.c:1340 0x85b013 nonimmediate_soft_df_operand_1 ../../gcc/gcc/config/arm/predicates.md:514 0x85b013 nonimmediate_soft_df_operand(rtx_def*, machine_mode) ../../gcc/gcc/config/arm/predicates.md:530 0x85b013 nonimmediate_soft_df_operand(rtx_def*, machine_mode) ../../gcc/gcc/config/arm/predicates.md:518 I'm unsure how to deal with this. It is an ICE, and it happened throughout the RTL stage as before. But the signature seems to be a different one. It could be "bad" with the actual issue we look for hidden behind this. It could be "good" as well with the actual issue we look fixed but hidden behind this. Or it could be "bad" as in, this is the same issue but with a different signature. For the time being I'll handle it as bad, with some luck we get our old trace back further down the bisect. But @Doko please have a look at the trace above (maybe it is a known one) and advise. Starting on r10-2027 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/groovy/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904819] [NEW] gnome-shell uses 100% cpu when screen blanked
Public bug reported: Recently I've noticed gnome-shell eating 100% of the CPU when the screen is blanked due to the session going idle. This seems to have started happening sometime after upgrading to groovy back when it was still in beta. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:04:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-13 (828 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RebootRequiredPkgs: linux-image-5.8.0-26-generic linux-base linux-image-5.8.0-28-generic linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-24 (55 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904819 Title: gnome-shell uses 100% cpu when screen blanked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
Is there a way to push fix into groovy kernel branch myself? This bug makes system unbootable on plenty of CPUs with eDRAM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901627] Re: Update product naming: Simplify UA Infrastructure ESM to UA Infra: ESM
** Merge proposal linked: https://code.launchpad.net/~chad.smith/ubuntu/+source/update-notifier/+git/update-notifier/+merge/394164 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901627 Title: Update product naming: Simplify UA Infrastructure ESM to UA Infra: ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1901627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904817] [NEW] Unable to upgrade to 20.04
Public bug reported: Not able to upgrade from 18.04 to 20.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 11:11:21 2020 InstallationDate: Installed on 2019-09-13 (432 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-19 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904817 Title: Unable to upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1904817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901627] Re: Update product naming: Simplify UA Infrastructure ESM to UA Infra: ESM
** Also affects: update-notifier (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: update-notifier (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: update-notifier (Ubuntu Xenial) 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/1901627 Title: Update product naming: Simplify UA Infrastructure ESM to UA Infra: ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1901627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904816] [NEW] ACPI BIOS Error on Startup Ubuntu 20.10
Public bug reported: Every time I reboot my Ubuntu 20.10, I get ACPI BIOS Error message on the left side of the screen. I was not getting this error message on 20.04 version. I was wondering if there is a solution or script to run? Here is the code: [0.157769] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.15] fbcon: Taking over console [0.157781] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.157784] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.157785] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.157788] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.157789] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.157790] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.157792] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.157794] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.157795] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.157797] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.157798] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.157826] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.157829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.157830] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.157831] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.157833] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.157835] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.159644] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.159648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.159649] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.159650] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.159653] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.159654] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.161514] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.161517] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.161519] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.161520] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.161522] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.161524] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.163291] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.163294] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.163296] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.163297] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.163300] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.163301] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.165159] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.165163] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.165164] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.165165] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._PLD], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.165168] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.165169] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.167027] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20200717/dswload2-326) [0.167030] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200717/psobject-220) [0.167032] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.167033] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._PLD],
[Bug 1904815] [NEW] Failed install on Ubuntu 20.04.1 Focal Fossa
Public bug reported: DKMS make.log for lttng-modules-2.12.2 for kernel 5.4.0-54-generic (x86_64) Wed 18 Nov 2020 10:33:48 PM CST make: Entering directory '/usr/src/linux-headers-5.4.0-54-generic' find: ‘/var/lib/dkms/lttng-modules/2.12.2/build/extra_version/patches/’: No such file or directory find: ‘/var/lib/dkms/lttng-modules/2.12.2/build/lib/../extra_version/patches/’: No such file or directory CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/ringbuffer/ring_buffer_backend.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/ringbuffer/ring_buffer_frontend.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/ringbuffer/ring_buffer_iterator.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/ringbuffer/ring_buffer_vfs.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/ringbuffer/ring_buffer_splice.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/ringbuffer/ring_buffer_mmap.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/prio_heap/lttng_prio_heap.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/../wrapper/splice.o LD [M] /var/lib/dkms/lttng-modules/2.12.2/build/lib/lttng-lib-ring-buffer.o find: ‘/var/lib/dkms/lttng-modules/2.12.2/build/probes/../extra_version/patches/’: No such file or directory /var/lib/dkms/lttng-modules/2.12.2/build/probes/Kbuild:62: File ./arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.12.2/build/probes/Kbuild:166: Files ./fs/btrfs/*.h not found. Probe "btrfs" is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.12.2/build/probes/Kbuild:177: Files ./fs/ext4/*.h not found. Probe "ext4" is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.12.2/build/probes/Kbuild:208: File ./drivers/base/regmap/trace.h not found. Probe "regmap" is disabled. Need Linux 4.1+ kernel source tree to enable it. CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-sched.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-irq.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-timer.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-kmem.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-module.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-power.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-statedump.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-9p.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-i2c.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-kvm.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-x86-irq-vectors.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-x86-exceptions.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-signal.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-block.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-napi.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-skb.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-net.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-sock.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-udp.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-asoc.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-gpio.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-jbd2.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-regulator.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-scsi.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-vmscan.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-compaction.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-printk.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-random.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-rcu.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-sunrpc.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-v4l2.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-workqueue.o CC [M] /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-writeback.o In file included from /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/define_trace.h:87, from /var/lib/dkms/lttng-modules/2.12.2/build/probes/../instrumentation/events/lttng-module/writeback.h:755, from /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-writeback.c:38: /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6:
[Bug 1904807] Re: Raspberry Pi libs check fails kernel version
The attachment "Fix libs check for kernel version" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904807 Title: Raspberry Pi libs check fails kernel version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/1904807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895370] Re: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (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/1895370 Title: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904813] [NEW] r8168 keeps dropping connection
Public bug reported: I swapped from the r8169 driver to r8168 for stability, but as time has passed stability has suffered here too. Now it's unreliable. [14.968070] r8168: enp2s0: link up [14.968427] br0: port 1(enp2s0) entered blocking state [14.968433] br0: port 1(enp2s0) entered forwarding state [17.991834] NFSD: client 192.168.0.15 testing state ID with incorrect client ID [200087.242816] rpc-srv/tcp: nfsd: sent only 89460 when sending 131180 bytes - shutting down socket [200206.806526] br0: port 1(enp2s0) entered disabled state [200211.034700] r8168: enp2s0: link up [200211.035035] br0: port 1(enp2s0) entered blocking state [200211.035038] br0: port 1(enp2s0) entered forwarding state [200212.081447] NFSD: client 192.168.0.15 testing state ID with incorrect client ID [200212.082268] NFSD: client 192.168.0.15 testing state ID with incorrect client ID [200458.713617] br0: port 1(enp2s0) entered disabled state And so on. Occurs when the network interface is busy with multiple connections. With a single busy connection it seems to work fine. Multiple connections work fine when things are not busy. [176460.408437] [ cut here ] [176460.408480] NETDEV WATCHDOG: enp2s0 (r8168): transmit queue 0 timed out [176460.408546] WARNING: CPU: 1 PID: 0 at /build/linux-hwe-5.4-P3jn7z/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 [176460.408549] Modules linked in: tcp_diag inet_diag rpcsec_gss_krb5 cpuid twofish_generic twofish_x86_64 twofish_common serpent_sse2_x86_64 serpent_generic blowfish_generic blowfish_common cast5_generic cast_common des_generic libdes algif_skcipher camellia_generic crypto_simd cryptd glue_helper xcbc md4 algif_hash af_alg xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo xt_CHECKSUM iptable_mangle xt_MASQUERADE iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_filter bpfilter bridge stp llc gpio_ich dcdbas intel_powerclamp pcspkr serio_raw lpc_ich mac_hid binfmt_misc sch_fq_codel cmdlinepart slram mtdblock nfsd mtd_blkdevs mtd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c i915 uas video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci usb_storage drm libahci e100 r8168(OE) mii pata_acpi z3fold lz4hc lz4hc_compress [176460.408629] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.4.0-52-generic #57~18.04.1-Ubuntu [176460.408633] Hardware name: Dell Inc. Dell DV051 /0JC474, BIOS A04 04/04/2006 [176460.408638] RIP: 0010:dev_watchdog+0x264/0x270 [176460.408641] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c0 e7 00 01 e8 e0 b6 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 f8 06 23 b7 e8 4c 30 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 [176460.408644] RSP: :b565400ece48 EFLAGS: 00010282 [176460.408647] RAX: RBX: RCX: [176460.408649] RDX: 88dcbd867740 RSI: 00f6 RDI: 0300 [176460.408651] RBP: b565400ece78 R08: 0374 R09: 0004 [176460.408653] R10: b565400ecc68 R11: 0001 R12: 0001 [176460.408655] R13: 88dc7347 R14: 88dc73470480 R15: 88dc73c0f480 [176460.408658] FS: () GS:88dcbd84() knlGS: [176460.408660] CS: 0010 DS: ES: CR0: 80050033 [176460.408662] CR2: ff60 CR3: 47aae000 CR4: 06e0 [176460.408665] Call Trace: [176460.408668] [176460.408678] ? pfifo_fast_reset+0x110/0x110 [176460.408683] call_timer_fn+0x32/0x130 [176460.408686] run_timer_softirq+0x443/0x480 [176460.408689] ? tick_sched_timer+0x3c/0x80 [176460.408692] ? ktime_get+0x43/0xa0 [176460.408696] ? lapic_next_event+0x20/0x30 [176460.408700] __do_softirq+0xe4/0x2da [176460.408703] irq_exit+0xae/0xb0 [176460.408706] smp_apic_timer_interrupt+0x79/0x130 [176460.408708] apic_timer_interrupt+0xf/0x20 [176460.408710] [176460.408713] RIP: 0010:mwait_idle+0x84/0x1d0 [176460.408715] Code: c0 6b 01 00 48 89 d1 0f 01 c8 48 8b 00 a8 08 0f 85 46 01 00 00 e9 07 00 00 00 0f 00 2d b7 30 53 00 31 c0 48 89 c1 fb 0f 01 c9 <65> 44 8b 25 d4 c9 73 49 0f 1f 44 00 00 eb 07 fb 66 0f 1f 44 00 00 [176460.408717] RSP: :b5654007fe80 EFLAGS: 0246 ORIG_RAX: ff13 [176460.408719] RAX: RBX: 0001 RCX: [176460.408721] RDX: RSI: a07cd6a88d44 RDI: [176460.408722] RBP: b5654007fea0 R08: 0001df80 R09: a07cd816c344 [176460.408723] R10: b5654007fe78 R11: 0001 R12: 0001 [176460.408724] R13: R14: R15: [176460.408730] arch_cpu_idle+0x15/0x20 [176460.408732] default_idle_call+0x23/0x30
[Bug 1899508] Re: alsa/hda/realtek - The front Mic on a HP machine doesn't work
Tried the "5.8.0-30-generic" kernel provided by "linux-generic-hwe-20.04" from -proposed. and confirmed the headset in front panel is working. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899508 Title: alsa/hda/realtek - The front Mic on a HP machine doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1899508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904811] [NEW] package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 18 19:09:53 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-11 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 35: missing argument. SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904811 Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1904811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I discovered a way to consistently trigger this. I don't know if all these steps are necessary, but it works for me consistently this way. Configuration: - Ubuntu MATE 20.10 - caja version 1.24.0 - Evolution version 3.38.1-1 Steps to Reproduce: 1. In Evolution, open the 'Compose Message' window. I have it set by default to 'Plain Text' editing mode, and attachment bar collapsed. 2. Open caja and navigate to the desired file. 3. drag & drop the file in the message body. This should result in the full file path URI being displayed as the message. 4. press `CTRL+Z` (Undo). 5. Now drag the same file again, over the message body, into the (collapsed) attachment bar. 6. Your mouse should now be stuck in DND mode, requiring `pkill caja` to release it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/402892 Title: Mouse cursor gets stuck in "drag and drop" mode To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904777] Re: Xorg randomly crashes under xrdp
Or just look in your system journal for "Assertion". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904777 Title: Xorg randomly crashes under xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1904777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904777] Re: Xorg randomly crashes under xrdp
Looks like an assertion failure so this is probably bug 1861609. Please try installing the debug symbols to see if that clarifies the situation next time it crashes. ** Changed in: xorg-server (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/1904777 Title: Xorg randomly crashes under xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1904777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899152] Re: [intel G33] Resolution limited to 1024x768
It looks like the system can't get the screen resolution information from the monitor over the VGA connection. This might be a connection problem or it might be a kernel bug. Please: 1. Run this command: grep . /sys/class/drm/*/modes > drmmodes.txt and attach the resulting text file here. 2. Try a different VGA cable if you can find one. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Invalid => New ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (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/1899152 Title: [intel G33] Resolution limited to 1024x768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904717] Re: Settings for external keyboard and mouse are not persisted
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1899206, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1899206 Input device settings not applied on hotplug/reconnect/resume in Xorg sessions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904717 Title: Settings for external keyboard and mouse are not persisted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904765] Re: Resolution not set or inappropriate
*** This bug is a duplicate of bug 1899152 *** https://bugs.launchpad.net/bugs/1899152 We ignored bug 1899152 because you closed it :) I have now reopened bug 1899152 for this. ** This bug has been marked a duplicate of bug 1899152 [intel G33] Resolution limited to 1024x768 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904765 Title: Resolution not set or inappropriate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1904765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899802] Re: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander
I have included a test kernel for both focal and groovy. Focal https://people.canonical.com/~mreed/dell/mpt3sas/bug_1899802/focal/ Groovy https://people.canonical.com/~mreed/dell/mpt3sas/bug_1899802/groovy/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899802 Title: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
Thanks. This looks most like the problem you describe. Unfortunately being an issue in LXDM or LXDE means it is no longer supported in 16.04 (since April 2019). Nov 18 19:58:57 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:58:57 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:03 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:03 monolith systemd[1]: Stopped LXDE Display Manager. Nov 18 19:59:03 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:59:03 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:08 monolith systemd[1]: Stopped LXDE Display Manager. Nov 18 19:59:08 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:59:08 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:13 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:13 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:13 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:14 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:14 monolith systemd[1]: Stopped LXDE Display Manager. Nov 18 19:59:14 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:59:14 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:19 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:19 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:19 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. ** Changed in: ubuntu Status: Incomplete => Won't Fix ** Package changed: ubuntu => lxdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904470] Re: Monitor fails to wake after lock when dash-to-panel is loaded
** Summary changed: - 100Hz monitor fails to wake after lock + Monitor fails to wake after lock when dash-to-panel is loaded ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-dash- to-panel (Ubuntu) ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904470 Title: Monitor fails to wake after lock when dash-to-panel is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1904470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing
Please try a newer kernel from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904638 Title: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing
Thanks. Your kernel log mentions the controller in a few messages: nov 17 22:08:49 glados kernel: Bluetooth: hci0: unexpected SMP command 0x06 from 98:7a:14:d9:68:15 nov 17 22:08:49 glados kernel: Bluetooth: hci0: unexpected SMP command 0x07 from 98:7a:14:d9:68:15 nov 17 22:08:49 glados kernel: Bluetooth: hci0: unexpected SMP command 0x08 from 98:7a:14:d9:68:15 nov 17 22:08:49 glados kernel: Bluetooth: hci0: unexpected SMP command 0x09 from 98:7a:14:d9:68:15 nov 17 22:08:49 glados kernel: Bluetooth: hci0: unexpected SMP command 0x0a from 98:7a:14:d9:68:15 nov 17 22:08:50 glados bluetoothd[1522]: src/service.c:service_accept() input-hog profile accept failed for 98:7A:14:D9:68:15 ... nov 17 22:09:14 glados gnome-control-c[6028]: Setting up /org/bluez/hci0/dev_98_7A_14_D9_68_15 failed: Timeout was reached ... nov 17 22:09:22 glados kernel: Bluetooth: hci0: link tx timeout -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904638 Title: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
There is no mechanism to make it come faster. It's already on the way as a proposed groovy update: https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1 You can't get faster than that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904797] Re: geoipupdate fails with 40` HTML error
I have it scheduled to run out of cron every Wednesday, today is the first day it failed. I do not understand much about how this works, it is used by a postfwd script to detect botnet uses of the mail server and force a password change if an account is compromised and used by them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904797 Title: geoipupdate fails with 40` HTML error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoipupdate/+bug/1904797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766775] Re: Notifications do not disappear
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766775 Title: Notifications do not disappear To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903230] Re: Mutter release 3.36.7
The only leak fix in 3.36.7 is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1449 but that one may never be noticeable so may not be the issue you describe. If you experience leaks then remove any extensions you have installed. If the problem keeps happening after that then open a new bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903230 Title: Mutter release 3.36.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904807] [NEW] Raspberry Pi libs check fails kernel version
Public bug reported:
The standard libs check when running on Raspberry Pi (this seems to work on
amd64) fails the kernel version check for two reasons. The first is known
(permissions on the image file), but the second seems to be a difference in the
way the kernel test results are provided.
Specifically, based on my looking at the perl code, I think this is the command
run to collect the information:
strings vmlinuz-5.8.0-1007-raspi | egrep ^5.8.0-1007-raspi\|"^Linux version"
Linux version 5.8.0-1007-raspi (buildd@bos02-arm64-039) (gcc (Ubuntu
10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #10-Ubuntu
SMP PREEMPT Thu Nov 5 17:52:40 UTC 2020 (Ubuntu 5.8.0-1007.10-raspi 5.8.14)
5.8.0-1007-raspi SMP preempt mod_unload aarch64
5.8.0-1007-raspi
5.8.0-1007-raspi
The problem seems to be on the first line, where after the expected version
string, is an extra " (Ubuntu 5.8.0-1007.10-raspi 5.8.14)" text.
Editing the libs file as follows seems to solve the problem for me:
--- libs2020-11-19 02:07:12.716041097 +
+++ libs.local 2020-11-19 02:05:20.625963787 +
@@ -104,7 +104,7 @@
"$newest_kernel_image. Can't check kernel
version!\n\n");
}
} else {
-if ($kernel_image_version =~ /^(Linux version
)?\Q$running_kernel_release\E \(.*\) \Q$running_kernel_version\E$/) {
+if ($kernel_image_version =~ /^(Linux version
)?\Q$running_kernel_release\E \(.*\) \Q$running_kernel_version\E/) {
$bb->color_line('green',
sprintf("Newest kernel is running: %s, version
%s\n\n",
$running_kernel_release,
Alternatively, adding .* before the $ would also resolve this issue. I'm
not sure how to collect and repeat the other version information to
resolve this, nor how this might affect other platforms, so the above
seems to be the simplest solution (to just ignore any extraneous text)
that should work on any platform that it worked on before.
Regards,
Adam
** Affects: hobbit-plugins (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "Fix libs check for kernel version"
https://bugs.launchpad.net/bugs/1904807/+attachment/5435830/+files/libspatch.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904807
Title:
Raspberry Pi libs check fails kernel version
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/1904807/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836188] Re: cpuset_exclusive in controllers from ubuntu_ltp failed on P9
Patch applied upstream \o/ https://github.com/linux-test-project/ltp/commit/6872ad15a836027cfc59c4836d503248d1917a29 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836188 Title: cpuset_exclusive in controllers from ubuntu_ltp failed on P9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904797] Re: geoipupdate fails with 40` HTML error
Hello Robert, Hopefully helpful: "Note that for geoipupdate versions less than 2.5.0, use UserId instead of AccountID and ProductIds instead of EditionIDs." https://dev.maxmind.com/geoip/geoipupdate/ Was this working on a previous version and need to be changed to reflect the new names of parameters in the new version? Thanks ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904797 Title: geoipupdate fails with 40` HTML error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoipupdate/+bug/1904797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904803] Re: During testing the live Lubuntu ISO, the monitor resolutions do not work as expected.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1904803 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904803 Title: During testing the live Lubuntu ISO, the monitor resolutions do not work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1904803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884299] Re: Chromium snap won't run with nfs home drive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (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/1884299 Title: Chromium snap won't run with nfs home drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1884299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832182] Re: systemd unable to detect running apache if invoked via "apache2ctl graceful"
** Changed in: apache2 (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: apache2 (Ubuntu Bionic) Status: Triaged => Fix Committed ** Changed in: apache2 (Ubuntu Focal) Status: Triaged => Fix Committed ** Changed in: apache2 (Ubuntu Groovy) Status: Triaged => Fix Committed ** Changed in: apache2 (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Changed in: apache2 (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: apache2 (Ubuntu Bionic) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: apache2 (Ubuntu Xenial) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904269] Re: Apply full upgrade - fails with no error message
Ran a quick test on the latest Lubuntu iso 18.11.2020 and the updates completed with no errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904269 Title: Apply full upgrade - fails with no error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1904269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904803] Re: During testing the live Lubuntu ISO, the monitor resolutions do not work as expected.
Video can be seen attached. ** Attachment added: "simplescreenrecorder-2020-11-18_16.13.18.mkv" https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1904803/+attachment/5435829/+files/simplescreenrecorder-2020-11-18_16.13.18.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904803 Title: During testing the live Lubuntu ISO, the monitor resolutions do not work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1904803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904803] [NEW] During testing the live Lubuntu ISO, the monitor resolutions do not work as expected.
Public bug reported: Lubuntu Live ISO 21.04 Hirsute 20201118 VirtualBox v. 6.1 Open the preferences > monitor > adjust screen resolution > choose high resolution > click apply At this point, a new window opens. It asks if you want to accept the changes or get rid of them. No matter what you click, a system notification applet (such as the calendar) will open up and be displayed and the mouse clicks do nothing. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lxqt-config 0.15.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Thu Nov 19 01:20:02 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201118) SourcePackage: lxqt-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904803 Title: During testing the live Lubuntu ISO, the monitor resolutions do not work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1904803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904802] [NEW] please provide firmware file for riscv64
Public bug reported: please provide firmware file for riscv64 I'm not sure which package should ship it, or what it should look like, but i want something like this: qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device loader,file=/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf,addr=0x8020 -device virtio-blk-device,drive=vda -drive file=livecd.ubuntu- cpc.img,id=vda -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 such that on riscv64 opensbi loader is available as firmware, with qemu smode uboot.elf. I don't know how to write the appropriate qmeu/firmware/*.json for it. ** Affects: opensbi (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: u-boot (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 ** Also affects: opensbi (Ubuntu) Importance: Undecided Status: New ** Also affects: u-boot (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/1904802 Title: please provide firmware file for riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/1904802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904801] [NEW] kleopatra will not export private certificates instaed exporting the public cert only
Public bug reported: Install kleopatra, Generate public/private key pair Export the private key to file The file will only hold the public key. To export the private key side by side with the public one you'll have to open a commandline and use gpg. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kleopatra 4:19.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-55.61-generic 5.4.73 Uname: Linux 5.4.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 02:05:36 2020 InstallationDate: Installed on 2011-10-19 (3318 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: kleopatra UpgradeStatus: Upgraded to focal on 2019-04-27 (571 days ago) ** Affects: kleopatra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904801 Title: kleopatra will not export private certificates instaed exporting the public cert only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kleopatra/+bug/1904801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904269] Re: Apply full upgrade - fails with no error message
That is correct Walter..initially I only saw this on Lubuntu as I had at that point not tested the other flavors..actually that is the main reason I looked at them as well. After seeing that also on Budgie I expected I would need to refile but was not sure what package would be appropriate. Also not 100% sure this is still the case with Lubuntu as the last 2 days no updates were available after installing the latest ISO's. Will test this further in the A.M. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904269 Title: Apply full upgrade - fails with no error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1904269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904269] Re: Apply full upgrade - fails with no error message
Leó are those comments re: Xubuntu and Ubuntu Budgie using some other updating mechanism beyond Discover? I presume so, in which case, it should affect *ALL* flavors including canonical Ubuntu Desktop. In that case, we need to refile this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904269 Title: Apply full upgrade - fails with no error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1904269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890958] Re: exfat month modification time increasing by simple consulting with "properties"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (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/1890958 Title: exfat month modification time increasing by simple consulting with "properties" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1890958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904760] Re: autopkgtest fails in hirsute on arm64
Launchpad has imported 4 comments from the remote bug at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97314. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-10-07T08:06:28+00:00 Matthias Klose wrote: seen with the gcc-10 branch 20201003, while originally building that for another architecture. The build succeeds on another 32bit arch (arm- linux-gnueabihf) and on 64bit archs, but fails on i686-linux-gnu. The build is also configured with --enable-default-pie and other hardening options turned on by default, built with make -j2. virtual memory exhausted: Operation not permitted make[5]: *** [Makefile:1117: insn-extract.o] Error 1 make[5]: *** Waiting for unfinished jobs rm gcc.pod gfortran.pod cpp.pod gccbrig.pod gccgo.pod gdc.pod make[5]: Leaving directory '/<>/build/gcc' make[4]: *** [Makefile:4878: all-stage3-gcc] Error 2 make[4]: Leaving directory '/<>/build' make[3]: *** [Makefile:27347: stage3-bubble] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [Makefile:27411: bootstrap] Error 2 make[2]: Leaving directory '/<>/build' Reply at: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain- base/+bug/1904760/comments/0 On 2020-10-07T08:46:20+00:00 Rguenth wrote: virtual memory exhausted: Operation not permitted ISTR Jakub mentioned a similar issue? Reply at: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain- base/+bug/1904760/comments/1 On 2020-10-07T09:00:47+00:00 Jakub-gcc wrote: Yes, but for me it was resolved with r11-3518-g37ffe56c01e4a9e80a3b3c4f5beb86d80a0663db. If the (huge) switch is optimized by switchconv, then DF doesn't run into the latent problematic case. I'm not using --enable-default-pie though. Reply at: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain- base/+bug/1904760/comments/2 On 2020-11-17T15:14:49+00:00 Rsandifo-gcc wrote: I see the same thing for arm-linux-gnueabihf on trunk, also on insn-extract.o. It's specific to RTL checking for me too. I found it does work if I bootstrap with --enable-checking=yes,extra, flip ENABLE_RTL_CHECKING to 1 in auto-host.h, and then recompile insn-extract.c. But it does take a large amount of VM: phase parsing : 51.10 ( 27%) 43.64 ( 74%) 94.74 ( 38%) 1334M ( 73%) This used to work “a while ago” but I don't know when it stopped. The file has 9975 lines, 435KiB, but that's a bairn compared to some of the stuff we kick out. Perhaps it's just the sheer number of (nested) XEXP macro expansions? Reply at: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain- base/+bug/1904760/comments/3 ** Changed in: gcc Status: Unknown => New ** Changed in: gcc Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904760 Title: autopkgtest fails in hirsute on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1904760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904797] [NEW] geoipupdate fails with 40` HTML error
*** This bug is a security vulnerability *** Public security bug reported: Linux mail.eskimo.com 5.8.17 #1 SMP Sun Nov 1 01:10:16 PST 2020 x86_64 x86_64 x86_64 GNU/Linux Description:Ubuntu 20.04.1 LTS Release:20.04 geoipupdate: Installed: 4.0.6-2 Candidate: 4.0.6-2 Version table: *** 4.0.6-2 500 500 http://us.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages 100 /var/lib/dpkg/status Expect it to update the geoip database without error. geoipupdate -v Using config file /etc/GeoIP.conf Using database directory /var/lib/GeoIP Acquired lock file lock (/var/lib/GeoIP/.geoipupdate.lock) Performing get filename request to https://updates.maxmind.com/app/update_getfilename?product_id=GeoLite2-Country Not calculating MD5 sum as file does not exist: /var/lib/GeoIP/GeoLite2-Country.mmdb Performing update request to https://updates.maxmind.com/geoip/databases/GeoLite2-Country/update?db_md5= Error retrieving updates: error updating GeoLite2-Country: error updating: unexpected HTTP status code: 401 Unauthorized: An account ID and license key are required to use this service. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: geoipupdate 4.0.6-2 Uname: Linux 5.8.17 x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 18 15:56:34 2020 SourcePackage: geoipupdate UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: geoipupdate (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904797 Title: geoipupdate fails with 40` HTML error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoipupdate/+bug/1904797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904797] Re: geoipupdate fails with 40` HTML error
This breaks a postfwd script I use to prevent botnets using my mail server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904797 Title: geoipupdate fails with 40` HTML error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoipupdate/+bug/1904797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900668] Re: MAAS PXE Boot stalls with grub 2.02
I believe between my setup and the other reported in here, it's been seen on at least 3 different platforms (some HP servers, Gigabyte servers and OVMF/EDK2 VMs). Unfortunately, the image used doesn't matter in this case. This is network booting and MAAS only has a single grub2 binary used for everything that's booting from it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900668 Title: MAAS PXE Boot stalls with grub 2.02 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1900668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
... sorry, I never worked with repositories...
may someone check this:
https://code.launchpad.net/~arter97/+archive/ubuntu/exfat-dev
exfat-dkms - 5.8~2arter97~ubuntu20.04.1 (maybe also in the other versions?)
in the file misc.c:
void exfat_get_entry_time(struct exfat_sb_info *sbi, struct timespec64 *ts,
u8 tz, __le16 time, __le16 date, u8 time_cs)
{
u16 t = le16_to_cpu(time);
u16 d = le16_to_cpu(date);
ts->tv_sec = mktime64(1980 + (d >> 9), d >> 5 & 0x000F, d & 0x001F,
t >> 11, (t >> 5) & 0x003F, (t & 0x001F) << 1);
...
shouldn't it be in line 82/83
ts->tv_sec = mktime64(1980 + (d >> 9), ((d >> 5) - 1) & 0x000F, d &
0x001F,
t >> 11, (t >> 5) & 0x003F, (t & 0x001F) << 1);
???
as month is given from 0-11 as far as i know, but in exfat from 1-12
(https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-
specification#748-timestamp-fields).
(other way round seems to be correct in lines 108-110:
time64_to_tm(ts->tv_sec, 0, );
t = (tm.tm_hour << 11) | (tm.tm_min << 5) | (tm.tm_sec >> 1);
d = ((tm.tm_year - 80) << 9) | ((tm.tm_mon + 1) << 5) | tm.tm_mday;
)
may someone check and fix this, as I don't know how.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872504
Title:
date modified is wrong for files on an exfat formatted drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904054] Re: kernel 5.8 general protection fault at boot
Tried the recently released ubuntu linux kernel 5.8.29 just now, still getting the GPFs. Attaching the output of "journalctl -xb" from that failed boot (I was dropped into "emergency mode"). ** Attachment added: "journalctl -xb output from failed boot of ubuntu kernel 5.8.0-29" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+attachment/5435819/+files/ubuntu-kernel-5.8.0-29.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904795] [NEW] qemu-system-x86_64 fails to boot qcow2 image
Public bug reported: Steps: 1.Created a qcow2 image using Ubuntu virt-manager. This qcow2 image boots fine inside the virt-manager. 2.However, the same qcow2 image fails to boot when I try to boot it using the qemu-system-x86_64: #!/bin/bash qemu-system-x86_64 -m 16384 -boot d -enable-kvm -smp 16 -cpu host -net nic -net user,hostfwd=tcp::-:22 -drive file=/var/lib/libvirt/images/ubuntu18.04.qcow2,if=virtio -nographic Error: SeaBIOS (version 1.13.0-1ubuntu1) iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+BFF8C8D0+BFECC8D0 CA00 Booting from DVD/CD... Boot failed: Could not read from CDROM (code 0003) Booting from Floppy... Boot failed: could not read the boot disk Booting from Hard Disk... -- More Info - :~$ qemu-system-x86_64 --version QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.8) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers :~$ qemu-img check ubuntu18.04.qcow2 No errors were found on the image. 245760/245760 = 100.00% allocated, 0.00% fragmented, 0.00% compressed clusters Image end offset: 16108814336 :~$ qemu-img info ubuntu18.04.qcow2 image: ubuntu18.04.qcow2 file format: qcow2 virtual size: 15 GiB (16106127360 bytes) disk size: 1.88 GiB cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: true refcount bits: 16 corrupt: false ** Affects: qemu (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/1904795 Title: qemu-system-x86_64 fails to boot qcow2 image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1904795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
The error occurs even without writing to the hard disk. I didn't find the exact procedure to reproduce the error, it seems to happen during mounting or unmounting, maybe only from nautilus, but even in this case I don't have the changes of the date any time. The Date doesn't change by 30 days but 1 month and there are only some files affected, but repeatedly. Even that not consistently. On my hard drive there is only one directory and the subdirectories affected: unmount + save remove from nautilus/mount automatically via entry in fstab, listings from terminal, from a single session on Nov 18 2020(!), here only the files "Fuga.blend1, Materials.blend1, Mixereinstellungen.vmsms" affeced - I have no idea, what the common feature may be. sebastian@osamu:/media/4tbp/Eigene Videoprojekte/Fuga BWV 863$ ls -l insgesamt 106752 -rwxr-xr-x 1 root root 1016 Dez 9 2020 Ablauf.txt -rwxr-xr-x 1 root root 2990398 Dez 5 2020 'BWV 863 (I, 18 gis-moll) Selbst.mp3' -rwxr-xr-x 1 root root 1325052 Dez 12 2020 Fuga.blend -rwxr-xr-x 1 root root 1325148 Jul 9 2021 Fuga.blend1 -rwxr-xr-x 1 root root73990 Dez 9 2020 'Fuga BWV 863.aup' drwxr-xr-x 4 root root 131072 Dez 5 2020 'Fuga BWV 863_data' -rwxr-xr-x 1 root root 231661 Dez 18 2020 Fuga_take2.aup drwxr-xr-x 4 root root 131072 Dez 18 2020 Fuga_take2_data -rwxr-xr-x 1 root root 4376783 Dez 9 2020 'Leuchtender Boden Cycles.png' -rwxr-xr-x 1 root root 1185996 Dez 9 2020 Materials.blend -rwxr-xr-x 1 root root 1185996 Jul 9 2021 Materials.blend1 -rwxr-xr-x 1 root root 2966841 Dez 9 2020 MIDI.mp3 -rwxr-xr-x 1 root root 151 Jul 9 2021 Mixereinstellungen.vmsms -rwxr-xr-x 1 root root 249378 Dez 5 2020 Synchro.kdenlive drwxr-xr-x 2 root root 131072 Dez 18 2020 take2_video -rwxr-xr-x 1 root root84884 Dez 6 2020 Test1.kdenlive -rwxr-xr-x 1 root root 91579391 Jan 6 2021 Test1.webm drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test Alphaclips' drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test-Rohdaten' no file used, just removed and mounted again: -rwxr-xr-x 1 root root 1016 Dez 9 2020 Ablauf.txt -rwxr-xr-x 1 root root 2990398 Dez 5 2020 'BWV 863 (I, 18 gis-moll) Selbst.mp3' -rwxr-xr-x 1 root root 1325052 Dez 12 2020 Fuga.blend -rwxr-xr-x 1 root root 1325148 Aug 9 2021 Fuga.blend1 -rwxr-xr-x 1 root root73990 Dez 9 2020 'Fuga BWV 863.aup' drwxr-xr-x 4 root root 131072 Dez 5 2020 'Fuga BWV 863_data' -rwxr-xr-x 1 root root 231661 Jan 18 2021 Fuga_take2.aup drwxr-xr-x 4 root root 131072 Dez 18 2020 Fuga_take2_data -rwxr-xr-x 1 root root 4376783 Dez 9 2020 'Leuchtender Boden Cycles.png' -rwxr-xr-x 1 root root 1185996 Dez 9 2020 Materials.blend -rwxr-xr-x 1 root root 1185996 Aug 9 2021 Materials.blend1 -rwxr-xr-x 1 root root 2966841 Dez 9 2020 MIDI.mp3 -rwxr-xr-x 1 root root 151 Aug 9 2021 Mixereinstellungen.vmsms -rwxr-xr-x 1 root root 249378 Dez 5 2020 Synchro.kdenlive drwxr-xr-x 2 root root 131072 Dez 18 2020 take2_video -rwxr-xr-x 1 root root84884 Dez 6 2020 Test1.kdenlive -rwxr-xr-x 1 root root 91579391 Jan 6 2021 Test1.webm drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test Alphaclips' drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test-Rohdaten' ... -rwxr-xr-x 1 root root 1325148 Sep 9 2021 Fuga.blend1 -rwxr-xr-x 1 root root 1325148 Okt 9 2021 Fuga.blend1 And: sebastian@osamu:/media/4tbp/Eigene Videoprojekte/Fuga BWV 863$ find -newer Fuga_take2.aup -printf '%Ac %Cc %Tc %p\n' Mo 31 Dez 1979 01:00:00 CET Sa 09 Okt 2021 18:16:36 CEST Sa 09 Okt 2021 18:16:38 CEST ./Mixereinstellungen.vmsms Mo 31 Dez 1979 01:00:00 CET Sa 09 Okt 2021 17:12:02 CEST Sa 09 Okt 2021 20:28:58 CEST ./Materials.blend1 Mo 31 Dez 1979 01:00:00 CET Sa 06 Nov 2021 00:30:36 CET Sa 09 Okt 2021 20:30:06 CEST ./Fuga.blend1 -> last status change and last modification timestamp may change independently as in "Fuga.blend1", but not in the other two files. Hope that information helps to find the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904618] Re: /usr/share/imapfilter/regex.lua:10: bad argument #1 to 'compile' (string expected, got nil)
I filed a bug upstream, the issue is fixed in v2.7.4. https://github.com/lefcha/imapfilter/issues/218 Here's the fix: https://github.com/lefcha/imapfilter/commit/987ea442fa0aa3dc5f5d59ec89c9a3d818cd48d3 ** Bug watch added: github.com/lefcha/imapfilter/issues #218 https://github.com/lefcha/imapfilter/issues/218 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904618 Title: /usr/share/imapfilter/regex.lua:10: bad argument #1 to 'compile' (string expected, got nil) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imapfilter/+bug/1904618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904192] Re: ebtables can not rename just created chain
FYI, sponsored Alex's upload to hirsute-proposed where it is building. Did the same for groovy-proposed and it is sitting in unapproved waiting for the next steps of the SRU process. ** Changed in: iptables (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: iptables (Ubuntu) Assignee: (unassigned) => Alex Murray (alexmurray) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904192 Title: ebtables can not rename just created chain To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1904192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904793] [NEW] upower abruptly thinks battery has gone to 1% and hibernates
Public bug reported: Whenever I go on battery after 20-30 minutes upower will very abruptly think my battery is at 1% and force my laptop to hibernate. This seems to happen at random times, I've seen it when my battery was reported to be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up forcing me to hard reset the machine. I suspect this is because upower thinks my battery is still at 1% when its not. My laptops firmware correctly reports the battery level and shows that I have plenty of power remaining. The last few times this happened I kept powertop up which shows that I do have plenty of power even when upower thinks I have none. Essentially this makes my laptop unusable on battery. Laptop: Lenovo X1 Carbon Extreme Gen 2 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: upower 0.99.11-2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 18 13:59:24 2020 InstallationDate: Installed on 2019-12-29 (325 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904793 Title: upower abruptly thinks battery has gone to 1% and hibernates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1904793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus and dialogs are not dark
I followed this guide and it sorted me out: https://allthings.how/how- to-fully-enable-dark-mode-in-ubuntu-20-04-including-calendar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus and dialogs are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
I can confirm this was fixed with version 340.108-0ubuntu5.20.10.2. The module failed to build after upgrading to groovy, but after installing the package from proposed it worked. uname -a: Linux ubuntu-desktop 5.8.0-29-generic #31-Ubuntu SMP Fri Nov 6 12:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
This bug was fixed in the package gtk+3.0 - 3.24.23-1ubuntu2 --- gtk+3.0 (3.24.23-1ubuntu2) hirsute; urgency=medium * debian/patches/fontchooser_Fix_family-only_mode.patch: - Show regular monospace fonts in gnome-terminal's profile editor and not arbitrary font styles (LP: #1900729) -- Gunnar Hjalmarsson Mon, 02 Nov 2020 10:45:57 +0100 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault
20190425 can be considered good it completed 4.5 times before I scheduled the next run. Next is r10-4054 which has -v of: gcc version 10.0.0 20191022 (experimental) (GCC) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/groovy/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904792] [NEW] Unable to upgrade from 18.04 to 20.04
Public bug reported: Trying to update from 18.04 to 20.04 and get the can't calculate update error message ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 21:41:56 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-18 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904792 Title: Unable to upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1904792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904192] Re: ebtables can not rename just created chain
** Changed in: iptables (Fedora) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904192 Title: ebtables can not rename just created chain To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1904192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904791] [NEW] Bionic update: upstream stable patchset 2020-11-18
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-11-18 Ported from the following upstream stable releases: v4.14.204, v4.19.155 from git://git.kernel.org/ scripts/setlocalversion: make git describe output more reliable arm64: link with -z norelro regardless of CONFIG_RELOCATABLE gtp: fix an use-before-init in gtp_newlink() ravb: Fix bit fields checking in ravb_hwtstamp_get() tipc: fix memory leak caused by tipc_buf_append() arch/x86/amd/ibs: Fix re-arming IBS Fetch x86/xen: disable Firmware First mode for correctable memory errors fuse: fix page dereference after free p54: avoid accessing the data mapped to streaming DMA mtd: lpddr: Fix bad logic in print_drs_error ata: sata_rcar: Fix DMA boundary mask fscrypt: return -EXDEV for incompatible rename or link into encrypted dir x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() futex: Fix incorrect should_fail_futex() handling powerpc/powernv/smp: Fix spurious DBG() warning powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: add trace exit in exception path f2fs: fix to check segment boundary during SIT page readahead um: change sigio_spinlock to a mutex ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses xfs: fix realtime bitmap/summary file truncation when growing rt volume video: fbdev: pvr2fb: initialize variables ath10k: start recovery process when payload length exceeds max htc length for sdio ath10k: fix VHT NSS calculation when STBC is enabled drm/brige/megachips: Add checking if ge_b850v3_lvds_init() is working correctly media: videodev2.h: RGB BT2020 and HSV are always full range media: platform: Improve queue set up flow for bug fixing usb: typec: tcpm: During PR_SWAP, source caps should be sent only after tSwapSourceStart media: tw5864: check status of tw5864_frameinterval_get mmc: via-sdmmc: Fix data race bug drm/bridge/synopsys: dsi: add support for non-continuous HS clock printk: reduce LOG_BUF_SHIFT range for H8300 kgdb: Make "kgdbcon" work properly with "kgdb_earlycon" cpufreq: sti-cpufreq: add stih418 support USB: adutux: fix debugging uio: free uio id after uio file node is freed arm64/mm: return cpu_all_mask when node is NUMA_NO_NODE ACPI: Add out of bounds and numa_off protections to pxm_to_node() drivers/net/wan/hdlc_fr: Correctly handle special skb->protocol values bus/fsl_mc: Do not rely on caller to provide non NULL mc_io power: supply: test_power: add missing newlines when printing parameters by sysfs md/bitmap: md_bitmap_get_counter returns wrong blocks bnxt_en: Log unknown link speed appropriately. clk: ti: clockdomain: fix static checker warning net: 9p: initialize sun_server.sun_path to have addr's value only when addr is valid drivers: watchdog: rdc321x_wdt: Fix race condition bugs ext4: Detect already used quota file early gfs2: add validation checks for size of superblock arm64: dts: renesas: ulcb: add full-pwr-cycle-in-suspend into eMMC nodes memory: emif: Remove bogus debugfs error handling ARM: dts: s5pv210: remove DMA controller bus node name to fix dtschema warnings ARM: dts: s5pv210: move PMU node out of clock controller ARM: dts: s5pv210: remove dedicated 'audio-subsystem' node nbd: make the config put is called before the notifying the waiter sgl_alloc_order: fix memory leak nvme-rdma: fix crash when connect rejected md/raid5: fix oops during stripe resizing perf/x86/amd/ibs: Don't include randomized bits in get_ibs_op_count() perf/x86/amd/ibs: Fix raw sample data accumulation leds: bcm6328, bcm6358: use devres LED registering function fs: Don't invalidate page buffers in block_write_full_page() NFS: fix nfs_path in case of a rename retry ACPI / extlog: Check for RDMSR failure ACPI: video: use ACPI backlight for HP 635 Notebook ACPI: debug: don't allow debugging when ACPI is disabled acpi-cpufreq: Honor _PSD table setting on new AMD CPUs w1: mxc_w1: Fix timeout resolution problem leading to bus error scsi: mptfusion: Fix null pointer dereferences in mptscsih_remove() btrfs: reschedule if necessary when logging directory items btrfs: send, recompute reference path after orphanization of a directory btrfs: use kvzalloc() to allocate clone_roots in btrfs_ioctl_send() btrfs: cleanup cow block on error btrfs: fix use-after-free on readahead extent after failure to create it usb: dwc3: ep0: Fix ZLP for OUT ep0 requests usb: dwc3: core: add phy cleanup
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@pesso82 There is your problem. Those headphones do not support HSP 1.6 profile, only 1.5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I meant HFP profile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893818] Re: Several blockprobe errors if trying to install the groovy daily live on LPAR
** Merge proposal linked: https://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/392353 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893818 Title: Several blockprobe errors if trying to install the groovy daily live on LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1893818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
... and DND from Nautilus to another Nautilus window work well. So Nautilus From/to Desktop only seems to freeze gnome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
Hello, Same issue for me, I can't drag and drop since last upgrade to 20.10. For instance, drag file(s) from Desktop and drop to an open directory doesn't work. ...But drag file from Desktop and drop to an icon closed directory work. Dell OptiPlex-7010 Description:Ubuntu 20.10 Release:20.10 Codename: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
** Merge proposal linked: https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/394142 ** Merge proposal linked: https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/394144 ** Merge proposal linked: https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/394145 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904790] [NEW] Safely remove is causing data loss
Public bug reported: In short When you do "Safely remove" on a removable device like USB stick in Dolphin file explorer, it does not guarantee you can safely remove it from the port. It does not wait till true copy completion. Longer story I was shocked last weekend when I went to my sister with a USB stick to show her some photos of mine. We've been watching them and suddenly at ~40% of the slideshow, a message started showing up saying that the TV can't read the file. The case was for the remaining 60% of the photos. Sadly we stopped. At home I checked that and indeed the rest of the files were corrupted. I tried to replicate this several times: 1. Start copying files to the USB stick (~3.5GB of photos). 2. Wait until copy notification of 100% done. 3. Click "Safely Remove" on USB stick in KDE's Dolphin File Explorer. 4. Remove USB Stick from the port (BOOM! Data loss). I couldn't believe that, but this behaviour is consistent. At first I was using a USB stick without a usage LED indicator, so I couldn't say if it is busy on the hardware level. Then I switched to an old Kingston USB stick with LED, and after step 3 (Click "Safely Remove" on USB stick), the usage LED was blinking for a few more minutes!!! Reason I've searched the net and this problem seems to be related to how Linux kernel buffers write operations to removable devices. There are suggestions out there mostly to reduce dirty_bytes kernel parameter value, but I think this is not a solution. Giving the user an impression that now he can safely remove the stick while in reality the copy process is in progress is a no-go. KDE apparently is being given a false sign from the kernel that the copy process is completed. But it is finished only from the shell's perspective. At the point of 100% done shell notification, it has just been fully moved to write cache. Then the kernel writes it slowly at real USB stick transfer speed to true completion. That is my understanding. Temporary solution The only solution I have found for now that works is the sync command. Before pulling out the USB stick, just call sync in the command line. That flushes all the buffers and waits until truly done. I confirmed that with the usage LED indicator on my Kingston stick. The LED stopped blinking right after the sync command returned. Solution That is the task to do. Please fix this issue as this is a very basic, common use case of the file explorer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: dolphin 4:19.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Nov 18 21:35:32 2020 InstallationDate: Installed on 2020-10-18 (31 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904790 Title: Safely remove is causing data loss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1904790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Yes, that’s the point I’m try to use JBL T450BT These are the available specs on official site Control and Connection Specifications Bluetooth profilesHFP v1.5, HSP v1.2, A2DP v1.2, AVRCP v1.4 Bluetooth frequency2.402GHz-2.48GHz Bluetooth transmitted modulationGFSK,π/4DQPSK, 8DPSK Bluetooth transmitter power0-4 d I don’t find mSBC information, so it’s supposed they don’t support mSBC What about Sony WH-CH700? They seems to support mSBC, but who knows.. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904789] [NEW] [snap] Cannot confirm security exception
Public bug reported: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. ** Affects: thunderbird (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/1904789 Title: [snap] Cannot confirm security exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887806] Re: [21.04 FEAT] zkey integration with EKMF stage1
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887806 Title: [21.04 FEAT] zkey integration with EKMF stage1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893818] Re: Several blockprobe errors if trying to install the groovy daily live on LPAR
** Changed in: ubuntu-z-systems Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893818 Title: Several blockprobe errors if trying to install the groovy daily live on LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1893818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904588] Re: Network boot from MAAS sometimes fails at "grub>" prompt
Sorry for the many comments, but net_dhcp is a more modern replacement for net_bootp too AFAIUI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904588 Title: Network boot from MAAS sometimes fails at "grub>" prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
'journalctl -b -1' comes back with: Specifying boot ID has no effect, no persistent journal was found I'm assuming though you're after the boot log for the previous session (that froze) so I've manually extracted this from /var/log/syslog in the attached archive (prevboot.txt). Unfortunately nothing new was added to /var/crash as a result of the freeze. Something additional to mention which may be related (given it's display related), I had to reboot the machine a couple of times to get this as it seemingly had issues starting the display manager. Visually the display kept flicking between the boot log and another one with some further logging info. The graphical login screen was never displayed. Syslog was showing messages as follows: Nov 18 19:58:57 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:58:57 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:03 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:03 monolith systemd[1]: Stopped LXDE Display Manager. Only fix was to reboot it. I've attached the boot log for this one as 'prevboot1.txt'. This problem happened on two different boots. ** Attachment added: "boot logs" https://bugs.launchpad.net/ubuntu/+bug/1904230/+attachment/5435802/+files/logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904588] Re: Network boot from MAAS sometimes fails at "grub>" prompt
The proper command name is net_bootp, not net_bootps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904588 Title: Network boot from MAAS sometimes fails at "grub>" prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904588] Re: Network boot from MAAS sometimes fails at "grub>" prompt
Hello! This seems to be a duplicate of https://launchpad.net/bugs/1900668 - could you check that? I have some list of things in there I'm looking for, mostly running with debug=all and trying current SRU in proposed with has a tftp fix (probably unrelated). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904588 Title: Network boot from MAAS sometimes fails at "grub>" prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889114] Re: Ubuntu 18.04 Update Breaks KVM Wireless Mouse
I am encountering this issue with my setup too after updating -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899824] Re: Internal pull-up resistors not working
** Description changed:
Consider the 3 following scripts :
1~
#!/bin/python3
from gpiozero import Button
import time
import os
stopButton = Button (17)
while True:
if stopButton.is_pressed:
os.system ("sudo shutdown now -h")
time.sleep (1)
exit (1)
2
#!/bin/python3
import RPi.GPIO as GPIO
import os
import time
from threading import Thread
GPIO.setwarnings (False)
GPIO.setmode (GPIO.BCM)
shutdown_pin = 26
GPIO.setup (shutdown_pin, GPIO.IN, pull_up_down=GPIO.PUD_UP)
def shutdown_check():
while True:
pulsetime = 1
GPIO.wait_for_edge (shutdown_pin, GPIO.FALLING)
print ("falling detected")
time.sleep (0.01)
while GPIO.input (shutdown_pin) == GPIO.LOW:
time.sleep (0.01)
pulsetime += 1
if pulsetime >=2 and pulsetime <=3:
os.system ("sudo reboot")
elif pulsetime >=4 and pulsetime <=5:
os.system ("sudo shutdown now -h")
try:
t1 = Thread (target = shutdown_check)
t1.start ()
except:
t1.stop ()
GPIO.cleanup ()
exit (0)
3
#!/bin/python3
import RPi.GPIO as GPIO
import time
import os
GPIO.setmode (GPIO.BCM)
GPIO.setup (17, GPIO.IN, pull_up_down = GPIO.PUD_UP)
def Shutdown (channel):
print ("Shutting down...")
os.system ("echo $(date) >> shutdown.log")
time.sleep (3)
os.system ("sudo shutdown now -h")
exit (0)
GPIO.add_event_detect (17, GPIO.FALLING, callback = Shutdown,
bouncetime=2000)
while 1:
time.sleep (1)
exit (1)
~
The above scripts are common shutdown scripts that can be found on the
web, utilizing an NO pushbutton connected to GPIO 26 and ground
(physical 37). None of the above scripts work though, since the internal
pull-up resistors don't seem to work, and the GPIOs always read LOW. My
setup has been tested twice in Raspberry Pi OS (the resistors worked
there, measured with a scope). gpiozero uses rpi.gpio as the pin
factory. A different pin was tested too.
+ UPDATE: The pip3 version of RPi.GPIO (and gpiozero) works fine.
+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-rpi.gpio 0.6.5-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-1021.24-raspi 5.4.65
Uname: Linux 5.4.0-1021-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: arm64
CasperMD5CheckResult: skip
Date: Wed Oct 14 20:27:59 2020
ImageMediaBuild: 20200731
ProcEnviron:
TERM=alacritty
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: rpi.gpio
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899824
Title:
Internal pull-up resistors not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpi.gpio/+bug/1899824/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878041] Re: installation fails creating user on large multipath system - multipathd show command times out in curtin log with 163 paths
** Also affects: multipath-tools (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/1878041 Title: installation fails creating user on large multipath system - multipathd show command times out in curtin log with 163 paths To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1878041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900773] Re: Timeout downloading initrd
= groovy verification = GNU GRUB GNU GRUB version 2.04buntu3.29 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> net_dhcp efinet0 grub> linux (tftp,192.168.122.1)/vmlinuz.orig console=ttyS0,115200n8 grub> initrd (tftp,192.168.122.1)/initrd.img grub> = focal verification = GNU GRUB version 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> net_dhcp efinet0 grub> linux (tftp,192.168.122.1)/vmlinuz.orig console=ttyS0,115200n8 grub> initrd (tftp,192.168.122.1)/initrd.img grub> = bionic verification = GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> net_add_addr test efinet0 192.168.122.86 grub> linux (tftp,192.168.122.1)/vmlinuz.orig console=ttyS0,115200n8 grub> initrd (tftp,192.168.122.1)/initrd.img grub> = xenial verification = GNU GRUB version 2.02~beta2-36ubuntu3.29 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> net_add_addr test efinet0 192.168.122.86 grub> linux (tftp,192.168.122.1)/vmlinuz.orig console=ttyS0,115200n8 grub> initrd (tftp,192.168.122.1)/initrd.img grub> ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done verification-done-focal verification-done-groovy verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900773 Title: Timeout downloading initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1900773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893818] Re: Several blockprobe errors if trying to install the groovy daily live on LPAR
** Changed in: curtin Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893818 Title: Several blockprobe errors if trying to install the groovy daily live on LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1893818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887920] Re: [21.04 FEAT] NVMe IPL Load Normal support - s390-tools part
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887920 Title: [21.04 FEAT] NVMe IPL Load Normal support - s390-tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892824] Re: [21.04 FEAT] NVMe stand-alone dump support - s390-tools part
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892824 Title: [21.04 FEAT] NVMe stand-alone dump support - s390-tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902047] Re: [21.04 FEAT] Server Time Protocol (STP) leap second handling - s390-tools part
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902047 Title: [21.04 FEAT] Server Time Protocol (STP) leap second handling - s390-tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1902047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902865] Re: [21.04 FEAT] zcrypt DD: add state for offline due to error - s390-tools
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902865 Title: [21.04 FEAT] zcrypt DD: add state for offline due to error - s390-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1902865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904740] Re: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
Did you try newer NV proprietary drivers like 455? ** Attachment added: "nv_drivers.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904740/+attachment/5435799/+files/nv_drivers.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904740 Title: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901074] Re: [SRU] Enable some arm64 performance optimizations already available for other architectures
I created a Focal and Groovy VMs, enabled proposed, and installed ruby2.7 from there. I was able to re-run the benchmarks and get a similar result as the one obtained in the experiment presented in the bug description. ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901074 Title: [SRU] Enable some arm64 performance optimizations already available for other architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.5/+bug/1901074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903849] Re: vim ftbfs
The failure I see is: ... Failures: From test_popupwin.vim: Found errors in Test_popup_drag_termwin(): Run 1: ... I've rebuilt Debian's version and it did not show the same failure. It looks like to be caused by the disabled mouse support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903849 Title: vim ftbfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1903849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899824] Re: Internal pull-up resistors not working
** Summary changed:
- RPi.GPIO doesn't detect falling edge (wait_for_edge, add_event_detect)
+ Internal pull-up resistors not working
** Description changed:
Consider the 3 following scripts :
1~
#!/bin/python3
from gpiozero import Button
import time
import os
stopButton = Button (17)
while True:
if stopButton.is_pressed:
os.system ("sudo shutdown now -h")
time.sleep (1)
exit (1)
2
#!/bin/python3
import RPi.GPIO as GPIO
import os
import time
from threading import Thread
GPIO.setwarnings (False)
GPIO.setmode (GPIO.BCM)
shutdown_pin = 26
GPIO.setup (shutdown_pin, GPIO.IN, pull_up_down=GPIO.PUD_UP)
def shutdown_check():
while True:
pulsetime = 1
GPIO.wait_for_edge (shutdown_pin, GPIO.FALLING)
print ("falling detected")
time.sleep (0.01)
while GPIO.input (shutdown_pin) == GPIO.LOW:
time.sleep (0.01)
pulsetime += 1
if pulsetime >=2 and pulsetime <=3:
os.system ("sudo reboot")
elif pulsetime >=4 and pulsetime <=5:
os.system ("sudo shutdown now -h")
try:
t1 = Thread (target = shutdown_check)
t1.start ()
except:
t1.stop ()
GPIO.cleanup ()
exit (0)
3
#!/bin/python3
import RPi.GPIO as GPIO
import time
import os
GPIO.setmode (GPIO.BCM)
GPIO.setup (17, GPIO.IN, pull_up_down = GPIO.PUD_UP)
def Shutdown (channel):
print ("Shutting down...")
os.system ("echo $(date) >> shutdown.log")
time.sleep (3)
os.system ("sudo shutdown now -h")
exit (0)
GPIO.add_event_detect (17, GPIO.FALLING, callback = Shutdown,
bouncetime=2000)
while 1:
time.sleep (1)
exit (1)
~
The above scripts are common shutdown scripts that can be found on the
web, utilizing an NO pushbutton connected to GPIO 26 and ground
- (physical 37). None of the above scripts work though, since a falling
- edge is never detected. My setup has been tested and actually, the 1st
- script was working properly on Raspberry Pi OS a few weeks ago (before
- switching to Ubuntu) and the other 2 were never tested on Raspberry Pi
- OS. gpiozero uses rpi.gpio as the pin factory. A different pin was
- tested too.
+ (physical 37). None of the above scripts work though, since the internal
+ pull-up resistors don't seem to work, and the GPIOs always read LOW. My
+ setup has been tested twice in Raspberry Pi OS (the resistors worked
+ there, measured with a scope). gpiozero uses rpi.gpio as the pin
+ factory. A different pin was tested too.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-rpi.gpio 0.6.5-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-1021.24-raspi 5.4.65
Uname: Linux 5.4.0-1021-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: arm64
CasperMD5CheckResult: skip
Date: Wed Oct 14 20:27:59 2020
ImageMediaBuild: 20200731
ProcEnviron:
TERM=alacritty
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: rpi.gpio
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899824
Title:
Internal pull-up resistors not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpi.gpio/+bug/1899824/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904602] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1904602/+attachment/5435798/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904602] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1904602/+attachment/5435797/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904602] Re: Strange crash of Software Properties
Including a pastebin of the *.crash file: https://pastebin.com/dr8G0C6E ** Tags added: apport-collected groovy ** Description changed: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. - Ubuntu version: 20.04 and above (it does apply also to the same version - of lUbuntu) + Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.455 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair + Package: software-properties-gtk 0.99.3 + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 + Tags: groovy + Uname: Linux 5.8.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
